PR #7447 - 01-09 10:33

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-dnq5m/autoscaling-t445b in 39s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-t445b util.go:2949: Successfully waited for HostedCluster e2e-clusters-dnq5m/autoscaling-t445b to have valid conditions in 0s 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-dnq5m/autoscaling-t445b in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-6b979bc995-6chjh has a restartCount > 0 (6)

create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-l5vtq/create-cluster-5hpnw in 1m25s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-5hpnw util.go:2949: Successfully waited for HostedCluster e2e-clusters-l5vtq/create-cluster-5hpnw to have valid conditions in 0s 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-l5vtq/create-cluster-5hpnw in 2m57s 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-5hpnw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.173.235.14:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-5hpnw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.219.68.53:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-5hpnw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.217.227.179:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-5hpnw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.219.68.53:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 1m12.575s util.go:565: Successfully waited for 3 nodes to become ready in 7m9s util.go:598: Successfully waited for HostedCluster e2e-clusters-l5vtq/create-cluster-5hpnw to rollout in 4m12s util.go:2949: Successfully waited for HostedCluster e2e-clusters-l5vtq/create-cluster-5hpnw to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-l5vtq/create-cluster-5hpnw in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-7c5c79ddd8-zqpgt has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9zn8h/custom-config-2jjd4 in 26s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-2jjd4 util.go:2949: Successfully waited for HostedCluster e2e-clusters-9zn8h/custom-config-2jjd4 to have valid conditions in 0s 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-9zn8h/custom-config-2jjd4 in 1m21s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2jjd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-2jjd4.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2jjd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.92.225:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2jjd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.152.80.249:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2jjd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.92.225:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2jjd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.152.80.249:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2jjd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.92.225:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2jjd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.152.80.249:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2jjd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.92.225:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m6.025s util.go:565: Successfully waited for 2 nodes to become ready in 7m39s util.go:598: Successfully waited for HostedCluster e2e-clusters-9zn8h/custom-config-2jjd4 to rollout in 7m21s util.go:2949: Successfully waited for HostedCluster e2e-clusters-9zn8h/custom-config-2jjd4 to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9zn8h/custom-config-2jjd4 in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-7b67fb4475-89745 has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-4zdtj/private-5qb2t in 32s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-5qb2t util.go:2949: Successfully waited for HostedCluster e2e-clusters-4zdtj/private-5qb2t to have valid conditions in 0s 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-4zdtj/private-5qb2t in 1m36s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-4zdtj/private-5qb2t to have all of their desired nodes in 10m39s util.go:598: Successfully waited for HostedCluster e2e-clusters-4zdtj/private-5qb2t to rollout in 3m42s util.go:2949: Successfully waited for HostedCluster e2e-clusters-4zdtj/private-5qb2t to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4zdtj/private-5qb2t in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-6fdb776d7f-jhnjx has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-tv7qc/private-flrjl in 1m8s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-flrjl util.go:2949: Successfully waited for HostedCluster e2e-clusters-tv7qc/private-flrjl to have valid conditions in 0s 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-tv7qc/private-flrjl in 1m45s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-tv7qc/private-flrjl to have all of their desired nodes in 9m48s util.go:598: Successfully waited for HostedCluster e2e-clusters-tv7qc/private-flrjl to rollout in 3m51s util.go:2949: Successfully waited for HostedCluster e2e-clusters-tv7qc/private-flrjl to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-tv7qc/private-flrjl in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-7c4c8c6cd7-jlt5q has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-sxz4w/proxy-9nz7j in 46s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-9nz7j util.go:2949: Successfully waited for HostedCluster e2e-clusters-sxz4w/proxy-9nz7j to have valid conditions in 0s 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-sxz4w/proxy-9nz7j in 1m33s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-9nz7j.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-9nz7j.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-9nz7j.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.6.77.109:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m41.025s util.go:565: Successfully waited for 2 nodes to become ready in 8m21s util.go:598: Successfully waited for HostedCluster e2e-clusters-sxz4w/proxy-9nz7j to rollout in 4m9s util.go:2949: Successfully waited for HostedCluster e2e-clusters-sxz4w/proxy-9nz7j to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sxz4w/proxy-9nz7j in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-56dd7db579-9t6gr has a restartCount > 0 (6)

