PR #7405 - 01-09 09:28

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-fwr9j/autoscaling-85bkh in 2m28s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-85bkh util.go:2949: Successfully waited for HostedCluster e2e-clusters-fwr9j/autoscaling-85bkh 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-fwr9j/autoscaling-85bkh in 2m36.075s util.go:301: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-85bkh.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 23.55s util.go:565: Successfully waited for 1 nodes to become ready in 7m39.05s util.go:598: Successfully waited for HostedCluster e2e-clusters-fwr9j/autoscaling-85bkh to rollout in 4m39.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-fwr9j/autoscaling-85bkh to have valid conditions in 25ms

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fwr9j/autoscaling-85bkh 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-794d64859d-c444l has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-qbzph/azure-scheduler-8j5kg in 2m21s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-8j5kg util.go:2949: Successfully waited for HostedCluster e2e-clusters-qbzph/azure-scheduler-8j5kg 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-qbzph/azure-scheduler-8j5kg in 3m39.025s util.go:301: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-8j5kg.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 17.475s util.go:565: Successfully waited for 2 nodes to become ready in 7m36.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-qbzph/azure-scheduler-8j5kg to rollout in 3m51.075s util.go:2949: Successfully waited for HostedCluster e2e-clusters-qbzph/azure-scheduler-8j5kg to have valid conditions in 50ms

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qbzph/azure-scheduler-8j5kg 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-5bf767c44b-6w5cg has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-gx7r8/create-cluster-h78zl in 2m9s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-h78zl util.go:2949: Successfully waited for HostedCluster e2e-clusters-gx7r8/create-cluster-h78zl 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-gx7r8/create-cluster-h78zl in 2m39.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-h78zl.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.25s util.go:565: Successfully waited for 2 nodes to become ready in 7m30.05s util.go:598: Successfully waited for HostedCluster e2e-clusters-gx7r8/create-cluster-h78zl to rollout in 2m30.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-gx7r8/create-cluster-h78zl to have valid conditions in 50ms

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-gx7r8/create-cluster-h78zl 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-78f6f49b5-4tk7n has a restartCount > 0 (5)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-7qrgh/custom-config-8pzr9 in 2m30s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-8pzr9 util.go:2949: Successfully waited for HostedCluster e2e-clusters-7qrgh/custom-config-8pzr9 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-7qrgh/custom-config-8pzr9 in 2m30.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-custom-config-8pzr9.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.25s util.go:565: Successfully waited for 2 nodes to become ready in 7m3.05s util.go:598: Successfully waited for HostedCluster e2e-clusters-7qrgh/custom-config-8pzr9 to rollout in 7m54.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-7qrgh/custom-config-8pzr9 to have valid conditions in 50ms

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7qrgh/custom-config-8pzr9 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-9c8699cb5-f72ch has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-plkf9/node-pool-m5dt4 in 2m15s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-m5dt4 util.go:2949: Failed to wait for HostedCluster e2e-clusters-plkf9/node-pool-m5dt4 to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-plkf9/node-pool-m5dt4 invalid at RV 67825 after 2s: 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-094055-test-ci-op-lm6297cg-latest) eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 4.22.0-0.ci-2026-01-09-094055-test-ci-op-lm6297cg-latest) eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion 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-plkf9/node-pool-m5dt4 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

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-plkf9/node-pool-m5dt4 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-769ddfd9f-r2szr 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-plkf9/node-pool-m5dt4-test-ntomachineconfig-replace in 13m6.075s nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-plkf9/node-pool-m5dt4-test-ntomachineconfig-replace to have correct status in 50ms util.go:474: Successfully waited for NodePool e2e-clusters-plkf9/node-pool-m5dt4-test-ntomachineconfig-replace to start config update in 15.05s util.go:490: Successfully waited for NodePool e2e-clusters-plkf9/node-pool-m5dt4-test-ntomachineconfig-replace to finish config update in 15m20.025s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-m5dt4-test-ntomachineconfig-replace to be ready in 150ms util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-plkf9/node-pool-m5dt4-test-ntomachineconfig-replace in 25ms nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-plkf9/node-pool-m5dt4-test-ntomachineconfig-replace to have correct status in 25ms

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-plkf9/node-pool-m5dt4 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-769ddfd9f-r2szr 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-plkf9/node-pool-m5dt4-test-machineconfig in 21m57.05s nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-plkf9/node-pool-m5dt4-test-machineconfig to have correct status in 25ms util.go:474: Successfully waited for NodePool e2e-clusters-plkf9/node-pool-m5dt4-test-machineconfig to start config update in 15.05s util.go:490: Successfully waited for NodePool e2e-clusters-plkf9/node-pool-m5dt4-test-machineconfig to finish config update in 8m40.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-plkf9/node-pool-m5dt4-test-machineconfig in 25ms nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-plkf9/node-pool-m5dt4-test-machineconfig to have correct status in 25ms

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-plkf9/node-pool-m5dt4 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-769ddfd9f-r2szr has a restartCount > 0 (10)

control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-lm6297cg/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-lm6297cg/release@sha256:99c1da35391291d14ab7532397ad4f5f78e0b198a8b7ac7c91423301260f75da hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-vgbzj/control-plane-upgrade-6jv99 in 2m19s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-6jv99 util.go:2949: Successfully waited for HostedCluster e2e-clusters-vgbzj/control-plane-upgrade-6jv99 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-vgbzj/control-plane-upgrade-6jv99 in 50ms 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-lm6297cg/release@sha256:99c1da35391291d14ab7532397ad4f5f78e0b198a8b7ac7c91423301260f75da util.go:598: Successfully waited for HostedCluster e2e-clusters-vgbzj/control-plane-upgrade-6jv99 to rollout in 75ms

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vgbzj/control-plane-upgrade-6jv99 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-6db464c8d7-dcc6b 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-vgbzj-control-plane-upgrade-6jv99/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-vgbzj-control-plane-upgrade-6jv99/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)