This job view page is being replaced by Spyglass soon. Check out the new job view.

PR	HanFa: E2E test should deploy a running CPI using helm chart.
Result	FAILURE
Tests	0 failed / 0 succeeded
Started	2022-04-27 19:44
Elapsed	11m44s
Revision	625248031f60ad6c8b7d563a99b5ed5fedbad937
Refs	620

• artifacts
• build log

No Test Failures!

---

Error lines from build-log.txt

• Expand Skipped Lines
• Raw build-log.txt

... skipping 636 lines ...
Deploy cloud provider vSphere with helm
/home/prow/go/src/k8s.io/cloud-provider-vsphere/test/e2e/helm_test.go:60
  should have running CPI [BeforeEach]
  /home/prow/go/src/k8s.io/cloud-provider-vsphere/test/e2e/helm_test.go:111

  Cannot install vsphere-cpi helm chart
  Unexpected error:
      <*errors.withStack | 0xc0028be720>: {
          error: <*errors.withMessage | 0xc001baae40>{
              cause: <*errors.errorString | 0xc001bb40a0>{
                  s: "ServiceAccount \"cloud-controller-manager\" in namespace \"kube-system\" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key \"app.kubernetes.io/managed-by\": must be set to \"Helm\"; annotation validation error: missing key \"meta.helm.sh/release-name\": must be set to \"vsphere-cpi-e2e\"; annotation validation error: missing key \"meta.helm.sh/release-namespace\": must be set to \"kube-system\"",
              },
              msg: "rendered manifests contain a resource that already exists. Unable to continue with install",
          },
          stack: [0x31254ad, 0x3123ef0, 0x3131065, 0x1ac3771, 0x1ac3165, 0x1ac3adb, 0x1ac8d6c, 0x1ac8427, 0x1ae9908, 0x1ae9625, 0x1ae8cc5, 0x1aeb312, 0x1af8029, 0x1af7e4a, 0x312e9b0, 0x1501e82, 0x143da61],
      }
      rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount "cloud-controller-manager" in namespace "kube-system" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "vsphere-cpi-e2e"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "kube-system"
  occurred

  /home/prow/go/src/k8s.io/cloud-provider-vsphere/test/e2e/helm_test.go:107
------------------------------
STEP: Tear down the workload cluster
STEP: Deleting cluster workload-klwo6p
... skipping 2 lines ...
STEP: Tear down the bootstrap cluster
I0427 19:55:26.343694   31515 e2e_suite_test.go:193] Deleted workload cluster default/workload-klwo6p


Summarizing 1 Failure:

[Fail] Deploy cloud provider vSphere with helm [BeforeEach] should have running CPI 
/home/prow/go/src/k8s.io/cloud-provider-vsphere/test/e2e/helm_test.go:107

Ran 2 of 2 Specs in 368.117 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestE2E (368.12s)
FAIL

Ginkgo ran 1 suite in 7m29.731853075s
Test Suite Failed
make[1]: *** [Makefile:58: run] Error 1
make[1]: Leaving directory '/home/prow/go/src/k8s.io/cloud-provider-vsphere/test/e2e'
make: *** [Makefile:251: e2e] Error 2
Releasing IP claims
ipclaim.ipam.metal3.io "ip-claim-3ff017a0425f6378e1287a484b9c46c410c3711f" deleted
ipclaim.ipam.metal3.io "workload-ip-claim-57efc531c8ac006467beb5c7eefa6edd224c6451" deleted
vpn
WARNING: [capv-prow@cluster-api-provider-vsphere.iam.gserviceaccount.com] appears to be a service account. Service account tokens cannot be revoked, but they will expire automatically. To prevent use of the service account token earlier than the expiration, delete or disable the parent service account.
Revoked credentials:
... skipping 13 lines ...