PR #9403 - 08-27 17:48

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

612
Total Tests
576
Passed
4
Failed
32
Skipped

Failed Tests

TestNodePool
0s
TestNodePool/HostedCluster0
1h5m19.83s
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-5qdcn/node-pool-4zg24 in 26s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-4zg24 util.go:3215: Failed to wait for HostedCluster e2e-clusters-5qdcn/node-pool-4zg24 to have valid conditions in 2s: context deadline exceeded eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-5qdcn/node-pool-4zg24 invalid at RV 145052 after 2s: eventually.go:228: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion eventually.go:228: - incorrect condition: wanted ControlPlaneConnectionAvailable=Unknown, got ControlPlaneConnectionAvailable=True: AsExpected(All is well) eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.1.0-0.ci-2026-08-27-180733-test-ci-op-80h2v9kb-latest) eventually.go:228: - incorrect condition: wanted DataPlaneConnectionAvailable=Unknown, got DataPlaneConnectionAvailable=True: AsExpected(All is well) eventually.go:228: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 5.1.0-0.ci-2026-08-27-180733-test-ci-op-80h2v9kb-latest) hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called
TestNodePool/HostedCluster0/Main
20ms
util.go:312: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5qdcn/node-pool-4zg24 in 0s util.go:329: Successfully waited for kubeconfig secret to have data in 0s util.go:391: Successfully waited for a successful connection to the guest API server in 0s
TestNodePool/HostedCluster0/Main/TestMirrorConfigs
18m21.07s
nodepool_mirrorconfigs_test.go:60: Starting test MirrorConfigsTest nodepool_test.go:376: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:512: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:512: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure util.go:590: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-5qdcn/node-pool-4zg24-test-mirrorconfigs in 8m12s nodepool_test.go:436: Successfully waited for NodePool e2e-clusters-5qdcn/node-pool-4zg24-test-mirrorconfigs to have correct status in 0s nodepool_mirrorconfigs_test.go:81: Entering MirrorConfigs test nodepool_mirrorconfigs_test.go:111: Hosted control plane namespace is e2e-clusters-5qdcn-node-pool-4zg24 nodepool_mirrorconfigs_test.go:113: Successfully waited for kubeletConfig should be mirrored and present in the hosted cluster in 3s nodepool_mirrorconfigs_test.go:157: Deleting KubeletConfig configmap reference from nodepool ... nodepool_mirrorconfigs_test.go:163: Failed to wait for KubeletConfig configmap to be deleted in 10m0s: context deadline exceeded eventually.go:384: observed invalid **v1.ConfigMap state after 10m0s eventually.go:401: - observed **v1.ConfigMap collection invalid: expected 1 KubeletConfig configmap, got 0 nodepool_mirrorconfigs_test.go:101: Exiting MirrorConfigs test: OK