This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2023-01-19 05:16
Elapsed1h5m
Revisionmain

No Test Failures!


Error lines from build-log.txt

... skipping 587 lines ...
  Patching MachineHealthCheck unhealthy condition to one of the nodes
  INFO: Patching the node condition to the node
  Waiting for remediation
  Waiting until the node with unhealthy node condition is remediated
  STEP: PASSED! @ 01/19/23 05:29:10.599
  STEP: Dumping logs from the "mhc-remediation-eeosvh" workload cluster @ 01/19/23 05:29:10.599
Failed to get logs for Machine mhc-remediation-eeosvh-5528v, Cluster mhc-remediation-1o8xih/mhc-remediation-eeosvh: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-eeosvh-md-0-5756b9bcbb-np85x, Cluster mhc-remediation-1o8xih/mhc-remediation-eeosvh: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "mhc-remediation-1o8xih" namespace @ 01/19/23 05:29:14.797
  STEP: Deleting cluster mhc-remediation-1o8xih/mhc-remediation-eeosvh @ 01/19/23 05:29:15.087
  STEP: Deleting cluster mhc-remediation-eeosvh @ 01/19/23 05:29:15.104
  INFO: Waiting for the Cluster mhc-remediation-1o8xih/mhc-remediation-eeosvh to be deleted
  STEP: Waiting for cluster mhc-remediation-eeosvh to be deleted @ 01/19/23 05:29:15.116
  STEP: Deleting namespace used for hosting the "mhc-remediation" test spec @ 01/19/23 05:29:45.136
... skipping 54 lines ...
  Patching MachineHealthCheck unhealthy condition to one of the nodes
  INFO: Patching the node condition to the node
  Waiting for remediation
  Waiting until the node with unhealthy node condition is remediated
  STEP: PASSED! @ 01/19/23 05:38:40.178
  STEP: Dumping logs from the "mhc-remediation-vk554d" workload cluster @ 01/19/23 05:38:40.178
Failed to get logs for Machine mhc-remediation-vk554d-ftzl9, Cluster mhc-remediation-hjc0lk/mhc-remediation-vk554d: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-vk554d-md-0-858d9d7cdd-4f72c, Cluster mhc-remediation-hjc0lk/mhc-remediation-vk554d: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-vk554d-qw4g4, Cluster mhc-remediation-hjc0lk/mhc-remediation-vk554d: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-vk554d-wxf62, Cluster mhc-remediation-hjc0lk/mhc-remediation-vk554d: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "mhc-remediation-hjc0lk" namespace @ 01/19/23 05:38:47.675
  STEP: Deleting cluster mhc-remediation-hjc0lk/mhc-remediation-vk554d @ 01/19/23 05:38:47.998
  STEP: Deleting cluster mhc-remediation-vk554d @ 01/19/23 05:38:48.017
  INFO: Waiting for the Cluster mhc-remediation-hjc0lk/mhc-remediation-vk554d to be deleted
  STEP: Waiting for cluster mhc-remediation-vk554d to be deleted @ 01/19/23 05:38:48.03
  STEP: Deleting namespace used for hosting the "mhc-remediation" test spec @ 01/19/23 05:39:28.055
... skipping 46 lines ...
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/19/23 05:42:19.418
  STEP: Checking all the machines controlled by quick-start-felqyp-md-0-qwbmr are in the "<None>" failure domain @ 01/19/23 05:43:29.505
  INFO: Waiting for the machine pools to be provisioned
  STEP: PASSED! @ 01/19/23 05:43:29.549
  STEP: Dumping logs from the "quick-start-felqyp" workload cluster @ 01/19/23 05:43:29.549
Failed to get logs for Machine quick-start-felqyp-md-0-qwbmr-6c4ccdb76f-s6n9s, Cluster quick-start-4ggw6n/quick-start-felqyp: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine quick-start-felqyp-zt9jq-mzzbd, Cluster quick-start-4ggw6n/quick-start-felqyp: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "quick-start-4ggw6n" namespace @ 01/19/23 05:43:34.07
  STEP: Deleting cluster quick-start-4ggw6n/quick-start-felqyp @ 01/19/23 05:43:34.43
  STEP: Deleting cluster quick-start-felqyp @ 01/19/23 05:43:34.453
  INFO: Waiting for the Cluster quick-start-4ggw6n/quick-start-felqyp to be deleted
  STEP: Waiting for cluster quick-start-felqyp to be deleted @ 01/19/23 05:43:34.464
  STEP: Deleting namespace used for hosting the "quick-start" test spec @ 01/19/23 05:44:04.487
