PR #9014 - 07-21 20:10

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

409
Total Tests
358
Passed
4
Failed
47
Skipped

Failed Tests

TestNodePool
0s
TestNodePool/HostedCluster0
59m33.96s
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-rp4pn/node-pool-c44nr in 3m27s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-c44nr util.go:3158: Failed to wait for HostedCluster e2e-clusters-rp4pn/node-pool-c44nr to have valid conditions in 2s: context deadline exceeded eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-rp4pn/node-pool-c44nr invalid at RV 64856 after 2s: 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.0.0-0.ci-2026-07-21-204435-test-ci-op-kzcstspm-latest) eventually.go:228: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.0.0-0.ci-2026-07-21-204435-test-ci-op-kzcstspm-latest) eventually.go:228: - incorrect condition: wanted ControlPlaneConnectionAvailable=Unknown, got ControlPlaneConnectionAvailable=True: AsExpected(All is well) hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called
TestNodePool/HostedCluster0/Main
460ms
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-rp4pn/node-pool-c44nr in 50ms util.go:322: Successfully waited for kubeconfig secret to have data in 325ms util.go:384: Successfully waited for a successful connection to the guest API server in 25ms
TestNodePool/HostedCluster0/Main/TestNodePoolPrevReleaseN1
33m34.76s
nodepool_prev_release_test.go:33: Starting NodePoolPrevReleaseCreateTest. nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-rp4pn/node-pool-c44nr-5gf9m in 13m6.05s nodepool_test.go:431: Failed to wait for NodePool e2e-clusters-rp4pn/node-pool-c44nr-5gf9m to have correct status in 20m0s: context deadline exceeded eventually.go:225: observed *v1beta1.NodePool e2e-clusters-rp4pn/node-pool-c44nr-5gf9m invalid at RV 71784 after 20m0s: incorrect condition: wanted ReachedIgnitionEndpoint=True, got ReachedIgnitionEndpoint=False: ignitionNotReached