requestserving.go:105: Created request serving nodepool clusters/190ac88fbd9aa5068f1a-mgmt-reqserving-vnwxt requestserving.go:105: Created request serving nodepool clusters/190ac88fbd9aa5068f1a-mgmt-reqserving-rmsd8 requestserving.go:113: Created non request serving nodepool clusters/190ac88fbd9aa5068f1a-mgmt-non-reqserving-42k4h requestserving.go:113: Created non request serving nodepool clusters/190ac88fbd9aa5068f1a-mgmt-non-reqserving-j5tfs requestserving.go:113: Created non request serving nodepool clusters/190ac88fbd9aa5068f1a-mgmt-non-reqserving-rsfqz util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/190ac88fbd9aa5068f1a-mgmt-reqserving-vnwxt in 3m48s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/190ac88fbd9aa5068f1a-mgmt-reqserving-rmsd8 in 21s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/190ac88fbd9aa5068f1a-mgmt-non-reqserving-42k4h in 36s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/190ac88fbd9aa5068f1a-mgmt-non-reqserving-j5tfs in 3s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/190ac88fbd9aa5068f1a-mgmt-non-reqserving-rsfqz in 100ms create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-mm6dg/request-serving-isolation-bkdc8 in 27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-bkdc8 util.go:2949: Successfully waited for HostedCluster e2e-clusters-mm6dg/request-serving-isolation-bkdc8 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/190ac88fbd9aa5068f1a-mgmt-reqserving-vnwxt requestserving.go:132: Tearing down custom nodepool clusters/190ac88fbd9aa5068f1a-mgmt-reqserving-rmsd8 requestserving.go:132: Tearing down custom nodepool clusters/190ac88fbd9aa5068f1a-mgmt-non-reqserving-42k4h requestserving.go:132: Tearing down custom nodepool clusters/190ac88fbd9aa5068f1a-mgmt-non-reqserving-j5tfs requestserving.go:132: Tearing down custom nodepool clusters/190ac88fbd9aa5068f1a-mgmt-non-reqserving-rsfqz hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mm6dg/request-serving-isolation-bkdc8 in 1m45s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-bkdc8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-bkdc8.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-bkdc8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.222.162.160:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m31.025s util.go:565: Successfully waited for 3 nodes to become ready in 8m12s util.go:598: Successfully waited for HostedCluster e2e-clusters-mm6dg/request-serving-isolation-bkdc8 to rollout in 6m57s util.go:2949: Successfully waited for HostedCluster e2e-clusters-mm6dg/request-serving-isolation-bkdc8 to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mm6dg/request-serving-isolation-bkdc8 in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-c95d7fdd7-v86w7 has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-7wtjq/node-pool-ntmlg in 41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-ntmlg util.go:2949: Failed to wait for HostedCluster e2e-clusters-7wtjq/node-pool-ntmlg to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-7wtjq/node-pool-ntmlg invalid at RV 107319 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-7wtjq/node-pool-ntmlg in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:363: Successfully waited for a successful connection to the guest API server in 0s

nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-inplace in 24m21s nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-inplace to have correct status in 0s util.go:474: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-inplace to start config update in 45s util.go:490: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-inplace to finish config update in 5m20s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-ntmlg-test-ntomachineconfig-inplace to be ready in 30s util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-inplace in 0s nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-inplace to have correct status in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7wtjq/node-pool-ntmlg in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-547c6c5b99-qfrrh has a restartCount > 0 (6)

nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-replace in 11m15s nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-replace to have correct status in 0s util.go:474: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-replace to start config update in 15s util.go:490: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-replace to finish config update in 16m20s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-ntmlg-test-ntomachineconfig-replace to be ready in 0s util.go:565: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-replace in 0s nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-ntomachineconfig-replace to have correct status in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7wtjq/node-pool-ntmlg in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-547c6c5b99-qfrrh has a restartCount > 0 (5)

nodepool_machineconfig_test.go:54: Starting test NodePoolMachineconfigRolloutTest util.go:565: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-machineconfig in 19m15s nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-machineconfig to have correct status in 0s util.go:474: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-machineconfig to start config update in 15s util.go:490: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-machineconfig to finish config update in 7m20s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/machineconfig-update-checker-replace to be ready in 25ms util.go:565: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-machineconfig in 0s nodepool_test.go:395: Successfully waited for NodePool e2e-clusters-7wtjq/node-pool-ntmlg-test-machineconfig to have correct status in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7wtjq/node-pool-ntmlg in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-547c6c5b99-qfrrh has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-cws2k/node-pool-j5n7x in 1m27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-j5n7x util.go:2949: Successfully waited for HostedCluster e2e-clusters-cws2k/node-pool-j5n7x to have valid conditions in 0s 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-cws2k/node-pool-j5n7x in 2m54s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-j5n7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.194.11.193:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-j5n7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.230.165.206:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-j5n7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.194.11.193:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 54.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-cws2k/node-pool-j5n7x to have valid conditions in 1m48s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cws2k/node-pool-j5n7x in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-78df95df47-8vg9p 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-hhlpl/control-plane-upgrade-4b76n in 13s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-4b76n util.go:2949: Successfully waited for HostedCluster e2e-clusters-hhlpl/control-plane-upgrade-4b76n to have valid conditions in 0s 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-hhlpl/control-plane-upgrade-4b76n in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:363: Successfully waited for a successful connection to the guest API server in 0s 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-hhlpl/control-plane-upgrade-4b76n to rollout in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hhlpl/control-plane-upgrade-4b76n in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-6697fb5f5-9ppjc has a restartCount > 0 (8)

eventually.go:258: Failed to get **v1beta1.ControlPlaneComponent: client rate limiter Wait returned an error: context deadline exceeded 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-hhlpl-control-plane-upgrade-4b76n/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-hhlpl-control-plane-upgrade-4b76n/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)