periodic-cluster-api-provider-vsphere-e2e-main #1615578789859823616
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h4m |
| Revision | main |
... skipping 587 lines ... INFO: Waiting for correct number of replicas to exist [1mSTEP:[0m Scaling the MachineDeployment down to 1 [38;5;243m@ 01/18/23 05:28:48.606[0m INFO: Scaling machine deployment md-scale-br15zh/md-scale-v13lae-md-0 from 3 to 1 replicas INFO: Waiting for correct number of replicas to exist [1mSTEP:[0m PASSED! [38;5;243m@ 01/18/23 05:28:58.788[0m [1mSTEP:[0m Dumping logs from the "md-scale-v13lae" workload cluster [38;5;243m@ 01/18/23 05:28:58.788[0m Failed to get logs for Machine md-scale-v13lae-md-0-5867697965-c4knh, Cluster md-scale-br15zh/md-scale-v13lae: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-scale-v13lae-tg9vm, Cluster md-scale-br15zh/md-scale-v13lae: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "md-scale-br15zh" namespace [38;5;243m@ 01/18/23 05:29:03.483[0m [1mSTEP:[0m Deleting cluster md-scale-br15zh/md-scale-v13lae [38;5;243m@ 01/18/23 05:29:03.745[0m [1mSTEP:[0m Deleting cluster md-scale-v13lae [38;5;243m@ 01/18/23 05:29:03.763[0m INFO: Waiting for the Cluster md-scale-br15zh/md-scale-v13lae to be deleted [1mSTEP:[0m Waiting for cluster md-scale-v13lae to be deleted [38;5;243m@ 01/18/23 05:29:03.777[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-scale" test spec [38;5;243m@ 01/18/23 05:29:33.793[0m ... skipping 52 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 [1mSTEP:[0m PASSED! [38;5;243m@ 01/18/23 05:34:59.707[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-m69ikv" workload cluster [38;5;243m@ 01/18/23 05:34:59.707[0m Failed to get logs for Machine mhc-remediation-m69ikv-kdfft, Cluster mhc-remediation-inp3cp/mhc-remediation-m69ikv: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-m69ikv-md-0-6986d6df9b-x5ppw, Cluster mhc-remediation-inp3cp/mhc-remediation-m69ikv: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "mhc-remediation-inp3cp" namespace [38;5;243m@ 01/18/23 05:35:04.733[0m [1mSTEP:[0m Deleting cluster mhc-remediation-inp3cp/mhc-remediation-m69ikv [38;5;243m@ 01/18/23 05:35:05.003[0m [1mSTEP:[0m Deleting cluster mhc-remediation-m69ikv [38;5;243m@ 01/18/23 05:35:05.018[0m INFO: Waiting for the Cluster mhc-remediation-inp3cp/mhc-remediation-m69ikv to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-m69ikv to be deleted [38;5;243m@ 01/18/23 05:35:05.03[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/18/23 05:35:35.048[0m ... 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 [1mSTEP:[0m PASSED! [38;5;243m@ 01/18/23 05:44:46.498[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-nkark0" workload cluster [38;5;243m@ 01/18/23 05:44:46.498[0m Failed to get logs for Machine mhc-remediation-nkark0-8qpdh, Cluster mhc-remediation-lhkbae/mhc-remediation-nkark0: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-nkark0-l9tw2, Cluster mhc-remediation-lhkbae/mhc-remediation-nkark0: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-nkark0-md-0-6974768d58-kqv7w, Cluster mhc-remediation-lhkbae/mhc-remediation-nkark0: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-nkark0-nkx4p, Cluster mhc-remediation-lhkbae/mhc-remediation-nkark0: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "mhc-remediation-lhkbae" namespace [38;5;243m@ 01/18/23 05:44:54.358[0m [1mSTEP:[0m Deleting cluster mhc-remediation-lhkbae/mhc-remediation-nkark0 [38;5;243m@ 01/18/23 05:44:54.647[0m [1mSTEP:[0m Deleting cluster mhc-remediation-nkark0 [38;5;243m@ 01/18/23 05:44:54.668[0m INFO: Waiting for the Cluster mhc-remediation-lhkbae/mhc-remediation-nkark0 to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-nkark0 to be deleted [38;5;243m@ 01/18/23 05:44:54.681[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/18/23 05:45:34.707[0m ... skipping 167 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 [1mSTEP:[0m PASSED! [38;5;243m@ 01/18/23 06:00:48.125[0m [1mSTEP:[0m Dumping logs from the "md-rollout-5qrxvx" workload cluster [38;5;243m@ 01/18/23 06:00:48.126[0m Failed to get logs for Machine md-rollout-5qrxvx-md-0-7ddf8d75cb-vwq89, Cluster md-rollout-vmhmlm/md-rollout-5qrxvx: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-rollout-5qrxvx-xsdjh, Cluster md-rollout-vmhmlm/md-rollout-5qrxvx: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "md-rollout-vmhmlm" namespace [38;5;243m@ 01/18/23 06:00:52.41[0m [1mSTEP:[0m Deleting cluster md-rollout-vmhmlm/md-rollout-5qrxvx [38;5;243m@ 01/18/23 06:00:52.672[0m [1mSTEP:[0m Deleting cluster md-rollout-5qrxvx [38;5;243m@ 01/18/23 06:00:52.689[0m INFO: Waiting for the Cluster md-rollout-vmhmlm/md-rollout-5qrxvx to be deleted [1mSTEP:[0m Waiting for cluster md-rollout-5qrxvx to be deleted [38;5;243m@ 01/18/23 06:00:52.701[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-rollout" test spec [38;5;243m@ 01/18/23 06:01:22.718[0m ... skipping 44 lines ... INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/18/23 06:04:34.004[0m [1mSTEP:[0m Checking all the machines controlled by quick-start-s8aryq-md-0 are in the "<None>" failure domain [38;5;243m@ 01/18/23 06:05:14.054[0m INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m PASSED! [38;5;243m@ 01/18/23 06:05:14.091[0m [1mSTEP:[0m Dumping logs from the "quick-start-s8aryq" workload cluster [38;5;243m@ 01/18/23 06:05:14.092[0m Failed to get logs for Machine quick-start-s8aryq-j8r9n, Cluster quick-start-mjgbj9/quick-start-s8aryq: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine quick-start-s8aryq-md-0-5bb47d787-r5xvq, Cluster quick-start-mjgbj9/quick-start-s8aryq: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "quick-start-mjgbj9" namespace [38;5;243m@ 01/18/23 06:05:18.618[0m [1mSTEP:[0m Deleting cluster quick-start-mjgbj9/quick-start-s8aryq [38;5;243m@ 01/18/23 06:05:18.884[0m [1mSTEP:[0m Deleting cluster quick-start-s8aryq [38;5;243m@ 01/18/23 06:05:18.901[0m INFO: Waiting for the Cluster quick-start-mjgbj9/quick-start-s8aryq to be deleted [1mSTEP:[0m Waiting for cluster quick-start-s8aryq to be deleted [38;5;243m@ 01/18/23 06:05:18.914[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/18/23 06:05:48.933[0m ... skipping 44 lines ... INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/18/23 06:08:00.115[0m [1mSTEP:[0m Checking all the machines controlled by quick-start-2nzsjh-md-0 are in the "<None>" failure domain [38;5;243m@ 01/18/23 06:09:20.223[0m INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m PASSED! [38;5;243m@ 01/18/23 06:09:20.269[0m [1mSTEP:[0m Dumping logs from the "quick-start-2nzsjh" workload cluster [38;5;243m@ 01/18/23 06:09:20.269[0m Failed to get logs for Machine quick-start-2nzsjh-lr9s6, Cluster quick-start-e3w53b/quick-start-2nzsjh: dialing host IP address at 192.168.6.135: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain Failed to get logs for Machine quick-start-2nzsjh-md-0-66947d445b-pqg2k, Cluster quick-start-e3w53b/quick-start-2nzsjh: dialing host IP address at 192.168.6.143: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain [1mSTEP:[0m Dumping all the Cluster API resources in the "quick-start-e3w53b" namespace [38;5;243m@ 01/18/23 06:09:22.818[0m [1mSTEP:[0m Deleting cluster quick-start-e3w53b/quick-start-2nzsjh [38;5;243m@ 01/18/23 06:09:23.142[0m [1mSTEP:[0m Deleting cluster quick-start-2nzsjh [38;5;243m@ 01/18/23 06:09:23.162[0m INFO: Waiting for the Cluster quick-start-e3w53b/quick-start-2nzsjh to be deleted [1mSTEP:[0m Waiting for cluster quick-start-2nzsjh to be deleted [38;5;243m@ 01/18/23 06:09:23.177[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/18/23 06:09:53.197[0m ... skipping 57 lines ... INFO: Waiting for MachineDeployment rollout for MachineDeploymentTopology "md-0" (class "quick-start-worker") to complete. [1mSTEP:[0m Deleting a MachineDeploymentTopology in the Cluster Topology and wait for associated MachineDeployment to be deleted [38;5;243m@ 01/18/23 06:13:54.958[0m INFO: Removing MachineDeploymentTopology from the Cluster Topology. INFO: Waiting for MachineDeployment to be deleted. [1mSTEP:[0m PASSED! [38;5;243m@ 01/18/23 06:14:05.029[0m [1mSTEP:[0m Dumping logs from the "clusterclass-changes-x460bi" workload cluster [38;5;243m@ 01/18/23 06:14:05.029[0m Failed to get logs for Machine clusterclass-changes-x460bi-9pdjw-r7nmx, Cluster clusterclass-changes-rnhcat/clusterclass-changes-x460bi: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "clusterclass-changes-rnhcat" namespace [38;5;243m@ 01/18/23 06:14:07.173[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-rnhcat/clusterclass-changes-x460bi [38;5;243m@ 01/18/23 06:14:07.457[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-x460bi [38;5;243m@ 01/18/23 06:14:07.474[0m INFO: Waiting for the Cluster clusterclass-changes-rnhcat/clusterclass-changes-x460bi to be deleted [1mSTEP:[0m Waiting for cluster clusterclass-changes-x460bi to be deleted [38;5;243m@ 01/18/23 06:14:07.484[0m [1mSTEP:[0m Deleting namespace used for hosting the "clusterclass-changes" test spec [38;5;243m@ 01/18/23 06:14:27.5[0m ... skipping 137 lines ... [38;5;9m[1mSummarizing 1 Failure:[0m [38;5;214m[TIMEDOUT][0m [0mCluster creation with anti affined nodes [38;5;214m[1m[It] should create a cluster with anti-affined nodes[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/anti_affinity_test.go:61[0m [38;5;9m[1mRan 10 of 17 Specs in 3580.214 seconds[0m [38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m9 Passed[0m | [38;5;9m[1m1 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m6 Skipped[0m --- FAIL: TestE2E (3580.22s) FAIL Ginkgo ran 1 suite in 1h0m31.497854773s Test Suite Failed real 60m31.515s user 5m31.695s sys 0m59.880s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-e13d9383c1f05993bf8a2b17132dcc647c59d762" deleted ipclaim.ipam.metal3.io "workload-ip-claim-090051fe3e090a2af6ce6ecd1a06811513491f93" 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 ...