PR #6033 - 04-14 14:17

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

448
Total Tests
422
Passed
5
Failed
21
Skipped

Failed Tests

TestNodePool
0s
TestNodePool/HostedCluster0
42m26.97s
hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-d4d6z/node-pool-2s7v5 in 12s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-2s7v5 util.go:2123: Failed to wait for HostedCluster e2e-clusters-d4d6z/node-pool-2s7v5 to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-d4d6z/node-pool-2s7v5 invalid at RV 125833 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 4.19.0-0.ci-2025-04-14-145837-test-ci-op-495q8z3v-latest) eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 4.19.0-0.ci-2025-04-14-145837-test-ci-op-495q8z3v-latest) eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called
TestNodePool/HostedCluster0/Main
30ms
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-d4d6z/node-pool-2s7v5 in 0s util.go:235: Successfully waited for kubeconfig secret to have data in 0s util.go:281: Successfully waited for a successful connection to the guest API server in 25ms
TestNodePool/HostedCluster0/Main/TestNodePoolPrevReleaseN1
18m55.01s
nodepool_prev_release_test.go:34: Starting NodePoolPrevReleaseCreateTest. util.go:462: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-d4d6z/node-pool-2s7v5-h48dw in 8m55s eventually.go:104: Failed to get *v1beta1.NodePool: client rate limiter Wait returned an error: context deadline exceeded nodepool_test.go:362: Failed to wait for NodePool e2e-clusters-d4d6z/node-pool-2s7v5-h48dw to have correct status in 10m0s: context deadline exceeded eventually.go:224: observed *v1beta1.NodePool e2e-clusters-d4d6z/node-pool-2s7v5-h48dw invalid at RV 104102 after 10m0s: incorrect condition: wanted SupportedVersionSkew=False, got SupportedVersionSkew=True: AsExpected(Release image version is valid)
TestNodePool/HostedCluster0/Main/TestNodePoolPrevReleaseN2
19m28.01s
nodepool_prev_release_test.go:34: Starting NodePoolPrevReleaseCreateTest. util.go:462: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-d4d6z/node-pool-2s7v5-xv5nj in 9m28s eventually.go:104: Failed to get *v1beta1.NodePool: client rate limiter Wait returned an error: context deadline exceeded nodepool_test.go:362: Failed to wait for NodePool e2e-clusters-d4d6z/node-pool-2s7v5-xv5nj to have correct status in 10m0s: context deadline exceeded eventually.go:224: observed *v1beta1.NodePool e2e-clusters-d4d6z/node-pool-2s7v5-xv5nj invalid at RV 77363 after 10m0s: incorrect condition: wanted SupportedVersionSkew=True, got SupportedVersionSkew=False: UnsupportedSkew(NodePool minor version 4.17 is not compatible with the HostedCluster minor version 4.19 (max allowed difference: 1))