PR #7816 - 02-27 01:51

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

473
Total Tests
444
Passed
7
Failed
22
Skipped

Failed Tests

TestNodePool
0s
TestNodePool/HostedCluster0
1h3m22.94s
hypershift_framework.go:459: Successfully created hostedcluster e2e-clusters-45cj6/node-pool-f775k in 1m3s hypershift_framework.go:128: Summarizing unexpected conditions for HostedCluster node-pool-f775k util.go:2975: Failed to wait for HostedCluster e2e-clusters-45cj6/node-pool-f775k to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-45cj6/node-pool-f775k invalid at RV 119876 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 4.22.0-0.ci-2026-02-27-020857-test-ci-op-g57dd1nv-latest) eventually.go:227: - incorrect condition: wanted DataPlaneConnectionAvailable=Unknown, got DataPlaneConnectionAvailable=True: AsExpected(All is well) eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 4.22.0-0.ci-2026-02-27-020857-test-ci-op-g57dd1nv-latest) eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion hypershift_framework.go:278: skipping postTeardown() hypershift_framework.go:256: skipping teardown, already called
TestNodePool/HostedCluster0/Main
20ms
util.go:291: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-45cj6/node-pool-f775k in 0s util.go:308: Successfully waited for kubeconfig secret to have data in 0s util.go:370: Successfully waited for a successful connection to the guest API server in 0s
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigAppliedInPlace
12m30.2s
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-inplace in 8m0s nodepool_test.go:404: Successfully waited for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-inplace to have correct status in 0s util.go:481: Successfully waited for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-inplace to start config update in 15s util.go:497: Successfully waited for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-inplace to finish config update in 4m0s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-f775k-test-ntomachineconfig-inplace to be ready in 15s util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-inplace in 0s nodepool_test.go:404: Successfully waited for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-inplace to have correct status in 0s
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigAppliedInPlace/EnsureNoCrashingPods
20ms
util.go:780: Container aws-node-termination-handler in pod aws-node-termination-handler-59f476b77b-dxz6z has a restartCount > 0 (1)
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigGetsRolledOut
20m2.2s
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-replace in 9m24s nodepool_test.go:404: Successfully waited for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-replace to have correct status in 3s util.go:481: Successfully waited for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-replace to start config update in 15s util.go:497: Successfully waited for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-replace to finish config update in 10m20s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-f775k-test-ntomachineconfig-replace to be ready in 0s util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-replace in 0s nodepool_test.go:404: Successfully waited for NodePool e2e-clusters-45cj6/node-pool-f775k-test-ntomachineconfig-replace to have correct status in 0s
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigGetsRolledOut/EnsureNoCrashingPods
30ms
util.go:780: Container aws-node-termination-handler in pod aws-node-termination-handler-59f476b77b-dxz6z has a restartCount > 0 (1)