PR #8874 - 06-30 16:04

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-9p9rm/ha-break-glass-creds-t7qkf in 18s hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called

journals.go:77: No machines associated with infra id ha-break-glass-creds-t7qkf were found. Skipping journal dump. hypershift_framework.go:591: Destroyed cluster. Namespace: e2e-clusters-9p9rm, name: ha-break-glass-creds-t7qkf hypershift_framework.go:605: Failed to delete test namespace: namespace still exists after deletion timeout: context deadline exceeded fixture.go:404: Failed saving machine console logs; this is nonfatal: failed to get machine console logs: failed to get hostedcluster: hostedclusters.hypershift.openshift.io "ha-break-glass-creds-t7qkf" not found fixture.go:412: Failed to dump machine journals; this is nonfatal: secrets "ha-break-glass-creds-t7qkf-ssh-key" not found hypershift_framework.go:546: archiving /logs/artifacts/TestCreateClusterHABreakGlassCredentials/hostedcluster-ha-break-glass-creds-t7qkf to /logs/artifacts/TestCreateClusterHABreakGlassCredentials/hostedcluster.tar.gz

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-6757m/node-pool-vdlz5 in 45s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-vdlz5 util.go:3158: Failed to wait for HostedCluster e2e-clusters-6757m/node-pool-vdlz5 to have valid conditions in 2s: context deadline exceeded eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-6757m/node-pool-vdlz5 invalid at RV 143641 after 2s: eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.0.0-0.ci-2026-06-30-165442-test-ci-op-86dcqx12-latest) eventually.go:228: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion eventually.go:228: - incorrect condition: wanted DataPlaneConnectionAvailable=Unknown, got DataPlaneConnectionAvailable=True: AsExpected(All is well) eventually.go:228: - incorrect condition: wanted ControlPlaneConnectionAvailable=Unknown, got ControlPlaneConnectionAvailable=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-06-30-165442-test-ci-op-86dcqx12-latest) hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called

nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-ntomachineconfig-replace in 7m54s nodepool_test.go:429: Successfully waited for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-ntomachineconfig-replace to have correct status in 0s util.go:499: Successfully waited for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-ntomachineconfig-replace to start config update in 15s util.go:515: Successfully waited for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-ntomachineconfig-replace to finish config update in 11m40s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-vdlz5-test-ntomachineconfig-replace to be ready in 25ms util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-ntomachineconfig-replace in 0s nodepool_test.go:429: Successfully waited for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-ntomachineconfig-replace to have correct status in 0s

util.go:826: Leader election failure detected in container manager in pod capi-provider-54cdd745d8-8h24l util.go:829: Container control-plane-operator in pod control-plane-operator-d8598665b-xtsq5 has a restartCount > 0 (3) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-68f6b6dc68-frflt has a restartCount > 0 (3)

nodepool_machineconfig_test.go:54: Starting test NodePoolMachineconfigRolloutTest nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-machineconfig in 6m9s nodepool_test.go:429: Successfully waited for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-machineconfig to have correct status in 0s util.go:499: Successfully waited for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-machineconfig to start config update in 15s util.go:515: Successfully waited for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-machineconfig to finish config update in 11m40s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/machineconfig-update-checker-replace to be ready in 25ms util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-machineconfig in 0s nodepool_test.go:429: Successfully waited for NodePool e2e-clusters-6757m/node-pool-vdlz5-test-machineconfig to have correct status in 0s

util.go:826: Leader election failure detected in container manager in pod capi-provider-54cdd745d8-8h24l util.go:829: Container control-plane-operator in pod control-plane-operator-d8598665b-xtsq5 has a restartCount > 0 (3) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-68f6b6dc68-frflt has a restartCount > 0 (3)

control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-86dcqx12/release@sha256:75c3af1a030259b6769961ab287403178d0575d77633b41844c0c202facdb0ef, toImage: registry.build01.ci.openshift.org/ci-op-86dcqx12/release@sha256:f033ebd17b32cd10962fabdf60ca06bea44396676e3897daeec00d958c48ed00 hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-h7dmp/control-plane-upgrade-m5h9p in 10s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-m5h9p upgrade_safe_check.go:87: UpgradeSafeFieldCheck: latch engaged for status.controlPlaneVersion util.go:3158: Successfully waited for HostedCluster e2e-clusters-h7dmp/control-plane-upgrade-m5h9p to have valid conditions in 0s hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called

util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-h7dmp/control-plane-upgrade-m5h9p 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 control_plane_upgrade_test.go:43: Starting version: 5.0.0-0.ci-2026-06-25-122017 control_plane_upgrade_test.go:53: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-86dcqx12/release@sha256:f033ebd17b32cd10962fabdf60ca06bea44396676e3897daeec00d958c48ed00 util.go:620: Successfully waited for HostedCluster e2e-clusters-h7dmp/control-plane-upgrade-m5h9p to rollout in 30s

util.go:826: Leader election failure detected in container manager in pod capi-provider-587f58546-fcml4 util.go:829: Container control-plane-operator in pod control-plane-operator-64b984588f-qxh5s has a restartCount > 0 (3) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-59978f5f44-8kgwh has a restartCount > 0 (3)