PR #9031 - 07-18 00:28

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

599
Total Tests
561
Passed
8
Failed
30
Skipped

Failed Tests

TestCreateCluster
50m24.25s
create_cluster_test.go:47: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-5f2s9/create-cluster-65wtw in 25s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster create-cluster-65wtw util.go:3158: Successfully waited for HostedCluster e2e-clusters-5f2s9/create-cluster-65wtw to have valid conditions in 0s hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called
TestCreateCluster/Main
20m56.5s
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5f2s9/create-cluster-65wtw 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-5f2s9/create-cluster-65wtw in 0s util.go:322: Successfully waited for kubeconfig secret to have data in 0s
TestCreateCluster/Main/EnsureGlobalPullSecret
3m35.39s
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5f2s9/create-cluster-65wtw 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 25ms util.go:2004: NodePool replicas: 1 util.go:2175: Waiting for nodes to stabilize after pull secret update util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-5f2s9/create-cluster-65wtw-us-east-1a in 0s util.go:2207: Deleting the additional-pull-secret secret in the DataPlane util.go:2226: Waiting for nodes to stabilize after pull secret deletion util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-5f2s9/create-cluster-65wtw-us-east-1a in 0s
TestCreateCluster/Main/EnsureGlobalPullSecret/When_management-cluster_hostedCluster.Spec.PullSecret_is_updated_in-place_it_should_propagate_to_guest_without_rollout
2m30.02s
util.go:2021: Reading management-cluster pull secret e2e-clusters-5f2s9/create-cluster-65wtw-pull-secret util.go:2057: Patching management-cluster pull secret with dummy auth entry util.go:2062: Waiting for openshift-config/pull-secret to update in guest cluster util.go:2069: Timed out after 150.001s. openshift-config/pull-secret did not propagate dummy entry Expected <bool>: false to be true util.go:2032: Restoring original management-cluster pull secret data
TestNodePool
0s
TestNodePool/HostedCluster0
1h6m19.5s
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-8hs5j/node-pool-7zvvl in 37s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-7zvvl util.go:3158: Failed to wait for HostedCluster e2e-clusters-8hs5j/node-pool-7zvvl to have valid conditions in 2s: context deadline exceeded eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-8hs5j/node-pool-7zvvl invalid at RV 150560 after 2s: eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.0.0-0.ci-2026-07-18-004204-test-ci-op-bwq9znkt-latest) eventually.go:228: - incorrect condition: wanted ControlPlaneConnectionAvailable=Unknown, got ControlPlaneConnectionAvailable=True: AsExpected(All is well) 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 ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 5.0.0-0.ci-2026-07-18-004204-test-ci-op-bwq9znkt-latest) 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-8hs5j/node-pool-7zvvl 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/TestNodePoolInPlaceUpgrade
28m54.03s
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-8hs5j/node-pool-7zvvl-test-inplaceupgrade in 8m51s nodepool_test.go:431: Failed to wait for NodePool e2e-clusters-8hs5j/node-pool-7zvvl-test-inplaceupgrade to have correct status in 20m0s: context deadline exceeded eventually.go:225: observed *v1beta1.NodePool e2e-clusters-8hs5j/node-pool-7zvvl-test-inplaceupgrade invalid at RV 106625 after 20m0s: incorrect condition: wanted ReachedIgnitionEndpoint=True, got ReachedIgnitionEndpoint=False: ignitionNotReached