This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultsuccess
Tests 0 failed / 17 succeeded
Started2022-09-04 13:11
Elapsed56m41s
Revision
uploadercrier
uploadercrier

No Test Failures!


Show 17 Passed Tests

Show 3 Skipped Tests

Error lines from build-log.txt

... skipping 942 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!
STEP: Dumping logs from the "mhc-remediation-z5c7iz" workload cluster
Failed to get logs for machine mhc-remediation-z5c7iz-control-plane-hjq7w, cluster mhc-remediation-0jkdkx/mhc-remediation-z5c7iz: exit status 2
Failed to get logs for machine mhc-remediation-z5c7iz-md-0-669b56b4d4-xh248, cluster mhc-remediation-0jkdkx/mhc-remediation-z5c7iz: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-0jkdkx" namespace
STEP: Deleting cluster mhc-remediation-0jkdkx/mhc-remediation-z5c7iz
STEP: Deleting cluster mhc-remediation-z5c7iz
INFO: Waiting for the Cluster mhc-remediation-0jkdkx/mhc-remediation-z5c7iz to be deleted
STEP: Waiting for cluster mhc-remediation-z5c7iz to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
... skipping 48 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!
STEP: Dumping logs from the "mhc-remediation-ugqz7f" workload cluster
Failed to get logs for machine mhc-remediation-ugqz7f-control-plane-gd25c, cluster mhc-remediation-2avg15/mhc-remediation-ugqz7f: exit status 2
Failed to get logs for machine mhc-remediation-ugqz7f-control-plane-sd6c8, cluster mhc-remediation-2avg15/mhc-remediation-ugqz7f: exit status 2
Failed to get logs for machine mhc-remediation-ugqz7f-control-plane-z27bj, cluster mhc-remediation-2avg15/mhc-remediation-ugqz7f: exit status 2
Failed to get logs for machine mhc-remediation-ugqz7f-md-0-5ccf6ffcf7-9wmst, cluster mhc-remediation-2avg15/mhc-remediation-ugqz7f: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-2avg15" namespace
STEP: Deleting cluster mhc-remediation-2avg15/mhc-remediation-ugqz7f
STEP: Deleting cluster mhc-remediation-ugqz7f
INFO: Waiting for the Cluster mhc-remediation-2avg15/mhc-remediation-ugqz7f to be deleted
STEP: Waiting for cluster mhc-remediation-ugqz7f to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
... skipping 104 lines ...
STEP: Deleting cluster clusterctl-upgrade/clusterctl-upgrade-ixzqz0
STEP: Deleting namespace clusterctl-upgrade used for hosting the "clusterctl-upgrade" test
INFO: Deleting namespace clusterctl-upgrade
STEP: Deleting providers
INFO: clusterctl delete --all
STEP: Dumping logs from the "clusterctl-upgrade-ixzqz0" workload cluster
Failed to get logs for machine clusterctl-upgrade-ixzqz0-control-plane-t2vgr, cluster clusterctl-upgrade-n1jv30/clusterctl-upgrade-ixzqz0: exit status 2
Failed to get logs for machine clusterctl-upgrade-ixzqz0-md-0-bdd7b7d55-982z5, cluster clusterctl-upgrade-n1jv30/clusterctl-upgrade-ixzqz0: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterctl-upgrade-n1jv30" namespace
STEP: Deleting cluster clusterctl-upgrade-n1jv30/clusterctl-upgrade-ixzqz0
STEP: Deleting cluster clusterctl-upgrade-ixzqz0
INFO: Waiting for the Cluster clusterctl-upgrade-n1jv30/clusterctl-upgrade-ixzqz0 to be deleted
STEP: Waiting for cluster clusterctl-upgrade-ixzqz0 to be deleted
STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
... skipping 49 lines ...
STEP: Waiting for the machine pool workload nodes
STEP: Scaling the machine pool to zero
INFO: Patching the replica count in Machine Pool machine-pool-36bedy/machine-pool-hmcjhc-mp-0
STEP: Waiting for the machine pool workload nodes
STEP: PASSED!
STEP: Dumping logs from the "machine-pool-hmcjhc" workload cluster
Failed to get logs for machine machine-pool-hmcjhc-control-plane-89dvf, cluster machine-pool-36bedy/machine-pool-hmcjhc: exit status 2
STEP: Dumping all the Cluster API resources in the "machine-pool-36bedy" namespace
STEP: Deleting cluster machine-pool-36bedy/machine-pool-hmcjhc
STEP: Deleting cluster machine-pool-hmcjhc
INFO: Waiting for the Cluster machine-pool-36bedy/machine-pool-hmcjhc to be deleted
STEP: Waiting for cluster machine-pool-hmcjhc to be deleted
STEP: Deleting namespace used for hosting the "machine-pool" test spec
... skipping 44 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!
STEP: Dumping logs from the "md-rollout-5rkr4o" workload cluster
Failed to get logs for machine md-rollout-5rkr4o-control-plane-nqtvw, cluster md-rollout-f9wpao/md-rollout-5rkr4o: exit status 2
Failed to get logs for machine md-rollout-5rkr4o-md-0-55bd946b4c-c7mgg, cluster md-rollout-f9wpao/md-rollout-5rkr4o: exit status 2
STEP: Dumping all the Cluster API resources in the "md-rollout-f9wpao" namespace
STEP: Deleting cluster md-rollout-f9wpao/md-rollout-5rkr4o
STEP: Deleting cluster md-rollout-5rkr4o
INFO: Waiting for the Cluster md-rollout-f9wpao/md-rollout-5rkr4o to be deleted
STEP: Waiting for cluster md-rollout-5rkr4o to be deleted
STEP: Deleting namespace used for hosting the "md-rollout" test spec
... skipping 52 lines ...
STEP: Waiting for deployment node-drain-j2d9z3-unevictable-workload/unevictable-pod-j4g to be available
STEP: Scale down the controlplane of the workload cluster and make sure that nodes running workload can be deleted even the draining process is blocked.
INFO: Scaling controlplane node-drain-j2d9z3/node-drain-gcfk8p-control-plane from 3 to 1 replicas
INFO: Waiting for correct number of replicas to exist
STEP: PASSED!
STEP: Dumping logs from the "node-drain-gcfk8p" workload cluster
Failed to get logs for machine node-drain-gcfk8p-control-plane-dngjt, cluster node-drain-j2d9z3/node-drain-gcfk8p: exit status 2
STEP: Dumping all the Cluster API resources in the "node-drain-j2d9z3" namespace
STEP: Deleting cluster node-drain-j2d9z3/node-drain-gcfk8p
STEP: Deleting cluster node-drain-gcfk8p
INFO: Waiting for the Cluster node-drain-j2d9z3/node-drain-gcfk8p to be deleted
STEP: Waiting for cluster node-drain-gcfk8p to be deleted
STEP: Deleting namespace used for hosting the "node-drain" test spec
... skipping 52 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-4u9dnd/k8s-upgrade-and-conformance-4y7qlz-md-0-cf42b to be upgraded to v1.24.0
INFO: Ensuring all MachineDeployment Machines have upgraded kubernetes version v1.24.0
STEP: Waiting until nodes are ready
STEP: PASSED!
STEP: Dumping logs from the "k8s-upgrade-and-conformance-4y7qlz" workload cluster
Failed to get logs for machine k8s-upgrade-and-conformance-4y7qlz-9bdkr-6kp9m, cluster k8s-upgrade-and-conformance-4u9dnd/k8s-upgrade-and-conformance-4y7qlz: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-4y7qlz-9bdkr-tgzdp, cluster k8s-upgrade-and-conformance-4u9dnd/k8s-upgrade-and-conformance-4y7qlz: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-4y7qlz-9bdkr-vcr2j, cluster k8s-upgrade-and-conformance-4u9dnd/k8s-upgrade-and-conformance-4y7qlz: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-4y7qlz-md-0-cf42b-6cc6b46b6b-vc6fz, cluster k8s-upgrade-and-conformance-4u9dnd/k8s-upgrade-and-conformance-4y7qlz: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-4u9dnd" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-4u9dnd/k8s-upgrade-and-conformance-4y7qlz
STEP: Deleting cluster k8s-upgrade-and-conformance-4y7qlz
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-4u9dnd/k8s-upgrade-and-conformance-4y7qlz to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-4y7qlz to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 38 lines ...
STEP: Waiting for the control plane to be ready
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-az3ufw" workload cluster
Failed to get logs for machine quick-start-az3ufw-control-plane-cxr7t, cluster quick-start-ylas57/quick-start-az3ufw: exit status 2
Failed to get logs for machine quick-start-az3ufw-md-0-79dc4fdb75-hzxxz, cluster quick-start-ylas57/quick-start-az3ufw: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-ylas57" namespace
STEP: Deleting cluster quick-start-ylas57/quick-start-az3ufw
STEP: Deleting cluster quick-start-az3ufw
INFO: Waiting for the Cluster quick-start-ylas57/quick-start-az3ufw to be deleted
STEP: Waiting for cluster quick-start-az3ufw to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 70 lines ...
STEP: Ensure API servers are stable before doing move
STEP: Moving the cluster back to bootstrap
STEP: Moving workload clusters
INFO: Waiting for the cluster to be reconciled after moving back to booststrap
STEP: Waiting for cluster to enter the provisioned phase
STEP: Dumping logs from the "self-hosted-27gaju" workload cluster
Failed to get logs for machine self-hosted-27gaju-md-0-r4hg8-d9574fc57-2t2n9, cluster self-hosted-8e7zzx/self-hosted-27gaju: exit status 2
Failed to get logs for machine self-hosted-27gaju-nlwkq-k5kx9, cluster self-hosted-8e7zzx/self-hosted-27gaju: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-8e7zzx" namespace
STEP: Deleting cluster self-hosted-8e7zzx/self-hosted-27gaju
STEP: Deleting cluster self-hosted-27gaju
INFO: Waiting for the Cluster self-hosted-8e7zzx/self-hosted-27gaju to be deleted
STEP: Waiting for cluster self-hosted-27gaju to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" test spec
... skipping 52 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-re06k6/k8s-upgrade-and-conformance-p5ot1w-md-0-tcf7d to be upgraded to v1.24.0
INFO: Ensuring all MachineDeployment Machines have upgraded kubernetes version v1.24.0
STEP: Waiting until nodes are ready
STEP: PASSED!
STEP: Dumping logs from the "k8s-upgrade-and-conformance-p5ot1w" workload cluster
Failed to get logs for machine k8s-upgrade-and-conformance-p5ot1w-6ncr6-2dhc4, cluster k8s-upgrade-and-conformance-re06k6/k8s-upgrade-and-conformance-p5ot1w: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-p5ot1w-md-0-tcf7d-759f699676-lqdbs, cluster k8s-upgrade-and-conformance-re06k6/k8s-upgrade-and-conformance-p5ot1w: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-p5ot1w-md-0-tcf7d-759f699676-rmdxh, cluster k8s-upgrade-and-conformance-re06k6/k8s-upgrade-and-conformance-p5ot1w: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-re06k6" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-re06k6/k8s-upgrade-and-conformance-p5ot1w
STEP: Deleting cluster k8s-upgrade-and-conformance-p5ot1w
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-re06k6/k8s-upgrade-and-conformance-p5ot1w to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-p5ot1w to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 35 lines ...

