PR #7439 - 01-09 12:18

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-25bmg/autoscaling-qgxks in 27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-qgxks util.go:2949: Successfully waited for HostedCluster e2e-clusters-25bmg/autoscaling-qgxks 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-25bmg/autoscaling-qgxks 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-7b8db66458-768hh 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-tprvp/create-cluster-lvlqb in 46s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-lvlqb util.go:2949: Successfully waited for HostedCluster e2e-clusters-tprvp/create-cluster-lvlqb 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-tprvp/create-cluster-lvlqb in 1m54s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-lvlqb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-lvlqb.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-create-cluster-lvlqb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.198.49.19:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-lvlqb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.217.113.0:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m40.025s util.go:565: Successfully waited for 3 nodes to become ready in 8m9s util.go:598: Successfully waited for HostedCluster e2e-clusters-tprvp/create-cluster-lvlqb to rollout in 3m45s util.go:2949: Successfully waited for HostedCluster e2e-clusters-tprvp/create-cluster-lvlqb to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-tprvp/create-cluster-lvlqb 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-579c86996c-bjw62 has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-hcsdm/custom-config-f4pgq in 41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-f4pgq util.go:2949: Successfully waited for HostedCluster e2e-clusters-hcsdm/custom-config-f4pgq 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-hcsdm/custom-config-f4pgq in 1m48s 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-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-f4pgq.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-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.162.243.176:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.239.19.84:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.20.214.55:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.162.243.176:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.20.214.55:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.239.19.84:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.20.214.55:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.239.19.84:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.20.214.55:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f4pgq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.239.19.84:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m39.05s util.go:565: Successfully waited for 2 nodes to become ready in 8m18s util.go:598: Successfully waited for HostedCluster e2e-clusters-hcsdm/custom-config-f4pgq to rollout in 7m18s util.go:2949: Successfully waited for HostedCluster e2e-clusters-hcsdm/custom-config-f4pgq to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hcsdm/custom-config-f4pgq 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-684ffd7cf8-b7f6x has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-xvfpm/private-2qjzt in 21s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-2qjzt util.go:2949: Successfully waited for HostedCluster e2e-clusters-xvfpm/private-2qjzt 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-xvfpm/private-2qjzt in 1m33s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-xvfpm/private-2qjzt to have all of their desired nodes in 9m30s util.go:598: Successfully waited for HostedCluster e2e-clusters-xvfpm/private-2qjzt to rollout in 6m27s util.go:2949: Successfully waited for HostedCluster e2e-clusters-xvfpm/private-2qjzt to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xvfpm/private-2qjzt 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-778796f9cd-gzk8d has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-m82pv/private-l6zp2 in 42s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-l6zp2 util.go:2949: Successfully waited for HostedCluster e2e-clusters-m82pv/private-l6zp2 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-m82pv/private-l6zp2 in 2m0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-m82pv/private-l6zp2 to have all of their desired nodes in 9m12s util.go:598: Successfully waited for HostedCluster e2e-clusters-m82pv/private-l6zp2 to rollout in 4m3s util.go:2949: Successfully waited for HostedCluster e2e-clusters-m82pv/private-l6zp2 to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m82pv/private-l6zp2 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-55964c9774-6n2tf has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-4tjp2/proxy-n7t2v in 1m0s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-n7t2v util.go:2949: Successfully waited for HostedCluster e2e-clusters-4tjp2/proxy-n7t2v 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-4tjp2/proxy-n7t2v in 1m24s 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-n7t2v.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-n7t2v.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-n7t2v.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.231.187.193:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m36.075s util.go:565: Successfully waited for 2 nodes to become ready in 8m27s util.go:598: Successfully waited for HostedCluster e2e-clusters-4tjp2/proxy-n7t2v to rollout in 4m12s util.go:2949: Successfully waited for HostedCluster e2e-clusters-4tjp2/proxy-n7t2v to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4tjp2/proxy-n7t2v 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-6d448b9666-97dm6 has a restartCount > 0 (7)

