Recent runs || View in Spyglass
PR | chrischdi: 🐛 Use Kubernetes 1.24 in quickstart and CAPD, bump to kind v0.14 |
Result | Not Finished |
Started | |
Revision | |
Refs |
6513 |
capi-e2e When following the Cluster API quick-start [PR-Blocking] Should create a workload cluster
capi-e2e When following the Cluster API quick-start with ClusterClass [PR-Informing] Should create a workload cluster
capi-e2e When following the Cluster API quick-start with IPv6 [IPv6] [PR-Informing] Should create a workload cluster
capi-e2e When following the Cluster API quick-start with Ignition Should create a workload cluster
capi-e2e When testing Cluster API working on self-hosted clusters Should pivot the bootstrap cluster to a self-hosted cluster
capi-e2e When testing Cluster API working on self-hosted clusters using ClusterClass Should pivot the bootstrap cluster to a self-hosted cluster
capi-e2e When testing ClusterClass changes Should successfully rollout the managed topology upon changes to the ClusterClass
capi-e2e When testing K8S conformance [Conformance] Should create a workload cluster and run kubetest
capi-e2e When testing KCP adoption Should adopt up-to-date control plane Machines without modification
capi-e2e When testing MachineDeployment rolling upgrades Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capi-e2e When testing MachineDeployment scale out/in Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capi-e2e When testing MachinePools Should successfully create a cluster with machine pool machines
capi-e2e When testing clusterctl upgrades [clusterctl-Upgrade] Should create a management cluster and then upgrade all the providers
capi-e2e When testing node drain timeout A node should be forcefully removed if it cannot be drained in time
capi-e2e When testing unhealthy machines remediation Should successfully trigger KCP remediation
capi-e2e When testing unhealthy machines remediation Should successfully trigger machine deployment remediation
capi-e2e When upgrading a workload cluster and testing K8S conformance [Conformance] [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capi-e2e When upgrading a workload cluster using ClusterClass Should create and upgrade a workload cluster and eventually run kubetest
capi-e2e When upgrading a workload cluster with a HA control plane Should create and upgrade a workload cluster and eventually run kubetest
capi-e2e When upgrading a workload cluster with a HA control plane using scale-in rollout Should create and upgrade a workload cluster and eventually run kubetest
capi-e2e When upgrading a workload cluster with a single control plane machine Should create and upgrade a workload cluster and eventually run kubetest
... skipping 910 lines ... INFO: Waiting for the machine deployments to be provisioned STEP: Waiting for the workload nodes to exist STEP: Checking all the machines controlled by quick-start-dplr8u-md-0 are in the "fd4" failure domain INFO: Waiting for the machine pools to be provisioned STEP: PASSED! STEP: Dumping logs from the "quick-start-dplr8u" workload cluster Failed to get logs for machine quick-start-dplr8u-control-plane-6wgkq, cluster quick-start-4qpmqo/quick-start-dplr8u: exit status 2 Failed to get logs for machine quick-start-dplr8u-md-0-dfb96bf99-fsqk5, cluster quick-start-4qpmqo/quick-start-dplr8u: exit status 2 STEP: Dumping all the Cluster API resources in the "quick-start-4qpmqo" namespace STEP: Deleting cluster quick-start-4qpmqo/quick-start-dplr8u STEP: Deleting cluster quick-start-dplr8u INFO: Waiting for the Cluster quick-start-4qpmqo/quick-start-dplr8u to be deleted STEP: Waiting for cluster quick-start-dplr8u to be deleted STEP: Deleting namespace used for hosting the "quick-start" test spec ... skipping 4 lines ... When following the Cluster API quick-start [PR-Blocking] /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/quick_start_test.go:27 Should create a workload cluster /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/quick_start.go:77 ------------------------------ STEP: Dumping logs from the bootstrap cluster Failed to get logs for the bootstrap cluster node test-gipfev-control-plane: exit status 2 STEP: Tearing down the management cluster Ran 1 of 21 Specs in 209.807 seconds SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 20 Skipped Ginkgo ran 1 suite in 4m32.032336845s Test Suite Passed make: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e' + cleanup ... skipping 25 lines ...