... skipping 104 lines ...
  INFO: Waiting for rolling upgrade to start.
  INFO: Waiting for MachineDeployment rolling upgrade to start
  INFO: Waiting for rolling upgrade to complete.
  INFO: Waiting for MachineDeployment rolling upgrade to complete
  STEP: PASSED! @ 01/19/23 05:54:02.834
  STEP: Dumping logs from the "md-rollout-3ovwwo" workload cluster @ 01/19/23 05:54:02.834
Failed to get logs for Machine md-rollout-3ovwwo-md-0-958d984c9-42lf5, Cluster md-rollout-hh62gv/md-rollout-3ovwwo: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-rollout-3ovwwo-zqt88, Cluster md-rollout-hh62gv/md-rollout-3ovwwo: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "md-rollout-hh62gv" namespace @ 01/19/23 05:54:07.098
  STEP: Deleting cluster md-rollout-hh62gv/md-rollout-3ovwwo @ 01/19/23 05:54:07.614
  STEP: Deleting cluster md-rollout-3ovwwo @ 01/19/23 05:54:07.653
  INFO: Waiting for the Cluster md-rollout-hh62gv/md-rollout-3ovwwo to be deleted
  STEP: Waiting for cluster md-rollout-3ovwwo to be deleted @ 01/19/23 05:54:07.677
  STEP: Deleting namespace used for hosting the "md-rollout" test spec @ 01/19/23 05:56:17.793
... skipping 118 lines ...
  INFO: Waiting for MachineDeployment rollout for MachineDeploymentTopology "md-0" (class "quick-start-worker") to complete.
  STEP: Deleting a MachineDeploymentTopology in the Cluster Topology and wait for associated MachineDeployment to be deleted @ 01/19/23 06:05:34.546
  INFO: Removing MachineDeploymentTopology from the Cluster Topology.
  INFO: Waiting for MachineDeployment to be deleted.
  STEP: PASSED! @ 01/19/23 06:05:44.623
  STEP: Dumping logs from the "clusterclass-changes-abpgff" workload cluster @ 01/19/23 06:05:44.623
Failed to get logs for Machine clusterclass-changes-abpgff-wrs8k-g9vxc, Cluster clusterclass-changes-vdi7hh/clusterclass-changes-abpgff: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "clusterclass-changes-vdi7hh" namespace @ 01/19/23 06:05:46.639
  STEP: Deleting cluster clusterclass-changes-vdi7hh/clusterclass-changes-abpgff @ 01/19/23 06:05:46.937
  STEP: Deleting cluster clusterclass-changes-abpgff @ 01/19/23 06:05:46.957
  INFO: Waiting for the Cluster clusterclass-changes-vdi7hh/clusterclass-changes-abpgff to be deleted
  STEP: Waiting for cluster clusterclass-changes-abpgff to be deleted @ 01/19/23 06:05:46.969
  STEP: Deleting namespace used for hosting the "clusterclass-changes" test spec @ 01/19/23 06:06:06.985
... skipping 50 lines ...
  INFO: Waiting for correct number of replicas to exist
  STEP: Scaling the MachineDeployment down to 1 @ 01/19/23 06:11:08.867
  INFO: Scaling machine deployment md-scale-0bjod1/md-scale-yldxy8-md-0 from 3 to 1 replicas
  INFO: Waiting for correct number of replicas to exist
  STEP: PASSED! @ 01/19/23 06:11:18.975
  STEP: Dumping logs from the "md-scale-yldxy8" workload cluster @ 01/19/23 06:11:18.975
