periodic-cluster-api-provider-vsphere-e2e-main #1616484801626247168
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h5m |
| Revision | main |
... skipping 764 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/20/23 17:45:34.217[0m INFO: Removing MachineDeploymentTopology from the Cluster Topology. INFO: Waiting for MachineDeployment to be deleted. [1mSTEP:[0m PASSED! [38;5;243m@ 01/20/23 17:45:44.293[0m [1mSTEP:[0m Dumping logs from the "clusterclass-changes-qnbi90" workload cluster [38;5;243m@ 01/20/23 17:45:44.293[0m Failed to get logs for Machine clusterclass-changes-qnbi90-wq59k-gxczn, Cluster clusterclass-changes-khqt6n/clusterclass-changes-qnbi90: 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-khqt6n" namespace [38;5;243m@ 01/20/23 17:45:46.345[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-khqt6n/clusterclass-changes-qnbi90 [38;5;243m@ 01/20/23 17:45:46.625[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-qnbi90 [38;5;243m@ 01/20/23 17:45:46.647[0m INFO: Waiting for the Cluster clusterclass-changes-khqt6n/clusterclass-changes-qnbi90 to be deleted [1mSTEP:[0m Waiting for cluster clusterclass-changes-qnbi90 to be deleted [38;5;243m@ 01/20/23 17:45:46.657[0m [1mSTEP:[0m Deleting namespace used for hosting the "clusterclass-changes" test spec [38;5;243m@ 01/20/23 17:46:06.673[0m ... skipping 105 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/20/23 17:55:31.573[0m [1mSTEP:[0m Dumping logs from the "md-rollout-90ut6e" workload cluster [38;5;243m@ 01/20/23 17:55:31.573[0m Failed to get logs for Machine md-rollout-90ut6e-7m5fr, Cluster md-rollout-ckly9t/md-rollout-90ut6e: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-rollout-90ut6e-md-0-847d65f96-wqnsz, Cluster md-rollout-ckly9t/md-rollout-90ut6e: 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-ckly9t" namespace [38;5;243m@ 01/20/23 17:55:36.023[0m [1mSTEP:[0m Deleting cluster md-rollout-ckly9t/md-rollout-90ut6e [38;5;243m@ 01/20/23 17:55:36.3[0m [1mSTEP:[0m Deleting cluster md-rollout-90ut6e [38;5;243m@ 01/20/23 17:55:36.318[0m INFO: Waiting for the Cluster md-rollout-ckly9t/md-rollout-90ut6e to be deleted [1mSTEP:[0m Waiting for cluster md-rollout-90ut6e to be deleted [38;5;243m@ 01/20/23 17:55:36.332[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-rollout" test spec [38;5;243m@ 01/20/23 17:56:06.35[0m ... skipping 56 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/20/23 18:02:02.622[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-hbpxok" workload cluster [38;5;243m@ 01/20/23 18:02:02.622[0m Failed to get logs for Machine mhc-remediation-hbpxok-btjsb, Cluster mhc-remediation-gnl3at/mhc-remediation-hbpxok: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-hbpxok-md-0-596c96cf96-zlwxp, Cluster mhc-remediation-gnl3at/mhc-remediation-hbpxok: 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-gnl3at" namespace [38;5;243m@ 01/20/23 18:02:07.247[0m [1mSTEP:[0m Deleting cluster mhc-remediation-gnl3at/mhc-remediation-hbpxok [38;5;243m@ 01/20/23 18:02:07.535[0m [1mSTEP:[0m Deleting cluster mhc-remediation-hbpxok [38;5;243m@ 01/20/23 18:02:07.554[0m INFO: Waiting for the Cluster mhc-remediation-gnl3at/mhc-remediation-hbpxok to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-hbpxok to be deleted [38;5;243m@ 01/20/23 18:02:07.566[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/20/23 18:02:37.586[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/20/23 18:11:25.256[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-4sz73q" workload cluster [38;5;243m@ 01/20/23 18:11:25.256[0m Failed to get logs for Machine mhc-remediation-4sz73q-md-0-66f64d8ccf-ltfsr, Cluster mhc-remediation-lyme1p/mhc-remediation-4sz73q: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-4sz73q-phxgh, Cluster mhc-remediation-lyme1p/mhc-remediation-4sz73q: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-4sz73q-qrjsx, Cluster mhc-remediation-lyme1p/mhc-remediation-4sz73q: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-4sz73q-vx84f, Cluster mhc-remediation-lyme1p/mhc-remediation-4sz73q: 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-lyme1p" namespace [38;5;243m@ 01/20/23 18:11:32.673[0m [1mSTEP:[0m Deleting cluster mhc-remediation-lyme1p/mhc-remediation-4sz73q [38;5;243m@ 01/20/23 18:11:32.986[0m [1mSTEP:[0m Deleting cluster mhc-remediation-4sz73q [38;5;243m@ 01/20/23 18:11:33.004[0m INFO: Waiting for the Cluster mhc-remediation-lyme1p/mhc-remediation-4sz73q to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-4sz73q to be deleted [38;5;243m@ 01/20/23 18:11:33.019[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/20/23 18:12:23.048[0m ... skipping 56 lines ... [1mSTEP:[0m Waiting for deployment node-drain-w8d5px-unevictable-workload/unevictable-pod-tb5 to be available [38;5;243m@ 01/20/23 18:19:39.919[0m [1mSTEP:[0m Scale down the controlplane of the workload cluster and make sure that nodes running workload can be deleted even the draining process is blocked. [38;5;243m@ 01/20/23 18:19:50.218[0m INFO: Scaling controlplane node-drain-w8d5px/node-drain-yct27j from 3 to 1 replicas INFO: Waiting for correct number of replicas to exist [38;5;214m[TIMEDOUT][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/node_drain_timeout.go:83 [38;5;243m@ 01/20/23 18:20:36.605[0m [1mSTEP:[0m Dumping logs from the "node-drain-yct27j" workload cluster [38;5;243m@ 01/20/23 18:20:36.606[0m Failed to get logs for Machine node-drain-yct27j-m6vgw, Cluster node-drain-w8d5px/node-drain-yct27j: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine node-drain-yct27j-qwmd9, Cluster node-drain-w8d5px/node-drain-yct27j: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine node-drain-yct27j-tk6ld, Cluster node-drain-w8d5px/node-drain-yct27j: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "node-drain-w8d5px" namespace [38;5;243m@ 01/20/23 18:20:41.886[0m [1mSTEP:[0m Deleting cluster node-drain-w8d5px/node-drain-yct27j [38;5;243m@ 01/20/23 18:20:42.174[0m [1mSTEP:[0m Deleting cluster node-drain-yct27j [38;5;243m@ 01/20/23 18:20:42.191[0m INFO: Waiting for the Cluster node-drain-w8d5px/node-drain-yct27j to be deleted [1mSTEP:[0m Waiting for cluster node-drain-yct27j to be deleted [38;5;243m@ 01/20/23 18:20:42.205[0m [38;5;214m[TIMEDOUT][0m in [AfterEach] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/node_drain_timeout.go:155 [38;5;243m@ 01/20/23 18:21:06.606[0m ... skipping 47 lines ... [38;5;9m[1mSummarizing 1 Failure:[0m [38;5;214m[TIMEDOUT][0m [0mWhen testing node drain timeout [38;5;214m[1m[It] A node should be forcefully removed if it cannot be drained in time[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/node_drain_timeout.go:83[0m [38;5;9m[1mRan 9 of 17 Specs in 3577.814 seconds[0m [38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m8 Passed[0m | [38;5;9m[1m1 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m7 Skipped[0m --- FAIL: TestE2E (3577.82s) FAIL Ginkgo ran 1 suite in 1h0m31.951397202s Test Suite Failed real 60m31.974s user 5m56.839s sys 1m14.989s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-68b0bde558b22e4739503c509bb672434ce1d551" deleted ipclaim.ipam.metal3.io "workload-ip-claim-f4c7cdbc1d8c3ec6247cb3fcf63a808f4b3a7c25" 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 ...