Failed Tests
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-ckhv7/autoscaling-8s8z4 in 2m35s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-8s8z4
util.go:2835: Failed to wait for HostedCluster e2e-clusters-ckhv7/autoscaling-8s8z4 to have valid conditions in 2s: context deadline exceeded
eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-ckhv7/autoscaling-8s8z4 invalid at RV 35149 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 ClusterVersionProgressing=False, got ClusterVersionProgressing=True: ClusterOperatorsNotAvailable(Unable to apply 4.21.0-0.ci-2025-11-06-031433-test-ci-op-4sy74mc4-latest: some cluster operators are not available)
eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=True, got ClusterVersionAvailable=False: FromClusterVersion
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-ckhv7/autoscaling-8s8z4 in 3m36.05s
util.go:297: Successfully waited for kubeconfig secret to have data in 50ms
util.go:359: Successfully waited for a successful connection to the guest API server in 9.35s
eventually.go:258: Failed to get **v1.Node: context deadline exceeded
util.go:541: Failed to wait for 1 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 1 nodes, got 0
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-67z6b/azure-scheduler-92z6v in 2m49s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-92z6v
util.go:2835: Failed to wait for HostedCluster e2e-clusters-67z6b/azure-scheduler-92z6v to have valid conditions in 2s: context deadline exceeded
eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-67z6b/azure-scheduler-92z6v invalid at RV 34944 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.21.0-0.ci-2025-11-06-031433-test-ci-op-4sy74mc4-latest: some cluster operators are not available)
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-67z6b/azure-scheduler-92z6v in 2m54.05s
util.go:297: Successfully waited for kubeconfig secret to have data in 50ms
eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-92z6v.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-92z6v.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout
util.go:359: Successfully waited for a successful connection to the guest API server in 37.45s
eventually.go:258: Failed to get **v1.Node: context deadline exceeded
util.go:541: 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:423: Successfully created hostedcluster e2e-clusters-vhzx7/create-cluster-6qcqq in 2m39s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-6qcqq
util.go:2835: Failed to wait for HostedCluster e2e-clusters-vhzx7/create-cluster-6qcqq to have valid conditions in 2s: context deadline exceeded
eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-vhzx7/create-cluster-6qcqq invalid at RV 35467 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 ClusterVersionProgressing=False, got ClusterVersionProgressing=True: ClusterOperatorsNotAvailable(Unable to apply 4.21.0-0.ci-2025-11-06-031433-test-ci-op-4sy74mc4-latest: some cluster operators are not available)
eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=True, got ClusterVersionAvailable=False: FromClusterVersion
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-vhzx7/create-cluster-6qcqq in 3m12.05s
util.go:297: Successfully waited for kubeconfig secret to have data in 50ms
eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-6qcqq.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout
util.go:359: Successfully waited for a successful connection to the guest API server in 27.65s
eventually.go:258: Failed to get **v1.Node: context deadline exceeded
util.go:541: 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:423: Successfully created hostedcluster e2e-clusters-wdfvp/custom-config-b4zkl in 2m42s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-b4zkl
util.go:2835: Failed to wait for HostedCluster e2e-clusters-wdfvp/custom-config-b4zkl to have valid conditions in 2s: context deadline exceeded
eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-wdfvp/custom-config-b4zkl invalid at RV 35121 after 2s:
eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=True, got ClusterVersionSucceeding=False: ClusterOperatorsNotAvailable(Cluster operators dns, kube-storage-version-migrator, monitoring, 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.21.0-0.ci-2025-11-06-031433-test-ci-op-4sy74mc4-latest: some cluster operators are not available)
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-wdfvp/custom-config-b4zkl in 3m9.075s
util.go:297: Successfully waited for kubeconfig secret to have data in 50ms
eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-b4zkl.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout
util.go:359: Successfully waited for a successful connection to the guest API server in 47.55s
eventually.go:258: Failed to get **v1.Node: context deadline exceeded
util.go:541: 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:423: Successfully created hostedcluster e2e-clusters-7s5pq/node-pool-zzljq in 2m47s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-zzljq
util.go:2835: Successfully waited for HostedCluster e2e-clusters-7s5pq/node-pool-zzljq to have valid conditions in 75ms
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-7s5pq/node-pool-zzljq in 50ms
util.go:297: Successfully waited for kubeconfig secret to have data in 50ms
util.go:359: Successfully waited for a successful connection to the guest API server in 25ms
nodepool_mirrorconfigs_test.go:61: Starting test MirrorConfigsTest
util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-7s5pq/node-pool-zzljq-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
eventually.go:258: Failed to get **v1.Node: context deadline exceeded
util.go:541: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-7s5pq/node-pool-zzljq-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_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest
eventually.go:258: Failed to get **v1.Node: context deadline exceeded
util.go:541: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-7s5pq/node-pool-zzljq-test-ntomachineconfig-replace 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
eventually.go:258: Failed to get **v1.Node: context deadline exceeded
util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-7s5pq/node-pool-zzljq-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:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-7s5pq/node-pool-zzljq-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.
util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-7s5pq/node-pool-zzljq-vt7b5 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:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-7s5pq/node-pool-zzljq-cgs46 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:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-7s5pq/node-pool-zzljq-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
util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-7s5pq/node-pool-zzljq-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
eventually.go:258: Failed to get **v1.Node: context deadline exceeded
util.go:541: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-7s5pq/node-pool-zzljq-test-rolling-upgrade 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:423: Successfully created hostedcluster e2e-clusters-mnglz/node-pool-z8cq8 in 2m41s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-z8cq8
util.go:2835: Successfully waited for HostedCluster e2e-clusters-mnglz/node-pool-z8cq8 to have valid conditions in 75ms
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-mnglz/node-pool-z8cq8 in 50ms
util.go:297: Successfully waited for kubeconfig secret to have data in 50ms
util.go:359: Successfully waited for a successful connection to the guest API server in 50ms
nodepool_additionalTrustBundlePropagation_test.go:39: Starting AdditionalTrustBundlePropagationTest.
eventually.go:258: Failed to get **v1.Node: context deadline exceeded
util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-mnglz/node-pool-z8cq8-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
control_plane_upgrade_test.go:26: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-4sy74mc4/release@sha256:2ebf274b990baf672f381029c76515a1dc3c55d49328e4025c91dc44c6872410, toImage: registry.build01.ci.openshift.org/ci-op-4sy74mc4/release@sha256:6704904707e9f569ef213942f4bec32ce70c93f09187a6a99d4895a9a4eb1c55
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-bx4th/control-plane-upgrade-d4hhm in 2m33s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-d4hhm
util.go:2835: Failed to wait for HostedCluster e2e-clusters-bx4th/control-plane-upgrade-d4hhm to have valid conditions in 2s: context deadline exceeded
eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-bx4th/control-plane-upgrade-d4hhm invalid at RV 37089 after 2s:
eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=False, got ClusterVersionProgressing=True: ClusterOperatorsNotAvailable(Unable to apply 4.21.0-0.ci-2025-11-05-190554: some cluster operators are not available)
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
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-bx4th/control-plane-upgrade-d4hhm in 4m6.075s
util.go:297: Successfully waited for kubeconfig secret to have data in 50ms
eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-control-plane-upgrade-d4hhm.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF
util.go:359: Successfully waited for a successful connection to the guest API server in 28.075s
util.go:541: 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