Failed to get logs for Machine md-scale-yldxy8-md-0-77f896888f-wjqgc, Cluster md-scale-0bjod1/md-scale-yldxy8: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-scale-yldxy8-tkhbx, Cluster md-scale-0bjod1/md-scale-yldxy8: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "md-scale-0bjod1" namespace @ 01/19/23 06:11:23.379
  STEP: Deleting cluster md-scale-0bjod1/md-scale-yldxy8 @ 01/19/23 06:11:23.663
  STEP: Deleting cluster md-scale-yldxy8 @ 01/19/23 06:11:23.682
  INFO: Waiting for the Cluster md-scale-0bjod1/md-scale-yldxy8 to be deleted
  STEP: Waiting for cluster md-scale-yldxy8 to be deleted @ 01/19/23 06:11:23.696
  STEP: Deleting namespace used for hosting the "md-scale" test spec @ 01/19/23 06:11:53.714
... skipping 44 lines ...
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/19/23 06:14:44.957
  STEP: Checking all the machines controlled by quick-start-tkakk1-md-0 are in the "<None>" failure domain @ 01/19/23 06:15:55.043
  INFO: Waiting for the machine pools to be provisioned
  STEP: PASSED! @ 01/19/23 06:15:55.089
  STEP: Dumping logs from the "quick-start-tkakk1" workload cluster @ 01/19/23 06:15:55.09
Failed to get logs for Machine quick-start-tkakk1-h6png, Cluster quick-start-ik0pp2/quick-start-tkakk1: dialing host IP address at 192.168.6.90: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Failed to get logs for Machine quick-start-tkakk1-md-0-658757d488-cnkkz, Cluster quick-start-ik0pp2/quick-start-tkakk1: dialing host IP address at 192.168.6.46: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
  STEP: Dumping all the Cluster API resources in the "quick-start-ik0pp2" namespace @ 01/19/23 06:15:57.558
  STEP: Deleting cluster quick-start-ik0pp2/quick-start-tkakk1 @ 01/19/23 06:15:57.831
  STEP: Deleting cluster quick-start-tkakk1 @ 01/19/23 06:15:57.849
  INFO: Waiting for the Cluster quick-start-ik0pp2/quick-start-tkakk1 to be deleted
  STEP: Waiting for cluster quick-start-tkakk1 to be deleted @ 01/19/23 06:15:57.862
  STEP: Deleting namespace used for hosting the "quick-start" test spec @ 01/19/23 06:16:27.883
... skipping 144 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0022fee70, 0x28}, {0xc0022feea0, 0x23}, {0xc00264e650, 0xb}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 21 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc001719fc0, 0x3e}, {0xc0005e6040, 0x39}, {0xc0027580f0, 0x21}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 6 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

        goroutine 33507 [select]
... skipping 3 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

        goroutine 77962 [chan receive, 4 minutes]
... skipping 41 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0029c39c0, 0x3a}, {0xc0029c3a00, 0x35}, {0xc000d32cc0, 0x1d}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 21 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc001f086f0, 0x27}, {0xc001f08720, 0x22}, {0xc001f045a4, 0xb}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 6 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

        goroutine 33460 [select]
... skipping 3 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

  There were additional failures detected.  To view them in detail run ginkgo -vv
... skipping 10 lines ...

Summarizing 1 Failure:
  [TIMEDOUT] Cluster creation with storage policy [It] should create a cluster successfully
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/storage_policy_test.go:57

Ran 10 of 17 Specs in 3578.003 seconds
FAIL! - Suite Timeout Elapsed -- 9 Passed | 1 Failed | 1 Pending | 6 Skipped
--- FAIL: TestE2E (3578.00s)
FAIL

Ginkgo ran 1 suite in 1h0m32.075861929s

Test Suite Failed

real	60m32.098s
user	5m42.325s
sys	1m9.170s
make: *** [Makefile:183: e2e] Error 1
Releasing IP claims
ipclaim.ipam.metal3.io "ip-claim-c9e421402ae63712272a5cdb3b3a6118c46324b8" deleted
ipclaim.ipam.metal3.io "workload-ip-claim-1ab9b7601de3cb3d744490dd420c8e25e5c0dc92" 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. To explicitly delete the key associated with the service account use `gcloud iam service-accounts keys delete` instead`.
Revoked credentials:
... skipping 13 lines ...