This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 3 succeeded
Started2022-09-16 13:16
Elapsed33m15s
Revisionrelease-1.1

Test Failures


capi-e2e When testing Cluster API working on self-hosted clusters using ClusterClass Should pivot the bootstrap cluster to a self-hosted cluster 10m23s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capi\-e2e\sWhen\stesting\sCluster\sAPI\sworking\son\sself\-hosted\sclusters\susing\sClusterClass\sShould\spivot\sthe\sbootstrap\scluster\sto\sa\sself\-hosted\scluster$'
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/self_hosted.go:80
Timed out after 600.000s.
Expected
    <bool>: false
to be true
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/controlplane_helpers.go:151
				
				Click to see stdout/stderrfrom junit.e2e_suite.2.xml

Filter through log files | View test history on testgrid


Show 3 Passed Tests

Show 16 Skipped Tests

Error lines from build-log.txt

... skipping 927 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-nkexgr" workload cluster
Failed to get logs for machine quick-start-nkexgr-control-plane-k7w8z, cluster quick-start-5ui5p5/quick-start-nkexgr: exit status 2
Failed to get logs for machine quick-start-nkexgr-md-0-55ff85c6-cf7wp, cluster quick-start-5ui5p5/quick-start-nkexgr: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-5ui5p5" namespace
STEP: Deleting cluster quick-start-5ui5p5/quick-start-nkexgr
STEP: Deleting cluster quick-start-nkexgr
INFO: Waiting for the Cluster quick-start-5ui5p5/quick-start-nkexgr to be deleted
STEP: Waiting for cluster quick-start-nkexgr to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 33 lines ...
INFO: Waiting for the cluster infrastructure to be provisioned
STEP: Waiting for cluster to enter the provisioned phase
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by self-hosted-7928ry/self-hosted-cqucwc-tl6ph to be provisioned
STEP: Waiting for one control plane node to exist
STEP: Dumping logs from the "self-hosted-cqucwc" workload cluster
Failed to get logs for machine self-hosted-cqucwc-md-0-rhcjq-d9d9ff586-6nqgp, cluster self-hosted-7928ry/self-hosted-cqucwc: error creating container exec: Error response from daemon: No such container: self-hosted-cqucwc-md-0-rhcjq-d9d9ff586-6nqgp
Failed to get logs for machine self-hosted-cqucwc-tl6ph-h2kt4, cluster self-hosted-7928ry/self-hosted-cqucwc: error creating container exec: Error response from daemon: Container 916684d439a6fbc6c2ec51e176c50b852bc7b06139c01e1af1ea0f7d45987554 is not running
STEP: Dumping all the Cluster API resources in the "self-hosted-7928ry" namespace
STEP: Deleting cluster self-hosted-7928ry/self-hosted-cqucwc
STEP: Deleting cluster self-hosted-cqucwc
INFO: Waiting for the Cluster self-hosted-7928ry/self-hosted-cqucwc to be deleted
STEP: Waiting for cluster self-hosted-cqucwc to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" test spec
... skipping 101 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-pj37kt/k8s-upgrade-and-conformance-g63m2g-md-0-wfpb2 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-g63m2g" workload cluster
Failed to get logs for machine k8s-upgrade-and-conformance-g63m2g-md-0-wfpb2-847d5b767f-q2nkq, cluster k8s-upgrade-and-conformance-pj37kt/k8s-upgrade-and-conformance-g63m2g: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-g63m2g-mdlmk-968j5, cluster k8s-upgrade-and-conformance-pj37kt/k8s-upgrade-and-conformance-g63m2g: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-g63m2g-mdlmk-n75rb, cluster k8s-upgrade-and-conformance-pj37kt/k8s-upgrade-and-conformance-g63m2g: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-g63m2g-mdlmk-zwvfp, cluster k8s-upgrade-and-conformance-pj37kt/k8s-upgrade-and-conformance-g63m2g: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-pj37kt" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-pj37kt/k8s-upgrade-and-conformance-g63m2g
STEP: Deleting cluster k8s-upgrade-and-conformance-g63m2g
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-pj37kt/k8s-upgrade-and-conformance-g63m2g to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-g63m2g to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" 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-hfak2r/k8s-upgrade-and-conformance-40nv0v-md-0-7xlbm 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-40nv0v" workload cluster
Failed to get logs for machine k8s-upgrade-and-conformance-40nv0v-md-0-7xlbm-6665d4cfb5-x7k55, cluster k8s-upgrade-and-conformance-hfak2r/k8s-upgrade-and-conformance-40nv0v: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-40nv0v-zstrg-8fmqs, cluster k8s-upgrade-and-conformance-hfak2r/k8s-upgrade-and-conformance-40nv0v: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-40nv0v-zstrg-m8v57, cluster k8s-upgrade-and-conformance-hfak2r/k8s-upgrade-and-conformance-40nv0v: exit status 2
Failed to get logs for machine k8s-upgrade-and-conformance-40nv0v-zstrg-r42xp, cluster k8s-upgrade-and-conformance-hfak2r/k8s-upgrade-and-conformance-40nv0v: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-hfak2r" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-hfak2r/k8s-upgrade-and-conformance-40nv0v
STEP: Deleting cluster k8s-upgrade-and-conformance-40nv0v
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-hfak2r/k8s-upgrade-and-conformance-40nv0v to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-40nv0v 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-0rsm81-control-plane: exit status 2
STEP: Tearing down the management cluster



Summarizing 1 Failure:

[Fail] When testing Cluster API working on self-hosted clusters using ClusterClass [It] Should pivot the bootstrap cluster to a self-hosted cluster 
/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/controlplane_helpers.go:151

Ran 4 of 20 Specs in 1533.281 seconds
FAIL! -- 3 Passed | 1 Failed | 0 Pending | 16 Skipped


Ginkgo ran 1 suite in 27m45.255760891s
Test Suite Failed

Ginkgo 2.0 is coming soon!
==========================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

To silence this notice, set the environment variable: ACK_GINKGO_RC=true
Alternatively you can: touch $HOME/.ack-ginkgo-rc
make: *** [Makefile:110: run] Error 1
make: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e'
+ cleanup
++ pgrep -f 'docker events'
+ kill 22118
++ pgrep -f 'ctr -n moby events'
+ kill 22119
... skipping 21 lines ...