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

No Test Failures!


Show 17 Passed Tests

Show 3 Skipped Tests

Error lines from build-log.txt

... skipping 932 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-96z63o" workload cluster
Failed to get logs for machine quick-start-96z63o-control-plane-t5k29, cluster quick-start-yepevd/quick-start-96z63o: exit status 2
Failed to get logs for machine quick-start-96z63o-md-0-664f89657d-mmk9z, cluster quick-start-yepevd/quick-start-96z63o: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-yepevd" namespace
STEP: Deleting cluster quick-start-yepevd/quick-start-96z63o
STEP: Deleting cluster quick-start-96z63o
INFO: Waiting for the Cluster quick-start-yepevd/quick-start-96z63o to be deleted
STEP: Waiting for cluster quick-start-96z63o to be deleted
STEP: Deleting namespace used for hosting the "quick-start" 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-wk0qj1" workload cluster
Failed to get logs for machine quick-start-wk0qj1-gks2g-ntr5d, cluster quick-start-hx79ka/quick-start-wk0qj1: exit status 2
Failed to get logs for machine quick-start-wk0qj1-md-0-mzsl2-8547d46f48-kgfgl, cluster quick-start-hx79ka/quick-start-wk0qj1: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-hx79ka" namespace
STEP: Deleting cluster quick-start-hx79ka/quick-start-wk0qj1
STEP: Deleting cluster quick-start-wk0qj1
INFO: Waiting for the Cluster quick-start-hx79ka/quick-start-wk0qj1 to be deleted
STEP: Waiting for cluster quick-start-wk0qj1 to be deleted
STEP: Deleting namespace used for hosting the "quick-start" 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-lpqkuc" workload cluster
Failed to get logs for machine mhc-remediation-lpqkuc-control-plane-st8m5, cluster mhc-remediation-rz3h4w/mhc-remediation-lpqkuc: exit status 2
Failed to get logs for machine mhc-remediation-lpqkuc-md-0-859c4b4968-4f57f, cluster mhc-remediation-rz3h4w/mhc-remediation-lpqkuc: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-rz3h4w" namespace
STEP: Deleting cluster mhc-remediation-rz3h4w/mhc-remediation-lpqkuc
STEP: Deleting cluster mhc-remediation-lpqkuc
INFO: Waiting for the Cluster mhc-remediation-rz3h4w/mhc-remediation-lpqkuc to be deleted
STEP: Waiting for cluster mhc-remediation-lpqkuc 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-cj0gtu" workload cluster
Failed to get logs for machine mhc-remediation-cj0gtu-control-plane-hpkl5, cluster mhc-remediation-4bptdy/mhc-remediation-cj0gtu: exit status 2
Failed to get logs for machine mhc-remediation-cj0gtu-control-plane-vnnsv, cluster mhc-remediation-4bptdy/mhc-remediation-cj0gtu: exit status 2
Failed to get logs for machine mhc-remediation-cj0gtu-control-plane-xv4tz, cluster mhc-remediation-4bptdy/mhc-remediation-cj0gtu: exit status 2
Failed to get logs for machine mhc-remediation-cj0gtu-md-0-5595dcdf4d-2rwg7, cluster mhc-remediation-4bptdy/mhc-remediation-cj0gtu: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-4bptdy" namespace
STEP: Deleting cluster mhc-remediation-4bptdy/mhc-remediation-cj0gtu
STEP: Deleting cluster mhc-remediation-cj0gtu
INFO: Waiting for the Cluster mhc-remediation-4bptdy/mhc-remediation-cj0gtu to be deleted
STEP: Waiting for cluster mhc-remediation-cj0gtu to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" 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-ridchu" workload cluster
Failed to get logs for machine clusterclass-changes-ridchu-hhl5s-tgp8f, cluster clusterclass-changes-bcr1g3/clusterclass-changes-ridchu: exit status 2
Failed to get logs for machine clusterclass-changes-ridchu-md-0-bdnvx-97646c78f-lmjxz, cluster clusterclass-changes-bcr1g3/clusterclass-changes-ridchu: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterclass-changes-bcr1g3" namespace
STEP: Deleting cluster clusterclass-changes-bcr1g3/clusterclass-changes-ridchu
STEP: Deleting cluster clusterclass-changes-ridchu
INFO: Waiting for the Cluster clusterclass-changes-bcr1g3/clusterclass-changes-ridchu to be deleted
STEP: Waiting for cluster clusterclass-changes-ridchu to be deleted
STEP: Deleting namespace used for hosting the "clusterclass-changes" 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-iouopb" workload cluster
Failed to get logs for machine kcp-adoption-iouopb-control-plane-0, cluster kcp-adoption-zizakn/kcp-adoption-iouopb: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-adoption-zizakn" namespace
STEP: Deleting cluster kcp-adoption-zizakn/kcp-adoption-iouopb
STEP: Deleting cluster kcp-adoption-iouopb
INFO: Waiting for the Cluster kcp-adoption-zizakn/kcp-adoption-iouopb to be deleted
STEP: Waiting for cluster kcp-adoption-iouopb to be deleted
STEP: Deleting namespace used for hosting the "kcp-adoption" 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-637r2u/k8s-upgrade-and-conformance-awq1as-md-0-6zltd 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-awq1as" workload cluster
Failed to get logs for machine k8s-upgrade-and-conformance-awq1as-l7qzb-8tf75, cluster k8s-upgrade-and-conformance-637r2u/k8s-upgrade-and-conformance-awq1as: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-awq1as-l7qzb-qvq6j, cluster k8s-upgrade-and-conformance-637r2u/k8s-upgrade-and-conformance-awq1as: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-awq1as-l7qzb-wn9q2, cluster k8s-upgrade-and-conformance-637r2u/k8s-upgrade-and-conformance-awq1as: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-awq1as-md-0-6zltd-574496765d-dvkcl, cluster k8s-upgrade-and-conformance-637r2u/k8s-upgrade-and-conformance-awq1as: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-637r2u" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-637r2u/k8s-upgrade-and-conformance-awq1as
STEP: Deleting cluster k8s-upgrade-and-conformance-awq1as
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-637r2u/k8s-upgrade-and-conformance-awq1as to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-awq1as to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 54 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-upp2o8/k8s-upgrade-and-conformance-8hqbpt-md-0-q5drh 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-8hqbpt" workload cluster
Failed to get logs for machine k8s-upgrade-and-conformance-8hqbpt-9bwhp-48q9g, cluster k8s-upgrade-and-conformance-upp2o8/k8s-upgrade-and-conformance-8hqbpt: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-8hqbpt-9bwhp-9kzkr, cluster k8s-upgrade-and-conformance-upp2o8/k8s-upgrade-and-conformance-8hqbpt: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-8hqbpt-9bwhp-vzfmd, cluster k8s-upgrade-and-conformance-upp2o8/k8s-upgrade-and-conformance-8hqbpt: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-8hqbpt-md-0-q5drh-657dd49bfb-s8wjq, cluster k8s-upgrade-and-conformance-upp2o8/k8s-upgrade-and-conformance-8hqbpt: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-upp2o8" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-upp2o8/k8s-upgrade-and-conformance-8hqbpt
STEP: Deleting cluster k8s-upgrade-and-conformance-8hqbpt
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-upp2o8/k8s-upgrade-and-conformance-8hqbpt to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-8hqbpt to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 47 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-avarv0/machine-pool-pydlth-mp-0
STEP: Waiting for the machine pool workload nodes
STEP: PASSED!
STEP: Dumping logs from the "machine-pool-pydlth" workload cluster
Failed to get logs for machine machine-pool-pydlth-control-plane-nfspg, cluster machine-pool-avarv0/machine-pool-pydlth: exit status 2
STEP: Dumping all the Cluster API resources in the "machine-pool-avarv0" namespace
STEP: Deleting cluster machine-pool-avarv0/machine-pool-pydlth
STEP: Deleting cluster machine-pool-pydlth
INFO: Waiting for the Cluster machine-pool-avarv0/machine-pool-pydlth to be deleted
STEP: Waiting for cluster machine-pool-pydlth to be deleted
STEP: Deleting namespace used for hosting the "machine-pool" 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-b63u6f" workload cluster
Failed to get logs for machine self-hosted-b63u6f-control-plane-vv4qr, cluster self-hosted-u2jgox/self-hosted-b63u6f: exit status 2
Failed to get logs for machine self-hosted-b63u6f-md-0-7ddf5c5959-gvzxx, cluster self-hosted-u2jgox/self-hosted-b63u6f: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-u2jgox" namespace
STEP: Deleting cluster self-hosted-u2jgox/self-hosted-b63u6f
STEP: Deleting cluster self-hosted-b63u6f
INFO: Waiting for the Cluster self-hosted-u2jgox/self-hosted-b63u6f to be deleted
STEP: Waiting for cluster self-hosted-b63u6f to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" 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-qoyibr" workload cluster
Failed to get logs for machine self-hosted-qoyibr-md-0-nvn4g-5696b45b7c-9sflk, cluster self-hosted-elfitw/self-hosted-qoyibr: exit status 2
Failed to get logs for machine self-hosted-qoyibr-wdrtq-fw2tv, cluster self-hosted-elfitw/self-hosted-qoyibr: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-elfitw" namespace
STEP: Deleting cluster self-hosted-elfitw/self-hosted-qoyibr
STEP: Deleting cluster self-hosted-qoyibr
INFO: Waiting for the Cluster self-hosted-elfitw/self-hosted-qoyibr to be deleted
STEP: Waiting for cluster self-hosted-qoyibr to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" 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-5offef" workload cluster
Failed to get logs for machine md-rollout-5offef-control-plane-7n8l8, cluster md-rollout-hhs1fz/md-rollout-5offef: exit status 2
Failed to get logs for machine md-rollout-5offef-md-0-86c6754b98-jn2hr, cluster md-rollout-hhs1fz/md-rollout-5offef: exit status 2
STEP: Dumping all the Cluster API resources in the "md-rollout-hhs1fz" namespace
STEP: Deleting cluster md-rollout-hhs1fz/md-rollout-5offef
STEP: Deleting cluster md-rollout-5offef
INFO: Waiting for the Cluster md-rollout-hhs1fz/md-rollout-5offef to be deleted
STEP: Waiting for cluster md-rollout-5offef to be deleted
STEP: Deleting namespace used for hosting the "md-rollout" test spec
... skipping 46 lines ...
INFO: Waiting for correct number of replicas to exist
STEP: Scaling the MachineDeployment down to 1
INFO: Scaling machine deployment md-scale-kluhvu/md-scale-1mc8t9-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-1mc8t9" workload cluster
Failed to get logs for machine md-scale-1mc8t9-control-plane-r8jnt, cluster md-scale-kluhvu/md-scale-1mc8t9: exit status 2
Failed to get logs for machine md-scale-1mc8t9-md-0-64dc589b55-rkcz6, cluster md-scale-kluhvu/md-scale-1mc8t9: exit status 2
STEP: Dumping all the Cluster API resources in the "md-scale-kluhvu" namespace
STEP: Deleting cluster md-scale-kluhvu/md-scale-1mc8t9
STEP: Deleting cluster md-scale-1mc8t9
INFO: Waiting for the Cluster md-scale-kluhvu/md-scale-1mc8t9 to be deleted
STEP: Waiting for cluster md-scale-1mc8t9 to be deleted
STEP: Deleting namespace used for hosting the "md-scale" test spec
... skipping 52 lines ...
STEP: Waiting for deployment node-drain-bmbjnd-unevictable-workload/unevictable-pod-km7 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-bmbjnd/node-drain-ktda0g-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-ktda0g" workload cluster
Failed to get logs for machine node-drain-ktda0g-control-plane-r5l45, cluster node-drain-bmbjnd/node-drain-ktda0g: exit status 2
STEP: Dumping all the Cluster API resources in the "node-drain-bmbjnd" namespace
STEP: Deleting cluster node-drain-bmbjnd/node-drain-ktda0g
STEP: Deleting cluster node-drain-ktda0g
INFO: Waiting for the Cluster node-drain-bmbjnd/node-drain-ktda0g to be deleted
STEP: Waiting for cluster node-drain-ktda0g to be deleted
STEP: Deleting namespace used for hosting the "node-drain" 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-pjo23d" workload cluster
Failed to get logs for machine quick-start-pjo23d-control-plane-xstfx, cluster quick-start-3cdku6/quick-start-pjo23d: exit status 2
Failed to get logs for machine quick-start-pjo23d-md-0-68454f775f-2sp8r, cluster quick-start-3cdku6/quick-start-pjo23d: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-3cdku6" namespace
STEP: Deleting cluster quick-start-3cdku6/quick-start-pjo23d
STEP: Deleting cluster quick-start-pjo23d
INFO: Waiting for the Cluster quick-start-3cdku6/quick-start-pjo23d to be deleted
STEP: Waiting for cluster quick-start-pjo23d to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 50 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-ndxp2a/k8s-upgrade-and-conformance-2qrqoj-md-0-nknwl 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-2qrqoj" workload cluster
Failed to get logs for machine k8s-upgrade-and-conformance-2qrqoj-2jgv5-h4qgr, cluster k8s-upgrade-and-conformance-ndxp2a/k8s-upgrade-and-conformance-2qrqoj: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-2qrqoj-md-0-nknwl-d88466875-2v85v, cluster k8s-upgrade-and-conformance-ndxp2a/k8s-upgrade-and-conformance-2qrqoj: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-2qrqoj-md-0-nknwl-d88466875-82lcb, cluster k8s-upgrade-and-conformance-ndxp2a/k8s-upgrade-and-conformance-2qrqoj: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-ndxp2a" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-ndxp2a/k8s-upgrade-and-conformance-2qrqoj
STEP: Deleting cluster k8s-upgrade-and-conformance-2qrqoj
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-ndxp2a/k8s-upgrade-and-conformance-2qrqoj to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-2qrqoj to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" test spec
... skipping 104 lines ...
STEP: Deleting cluster clusterctl-upgrade/clusterctl-upgrade-xxhsbm
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-xxhsbm" workload cluster
Failed to get logs for machine clusterctl-upgrade-xxhsbm-control-plane-7p7bg, cluster clusterctl-upgrade-rleg4t/clusterctl-upgrade-xxhsbm: exit status 2
Failed to get logs for machine clusterctl-upgrade-xxhsbm-md-0-56f87677cc-md57f, cluster clusterctl-upgrade-rleg4t/clusterctl-upgrade-xxhsbm: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterctl-upgrade-rleg4t" namespace
STEP: Deleting cluster clusterctl-upgrade-rleg4t/clusterctl-upgrade-xxhsbm
STEP: Deleting cluster clusterctl-upgrade-xxhsbm
INFO: Waiting for the Cluster clusterctl-upgrade-rleg4t/clusterctl-upgrade-xxhsbm to be deleted
STEP: Waiting for cluster clusterctl-upgrade-xxhsbm to be deleted
STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
... skipping 4 lines ...
When testing clusterctl upgrades [clusterctl-Upgrade]
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterctl_upgrade_test.go:26
  Should create a management cluster and then upgrade all the providers
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterctl_upgrade.go:147
------------------------------
STEP: Dumping logs from the bootstrap cluster
Failed to get logs for the bootstrap cluster node test-dtihq5-control-plane: exit status 2
STEP: Tearing down the management cluster


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


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