PR #7192 - 11-10 17:35

create_cluster_test.go:2207: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-knmwp/create-cluster-x7wvw in 1m9s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-x7wvw util.go:2835: Successfully waited for HostedCluster e2e-clusters-knmwp/create-cluster-x7wvw to have valid conditions in 0s hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called

util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-knmwp/create-cluster-x7wvw in 0s util.go:297: Successfully waited for kubeconfig secret to have data in 0s util.go:359: Successfully waited for a successful connection to the guest API server in 0s util.go:2835: Successfully waited for HostedCluster e2e-clusters-knmwp/create-cluster-x7wvw to have valid conditions in 0s

util.go:1133: Connecting to kubernetes endpoint on: https://172.20.0.1:6443 util.go:1164: cluster api pod was unexpectedly not allowed to reach the management KAS. stdOut: . stdErr: command terminated with exit code 28

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-crz6f/node-pool-5ffzv in 39s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-5ffzv util.go:2835: Failed to wait for HostedCluster e2e-clusters-crz6f/node-pool-5ffzv to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-crz6f/node-pool-5ffzv invalid at RV 107307 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 4.21.0-0.ci-2025-11-10-175619-test-ci-op-6s7pl2ny-latest) eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 4.21.0-0.ci-2025-11-10-175619-test-ci-op-6s7pl2ny-latest) eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called

nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest util.go:541: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-crz6f/node-pool-5ffzv-test-machineconfig in 5m33s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-crz6f/node-pool-5ffzv-test-machineconfig to have correct status in 0s util.go:455: Successfully waited for NodePool e2e-clusters-crz6f/node-pool-5ffzv-test-machineconfig to start config update in 15s util.go:471: Successfully waited for NodePool e2e-clusters-crz6f/node-pool-5ffzv-test-machineconfig to finish config update in 7m0s nodepool_machineconfig_test.go:166: Successfully waited for all pods in the DaemonSet kube-system/machineconfig-update-checker-replace to be ready in 45s util.go:541: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-crz6f/node-pool-5ffzv-test-machineconfig in 0s eventually.go:104: Failed to get *v1beta1.NodePool: client rate limiter Wait returned an error: context deadline exceeded nodepool_test.go:358: Failed to wait for NodePool e2e-clusters-crz6f/node-pool-5ffzv-test-machineconfig to have correct status in 10m0s: context deadline exceeded eventually.go:224: observed *v1beta1.NodePool e2e-clusters-crz6f/node-pool-5ffzv-test-machineconfig invalid at RV 88442 after 10m0s: incorrect condition: wanted ReachedIgnitionEndpoint=True, got ReachedIgnitionEndpoint=False: ignitionNotReached