This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 11 succeeded
Started2022-08-17 15:20
Elapsed35m47s
Revisionmain

Test Failures


capi-e2e When testing ClusterClass changes [ClusterClass] Should successfully rollout the managed topology upon changes to the ClusterClass 11m53s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capi\-e2e\sWhen\stesting\sClusterClass\schanges\s\[ClusterClass\]\sShould\ssuccessfully\srollout\sthe\smanaged\stopology\supon\schanges\sto\sthe\sClusterClass$'
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterclass_changes.go:119
Timed out after 600.002s.
Expected
    <*errors.fundamental | 0xc00030cd20>: {
        msg: "field \"spec.machineTemplate.nodeDrainTimeout\" should be equal to \"10s\", but is \"30s\"",
        stack: [0x1be4da5, 0x4d7245, 0x4d67bf, 0x7df971, 0x7dfcd9, 0x7e0507, 0x7dfa6b, 0x1be4ad2, 0x1be35a6, 0x7a9cd1, 0x7a96c5, 0x7a8dbb, 0x7aeaaa, 0x7ae4a7, 0x7ceea8, 0x7cebc5, 0x7ce265, 0x7d0632, 0x7dc529, 0x7dc336, 0x1bffb8d, 0x5204a2, 0x46d941],
    }
to be nil
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterclass_changes.go:240
				
				Click to see stdout/stderrfrom junit.e2e_suite.3.xml

Filter through log files | View test history on testgrid


Show 11 Passed Tests

Show 9 Skipped Tests

Error lines from build-log.txt