STEP: Waiting for the control plane to be ready
STEP: Taking stable ownership of the Machines
STEP: Taking ownership of the cluster's PKI material
STEP: PASSED!
STEP: Dumping logs from the "kcp-adoption-lt3o4g" workload cluster
Failed to get logs for machine kcp-adoption-lt3o4g-control-plane-0, cluster kcp-adoption-lqgl4v/kcp-adoption-lt3o4g: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-adoption-lqgl4v" namespace
STEP: Deleting cluster kcp-adoption-lqgl4v/kcp-adoption-lt3o4g
STEP: Deleting cluster kcp-adoption-lt3o4g
INFO: Waiting for the Cluster kcp-adoption-lqgl4v/kcp-adoption-lt3o4g to be deleted
STEP: Waiting for cluster kcp-adoption-lt3o4g to be deleted
STEP: Deleting namespace used for hosting the "kcp-adoption" test spec
... skipping 44 lines ...
INFO: Waiting for correct number of replicas to exist
STEP: Scaling the MachineDeployment down to 1
INFO: Scaling machine deployment md-scale-wvuhnl/md-scale-fd1duy-md-0 from 3 to 1 replicas
INFO: Waiting for correct number of replicas to exist
STEP: PASSED!
STEP: Dumping logs from the "md-scale-fd1duy" workload cluster
Failed to get logs for machine md-scale-fd1duy-control-plane-4kjbv, cluster md-scale-wvuhnl/md-scale-fd1duy: exited with status: 1, &{%!s(*os.file=&{{{0 0 0} 8 {0} <nil> 0 1 true true true} /tmp/md-scale-fd1duy-control-plane-4kjbv4093508974 <nil> false false false})}
Failed to get logs for machine md-scale-fd1duy-md-0-6d4b9b59bd-7h6w5, cluster md-scale-wvuhnl/md-scale-fd1duy: exit status 2
STEP: Dumping all the Cluster API resources in the "md-scale-wvuhnl" namespace
STEP: Deleting cluster md-scale-wvuhnl/md-scale-fd1duy
STEP: Deleting cluster md-scale-fd1duy
INFO: Waiting for the Cluster md-scale-wvuhnl/md-scale-fd1duy to be deleted
STEP: Waiting for cluster md-scale-fd1duy to be deleted
STEP: Deleting namespace used for hosting the "md-scale" test spec
... skipping 38 lines ...
STEP: Waiting for the control plane to be ready
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-8fv3lx" workload cluster
Failed to get logs for machine quick-start-8fv3lx-md-0-bp6dg-587c898b78-gqzbq, cluster quick-start-kquute/quick-start-8fv3lx: exit status 2
Failed to get logs for machine quick-start-8fv3lx-nl8gh-mjjz9, cluster quick-start-kquute/quick-start-8fv3lx: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-kquute" namespace
STEP: Deleting cluster quick-start-kquute/quick-start-8fv3lx
STEP: Deleting cluster quick-start-8fv3lx
INFO: Waiting for the Cluster quick-start-kquute/quick-start-8fv3lx to be deleted
STEP: Waiting for cluster quick-start-8fv3lx to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 70 lines ...
STEP: Ensure API servers are stable before doing move
STEP: Moving the cluster back to bootstrap
STEP: Moving workload clusters
INFO: Waiting for the cluster to be reconciled after moving back to booststrap
STEP: Waiting for cluster to enter the provisioned phase
STEP: Dumping logs from the "self-hosted-gfykix" workload cluster
Failed to get logs for machine self-hosted-gfykix-control-plane-dnzqq, cluster self-hosted-x4f6q3/self-hosted-gfykix: exit status 2
Failed to get logs for machine self-hosted-gfykix-md-0-66b4497c5-8dx4m, cluster self-hosted-x4f6q3/self-hosted-gfykix: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-x4f6q3" namespace
STEP: Deleting cluster self-hosted-x4f6q3/self-hosted-gfykix
STEP: Deleting cluster self-hosted-gfykix
INFO: Waiting for the Cluster self-hosted-x4f6q3/self-hosted-gfykix to be deleted
STEP: Waiting for cluster self-hosted-gfykix to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" test spec
... skipping 38 lines ...
STEP: Waiting for the control plane to be ready
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-wdb2wn" workload cluster
Failed to get logs for machine quick-start-wdb2wn-control-plane-l8jj2, cluster quick-start-594rnb/quick-start-wdb2wn: exit status 2
Failed to get logs for machine quick-start-wdb2wn-md-0-6cd8bd54d9-st8zw, cluster quick-start-594rnb/quick-start-wdb2wn: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-594rnb" namespace
STEP: Deleting cluster quick-start-594rnb/quick-start-wdb2wn
STEP: Deleting cluster quick-start-wdb2wn
INFO: Waiting for the Cluster quick-start-594rnb/quick-start-wdb2wn to be deleted
STEP: Waiting for cluster quick-start-wdb2wn to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 48 lines ...
INFO: Waiting for MachineDeployment rollout for MachineDeploymentTopology "md-0" (class "default-worker") to complete.
STEP: Rebasing the Cluster to a ClusterClass with a modified label for MachineDeployments and wait for changes to be applied to the MachineDeployment objects
INFO: Waiting for MachineDeployment rollout to complete.
INFO: Waiting for MachineDeployment rollout for MachineDeploymentTopology "md-0" (class "default-worker") to complete.
STEP: PASSED!
STEP: Dumping logs from the "clusterclass-changes-4xdpky" workload cluster
Failed to get logs for machine clusterclass-changes-4xdpky-md-0-9h47l-57c78df885-mbt6s, cluster clusterclass-changes-mb8x7w/clusterclass-changes-4xdpky: exit status 2
Failed to get logs for machine clusterclass-changes-4xdpky-md-0-9h47l-76cc94b495-q4vcq, cluster clusterclass-changes-mb8x7w/clusterclass-changes-4xdpky: exit status 2
Failed to get logs for machine clusterclass-changes-4xdpky-rr2wr-2cctm, cluster clusterclass-changes-mb8x7w/clusterclass-changes-4xdpky: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterclass-changes-mb8x7w" namespace
STEP: Deleting cluster clusterclass-changes-mb8x7w/clusterclass-changes-4xdpky
STEP: Deleting cluster clusterclass-changes-4xdpky
INFO: Waiting for the Cluster clusterclass-changes-mb8x7w/clusterclass-changes-4xdpky to be deleted
STEP: Waiting for cluster clusterclass-changes-4xdpky to be deleted
STEP: Deleting namespace used for hosting the "clusterclass-changes" test spec
... skipping 52 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-6vkhzw/k8s-upgrade-and-conformance-x2a261-md-0-dldzw to be upgraded to v1.24.0
INFO: Ensuring all MachineDeployment Machines have upgraded kubernetes version v1.24.0
STEP: Waiting until nodes are ready
STEP: PASSED!
STEP: Dumping logs from the "k8s-upgrade-and-conformance-x2a261" workload cluster
Failed to get logs for machine k8s-upgrade-and-conformance-x2a261-md-0-dldzw-569b6f474b-rhrnw, cluster k8s-upgrade-and-conformance-6vkhzw/k8s-upgrade-and-conformance-x2a261: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-x2a261-zmxtj-4jbnr, cluster k8s-upgrade-and-conformance-6vkhzw/k8s-upgrade-and-conformance-x2a261: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-x2a261-zmxtj-knznj, cluster k8s-upgrade-and-conformance-6vkhzw/k8s-upgrade-and-conformance-x2a261: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-x2a261-zmxtj-sdkkn, cluster k8s-upgrade-and-conformance-6vkhzw/k8s-upgrade-and-conformance-x2a261: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-6vkhzw" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-6vkhzw/k8s-upgrade-and-conformance-x2a261
STEP: Deleting cluster k8s-upgrade-and-conformance-x2a261
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-6vkhzw/k8s-upgrade-and-conformance-x2a261 to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-x2a261 to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 4 lines ...
When upgrading a workload cluster using ClusterClass with a HA control plane using scale-in rollout
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_test.go:101
  Should create and upgrade a workload cluster and run kubetest
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade.go:115
------------------------------
STEP: Dumping logs from the bootstrap cluster
Failed to get logs for the bootstrap cluster node test-i31dfd-control-plane: exit status 2
STEP: Tearing down the management cluster


Ran 17 of 20 Specs in 2804.823 seconds
SUCCESS! -- 17 Passed | 0 Failed | 0 Pending | 3 Skipped


Ginkgo ran 1 suite in 48m5.619708888s
Test Suite Passed
make: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e'
+ cleanup
... skipping 25 lines ...