Failed Tests
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-w26cn/autoscaling-fk9l2 in 2m40s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-fk9l2
util.go:2949: Successfully waited for HostedCluster e2e-clusters-w26cn/autoscaling-fk9l2 to have valid conditions in 50ms
hypershift_framework.go:249: skipping postTeardown()
hypershift_framework.go:230: skipping teardown, already called
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-w26cn/autoscaling-fk9l2 in 2m42.05s
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-fk9l2.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-autoscaling-fk9l2.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout
util.go:363: Successfully waited for a successful connection to the guest API server in 33.6s
util.go:565: Successfully waited for 1 nodes to become ready in 10m15.05s
util.go:598: Successfully waited for HostedCluster e2e-clusters-w26cn/autoscaling-fk9l2 to rollout in 3m45.025s
util.go:2949: Successfully waited for HostedCluster e2e-clusters-w26cn/autoscaling-fk9l2 to have valid conditions in 25ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-w26cn/autoscaling-fk9l2 in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:782: Container controller in pod cloud-network-config-controller-57d5c4df6f-7l9h5 has a restartCount > 0 (5)
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-krkwv/azure-scheduler-l7hfb in 2m52s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-l7hfb
util.go:2949: Successfully waited for HostedCluster e2e-clusters-krkwv/azure-scheduler-l7hfb to have valid conditions in 25ms
hypershift_framework.go:249: skipping postTeardown()
hypershift_framework.go:230: skipping teardown, already called
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-krkwv/azure-scheduler-l7hfb in 2m45.05s
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-l7hfb.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout
util.go:363: Successfully waited for a successful connection to the guest API server in 30.225s
util.go:565: Successfully waited for 2 nodes to become ready in 9m39.05s
util.go:598: Successfully waited for HostedCluster e2e-clusters-krkwv/azure-scheduler-l7hfb to rollout in 2m21.1s
util.go:2949: Successfully waited for HostedCluster e2e-clusters-krkwv/azure-scheduler-l7hfb to have valid conditions in 25ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-krkwv/azure-scheduler-l7hfb in 25ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:782: Container controller in pod cloud-network-config-controller-69bfbbf9cf-dlrmq has a restartCount > 0 (5)
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-m8nnp/create-cluster-pcrv6 in 2m41s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-pcrv6
util.go:2949: Successfully waited for HostedCluster e2e-clusters-m8nnp/create-cluster-pcrv6 to have valid conditions in 50ms
hypershift_framework.go:249: skipping postTeardown()
hypershift_framework.go:230: skipping teardown, already called
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m8nnp/create-cluster-pcrv6 in 3m15.05s
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-pcrv6.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout
util.go:363: Successfully waited for a successful connection to the guest API server in 10.175s
util.go:565: Successfully waited for 2 nodes to become ready in 9m21.075s
util.go:598: Successfully waited for HostedCluster e2e-clusters-m8nnp/create-cluster-pcrv6 to rollout in 3m54.05s
util.go:2949: Successfully waited for HostedCluster e2e-clusters-m8nnp/create-cluster-pcrv6 to have valid conditions in 25ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m8nnp/create-cluster-pcrv6 in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:782: Container controller in pod cloud-network-config-controller-7c6885db5f-2bztr has a restartCount > 0 (5)
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-7fbt5/custom-config-s5kxx in 2m45s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-s5kxx
util.go:2949: Successfully waited for HostedCluster e2e-clusters-7fbt5/custom-config-s5kxx to have valid conditions in 25ms
hypershift_framework.go:249: skipping postTeardown()
hypershift_framework.go:230: skipping teardown, already called
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7fbt5/custom-config-s5kxx in 2m54.075s
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-s5kxx.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout
util.go:363: Successfully waited for a successful connection to the guest API server in 37.9s
util.go:565: Successfully waited for 2 nodes to become ready in 9m0.075s
util.go:598: Successfully waited for HostedCluster e2e-clusters-7fbt5/custom-config-s5kxx to rollout in 7m24.05s
util.go:2949: Successfully waited for HostedCluster e2e-clusters-7fbt5/custom-config-s5kxx to have valid conditions in 50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7fbt5/custom-config-s5kxx in 25ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:782: Container controller in pod cloud-network-config-controller-79b479db49-r9g6v has a restartCount > 0 (6)
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-b7w2d/node-pool-bt6xp in 2m39s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-bt6xp
util.go:2949: Failed to wait for HostedCluster e2e-clusters-b7w2d/node-pool-bt6xp to have valid conditions in 2s: context deadline exceeded
eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-b7w2d/node-pool-bt6xp invalid at RV 70163 after 2s:
eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion
eventually.go:227: - incorrect condition: wanted DataPlaneConnectionAvailable=Unknown, got DataPlaneConnectionAvailable=True: AsExpected(All is well)
eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 4.22.0-0.ci-2026-01-09-104153-test-ci-op-j5f7j3py-latest)
eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 4.22.0-0.ci-2026-01-09-104153-test-ci-op-j5f7j3py-latest)
hypershift_framework.go:249: skipping postTeardown()
hypershift_framework.go:230: skipping teardown, already called
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b7w2d/node-pool-bt6xp in 25ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:363: Successfully waited for a successful connection to the guest API server in 25ms
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest
util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-inplace in 23m0.05s
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-inplace to have correct status in 25ms
util.go:474: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-inplace to start config update in 15.05s
util.go:490: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-inplace to finish config update in 8m0.025s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-bt6xp-test-ntomachineconfig-inplace to be ready in 25ms
util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-inplace in 75ms
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-inplace to have correct status in 25ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b7w2d/node-pool-bt6xp in 75ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:782: Container controller in pod cloud-network-config-controller-855b488f66-vlcqn has a restartCount > 0 (10)
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest
util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-replace in 12m48.275s
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-replace to have correct status in 50ms
util.go:474: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-replace to start config update in 15.05s
util.go:490: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-replace to finish config update in 18m0.025s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-bt6xp-test-ntomachineconfig-replace to be ready in 75ms
util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-replace in 25ms
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-ntomachineconfig-replace to have correct status in 25ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b7w2d/node-pool-bt6xp in 75ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:782: Container controller in pod cloud-network-config-controller-855b488f66-vlcqn has a restartCount > 0 (10)
nodepool_machineconfig_test.go:54: Starting test NodePoolMachineconfigRolloutTest
util.go:565: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-machineconfig in 8m30.05s
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-machineconfig to have correct status in 25ms
util.go:474: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-machineconfig to start config update in 15.025s
util.go:490: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-machineconfig to finish config update in 19m40.025s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/machineconfig-update-checker-replace to be ready in 125ms
util.go:565: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-machineconfig in 25ms
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-b7w2d/node-pool-bt6xp-test-machineconfig to have correct status in 25ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b7w2d/node-pool-bt6xp in 75ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:782: Container controller in pod cloud-network-config-controller-855b488f66-vlcqn has a restartCount > 0 (10)
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-59qxx/node-pool-b22xx in 2m29s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-b22xx
util.go:2949: Successfully waited for HostedCluster e2e-clusters-59qxx/node-pool-b22xx to have valid conditions in 25ms
hypershift_framework.go:249: skipping postTeardown()
hypershift_framework.go:230: skipping teardown, already called
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-59qxx/node-pool-b22xx in 3m0.05s
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-b22xx.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout
util.go:363: Successfully waited for a successful connection to the guest API server in 24.3s
util.go:565: Successfully waited for 0 nodes to become ready in 75ms
util.go:2949: Successfully waited for HostedCluster e2e-clusters-59qxx/node-pool-b22xx to have valid conditions in 8m15.075s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-59qxx/node-pool-b22xx in 25ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:782: Container controller in pod cloud-network-config-controller-77fc5b76ff-x8ntx has a restartCount > 0 (3)
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-j5f7j3py/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-j5f7j3py/release@sha256:6be5298dc63d9e327a6aea4621431c1ee1762b90f791f70dbbcde65bb588b535
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9bggp/control-plane-upgrade-px5j2 in 2m46s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-px5j2
util.go:2949: Successfully waited for HostedCluster e2e-clusters-9bggp/control-plane-upgrade-px5j2 to have valid conditions in 25ms
hypershift_framework.go:249: skipping postTeardown()
hypershift_framework.go:230: skipping teardown, already called
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9bggp/control-plane-upgrade-px5j2 in 25ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:363: Successfully waited for a successful connection to the guest API server in 25ms
control_plane_upgrade_test.go:52: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-j5f7j3py/release@sha256:6be5298dc63d9e327a6aea4621431c1ee1762b90f791f70dbbcde65bb588b535
util.go:598: Successfully waited for HostedCluster e2e-clusters-9bggp/control-plane-upgrade-px5j2 to rollout in 75ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9bggp/control-plane-upgrade-px5j2 in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 25ms
util.go:782: Container controller in pod cloud-network-config-controller-b6c964774-ld9qc has a restartCount > 0 (9)
util.go:638: Failed to wait for control plane components to complete rollout in 30m0s: context deadline exceeded
eventually.go:383: observed invalid **v1beta1.ControlPlaneComponent state after 30m0s
eventually.go:400: - observed **v1beta1.ControlPlaneComponent e2e-clusters-9bggp-control-plane-upgrade-px5j2/cluster-network-operator invalid: incorrect condition: wanted RolloutComplete=True, got RolloutComplete=False: WaitingForOperands(deployment cloud-network-config-controller is not ready)
util.go:638: *v1beta1.ControlPlaneComponent e2e-clusters-9bggp-control-plane-upgrade-px5j2/cluster-network-operator conditions:
util.go:638: Available=True: AsExpected(Deployment cluster-network-operator is available)
util.go:638: RolloutComplete=False: WaitingForOperands(deployment cloud-network-config-controller is not ready)