requestserving.go:105: Created request serving nodepool clusters/328f596eb2b72236cded-mgmt-reqserving-k8skw requestserving.go:105: Created request serving nodepool clusters/328f596eb2b72236cded-mgmt-reqserving-fs2vq requestserving.go:113: Created non request serving nodepool clusters/328f596eb2b72236cded-mgmt-non-reqserving-x9vwr requestserving.go:113: Created non request serving nodepool clusters/328f596eb2b72236cded-mgmt-non-reqserving-btmnh requestserving.go:113: Created non request serving nodepool clusters/328f596eb2b72236cded-mgmt-non-reqserving-cmlph util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/328f596eb2b72236cded-mgmt-reqserving-k8skw in 3m18s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/328f596eb2b72236cded-mgmt-reqserving-fs2vq in 21s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/328f596eb2b72236cded-mgmt-non-reqserving-x9vwr in 2m51s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/328f596eb2b72236cded-mgmt-non-reqserving-btmnh in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/328f596eb2b72236cded-mgmt-non-reqserving-cmlph in 0s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-7lrdm/request-serving-isolation-6v6cv in 20s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-6v6cv util.go:2949: Successfully waited for HostedCluster e2e-clusters-7lrdm/request-serving-isolation-6v6cv to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/328f596eb2b72236cded-mgmt-reqserving-k8skw requestserving.go:132: Tearing down custom nodepool clusters/328f596eb2b72236cded-mgmt-reqserving-fs2vq requestserving.go:132: Tearing down custom nodepool clusters/328f596eb2b72236cded-mgmt-non-reqserving-x9vwr requestserving.go:132: Tearing down custom nodepool clusters/328f596eb2b72236cded-mgmt-non-reqserving-btmnh requestserving.go:132: Tearing down custom nodepool clusters/328f596eb2b72236cded-mgmt-non-reqserving-cmlph hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7lrdm/request-serving-isolation-6v6cv in 1m30s 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-6v6cv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-6v6cv.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-6v6cv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.172.166.164: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 3 nodes to become ready in 8m6s util.go:598: Successfully waited for HostedCluster e2e-clusters-7lrdm/request-serving-isolation-6v6cv to rollout in 6m12s util.go:2949: Successfully waited for HostedCluster e2e-clusters-7lrdm/request-serving-isolation-6v6cv to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7lrdm/request-serving-isolation-6v6cv 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-749484ff8b-bgcbc has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-v5p7v/node-pool-cs89l in 36s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-cs89l util.go:2949: Successfully waited for HostedCluster e2e-clusters-v5p7v/node-pool-cs89l 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-v5p7v/node-pool-cs89l in 1m36s 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-cs89l.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-cs89l.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-node-pool-cs89l.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.217.16.183:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m33.025s util.go:565: Successfully waited for 0 nodes to become ready in 25ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-v5p7v/node-pool-cs89l to have valid conditions in 2m27s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-v5p7v/node-pool-cs89l 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-675975dc5d-x642n has a restartCount > 0 (3)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-59pqd/node-pool-js78k in 27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-js78k util.go:2949: Successfully waited for HostedCluster e2e-clusters-59pqd/node-pool-js78k 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-59pqd/node-pool-js78k 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-node-pool-js78k.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-js78k.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-node-pool-js78k.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.237.143.194:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-js78k.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.239.236.176:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 2m2.05s util.go:565: Successfully waited for 0 nodes to become ready in 25ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-59pqd/node-pool-js78k to have valid conditions in 2m12s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-59pqd/node-pool-js78k 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-7bfc4fdf5d-zk8tz has a restartCount > 0 (3)

control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-8fcm606c/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-8fcm606c/release@sha256:772e3c0949a7ac5f190d410ac677e8c46c8200b71f857b730eb547f820ed6fc3 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-f5qtq/control-plane-upgrade-whl7m in 29s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-whl7m util.go:2949: Successfully waited for HostedCluster e2e-clusters-f5qtq/control-plane-upgrade-whl7m 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-f5qtq/control-plane-upgrade-whl7m 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-8fcm606c/release@sha256:772e3c0949a7ac5f190d410ac677e8c46c8200b71f857b730eb547f820ed6fc3 util.go:598: Successfully waited for HostedCluster e2e-clusters-f5qtq/control-plane-upgrade-whl7m to rollout in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-f5qtq/control-plane-upgrade-whl7m 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-76f9b96946-62zch has a restartCount > 0 (7)

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-f5qtq-control-plane-upgrade-whl7m/cluster-network-operator invalid: eventually.go:403: - incorrect condition: wanted RolloutComplete=True, got RolloutComplete=False: WaitingForOperands(deployment cloud-network-config-controller is not ready) eventually.go:403: - component cluster-network-operator is still on version 4.22.0-0.ci-2026-01-08-185312 util.go:638: *v1beta1.ControlPlaneComponent e2e-clusters-f5qtq-control-plane-upgrade-whl7m/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)