This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultsuccess
Tests 0 failed / 13 succeeded
Started2022-09-08 03:18
Elapsed37m58s
Revision
uploadercrier

No Test Failures!


Show 13 Passed Tests

Show 2 Skipped Tests

Error lines from build-log.txt

... skipping 844 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-3h9xoh" workload cluster
Failed to get logs for machine kcp-adoption-3h9xoh-control-plane-0, cluster kcp-adoption-t9t1o9/kcp-adoption-3h9xoh: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-adoption-t9t1o9" namespace
STEP: Deleting cluster kcp-adoption-t9t1o9/kcp-adoption-3h9xoh
STEP: Deleting cluster kcp-adoption-3h9xoh
INFO: Waiting for the Cluster kcp-adoption-t9t1o9/kcp-adoption-3h9xoh to be deleted
STEP: Waiting for cluster kcp-adoption-3h9xoh to be deleted
STEP: Deleting namespace used for hosting the "kcp-adoption" 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-ky69hx" workload cluster
Failed to get logs for machine md-rollout-ky69hx-control-plane-jd8sr, cluster md-rollout-o9ia83/md-rollout-ky69hx: exit status 2
Failed to get logs for machine md-rollout-ky69hx-md-0-6788789495-8n5zd, cluster md-rollout-o9ia83/md-rollout-ky69hx: error creating container exec: Error response from daemon: No such container: md-rollout-ky69hx-md-0-6788789495-8n5zd
Failed to get logs for machine md-rollout-ky69hx-md-0-6f98cc968c-k9bvf, cluster md-rollout-o9ia83/md-rollout-ky69hx: exit status 2
STEP: Dumping all the Cluster API resources in the "md-rollout-o9ia83" namespace
STEP: Deleting cluster md-rollout-o9ia83/md-rollout-ky69hx
STEP: Deleting cluster md-rollout-ky69hx
INFO: Waiting for the Cluster md-rollout-o9ia83/md-rollout-ky69hx to be deleted
STEP: Waiting for cluster md-rollout-ky69hx to be deleted
STEP: Deleting namespace used for hosting the "md-rollout" test spec
... skipping 46 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-yv92qs" workload cluster
Failed to get logs for machine mhc-remediation-yv92qs-control-plane-xwh58, cluster mhc-remediation-kxjp98/mhc-remediation-yv92qs: exit status 2
Failed to get logs for machine mhc-remediation-yv92qs-md-0-85589bfd46-kn9ss, cluster mhc-remediation-kxjp98/mhc-remediation-yv92qs: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-kxjp98" namespace
STEP: Deleting cluster mhc-remediation-kxjp98/mhc-remediation-yv92qs
STEP: Deleting cluster mhc-remediation-yv92qs
INFO: Waiting for the Cluster mhc-remediation-kxjp98/mhc-remediation-yv92qs to be deleted
STEP: Waiting for cluster mhc-remediation-yv92qs to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
... skipping 47 lines ...
STEP: Ensuring kube-proxy has the correct image
INFO: Waiting for CoreDNS to have the upgraded image tag
STEP: Ensuring CoreDNS has the correct image
INFO: Waiting for etcd to have the upgraded image tag
STEP: PASSED!
STEP: Dumping logs from the "kcp-upgrade-1r90gr" workload cluster
Failed to get logs for machine kcp-upgrade-1r90gr-control-plane-sbrr8, cluster kcp-upgrade-hw3fr3/kcp-upgrade-1r90gr: exit status 2
Failed to get logs for machine kcp-upgrade-1r90gr-md-0-85b5745c8-tx7rt, cluster kcp-upgrade-hw3fr3/kcp-upgrade-1r90gr: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-upgrade-hw3fr3" namespace
STEP: Deleting cluster kcp-upgrade-hw3fr3/kcp-upgrade-1r90gr
STEP: Deleting cluster kcp-upgrade-1r90gr
INFO: Waiting for the Cluster kcp-upgrade-hw3fr3/kcp-upgrade-1r90gr to be deleted
STEP: Waiting for cluster kcp-upgrade-1r90gr to be deleted
STEP: Deleting namespace used for hosting the "kcp-upgrade" test spec
... skipping 52 lines ...
STEP: Waiting for deployment node-drain-y17kbk-unevictable-workload/unevictable-pod-9g7 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-y17kbk/node-drain-8r2rqa-control-plane from 0xc001534890 to 1 replicas
INFO: Waiting for correct number of replicas to exist
STEP: PASSED!
STEP: Dumping logs from the "node-drain-8r2rqa" workload cluster
Failed to get logs for machine node-drain-8r2rqa-control-plane-dn22j, cluster node-drain-y17kbk/node-drain-8r2rqa: exit status 2
STEP: Dumping all the Cluster API resources in the "node-drain-y17kbk" namespace
STEP: Deleting cluster node-drain-y17kbk/node-drain-8r2rqa
STEP: Deleting cluster node-drain-8r2rqa
INFO: Waiting for the Cluster node-drain-y17kbk/node-drain-8r2rqa to be deleted
STEP: Waiting for cluster node-drain-8r2rqa to be deleted
STEP: Deleting namespace used for hosting the "node-drain" 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-ngn2gf/md-scale-mxoo7f-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-mxoo7f" workload cluster
Failed to get logs for machine md-scale-mxoo7f-control-plane-s62pf, cluster md-scale-ngn2gf/md-scale-mxoo7f: exit status 2
Failed to get logs for machine md-scale-mxoo7f-md-0-56b49d745-2897n, cluster md-scale-ngn2gf/md-scale-mxoo7f: exit status 2
STEP: Dumping all the Cluster API resources in the "md-scale-ngn2gf" namespace
STEP: Deleting cluster md-scale-ngn2gf/md-scale-mxoo7f
STEP: Deleting cluster md-scale-mxoo7f
INFO: Waiting for the Cluster md-scale-ngn2gf/md-scale-mxoo7f to be deleted
STEP: Waiting for cluster md-scale-mxoo7f to be deleted
STEP: Deleting namespace used for hosting the "md-scale" 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-dexy1e" workload cluster
Failed to get logs for machine mhc-remediation-dexy1e-control-plane-fs9vx, cluster mhc-remediation-amds2b/mhc-remediation-dexy1e: exited with status: 1, &{%!s(*os.file=&{{{0 0 0} 7 {0} <nil> 0 1 true true true} /tmp/mhc-remediation-dexy1e-control-plane-fs9vx611563185 <nil> false false false})}
Failed to get logs for machine mhc-remediation-dexy1e-control-plane-px7b4, cluster mhc-remediation-amds2b/mhc-remediation-dexy1e: exited with status: 1, &{%!s(*os.file=&{{{0 0 0} 35 {0} <nil> 0 1 true true true} /tmp/mhc-remediation-dexy1e-control-plane-px7b43158570994 <nil> false false false})}
Failed to get logs for machine mhc-remediation-dexy1e-control-plane-xrdnc, cluster mhc-remediation-amds2b/mhc-remediation-dexy1e: exit status 2
Failed to get logs for machine mhc-remediation-dexy1e-md-0-6567644d9f-rfshr, cluster mhc-remediation-amds2b/mhc-remediation-dexy1e: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-amds2b" namespace
STEP: Deleting cluster mhc-remediation-amds2b/mhc-remediation-dexy1e
STEP: Deleting cluster mhc-remediation-dexy1e
INFO: Waiting for the Cluster mhc-remediation-amds2b/mhc-remediation-dexy1e to be deleted
STEP: Waiting for cluster mhc-remediation-dexy1e to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
... skipping 44 lines ...
STEP: Waiting for the machine pool workload nodes to exist
STEP: Scaling the machine pool down
INFO: Patching the replica count in Machine Pool machine-pool-tluof3/machine-pool-zzo8ku-mp-0
STEP: Waiting for the machine pool workload nodes to exist
STEP: PASSED!
STEP: Dumping logs from the "machine-pool-zzo8ku" workload cluster
Failed to get logs for machine machine-pool-zzo8ku-control-plane-h7h29, cluster machine-pool-tluof3/machine-pool-zzo8ku: exit status 2
Failed to get logs for machine pool machine-pool-zzo8ku-mp-0, cluster machine-pool-tluof3/machine-pool-zzo8ku: exit status 2
STEP: Dumping all the Cluster API resources in the "machine-pool-tluof3" namespace
STEP: Deleting cluster machine-pool-tluof3/machine-pool-zzo8ku
STEP: Deleting cluster machine-pool-zzo8ku
INFO: Waiting for the Cluster machine-pool-tluof3/machine-pool-zzo8ku to be deleted
STEP: Waiting for cluster machine-pool-zzo8ku to be deleted
STEP: Deleting namespace used for hosting the "machine-pool" 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-ilj7xt" workload cluster
Failed to get logs for machine quick-start-ilj7xt-control-plane-n9fg4, cluster quick-start-54qkya/quick-start-ilj7xt: exit status 2
Failed to get logs for machine quick-start-ilj7xt-md-0-964cc9d7-mxphm, cluster quick-start-54qkya/quick-start-ilj7xt: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-54qkya" namespace
STEP: Deleting cluster quick-start-54qkya/quick-start-ilj7xt
STEP: Deleting cluster quick-start-ilj7xt
INFO: Waiting for the Cluster quick-start-54qkya/quick-start-ilj7xt to be deleted
STEP: Waiting for cluster quick-start-ilj7xt 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-c0pddb" workload cluster
Failed to get logs for machine self-hosted-c0pddb-control-plane-2bcfx, cluster self-hosted-ho98mm/self-hosted-c0pddb: exit status 2
Failed to get logs for machine self-hosted-c0pddb-md-0-859bf7875b-thfpq, cluster self-hosted-ho98mm/self-hosted-c0pddb: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-ho98mm" namespace
STEP: Deleting cluster self-hosted-ho98mm/self-hosted-c0pddb
STEP: Deleting cluster self-hosted-c0pddb
INFO: Waiting for the Cluster self-hosted-ho98mm/self-hosted-c0pddb to be deleted
STEP: Waiting for cluster self-hosted-c0pddb to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" test spec
... skipping 49 lines ...
STEP: Ensuring kube-proxy has the correct image
INFO: Waiting for CoreDNS to have the upgraded image tag
STEP: Ensuring CoreDNS has the correct image
INFO: Waiting for etcd to have the upgraded image tag
STEP: PASSED!
STEP: Dumping logs from the "kcp-upgrade-qylyqb" workload cluster
Failed to get logs for machine kcp-upgrade-qylyqb-control-plane-4c8xq, cluster kcp-upgrade-wgpw9l/kcp-upgrade-qylyqb: exit status 2
Failed to get logs for machine kcp-upgrade-qylyqb-control-plane-mf6zc, cluster kcp-upgrade-wgpw9l/kcp-upgrade-qylyqb: exit status 2
Failed to get logs for machine kcp-upgrade-qylyqb-control-plane-r8vbl, cluster kcp-upgrade-wgpw9l/kcp-upgrade-qylyqb: exit status 2
Failed to get logs for machine kcp-upgrade-qylyqb-md-0-66795f9967-mpjlj, cluster kcp-upgrade-wgpw9l/kcp-upgrade-qylyqb: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-upgrade-wgpw9l" namespace
STEP: Deleting cluster kcp-upgrade-wgpw9l/kcp-upgrade-qylyqb
STEP: Deleting cluster kcp-upgrade-qylyqb
INFO: Waiting for the Cluster kcp-upgrade-wgpw9l/kcp-upgrade-qylyqb to be deleted
STEP: Waiting for cluster kcp-upgrade-qylyqb to be deleted
STEP: Deleting namespace used for hosting the "kcp-upgrade" test spec
... skipping 101 lines ...
INFO: Waiting for the Cluster clusterctl-upgrade/clusterctl-upgrade-i740ib to be deleted
STEP: Waiting for cluster clusterctl-upgrade-i740ib to be deleted
STEP: Deleting cluster clusterctl-upgrade and clusterctl-upgrade-ju7g7v
STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test
INFO: Deleting namespace clusterctl-upgrade
STEP: Dumping logs from the "clusterctl-upgrade-ju7g7v" workload cluster
Failed to get logs for machine clusterctl-upgrade-ju7g7v-control-plane-ps75j, cluster clusterctl-upgrade-lm1tkq/clusterctl-upgrade-ju7g7v: exit status 2
Failed to get logs for machine clusterctl-upgrade-ju7g7v-md-0-7d85b6bd9c-w2cm5, cluster clusterctl-upgrade-lm1tkq/clusterctl-upgrade-ju7g7v: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterctl-upgrade-lm1tkq" namespace
STEP: Deleting cluster clusterctl-upgrade-lm1tkq/clusterctl-upgrade-ju7g7v
STEP: Deleting cluster clusterctl-upgrade-ju7g7v
INFO: Waiting for the Cluster clusterctl-upgrade-lm1tkq/clusterctl-upgrade-ju7g7v to be deleted
STEP: Waiting for cluster clusterctl-upgrade-ju7g7v to be deleted
STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
... skipping 49 lines ...
STEP: Ensuring kube-proxy has the correct image
INFO: Waiting for CoreDNS to have the upgraded image tag
STEP: Ensuring CoreDNS has the correct image
INFO: Waiting for etcd to have the upgraded image tag
STEP: PASSED!
STEP: Dumping logs from the "kcp-upgrade-dxbsyw" workload cluster
Failed to get logs for machine kcp-upgrade-dxbsyw-control-plane-t6nnc, cluster kcp-upgrade-nnf6bp/kcp-upgrade-dxbsyw: exit status 2
Failed to get logs for machine kcp-upgrade-dxbsyw-control-plane-vp8zr, cluster kcp-upgrade-nnf6bp/kcp-upgrade-dxbsyw: exit status 2
Failed to get logs for machine kcp-upgrade-dxbsyw-control-plane-zzwps, cluster kcp-upgrade-nnf6bp/kcp-upgrade-dxbsyw: exit status 2
Failed to get logs for machine kcp-upgrade-dxbsyw-md-0-6777d577f8-rl2zv, cluster kcp-upgrade-nnf6bp/kcp-upgrade-dxbsyw: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-upgrade-nnf6bp" namespace
STEP: Deleting cluster kcp-upgrade-nnf6bp/kcp-upgrade-dxbsyw
STEP: Deleting cluster kcp-upgrade-dxbsyw
INFO: Waiting for the Cluster kcp-upgrade-nnf6bp/kcp-upgrade-dxbsyw to be deleted
STEP: Waiting for cluster kcp-upgrade-dxbsyw to be deleted
STEP: Deleting namespace used for hosting the "kcp-upgrade" test spec
... skipping 4 lines ...
When testing KCP upgrade in a HA cluster using scale in rollout
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/kcp_upgrade_test.go:55
  Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/kcp_upgrade.go:75
------------------------------
STEP: Dumping logs from the bootstrap cluster
Failed to get logs for the bootstrap cluster node test-ojkuim-control-plane: exit status 2
STEP: Tearing down the management cluster


Ran 13 of 15 Specs in 1910.708 seconds
SUCCESS! -- 13 Passed | 0 Failed | 0 Pending | 2 Skipped


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