PR #8957 - 07-12 21:41

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

599
Total Tests
560
Passed
9
Failed
30
Skipped

Failed Tests

TestKarpenterUpgradeControlPlane
1h42m8.76s
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-lp746/karpenter-upgrade-control-plane-tbhzj in 35s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster karpenter-upgrade-control-plane-tbhzj upgrade_safe_check.go:87: UpgradeSafeFieldCheck: latch engaged for status.controlPlaneVersion util.go:3158: Successfully waited for HostedCluster e2e-clusters-lp746/karpenter-upgrade-control-plane-tbhzj to have valid conditions in 0s hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called
TestKarpenterUpgradeControlPlane/Main
1h14m3.65s
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lp746/karpenter-upgrade-control-plane-tbhzj in 0s util.go:322: Successfully waited for kubeconfig secret to have data in 0s util.go:384: Successfully waited for a successful connection to the guest API server in 0s karpenter_control_plane_upgrade_test.go:57: Starting Karpenter control plane upgrade. FromImage: registry.build01.ci.openshift.org/ci-op-snnps8zb/release@sha256:2fdce3b77b7da94b1052ffe625b8337bbc8e46ac56fabf701f0ff33bbce6f57c, toImage: registry.build01.ci.openshift.org/ci-op-snnps8zb/release@sha256:ba3754013220fabd559c9d73be5819f38b34fcae11bf5a6167d8783c9127ffe6 karpenter_control_plane_upgrade_test.go:68: machine-os version(s) in latest release: [9.8.20260708-0 10.2.20260709-0] karpenter_control_plane_upgrade_test.go:73: Created Karpenter NodePool karpenter_control_plane_upgrade_test.go:75: Created workloads util.go:583: Successfully waited for 1 nodes to become ready in 4m45s karpenter_test.go:1557: Successfully waited for NodeClaims to be ready in 3s karpenter_test.go:1513: Successfully waited for Pods to be scheduled on provisioned Karpenter nodes in 9s karpenter_control_plane_upgrade_test.go:82: Pre-upgrade node: ip-10-0-132-154.ec2.internal, OS image: Red Hat Enterprise Linux CoreOS 9.8.20260702-0 (Plow) karpenter_control_plane_upgrade_test.go:84: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-snnps8zb/release@sha256:ba3754013220fabd559c9d73be5819f38b34fcae11bf5a6167d8783c9127ffe6 util.go:620: Successfully waited for HostedCluster e2e-clusters-lp746/karpenter-upgrade-control-plane-tbhzj to rollout in 24m6s karpenter_control_plane_upgrade_test.go:110: Control plane upgrade complete, waiting for NodeClaim drift detection karpenter_test.go:1608: Successfully waited for NodeClaim on-demand-z4cmn to be drifted in 0s karpenter_control_plane_upgrade_test.go:114: Karpenter Nodes drifted util.go:583: Failed to wait for 1 nodes to become ready in 45m0s: context deadline exceeded eventually.go:384: observed invalid **v1.Node state after 45m0s eventually.go:401: - observed **v1.Node /ip-10-0-132-154.ec2.internal invalid: expected node OS image "Red Hat Enterprise Linux CoreOS 9.8.20260702-0 (Plow)" to contain one of [9.8.20260708-0 10.2.20260709-0] util.go:583: *v1.Node /ip-10-0-132-154.ec2.internal conditions: util.go:583: MemoryPressure=False: KubeletHasSufficientMemory(kubelet has sufficient memory available) util.go:583: DiskPressure=False: KubeletHasNoDiskPressure(kubelet has no disk pressure) util.go:583: PIDPressure=False: KubeletHasSufficientPID(kubelet has sufficient PID available) util.go:583: Ready=True: KubeletReady(kubelet is posting ready status)
TestNodePool
0s
TestNodePool/HostedCluster0
1h5m46.64s
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-l4g6m/node-pool-g5gvx in 23s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-g5gvx util.go:3158: Failed to wait for HostedCluster e2e-clusters-l4g6m/node-pool-g5gvx to have valid conditions in 2s: context deadline exceeded eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-l4g6m/node-pool-g5gvx invalid at RV 144898 after 2s: eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.0.0-0.ci-2026-07-13-002258-test-ci-op-snnps8zb-latest) eventually.go:228: - incorrect condition: wanted DataPlaneConnectionAvailable=Unknown, got DataPlaneConnectionAvailable=True: AsExpected(All is well) eventually.go:228: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion eventually.go:228: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 5.0.0-0.ci-2026-07-13-002258-test-ci-op-snnps8zb-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
20ms
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-l4g6m/node-pool-g5gvx in 0s util.go:322: Successfully waited for kubeconfig secret to have data in 0s util.go:384: Successfully waited for a successful connection to the guest API server in 0s
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigGetsRolledOut
17m34.13s
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest 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=InstanceProvisionStarted util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-ntomachineconfig-replace in 7m36s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-ntomachineconfig-replace to have correct status in 0s util.go:499: Successfully waited for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-ntomachineconfig-replace to start config update in 15s util.go:515: Successfully waited for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-ntomachineconfig-replace to finish config update in 9m40s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-g5gvx-test-ntomachineconfig-replace to be ready in 0s util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-ntomachineconfig-replace in 0s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-ntomachineconfig-replace to have correct status in 0s
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigGetsRolledOut/EnsureNoCrashingPods
20ms
util.go:829: Container cluster-version-operator in pod cluster-version-operator-6c7c894474-nl6bt has a restartCount > 0 (1)
TestNodePool/HostedCluster0/Main/TestNodepoolMachineconfigGetsRolledout
14m30.4s
nodepool_machineconfig_test.go:54: Starting test NodePoolMachineconfigRolloutTest 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=InstanceProvisionStarted util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-machineconfig in 6m12.025s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-machineconfig to have correct status in 0s util.go:499: Successfully waited for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-machineconfig to start config update in 15s util.go:515: Successfully waited for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-machineconfig to finish config update in 8m0s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/machineconfig-update-checker-replace to be ready in 0s util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-machineconfig in 0s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-l4g6m/node-pool-g5gvx-test-machineconfig to have correct status in 0s
TestNodePool/HostedCluster0/Main/TestNodepoolMachineconfigGetsRolledout/EnsureNoCrashingPods
30ms
util.go:829: Container cluster-version-operator in pod cluster-version-operator-6c7c894474-nl6bt has a restartCount > 0 (1)