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

Test Failures


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

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.001s.
Expected
    <*errors.fundamental | 0xc001f1c720>: {
        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.1.xml

Filter through log files | View test history on testgrid


Show 12 Passed Tests

Show 8 Skipped Tests

Error lines from build-log.txt

... skipping 1131 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-n03j0t/machine-pool-hce7r0-mp-0
STEP: Waiting for the machine pool workload nodes
STEP: PASSED!
STEP: Dumping logs from the "machine-pool-hce7r0" workload cluster
Failed to get logs for Machine machine-pool-hce7r0-control-plane-cn474, Cluster machine-pool-n03j0t/machine-pool-hce7r0: exit status 2
STEP: Dumping all the Cluster API resources in the "machine-pool-n03j0t" namespace
STEP: Deleting cluster machine-pool-n03j0t/machine-pool-hce7r0
STEP: Deleting cluster machine-pool-hce7r0
INFO: Waiting for the Cluster machine-pool-n03j0t/machine-pool-hce7r0 to be deleted
STEP: Waiting for cluster machine-pool-hce7r0 to be deleted
STEP: Deleting namespace used for hosting the "machine-pool" 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-k8cmtr" workload cluster
Failed to get logs for Machine self-hosted-k8cmtr-control-plane-gzqsk, Cluster self-hosted-gf6n1x/self-hosted-k8cmtr: exit status 2
Failed to get logs for Machine self-hosted-k8cmtr-md-0-5999dd6f47-4xt2h, Cluster self-hosted-gf6n1x/self-hosted-k8cmtr: exit status 2
STEP: Dumping all the Cluster API resources in the "self-hosted-gf6n1x" namespace
STEP: Deleting cluster self-hosted-gf6n1x/self-hosted-k8cmtr
STEP: Deleting cluster self-hosted-k8cmtr
INFO: Waiting for the Cluster self-hosted-gf6n1x/self-hosted-k8cmtr to be deleted
STEP: Waiting for cluster self-hosted-k8cmtr to be deleted
STEP: Deleting namespace used for hosting the "self-hosted" 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-ul3q0c-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-ul3q0c" workload cluster
Failed to get logs for Machine quick-start-ul3q0c-control-plane-665bp, Cluster quick-start-nu36g9/quick-start-ul3q0c: exit status 2
Failed to get logs for Machine quick-start-ul3q0c-md-0-57897d55c4-vkb6l, Cluster quick-start-nu36g9/quick-start-ul3q0c: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-nu36g9" namespace
STEP: Deleting cluster quick-start-nu36g9/quick-start-ul3q0c
STEP: Deleting cluster quick-start-ul3q0c
INFO: Waiting for the Cluster quick-start-nu36g9/quick-start-ul3q0c to be deleted
STEP: Waiting for cluster quick-start-ul3q0c to be deleted
STEP: Deleting namespace used for hosting the "quick-start" 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-3kq3ku/k8s-upgrade-and-conformance-0fysqx-md-0-xbszr 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-0fysqx" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-0fysqx-fjtxq-kcc68, Cluster k8s-upgrade-and-conformance-3kq3ku/k8s-upgrade-and-conformance-0fysqx: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-0fysqx-md-0-xbszr-55f8696859-klcsk, Cluster k8s-upgrade-and-conformance-3kq3ku/k8s-upgrade-and-conformance-0fysqx: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-0fysqx-md-0-xbszr-55f8696859-p8c7k, Cluster k8s-upgrade-and-conformance-3kq3ku/k8s-upgrade-and-conformance-0fysqx: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-3kq3ku" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-3kq3ku/k8s-upgrade-and-conformance-0fysqx
STEP: Deleting cluster k8s-upgrade-and-conformance-0fysqx
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-3kq3ku/k8s-upgrade-and-conformance-0fysqx to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-0fysqx to be deleted
STEP: Deleting namespace used for hosting the "k8s-upgrade-and-conformance" 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-fo49pm-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-fo49pm" workload cluster
Failed to get logs for Machine quick-start-fo49pm-control-plane-vh4t5, Cluster quick-start-ifate7/quick-start-fo49pm: exit status 2
Failed to get logs for Machine quick-start-fo49pm-md-0-6d9549b6bf-gn2mh, Cluster quick-start-ifate7/quick-start-fo49pm: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-ifate7" namespace
STEP: Deleting cluster quick-start-ifate7/quick-start-fo49pm
STEP: Deleting cluster quick-start-fo49pm
INFO: Waiting for the Cluster quick-start-ifate7/quick-start-fo49pm to be deleted
STEP: Waiting for cluster quick-start-fo49pm to be deleted
STEP: Deleting namespace used for hosting the "quick-start" 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-u3owq2/md-scale-z5byra-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-z5byra" workload cluster
Failed to get logs for Machine md-scale-z5byra-control-plane-287l7, Cluster md-scale-u3owq2/md-scale-z5byra: exit status 2
Failed to get logs for Machine md-scale-z5byra-md-0-6c555d6f77-g8pth, Cluster md-scale-u3owq2/md-scale-z5byra: exit status 2
STEP: Dumping all the Cluster API resources in the "md-scale-u3owq2" namespace
STEP: Deleting cluster md-scale-u3owq2/md-scale-z5byra
STEP: Deleting cluster md-scale-z5byra
INFO: Waiting for the Cluster md-scale-u3owq2/md-scale-z5byra to be deleted
STEP: Waiting for cluster md-scale-z5byra to be deleted
STEP: Deleting namespace used for hosting the "md-scale" test spec
... skipping 52 lines ...
STEP: Waiting for deployment node-drain-ow4fgp-unevictable-workload/unevictable-pod-xkw 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-ow4fgp/node-drain-i1tvjh-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-i1tvjh" workload cluster
Failed to get logs for Machine node-drain-i1tvjh-control-plane-czqgw, Cluster node-drain-ow4fgp/node-drain-i1tvjh: exit status 2
STEP: Dumping all the Cluster API resources in the "node-drain-ow4fgp" namespace
STEP: Deleting cluster node-drain-ow4fgp/node-drain-i1tvjh
STEP: Deleting cluster node-drain-i1tvjh
INFO: Waiting for the Cluster node-drain-ow4fgp/node-drain-i1tvjh to be deleted
STEP: Waiting for cluster node-drain-i1tvjh to be deleted
STEP: Deleting namespace used for hosting the "node-drain" 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-xauoez/k8s-upgrade-and-conformance-x91nvf-md-0-4f5dl 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-x91nvf" workload cluster
Failed to get logs for Machine k8s-upgrade-and-conformance-x91nvf-f6mpz-l92qk, Cluster k8s-upgrade-and-conformance-xauoez/k8s-upgrade-and-conformance-x91nvf: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-x91nvf-f6mpz-qcm4m, Cluster k8s-upgrade-and-conformance-xauoez/k8s-upgrade-and-conformance-x91nvf: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-x91nvf-f6mpz-sbppd, Cluster k8s-upgrade-and-conformance-xauoez/k8s-upgrade-and-conformance-x91nvf: exit status 2
Failed to get logs for Machine k8s-upgrade-and-conformance-x91nvf-md-0-4f5dl-775d5c4c4f-br9h5, Cluster k8s-upgrade-and-conformance-xauoez/k8s-upgrade-and-conformance-x91nvf: exit status 2
STEP: Dumping all the Cluster API resources in the "k8s-upgrade-and-conformance-xauoez" namespace
STEP: Deleting cluster k8s-upgrade-and-conformance-xauoez/k8s-upgrade-and-conformance-x91nvf
STEP: Deleting cluster k8s-upgrade-and-conformance-x91nvf
INFO: Waiting for the Cluster k8s-upgrade-and-conformance-xauoez/k8s-upgrade-and-conformance-x91nvf to be deleted
STEP: Waiting for cluster k8s-upgrade-and-conformance-x91nvf 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-ejiby5" workload cluster
Failed to get logs for Machine kcp-adoption-ejiby5-control-plane-0, Cluster kcp-adoption-k3li7l/kcp-adoption-ejiby5: exit status 2
STEP: Dumping all the Cluster API resources in the "kcp-adoption-k3li7l" namespace
STEP: Deleting cluster kcp-adoption-k3li7l/kcp-adoption-ejiby5
STEP: Deleting cluster kcp-adoption-ejiby5
INFO: Waiting for the Cluster kcp-adoption-k3li7l/kcp-adoption-ejiby5 to be deleted
STEP: Waiting for cluster kcp-adoption-ejiby5 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-g37kxg-md-0-8wnxz are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: PASSED!
STEP: Dumping logs from the "quick-start-g37kxg" workload cluster
Failed to get logs for Machine quick-start-g37kxg-2dmn8-m97rm, Cluster quick-start-thu3ee/quick-start-g37kxg: exit status 2
Failed to get logs for Machine quick-start-g37kxg-md-0-8wnxz-7bcc5dd79c-4s9wf, Cluster quick-start-thu3ee/quick-start-g37kxg: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-thu3ee" namespace
STEP: Deleting cluster quick-start-thu3ee/quick-start-g37kxg
STEP: Deleting cluster quick-start-g37kxg
INFO: Waiting for the Cluster quick-start-thu3ee/quick-start-g37kxg to be deleted
STEP: Waiting for cluster quick-start-g37kxg 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-l2aeek-md-0-7mws2 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-685ugm/quick-start
INFO: Waiting for ControlPlane rollout to complete.
STEP: Dumping logs from the "clusterclass-changes-l2aeek" workload cluster
Failed to get logs for Machine clusterclass-changes-l2aeek-md-0-7mws2-6c686df9b6-hc7n6, Cluster clusterclass-changes-685ugm/clusterclass-changes-l2aeek: exit status 2
Failed to get logs for Machine clusterclass-changes-l2aeek-qq5rj-7k56r, Cluster clusterclass-changes-685ugm/clusterclass-changes-l2aeek: exit status 2
STEP: Dumping all the Cluster API resources in the "clusterclass-changes-685ugm" namespace
STEP: Deleting cluster clusterclass-changes-685ugm/clusterclass-changes-l2aeek
STEP: Deleting cluster clusterclass-changes-l2aeek
INFO: Waiting for the Cluster clusterclass-changes-685ugm/clusterclass-changes-l2aeek to be deleted
STEP: Waiting for cluster clusterclass-changes-l2aeek to be deleted
STEP: Deleting namespace used for hosting the "clusterclass-changes" test spec
... skipping 94 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-q54o7n" workload cluster
Failed to get logs for Machine mhc-remediation-q54o7n-control-plane-kqbck, Cluster mhc-remediation-6dg4qr/mhc-remediation-q54o7n: exit status 2
Failed to get logs for Machine mhc-remediation-q54o7n-md-0-b67b6c8c5-gqqdd, Cluster mhc-remediation-6dg4qr/mhc-remediation-q54o7n: exit status 2
STEP: Dumping all the Cluster API resources in the "mhc-remediation-6dg4qr" namespace
STEP: Deleting cluster mhc-remediation-6dg4qr/mhc-remediation-q54o7n
STEP: Deleting cluster mhc-remediation-q54o7n
INFO: Waiting for the Cluster mhc-remediation-6dg4qr/mhc-remediation-q54o7n to be deleted
STEP: Waiting for cluster mhc-remediation-q54o7n to be deleted
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
... skipping 81 lines ...
INFO: Patching the new Kubernetes version to Machine Pool k8s-upgrade-with-runtimesdk-fniom1/k8s-upgrade-with-runtimesdk-b3c53e-mp-0
INFO: Waiting for Kubernetes versions of machines in MachinePool k8s-upgrade-with-runtimesdk-fniom1/k8s-upgrade-with-runtimesdk-b3c53e-mp-0 to be upgraded from v1.23.6 to v1.24.0
INFO: Ensuring all MachinePool Instances have upgraded kubernetes version v1.24.0
STEP: Waiting until nodes are ready
STEP: Dumping resources and deleting the workload cluster
STEP: Deleting the workload cluster
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-b3c53e-kptq4-vg4wc, Cluster k8s-upgrade-with-runtimesdk-fniom1/k8s-upgrade-with-runtimesdk-b3c53e: exit status 2
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-b3c53e-md-0-7r8dt-7d4bd5f5b9-bwbxr, Cluster k8s-upgrade-with-runtimesdk-fniom1/k8s-upgrade-with-runtimesdk-b3c53e: exit status 2
Failed to get logs for Machine k8s-upgrade-with-runtimesdk-b3c53e-md-0-7r8dt-7d4bd5f5b9-xmrs4, Cluster k8s-upgrade-with-runtimesdk-fniom1/k8s-upgrade-with-runtimesdk-b3c53e: exit status 2
Failed to get logs for MachinePool k8s-upgrade-with-runtimesdk-b3c53e-mp-0, Cluster k8s-upgrade-with-runtimesdk-fniom1/k8s-upgrade-with-runtimesdk-b3c53e: exit status 2
STEP: Deleting the workload cluster
STEP: Deleting cluster k8s-upgrade-with-runtimesdk-b3c53e
INFO: Blocking with BeforeClusterDelete hook
STEP: Setting BeforeClusterDelete response to Status:Success to unblock the reconciliation
STEP: Checking all lifecycle hooks have been called
STEP: PASSED!
... skipping 8 lines ...
When upgrading a workload cluster using ClusterClass with RuntimeSDK [PR-Informing] [ClusterClass]
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_runtimesdk_test.go:29
  Should create, upgrade and delete a workload cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_runtimesdk.go:130
------------------------------
STEP: Dumping logs from the bootstrap cluster
Failed to get logs for the bootstrap cluster node test-3vfhcr-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 13 of 21 Specs in 1863.137 seconds
FAIL! -- 12 Passed | 1 Failed | 0 Pending | 8 Skipped


Ginkgo ran 1 suite in 32m9.11393576s
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 25943
++ pgrep -f 'ctr -n moby events'
+ kill 25944
... skipping 21 lines ...