periodic-cluster-api-provider-vsphere-e2e-main #1616122379518349312
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h5m |
| Revision | main |
... skipping 573 lines ... INFO: Waiting for correct number of replicas to exist [1mSTEP:[0m Scaling the MachineDeployment down to 1 [38;5;243m@ 01/19/23 17:31:21.64[0m INFO: Scaling machine deployment md-scale-8718pe/md-scale-rjb0vo-md-0 from 3 to 1 replicas INFO: Waiting for correct number of replicas to exist [1mSTEP:[0m PASSED! [38;5;243m@ 01/19/23 17:31:31.789[0m [1mSTEP:[0m Dumping logs from the "md-scale-rjb0vo" workload cluster [38;5;243m@ 01/19/23 17:31:31.79[0m Failed to get logs for Machine md-scale-rjb0vo-c6859, Cluster md-scale-8718pe/md-scale-rjb0vo: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-scale-rjb0vo-md-0-5597549596-nmslc, Cluster md-scale-8718pe/md-scale-rjb0vo: 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-8718pe" namespace [38;5;243m@ 01/19/23 17:31:36.108[0m [1mSTEP:[0m Deleting cluster md-scale-8718pe/md-scale-rjb0vo [38;5;243m@ 01/19/23 17:31:36.453[0m [1mSTEP:[0m Deleting cluster md-scale-rjb0vo [38;5;243m@ 01/19/23 17:31:36.482[0m INFO: Waiting for the Cluster md-scale-8718pe/md-scale-rjb0vo to be deleted [1mSTEP:[0m Waiting for cluster md-scale-rjb0vo to be deleted [38;5;243m@ 01/19/23 17:31:36.497[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-scale" test spec [38;5;243m@ 01/19/23 17:32:06.518[0m ... skipping 100 lines ... INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/19/23 17:39:04.718[0m [1mSTEP:[0m Checking all the machines controlled by quick-start-zgelom-md-0 are in the "<None>" failure domain [38;5;243m@ 01/19/23 17:40:14.825[0m INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m PASSED! [38;5;243m@ 01/19/23 17:40:14.876[0m [1mSTEP:[0m Dumping logs from the "quick-start-zgelom" workload cluster [38;5;243m@ 01/19/23 17:40:14.876[0m Failed to get logs for Machine quick-start-zgelom-6gq4j, Cluster quick-start-3581h4/quick-start-zgelom: dialing host IP address at 192.168.6.156: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain Failed to get logs for Machine quick-start-zgelom-md-0-db59cf85f-x22z7, Cluster quick-start-3581h4/quick-start-zgelom: dialing host IP address at 192.168.6.87: 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-3581h4" namespace [38;5;243m@ 01/19/23 17:40:17.331[0m [1mSTEP:[0m Deleting cluster quick-start-3581h4/quick-start-zgelom [38;5;243m@ 01/19/23 17:40:17.71[0m [1mSTEP:[0m Deleting cluster quick-start-zgelom [38;5;243m@ 01/19/23 17:40:17.735[0m INFO: Waiting for the Cluster quick-start-3581h4/quick-start-zgelom to be deleted [1mSTEP:[0m Waiting for cluster quick-start-zgelom to be deleted [38;5;243m@ 01/19/23 17:40:17.755[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/19/23 17:40:47.779[0m ... skipping 113 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/19/23 17:51:18.507[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-m7ghs9" workload cluster [38;5;243m@ 01/19/23 17:51:18.507[0m Failed to get logs for Machine mhc-remediation-m7ghs9-fq5vv, Cluster mhc-remediation-jhwv9y/mhc-remediation-m7ghs9: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-m7ghs9-md-0-6fc6989c79-ml58z, Cluster mhc-remediation-jhwv9y/mhc-remediation-m7ghs9: 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-jhwv9y" namespace [38;5;243m@ 01/19/23 17:51:23.07[0m [1mSTEP:[0m Deleting cluster mhc-remediation-jhwv9y/mhc-remediation-m7ghs9 [38;5;243m@ 01/19/23 17:51:23.4[0m [1mSTEP:[0m Deleting cluster mhc-remediation-m7ghs9 [38;5;243m@ 01/19/23 17:51:23.428[0m INFO: Waiting for the Cluster mhc-remediation-jhwv9y/mhc-remediation-m7ghs9 to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-m7ghs9 to be deleted [38;5;243m@ 01/19/23 17:51:23.442[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/19/23 17:51:53.464[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/19/23 18:01:00.902[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-vrbxel" workload cluster [38;5;243m@ 01/19/23 18:01:00.902[0m Failed to get logs for Machine mhc-remediation-vrbxel-7gcdx, Cluster mhc-remediation-tnv00w/mhc-remediation-vrbxel: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-vrbxel-blsnn, Cluster mhc-remediation-tnv00w/mhc-remediation-vrbxel: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-vrbxel-klz7t, Cluster mhc-remediation-tnv00w/mhc-remediation-vrbxel: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-vrbxel-md-0-6ccc59cb58-77g8s, Cluster mhc-remediation-tnv00w/mhc-remediation-vrbxel: 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-tnv00w" namespace [38;5;243m@ 01/19/23 18:01:08.484[0m [1mSTEP:[0m Deleting cluster mhc-remediation-tnv00w/mhc-remediation-vrbxel [38;5;243m@ 01/19/23 18:01:09.086[0m [1mSTEP:[0m Deleting cluster mhc-remediation-vrbxel [38;5;243m@ 01/19/23 18:01:09.117[0m INFO: Waiting for the Cluster mhc-remediation-tnv00w/mhc-remediation-vrbxel to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-vrbxel to be deleted [38;5;243m@ 01/19/23 18:01:09.141[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/19/23 18:01:59.183[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/19/23 18:04:40.912[0m [1mSTEP:[0m Checking all the machines controlled by quick-start-x3pjxv-md-0 are in the "<None>" failure domain [38;5;243m@ 01/19/23 18:05:30.995[0m INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m PASSED! [38;5;243m@ 01/19/23 18:05:31.042[0m [1mSTEP:[0m Dumping logs from the "quick-start-x3pjxv" workload cluster [38;5;243m@ 01/19/23 18:05:31.043[0m Failed to get logs for Machine quick-start-x3pjxv-9tvxq, Cluster quick-start-b4t3l9/quick-start-x3pjxv: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine quick-start-x3pjxv-md-0-656fcf4cc6-clvz8, Cluster quick-start-b4t3l9/quick-start-x3pjxv: 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-b4t3l9" namespace [38;5;243m@ 01/19/23 18:05:35.672[0m [1mSTEP:[0m Deleting cluster quick-start-b4t3l9/quick-start-x3pjxv [38;5;243m@ 01/19/23 18:05:36.025[0m [1mSTEP:[0m Deleting cluster quick-start-x3pjxv [38;5;243m@ 01/19/23 18:05:36.046[0m INFO: Waiting for the Cluster quick-start-b4t3l9/quick-start-x3pjxv to be deleted [1mSTEP:[0m Waiting for cluster quick-start-x3pjxv to be deleted [38;5;243m@ 01/19/23 18:05:36.062[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/19/23 18:06:06.083[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/19/23 18:08:27.746[0m [1mSTEP:[0m Checking all the machines controlled by quick-start-gz98vg-md-0-l9t4g are in the "<None>" failure domain [38;5;243m@ 01/19/23 18:10:07.889[0m INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m PASSED! [38;5;243m@ 01/19/23 18:10:07.938[0m [1mSTEP:[0m Dumping logs from the "quick-start-gz98vg" workload cluster [38;5;243m@ 01/19/23 18:10:07.938[0m Failed to get logs for Machine quick-start-gz98vg-l9j49-zwkhh, Cluster quick-start-u5e14d/quick-start-gz98vg: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine quick-start-gz98vg-md-0-l9t4g-7bf5b7bd69-x2k8f, Cluster quick-start-u5e14d/quick-start-gz98vg: 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-u5e14d" namespace [38;5;243m@ 01/19/23 18:10:12.383[0m [1mSTEP:[0m Deleting cluster quick-start-u5e14d/quick-start-gz98vg [38;5;243m@ 01/19/23 18:10:12.705[0m [1mSTEP:[0m Deleting cluster quick-start-gz98vg [38;5;243m@ 01/19/23 18:10:12.732[0m INFO: Waiting for the Cluster quick-start-u5e14d/quick-start-gz98vg to be deleted [1mSTEP:[0m Waiting for cluster quick-start-gz98vg to be deleted [38;5;243m@ 01/19/23 18:10:12.749[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/19/23 18:10:42.779[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/19/23 18:15:14.971[0m INFO: Removing MachineDeploymentTopology from the Cluster Topology. INFO: Waiting for MachineDeployment to be deleted. [1mSTEP:[0m PASSED! [38;5;243m@ 01/19/23 18:15:25.049[0m [1mSTEP:[0m Dumping logs from the "clusterclass-changes-j8y1fm" workload cluster [38;5;243m@ 01/19/23 18:15:25.049[0m Failed to get logs for Machine clusterclass-changes-j8y1fm-q9knj-c6mtj, Cluster clusterclass-changes-vtnxs4/clusterclass-changes-j8y1fm: 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-vtnxs4" namespace [38;5;243m@ 01/19/23 18:15:27.122[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-vtnxs4/clusterclass-changes-j8y1fm [38;5;243m@ 01/19/23 18:15:27.452[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-j8y1fm [38;5;243m@ 01/19/23 18:15:27.473[0m INFO: Waiting for the Cluster clusterclass-changes-vtnxs4/clusterclass-changes-j8y1fm to be deleted [1mSTEP:[0m Waiting for cluster clusterclass-changes-j8y1fm to be deleted [38;5;243m@ 01/19/23 18:15:27.49[0m [1mSTEP:[0m Deleting namespace used for hosting the "clusterclass-changes" test spec [38;5;243m@ 01/19/23 18:15:47.507[0m ... skipping 50 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 [38;5;214m[TIMEDOUT][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_rollout.go:71 [38;5;243m@ 01/19/23 18:21:21.398[0m [1mSTEP:[0m Dumping logs from the "md-rollout-lixkmy" workload cluster [38;5;243m@ 01/19/23 18:21:21.4[0m Failed to get logs for Machine md-rollout-lixkmy-md-0-6864f5686b-5vhpn, Cluster md-rollout-oaxuax/md-rollout-lixkmy: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-rollout-lixkmy-t78hq, Cluster md-rollout-oaxuax/md-rollout-lixkmy: 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-oaxuax" namespace [38;5;243m@ 01/19/23 18:21:25.989[0m [1mSTEP:[0m Deleting cluster md-rollout-oaxuax/md-rollout-lixkmy [38;5;243m@ 01/19/23 18:21:26.295[0m [1mSTEP:[0m Deleting cluster md-rollout-lixkmy [38;5;243m@ 01/19/23 18:21:26.316[0m INFO: Waiting for the Cluster md-rollout-oaxuax/md-rollout-lixkmy to be deleted [1mSTEP:[0m Waiting for cluster md-rollout-lixkmy to be deleted [38;5;243m@ 01/19/23 18:21:26.332[0m [38;5;214m[TIMEDOUT][0m in [AfterEach] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_rollout.go:103 [38;5;243m@ 01/19/23 18:21:51.401[0m ... skipping 49 lines ... [38;5;9m[1mSummarizing 1 Failure:[0m [38;5;214m[TIMEDOUT][0m [0mClusterAPI Machine Deployment Tests [38;5;243mRunning the MachineDeployment rollout spec [38;5;214m[1m[It] Should successfully upgrade Machines upon changes in relevant MachineDeployment fields[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_rollout.go:71[0m [38;5;9m[1mRan 10 of 17 Specs in 3517.048 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 (3517.05s) FAIL Ginkgo ran 1 suite in 1h0m31.903975473s Test Suite Failed real 60m31.945s user 10m21.354s sys 3m8.113s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-fbe596c8ff8bb5fa23c80e7b44f81550990e08ee" deleted ipclaim.ipam.metal3.io "workload-ip-claim-f3715867f6fe6252ceb73be542688cb484d7279a" 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 ...