PR #9063 - 07-22 18:16

create_cluster_test.go:47: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-8pr2c/create-cluster-kcn67 in 51s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster create-cluster-kcn67 util.go:3185: Successfully waited for HostedCluster e2e-clusters-8pr2c/create-cluster-kcn67 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-8pr2c/create-cluster-kcn67 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 create_cluster_test.go:87: fetching mgmt kubeconfig util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8pr2c/create-cluster-kcn67 in 0s util.go:322: Successfully waited for kubeconfig secret to have data in 0s

util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8pr2c/create-cluster-kcn67 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 util.go:2004: NodePool replicas: 1 util.go:2195: Waiting for nodes to stabilize after pull secret update util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-8pr2c/create-cluster-kcn67-us-east-1a in 0s util.go:2227: Deleting the additional-pull-secret secret in the DataPlane util.go:2246: Waiting for nodes to stabilize after pull secret deletion util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-8pr2c/create-cluster-kcn67-us-east-1a in 0s util.go:2252: Expected success, but got an error: <*fmt.wrapError | 0xc00493b160>: failed to wait for DaemonSet global-pull-secret-syncer to be ready: context deadline exceeded { msg: "failed to wait for DaemonSet global-pull-secret-syncer to be ready: context deadline exceeded", err: <context.deadlineExceededError>{}, } util.go:2031: Restoring original management-cluster pull secret data

util.go:4098: Creating a pod which uses the restricted image util.go:4123: Attempt 1/3: Creating pod util.go:4128: Successfully created pod global-pull-secret-success-pod in namespace kube-system on attempt 1 util.go:4149: Created pod global-pull-secret-success-pod in namespace kube-system util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4166: Pod phase: Pending, shouldFail: false util.go:4173: Timed out after 420.001s. pod is not running Expected success, but got an error: <*errors.errorString | 0xc006ba34a0>: pod is not running yet, current phase: Pending { s: "pod is not running yet, current phase: Pending", }

util.go:2251: Waiting for GlobalPullSecretDaemonSet to process the deletion and stabilize all nodes util.go:2284: Waiting for global-pull-secret-syncer DaemonSet to be ready (min expected: 1) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2295: DaemonSet global-pull-secret-syncer status has not observed generation 5 yet (current 4) util.go:2290: Failed to get DaemonSet global-pull-secret-syncer: context deadline exceeded testing.go:1811: test executed panic(nil) or runtime.Goexit: subtest may have called FailNow on a parent test

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-mhn4x/karpenter-upgrade-control-plane-2lcgj in 1m0s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster karpenter-upgrade-control-plane-2lcgj util.go:3185: Successfully waited for HostedCluster e2e-clusters-mhn4x/karpenter-upgrade-control-plane-2lcgj 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-mhn4x/karpenter-upgrade-control-plane-2lcgj 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-tw1rmnx6/release@sha256:9e4894529668fec35e364104cdd3346385f0d04f0ee2209bd5b96b5a1910a6e4, toImage: registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:e38554f48015bffc82abc779889653e4848c19bdd1a6b1a21e479e14aea1c1aa karpenter_control_plane_upgrade_test.go:64: Unexpected error: <*fmt.wrapError | 0xc0087dea00>: failed to extract release metadata: failed to obtain root manifest for registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:e38554f48015bffc82abc779889653e4848c19bdd1a6b1a21e479e14aea1c1aa: received unexpected HTTP status: 504 Gateway Time-out { msg: "failed to extract release metadata: failed to obtain root manifest for registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:e38554f48015bffc82abc779889653e4848c19bdd1a6b1a21e479e14aea1c1aa: received unexpected HTTP status: 504 Gateway Time-out", err: <*fmt.wrapError | 0xc0087de9e0>{ msg: "failed to obtain root manifest for registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:e38554f48015bffc82abc779889653e4848c19bdd1a6b1a21e479e14aea1c1aa: received unexpected HTTP status: 504 Gateway Time-out", err: <*client.UnexpectedHTTPStatusError | 0xc008e3f930>{ Status: "504 Gateway Time-out", }, }, } occurred

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-7txnb/node-pool-rsc9j in 40s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-rsc9j util.go:3185: Failed to wait for HostedCluster e2e-clusters-7txnb/node-pool-rsc9j to have valid conditions in 2s: context deadline exceeded eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-7txnb/node-pool-rsc9j invalid at RV 146026 after 2s: 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-22-183611-test-ci-op-tw1rmnx6-latest) eventually.go:228: - incorrect condition: wanted ControlPlaneConnectionAvailable=Unknown, got ControlPlaneConnectionAvailable=True: AsExpected(All is well) eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.0.0-0.ci-2026-07-22-183611-test-ci-op-tw1rmnx6-latest) 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-7txnb/node-pool-rsc9j 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

