PR #5792 - 04-16 19:08

hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-bvk85/azure-scheduler-sxl9h in 1m35s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster azure-scheduler-sxl9h eventually.go:104: Failed to get *v1beta1.HostedCluster: client rate limiter Wait returned an error: context deadline exceeded util.go:2123: Failed to wait for HostedCluster e2e-clusters-bvk85/azure-scheduler-sxl9h to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-bvk85/azure-scheduler-sxl9h invalid at RV 21203 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=True, got ClusterVersionSucceeding=False: ClusterOperatorsNotAvailable(Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available) eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=True, got ClusterVersionAvailable=False: FromClusterVersion eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=False, got ClusterVersionProgressing=True: ClusterOperatorsNotAvailable(Unable to apply 4.19.0-0.ci-2025-04-16-192511-test-ci-op-dwn3krhm-latest: some cluster operators are not available) hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called

util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bvk85/azure-scheduler-sxl9h in 2m8.025s util.go:235: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-sxl9h.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-sxl9h.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-sxl9h.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 135.18.203.124:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-sxl9h.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF util.go:281: Successfully waited for a successful connection to the guest API server in 28.175s eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 2 nodes to become ready in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 2 nodes, got 0

hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-9j229/node-pool-5q8s4 in 1m31s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-5q8s4 util.go:2123: Successfully waited for HostedCluster e2e-clusters-9j229/node-pool-5q8s4 to have valid conditions in 25ms hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called

util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9j229/node-pool-5q8s4 in 25ms util.go:235: Successfully waited for kubeconfig secret to have data in 0s util.go:281: Successfully waited for a successful connection to the guest API server in 0s

nodepool_mirrorconfigs_test.go:61: Starting test MirrorConfigsTest eventually.go:258: Failed to get **v1.Node: Get "https://api-node-pool-5q8s4.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes?labelSelector=hypershift.openshift.io%2FnodePool%3Dnode-pool-5q8s4-test-mirrorconfigs": context deadline exceeded util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-9j229/node-pool-5q8s4-test-mirrorconfigs in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0

nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest util.go:462: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-9j229/node-pool-5q8s4-test-ntomachineconfig-inplace in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 2 nodes, got 0

nodepool_nto_performanceprofile_test.go:60: Starting test NTOPerformanceProfileTest util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-9j229/node-pool-5q8s4-test-ntoperformanceprofile in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0

nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-9j229/node-pool-5q8s4-test-inplaceupgrade in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0

nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-9j229/node-pool-5q8s4-7hcrx in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0

nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-9j229/node-pool-5q8s4-vbt6w in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0

nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest eventually.go:258: Failed to get **v1.Node: Get "https://api-node-pool-5q8s4.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes?labelSelector=hypershift.openshift.io%2FnodePool%3Dnode-pool-5q8s4-test-replaceupgrade": context deadline exceeded util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-9j229/node-pool-5q8s4-test-replaceupgrade in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0

nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-9j229/node-pool-5q8s4-test-machineconfig in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0

hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-b5cp5/node-pool-66sqf in 1m29s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-66sqf util.go:2123: Successfully waited for HostedCluster e2e-clusters-b5cp5/node-pool-66sqf to have valid conditions in 25ms hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called

util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b5cp5/node-pool-66sqf in 50ms util.go:235: Successfully waited for kubeconfig secret to have data in 75ms util.go:281: Successfully waited for a successful connection to the guest API server in 0s

nodepool_additionalTrustBundlePropagation_test.go:36: Starting AdditionalTrustBundlePropagationTest. eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-b5cp5/node-pool-66sqf-test-additional-trust-bundle-propagation in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0