PR #7450 - 01-10 02:03

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-2qvfh/autoscaling-zd2p7 in 23s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-zd2p7 util.go:2949: Successfully waited for HostedCluster e2e-clusters-2qvfh/autoscaling-zd2p7 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-2qvfh/autoscaling-zd2p7 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-autoscaling-zd2p7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-zd2p7.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-autoscaling-zd2p7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.203.70.218:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m30.1s util.go:565: Successfully waited for 1 nodes to become ready in 7m39s util.go:598: Successfully waited for HostedCluster e2e-clusters-2qvfh/autoscaling-zd2p7 to rollout in 2m39s util.go:2949: Successfully waited for HostedCluster e2e-clusters-2qvfh/autoscaling-zd2p7 to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2qvfh/autoscaling-zd2p7 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-c45444957-fjrkf 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-csmdd/create-cluster-cv46n in 1m32s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-cv46n util.go:2949: Successfully waited for HostedCluster e2e-clusters-csmdd/create-cluster-cv46n 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-csmdd/create-cluster-cv46n in 1m15s 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-cv46n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-cv46n.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-cv46n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.231.167:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-cv46n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.49.80.36:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m58.025s util.go:565: Successfully waited for 3 nodes to become ready in 8m3s util.go:598: Successfully waited for HostedCluster e2e-clusters-csmdd/create-cluster-cv46n to rollout in 6m6s util.go:2949: Successfully waited for HostedCluster e2e-clusters-csmdd/create-cluster-cv46n to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-csmdd/create-cluster-cv46n 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-65c4d8cbc4-j5zrz has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-5gmg2/custom-config-25ggs in 27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-25ggs util.go:2949: Successfully waited for HostedCluster e2e-clusters-5gmg2/custom-config-25ggs 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-5gmg2/custom-config-25ggs 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-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-25ggs.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-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.44.211:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.211.65.55:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.209.161.187:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.211.65.55:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.209.161.187:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.211.65.55:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.44.211:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.211.65.55:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.44.211:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.211.65.55:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.209.161.187:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.44.211:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.211.65.55:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.44.211:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.211.65.55:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-25ggs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.44.211:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m45.025s util.go:565: Successfully waited for 2 nodes to become ready in 7m12s util.go:598: Successfully waited for HostedCluster e2e-clusters-5gmg2/custom-config-25ggs to rollout in 7m12s util.go:2949: Successfully waited for HostedCluster e2e-clusters-5gmg2/custom-config-25ggs to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5gmg2/custom-config-25ggs 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-6f4dfb8997-dbc6b has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-xpdtv/private-66rjc in 28s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-66rjc util.go:2949: Successfully waited for HostedCluster e2e-clusters-xpdtv/private-66rjc 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-xpdtv/private-66rjc 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-xpdtv/private-66rjc to have all of their desired nodes in 9m39s util.go:598: Successfully waited for HostedCluster e2e-clusters-xpdtv/private-66rjc to rollout in 3m21s util.go:2949: Successfully waited for HostedCluster e2e-clusters-xpdtv/private-66rjc to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xpdtv/private-66rjc 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-57bb9fc77-t8dp9 has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9fq7s/private-lxvtm in 16s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-lxvtm util.go:2949: Successfully waited for HostedCluster e2e-clusters-9fq7s/private-lxvtm 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-9fq7s/private-lxvtm 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-9fq7s/private-lxvtm to have all of their desired nodes in 9m42s util.go:598: Successfully waited for HostedCluster e2e-clusters-9fq7s/private-lxvtm to rollout in 6m33s util.go:2949: Successfully waited for HostedCluster e2e-clusters-9fq7s/private-lxvtm to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9fq7s/private-lxvtm 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-5579b5dbf7-wclv2 has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-7nn4w/proxy-lvbbw in 57s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-lvbbw util.go:2949: Successfully waited for HostedCluster e2e-clusters-7nn4w/proxy-lvbbw 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-7nn4w/proxy-lvbbw in 1m18s 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-lvbbw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-lvbbw.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-lvbbw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.200.51.98:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m48.15s util.go:565: Successfully waited for 2 nodes to become ready in 8m6s util.go:598: Successfully waited for HostedCluster e2e-clusters-7nn4w/proxy-lvbbw to rollout in 5m21s util.go:2949: Successfully waited for HostedCluster e2e-clusters-7nn4w/proxy-lvbbw to have valid conditions in 0s