nodepool_upgrade_test.go:99: starting test NodePoolUpgradeTest 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-7txnb/node-pool-rsc9j-test-inplaceupgrade in 5m21s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-7txnb/node-pool-rsc9j-test-inplaceupgrade to have correct status in 0s nodepool_upgrade_test.go:173: failed to get release info for previous image Unexpected error: <*fmt.wrapError | 0xc005fca500>: failed to extract release metadata: failed to obtain root manifest for registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:9e4894529668fec35e364104cdd3346385f0d04f0ee2209bd5b96b5a1910a6e4: unable to retrieve source image registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:9e4894529668fec35e364104cdd3346385f0d04f0ee2209bd5b96b5a1910a6e4 manifest #1 from manifest list: received unexpected HTTP status: 504 Gateway Time-out { msg: "failed to extract release metadata: failed to obtain root manifest for registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:9e4894529668fec35e364104cdd3346385f0d04f0ee2209bd5b96b5a1910a6e4: unable to retrieve source image registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:9e4894529668fec35e364104cdd3346385f0d04f0ee2209bd5b96b5a1910a6e4 manifest #1 from manifest list: received unexpected HTTP status: 504 Gateway Time-out", err: <*fmt.wrapError | 0xc005fca4e0>{ msg: "failed to obtain root manifest for registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:9e4894529668fec35e364104cdd3346385f0d04f0ee2209bd5b96b5a1910a6e4: unable to retrieve source image registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:9e4894529668fec35e364104cdd3346385f0d04f0ee2209bd5b96b5a1910a6e4 manifest #1 from manifest list: received unexpected HTTP status: 504 Gateway Time-out", err: <*fmt.wrapError | 0xc005fca4c0>{ msg: "unable to retrieve source image registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:9e4894529668fec35e364104cdd3346385f0d04f0ee2209bd5b96b5a1910a6e4 manifest #1 from manifest list: received unexpected HTTP status: 504 Gateway Time-out", err: <*client.UnexpectedHTTPStatusError | 0xc0082488c0>{ Status: "504 Gateway Time-out", }, }, }, } occurred

control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:9e4894529668fec35e364104cdd3346385f0d04f0ee2209bd5b96b5a1910a6e4, toImage: registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:e38554f48015bffc82abc779889653e4848c19bdd1a6b1a21e479e14aea1c1aa hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-llp8q/control-plane-upgrade-prjlr in 1m13s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-prjlr util.go:3185: Successfully waited for HostedCluster e2e-clusters-llp8q/control-plane-upgrade-prjlr 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-llp8q/control-plane-upgrade-prjlr 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-07-20-062541 control_plane_upgrade_test.go:49: failed to set latest release image version Unexpected error: <*fmt.wrapError | 0xc001f28d40>: error looking up latest release image: failed to extract release metadata: failed to obtain root manifest for registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:e38554f48015bffc82abc779889653e4848c19bdd1a6b1a21e479e14aea1c1aa: received unexpected HTTP status: 504 Gateway Time-out { msg: "error looking up latest release image: failed to extract release metadata: failed to obtain root manifest for registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:e38554f48015bffc82abc779889653e4848c19bdd1a6b1a21e479e14aea1c1aa: received unexpected HTTP status: 504 Gateway Time-out", err: <*fmt.wrapError | 0xc001f28d20>{ msg: "failed to extract release metadata: failed to obtain root manifest for registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:e38554f48015bffc82abc779889653e4848c19bdd1a6b1a21e479e14aea1c1aa: received unexpected HTTP status: 504 Gateway Time-out", err: <*fmt.wrapError | 0xc001f28d00>{ msg: "failed to obtain root manifest for registry.build01.ci.openshift.org/ci-op-tw1rmnx6/release@sha256:e38554f48015bffc82abc779889653e4848c19bdd1a6b1a21e479e14aea1c1aa: received unexpected HTTP status: 504 Gateway Time-out", err: <*client.UnexpectedHTTPStatusError | 0xc008e45510>{ Status: "504 Gateway Time-out", }, }, }, } occurred