... skipping 1120 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-ehph8t" workload cluster
Failed to get logs for Machine kcp-adoption-ehph8t-control-plane-0, Cluster kcp-adoption-hoeqz2/kcp-adoption-ehph8t: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-adoption-hoeqz2" namespace
STEP: Deleting cluster kcp-adoption-hoeqz2/kcp-adoption-ehph8t
STEP: Deleting cluster kcp-adoption-ehph8t
INFO: Waiting for the Cluster kcp-adoption-hoeqz2/kcp-adoption-ehph8t to be deleted
STEP: Waiting for cluster kcp-adoption-ehph8t to be deleted
STEP: Deleting namespace used for hosting the "kcp-adoption" test spec
... skipping 40 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-qjgaik-md-0-k27jd are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-qjgaik" workload cluster
Failed to get logs for Machine quick-start-qjgaik-gz7tg-qzvpp, Cluster quick-start-u1ulf2/quick-start-qjgaik: exit status 2
Failed to get logs for Machine quick-start-qjgaik-md-0-k27jd-599bf9c6f7-frjm5, Cluster quick-start-u1ulf2/quick-start-qjgaik: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-u1ulf2" namespace
STEP: Deleting cluster quick-start-u1ulf2/quick-start-qjgaik
STEP: Deleting cluster quick-start-qjgaik
INFO: Waiting for the Cluster quick-start-u1ulf2/quick-start-qjgaik to be deleted
STEP: Waiting for cluster quick-start-qjgaik to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 46 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-pdxdgl" workload cluster
Failed to get logs for Machine md-rollout-pdxdgl-control-plane-znzdf, Cluster md-rollout-vcdbff/md-rollout-pdxdgl: exit status 2
Failed to get logs for Machine md-rollout-pdxdgl-md-0-76d65cd897-mqcnq, Cluster md-rollout-vcdbff/md-rollout-pdxdgl: exit status 2
Failed to get logs for Machine md-rollout-pdxdgl-md-0-d75588fdb-rrnsw, Cluster md-rollout-vcdbff/md-rollout-pdxdgl: error creating container exec: Error response from daemon: No such container: md-rollout-pdxdgl-md-0-d75588fdb-rrnsw
STEP: Dumping all the Cluster API resources in the "md-rollout-vcdbff" namespace
STEP: Deleting cluster md-rollout-vcdbff/md-rollout-pdxdgl
STEP: Deleting cluster md-rollout-pdxdgl
INFO: Waiting for the Cluster md-rollout-vcdbff/md-rollout-pdxdgl to be deleted
STEP: Waiting for cluster md-rollout-pdxdgl 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-0hrkoc/md-scale-xneyso-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-xneyso" workload cluster
Failed to get logs for Machine md-scale-xneyso-control-plane-6vxtt, Cluster md-scale-0hrkoc/md-scale-xneyso: exit status 2
Failed to get logs for Machine md-scale-xneyso-md-0-55b4799846-2vd2n, Cluster md-scale-0hrkoc/md-scale-xneyso: exit status 2
STEP: Dumping all the Cluster API resources in the "md-scale-0hrkoc" namespace
STEP: Deleting cluster md-scale-0hrkoc/md-scale-xneyso
STEP: Deleting cluster md-scale-xneyso
INFO: Waiting for the Cluster md-scale-0hrkoc/md-scale-xneyso to be deleted
STEP: Waiting for cluster md-scale-xneyso to be deleted
STEP: Deleting namespace used for hosting the "md-scale" test spec
... skipping 81 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 bootstrap
STEP: Waiting for cluster to enter the provisioned phase
STEP: Dumping logs from the "self-hosted-sh3h7r" workload cluster
Failed to get logs for Machine self-hosted-sh3h7r-74rnr-v7vlx, Cluster self-hosted-xvcb3w/self-hosted-sh3h7r: exit status 2
Failed to get logs for Machine self-hosted-sh3h7r-md-0-8l2np-6665859698-tk7t8, Cluster self-hosted-xvcb3w/self-hosted-sh3h7r: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-xvcb3w" namespace
STEP: Deleting cluster self-hosted-xvcb3w/self-hosted-sh3h7r
STEP: Deleting cluster self-hosted-sh3h7r
INFO: Waiting for the Cluster self-hosted-xvcb3w/self-hosted-sh3h7r to be deleted
STEP: Waiting for cluster self-hosted-sh3h7r to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" test spec
... skipping 52 lines ...
STEP: Waiting for deployment node-drain-5tywam-unevictable-workload/unevictable-pod-v1f 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-5tywam/node-drain-onmcba-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-onmcba" workload cluster
Failed to get logs for Machine node-drain-onmcba-control-plane-xx9m6, Cluster node-drain-5tywam/node-drain-onmcba: exit status 2
STEP: Dumping all the Cluster API resources in the "node-drain-5tywam" namespace
STEP: Deleting cluster node-drain-5tywam/node-drain-onmcba
STEP: Deleting cluster node-drain-onmcba
INFO: Waiting for the Cluster node-drain-5tywam/node-drain-onmcba to be deleted
STEP: Waiting for cluster node-drain-onmcba to be deleted
STEP: Deleting namespace used for hosting the "node-drain" test spec
... skipping 48 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-vzx5re/machine-pool-xk5s0l-mp-0
STEP: Waiting for the machine pool workload nodes
STEP: PASSED!
STEP: Dumping logs from the "machine-pool-xk5s0l" workload cluster
Failed to get logs for Machine machine-pool-xk5s0l-control-plane-827x8, Cluster machine-pool-vzx5re/machine-pool-xk5s0l: exit status 2
STEP: Dumping all the Cluster API resources in the "machine-pool-vzx5re" namespace
STEP: Deleting cluster machine-pool-vzx5re/machine-pool-xk5s0l
STEP: Deleting cluster machine-pool-xk5s0l
INFO: Waiting for the Cluster machine-pool-vzx5re/machine-pool-xk5s0l to be deleted
STEP: Waiting for cluster machine-pool-xk5s0l to be deleted
STEP: Deleting namespace used for hosting the "machine-pool" test spec
... skipping 40 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-gmbf4t-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-gmbf4t" workload cluster
Failed to get logs for Machine quick-start-gmbf4t-control-plane-d5p7f, Cluster quick-start-nvf9e6/quick-start-gmbf4t: exit status 2
Failed to get logs for Machine quick-start-gmbf4t-md-0-6fddd7d76b-ztvs6, Cluster quick-start-nvf9e6/quick-start-gmbf4t: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-nvf9e6" namespace
STEP: Deleting cluster quick-start-nvf9e6/quick-start-gmbf4t
STEP: Deleting cluster quick-start-gmbf4t
INFO: Waiting for the Cluster quick-start-nvf9e6/quick-start-gmbf4t to be deleted
STEP: Waiting for cluster quick-start-gmbf4t to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 40 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-rv7hlr-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-rv7hlr" workload cluster
Failed to get logs for Machine quick-start-rv7hlr-control-plane-8pbs9, Cluster quick-start-9mz4ks/quick-start-rv7hlr: exit status 2
Failed to get logs for Machine quick-start-rv7hlr-md-0-95f976fd7-twmvp, Cluster quick-start-9mz4ks/quick-start-rv7hlr: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-9mz4ks" namespace
STEP: Deleting cluster quick-start-9mz4ks/quick-start-rv7hlr
STEP: Deleting cluster quick-start-rv7hlr
INFO: Waiting for the Cluster quick-start-9mz4ks/quick-start-rv7hlr to be deleted
STEP: Waiting for cluster quick-start-rv7hlr to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 44 lines ...
STEP: Checking all the machines controlled by clusterclass-changes-x8awiy-md-0-tw246 are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: Modifying the control plane configuration in ClusterClass and wait for changes to be applied to the control plane object
INFO: Modifying the ControlPlaneTemplate of ClusterClass clusterclass-changes-pn2byc/quick-start
INFO: Waiting for ControlPlane rollout to complete.
STEP: Dumping logs from the "clusterclass-changes-x8awiy" workload cluster
Failed to get logs for Machine clusterclass-changes-x8awiy-k8g6l-vb2x9, Cluster clusterclass-changes-pn2byc/clusterclass-changes-x8awiy: exit status 2
Failed to get logs for Machine clusterclass-changes-x8awiy-md-0-tw246-597b65978-zz598, Cluster clusterclass-changes-pn2byc/clusterclass-changes-x8awiy: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterclass-changes-pn2byc" namespace
STEP: Deleting cluster clusterclass-changes-pn2byc/clusterclass-changes-x8awiy
STEP: Deleting cluster clusterclass-changes-x8awiy
INFO: Waiting for the Cluster clusterclass-changes-pn2byc/clusterclass-changes-x8awiy to be deleted
STEP: Waiting for cluster clusterclass-changes-x8awiy to be deleted
STEP: Deleting namespace used for hosting the "clusterclass-changes" test spec
... skipping 100 lines ...
INFO: Waiting for etcd to have the upgraded image tag
INFO: Waiting for Kubernetes versions of machines in MachineDeployment k8s-upgrade-and-conformance-f1x4rr/k8s-upgrade-and-conformance-fxo3sq-md-0-dfkk4 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-fxo3sq" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-fxo3sq-md-0-dfkk4-85d6cf75f-f68kx, Cluster k8s-upgrade-and-conformance-f1x4rr/k8s-upgrade-and-conformance-fxo3sq: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-fxo3sq-npkrg-dfzb9, Cluster k8s-upgrade-and-conformance-f1x4rr/k8s-upgrade-and-conformance-fxo3sq: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-fxo3sq-npkrg-fgbds, Cluster k8s-upgrade-and-conformance-f1x4rr/k8s-upgrade-and-conformance-fxo3sq: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-fxo3sq-npkrg-xw4hm, Cluster k8s-upgrade-and-conformance-f1x4rr/k8s-upgrade-and-conformance-fxo3sq: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-f1x4rr" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-f1x4rr/k8s-upgrade-and-conformance-fxo3sq
STEP: Deleting cluster k8s-upgrade-and-conformance-fxo3sq
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-f1x4rr/k8s-upgrade-and-conformance-fxo3sq to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-fxo3sq 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-1kai5d/k8s-upgrade-and-conformance-ayn3xy-md-0-rqp67 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-ayn3xy" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-ayn3xy-md-0-rqp67-764bd4dbc-44gfz, Cluster k8s-upgrade-and-conformance-1kai5d/k8s-upgrade-and-conformance-ayn3xy: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-ayn3xy-md-0-rqp67-764bd4dbc-s8x25, Cluster k8s-upgrade-and-conformance-1kai5d/k8s-upgrade-and-conformance-ayn3xy: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-ayn3xy-r9n9q-7x6f8, Cluster k8s-upgrade-and-conformance-1kai5d/k8s-upgrade-and-conformance-ayn3xy: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-1kai5d" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-1kai5d/k8s-upgrade-and-conformance-ayn3xy
STEP: Deleting cluster k8s-upgrade-and-conformance-ayn3xy
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-1kai5d/k8s-upgrade-and-conformance-ayn3xy to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-ayn3xy 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 [ClusterClass]
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_test.go:65
  Should create and upgrade a workload cluster and eventually run kubetest
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade.go:118
------------------------------
STEP: Dumping logs from the bootstrap cluster
Failed to get logs for the bootstrap cluster node test-140yn9-control-plane: exit status 2
STEP: Tearing down the management cluster



Summarizing 1 Failure:

[Fail] When testing ClusterClass changes [ClusterClass] [It] Should successfully rollout the managed topology upon changes to the ClusterClass 
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/clusterclass_changes.go:240

Ran 12 of 21 Specs in 1751.341 seconds
FAIL! -- 11 Passed | 1 Failed | 0 Pending | 9 Skipped


Ginkgo ran 1 suite in 30m17.909735323s
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:129: run] Error 1
make: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e'
+ cleanup
++ pgrep -f 'docker events'
+ kill 25388
++ pgrep -f 'ctr -n moby events'
+ kill 25389
... skipping 21 lines ...