requestserving.go:105: Created request serving nodepool clusters/cb5b0195b784afee40cd-mgmt-reqserving-pz6v6 requestserving.go:105: Created request serving nodepool clusters/cb5b0195b784afee40cd-mgmt-reqserving-tlfzh requestserving.go:113: Created non request serving nodepool clusters/cb5b0195b784afee40cd-mgmt-non-reqserving-k4nxh requestserving.go:113: Created non request serving nodepool clusters/cb5b0195b784afee40cd-mgmt-non-reqserving-8q5t9 requestserving.go:113: Created non request serving nodepool clusters/cb5b0195b784afee40cd-mgmt-non-reqserving-kmvq9 util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/cb5b0195b784afee40cd-mgmt-reqserving-pz6v6 in 3m6s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/cb5b0195b784afee40cd-mgmt-reqserving-tlfzh in 1m9s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/cb5b0195b784afee40cd-mgmt-non-reqserving-k4nxh in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/cb5b0195b784afee40cd-mgmt-non-reqserving-8q5t9 in 2m42s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/cb5b0195b784afee40cd-mgmt-non-reqserving-kmvq9 in 0s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-qwhhw/request-serving-isolation-rl5v4 in 14s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-rl5v4 util.go:2949: Successfully waited for HostedCluster e2e-clusters-qwhhw/request-serving-isolation-rl5v4 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/cb5b0195b784afee40cd-mgmt-reqserving-pz6v6 requestserving.go:132: Tearing down custom nodepool clusters/cb5b0195b784afee40cd-mgmt-reqserving-tlfzh requestserving.go:132: Tearing down custom nodepool clusters/cb5b0195b784afee40cd-mgmt-non-reqserving-k4nxh requestserving.go:132: Tearing down custom nodepool clusters/cb5b0195b784afee40cd-mgmt-non-reqserving-8q5t9 requestserving.go:132: Tearing down custom nodepool clusters/cb5b0195b784afee40cd-mgmt-non-reqserving-kmvq9 hypershift_framework.go:230: skipping teardown, already called

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

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qwhhw/request-serving-isolation-rl5v4 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-5c56c654fc-j9wfn has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-n8ckr/node-pool-jrfqv in 44s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-jrfqv util.go:2949: Successfully waited for HostedCluster e2e-clusters-n8ckr/node-pool-jrfqv 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-n8ckr/node-pool-jrfqv in 1m42.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-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-jrfqv.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-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.206.196.242:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.80.40.253:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.206.196.242:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.227.168.174:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.206.196.242:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.227.168.174:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.206.196.242:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.80.40.253:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.206.196.242:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.80.40.253:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.227.168.174:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-jrfqv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.80.40.253:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m15.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-n8ckr/node-pool-jrfqv to have valid conditions in 1m39s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-n8ckr/node-pool-jrfqv 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-85d56fd449-w5hxl has a restartCount > 0 (2)

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

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-blh8q/node-pool-gkk99 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-797dfbbc77-4qf9c has a restartCount > 0 (4)

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-j4xh2/control-plane-upgrade-5gzxz in 1m9s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-5gzxz util.go:2949: Successfully waited for HostedCluster e2e-clusters-j4xh2/control-plane-upgrade-5gzxz 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-j4xh2/control-plane-upgrade-5gzxz 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-fqrj10p9/release@sha256:c1062c106be03538afb4169bc81411491fbd3674ffa05331e838637bb0547d1e util.go:598: Successfully waited for HostedCluster e2e-clusters-j4xh2/control-plane-upgrade-5gzxz to rollout in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-j4xh2/control-plane-upgrade-5gzxz 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-7c558f9cb5-lfzns has a restartCount > 0 (7)

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-j4xh2-control-plane-upgrade-5gzxz/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-j4xh2-control-plane-upgrade-5gzxz/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)