Failed Tests
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-p4l2g/autoscaling-z4ms6 in 2m28s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-z4ms6
util.go:2949: Successfully waited for HostedCluster e2e-clusters-p4l2g/autoscaling-z4ms6 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-p4l2g/autoscaling-z4ms6 in 2m54.05s
util.go:301: Successfully waited for kubeconfig secret to have data in 75ms
eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-z4ms6.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 17.5s
util.go:565: Successfully waited for 1 nodes to become ready in 9m15.05s
util.go:598: Successfully waited for HostedCluster e2e-clusters-p4l2g/autoscaling-z4ms6 to rollout in 2m42.075s
util.go:2949: Successfully waited for HostedCluster e2e-clusters-p4l2g/autoscaling-z4ms6 to have valid conditions in 50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-p4l2g/autoscaling-z4ms6 in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
util.go:782: Container controller in pod cloud-network-config-controller-87bb6cd78-r6zwg has a restartCount > 0 (5)
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-r77hf/azure-scheduler-s88d6 in 2m20s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-s88d6
util.go:2949: Successfully waited for HostedCluster e2e-clusters-r77hf/azure-scheduler-s88d6 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-r77hf/azure-scheduler-s88d6 in 3m6.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-s88d6.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 12.25s
util.go:565: Successfully waited for 2 nodes to become ready in 9m30.125s
util.go:598: Successfully waited for HostedCluster e2e-clusters-r77hf/azure-scheduler-s88d6 to rollout in 3m48.05s
util.go:2949: Successfully waited for HostedCluster e2e-clusters-r77hf/azure-scheduler-s88d6 to have valid conditions in 50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-r77hf/azure-scheduler-s88d6 in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
util.go:782: Container controller in pod cloud-network-config-controller-7bb99576d9-dk7n8 has a restartCount > 0 (5)
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-p5bcg/create-cluster-ts2m9 in 2m33s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-ts2m9
util.go:2949: Successfully waited for HostedCluster e2e-clusters-p5bcg/create-cluster-ts2m9 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-p5bcg/create-cluster-ts2m9 in 2m33.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-create-cluster-ts2m9.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 27.575s
util.go:565: Successfully waited for 2 nodes to become ready in 9m15.05s
util.go:598: Successfully waited for HostedCluster e2e-clusters-p5bcg/create-cluster-ts2m9 to rollout in 4m27.05s
util.go:2949: Successfully waited for HostedCluster e2e-clusters-p5bcg/create-cluster-ts2m9 to have valid conditions in 50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-p5bcg/create-cluster-ts2m9 in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
util.go:782: Container controller in pod cloud-network-config-controller-668dd54948-h55hh has a restartCount > 0 (6)
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9zbkd/custom-config-96qzs in 2m17s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-96qzs
util.go:2949: Successfully waited for HostedCluster e2e-clusters-9zbkd/custom-config-96qzs 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-9zbkd/custom-config-96qzs in 2m39.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-custom-config-96qzs.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-custom-config-96qzs.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-custom-config-96qzs.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-custom-config-96qzs.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-custom-config-96qzs.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-custom-config-96qzs.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-custom-config-96qzs.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF
util.go:363: Successfully waited for a successful connection to the guest API server in 1m33.1s
util.go:565: Successfully waited for 2 nodes to become ready in 8m45.35s
util.go:598: Successfully waited for HostedCluster e2e-clusters-9zbkd/custom-config-96qzs to rollout in 7m21.05s
util.go:2949: Successfully waited for HostedCluster e2e-clusters-9zbkd/custom-config-96qzs to have valid conditions in 50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9zbkd/custom-config-96qzs in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
util.go:782: Container controller in pod cloud-network-config-controller-78f9dd4c68-xppmg has a restartCount > 0 (6)
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-jx4n2/node-pool-x4vxr in 2m16s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-x4vxr
util.go:2949: Failed to wait for HostedCluster e2e-clusters-jx4n2/node-pool-x4vxr to have valid conditions in 2s: context deadline exceeded
eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-jx4n2/node-pool-x4vxr invalid at RV 69441 after 2s:
eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion
eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 4.22.0-0.ci-2026-01-10-022456-test-ci-op-fqrj10p9-latest)
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-10-022456-test-ci-op-fqrj10p9-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-jx4n2/node-pool-x4vxr in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
util.go:363: Successfully waited for a successful connection to the guest API server in 50ms
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest
util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-inplace in 24m12.075s
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-inplace to have correct status in 50ms
util.go:474: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-inplace to start config update in 15.05s
util.go:490: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-inplace to finish config update in 8m0.05s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-x4vxr-test-ntomachineconfig-inplace to be ready in 150ms
util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-inplace in 75ms
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-inplace to have correct status in 50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jx4n2/node-pool-x4vxr in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
util.go:782: Container controller in pod cloud-network-config-controller-7c84bb8dd5-x94kv has a restartCount > 0 (11)
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest
util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-replace in 12m48.075s
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-replace to have correct status in 50ms
util.go:474: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-replace to start config update in 15.05s
util.go:490: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-replace to finish config update in 16m20.05s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-x4vxr-test-ntomachineconfig-replace to be ready in 150ms
util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-replace in 25ms
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-ntomachineconfig-replace to have correct status in 50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jx4n2/node-pool-x4vxr in 75ms
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
util.go:782: Container controller in pod cloud-network-config-controller-7c84bb8dd5-x94kv 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-jx4n2/node-pool-x4vxr-test-machineconfig in 26m33.075s
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-machineconfig to have correct status in 50ms
util.go:474: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-machineconfig to start config update in 15.05s
util.go:490: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-machineconfig to finish config update in 5m40.05s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/machineconfig-update-checker-replace to be ready in 50ms
util.go:565: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-machineconfig in 25ms
nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-jx4n2/node-pool-x4vxr-test-machineconfig to have correct status in 50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jx4n2/node-pool-x4vxr in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
util.go:782: Container controller in pod cloud-network-config-controller-7c84bb8dd5-x94kv has a restartCount > 0 (11)
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-fqrj10p9/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-fqrj10p9/release@sha256:c1062c106be03538afb4169bc81411491fbd3674ffa05331e838637bb0547d1e
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-8bdsc/control-plane-upgrade-czcsq in 2m36s
hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-czcsq
util.go:2949: Successfully waited for HostedCluster e2e-clusters-8bdsc/control-plane-upgrade-czcsq 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-8bdsc/control-plane-upgrade-czcsq in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
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-fqrj10p9/release@sha256:c1062c106be03538afb4169bc81411491fbd3674ffa05331e838637bb0547d1e
util.go:598: Successfully waited for HostedCluster e2e-clusters-8bdsc/control-plane-upgrade-czcsq to rollout in 75ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8bdsc/control-plane-upgrade-czcsq in 50ms
util.go:301: Successfully waited for kubeconfig secret to have data in 50ms
util.go:782: Container controller in pod cloud-network-config-controller-54fc8ccd48-v6rsm 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-8bdsc-control-plane-upgrade-czcsq/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-8bdsc-control-plane-upgrade-czcsq/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)