PR #7430 - 01-09 09:55

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

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7g679/autoscaling-gzbjm 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-65787fd7d6-975wg 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-9jkr6/create-cluster-zww24 in 41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-zww24 util.go:2949: Successfully waited for HostedCluster e2e-clusters-9jkr6/create-cluster-zww24 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-9jkr6/create-cluster-zww24 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-create-cluster-zww24.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-zww24.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-zww24.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.198.108.238:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-zww24.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.233.87.49:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m30.025s util.go:565: Successfully waited for 3 nodes to become ready in 8m12s util.go:598: Successfully waited for HostedCluster e2e-clusters-9jkr6/create-cluster-zww24 to rollout in 4m3s util.go:2949: Successfully waited for HostedCluster e2e-clusters-9jkr6/create-cluster-zww24 to have valid conditions in 0s

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

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-h8rv8/custom-config-jc5jl 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-cc56c59c8-h6jps has a restartCount > 0 (7)

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

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ntk7p/private-bj4hd 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-8d6dcf958-2nc8j has a restartCount > 0 (6)

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

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-g4rbg/private-zrrff 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-6bcb6884b6-tbzjd has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-pl4bt/proxy-5g7nw in 32s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-5g7nw util.go:2949: Successfully waited for HostedCluster e2e-clusters-pl4bt/proxy-5g7nw 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-pl4bt/proxy-5g7nw 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-5g7nw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-5g7nw.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-5g7nw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.21.145.75:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-5g7nw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.95.218.254:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m49.15s util.go:565: Successfully waited for 2 nodes to become ready in 8m12s util.go:598: Successfully waited for HostedCluster e2e-clusters-pl4bt/proxy-5g7nw to rollout in 3m45s util.go:2949: Successfully waited for HostedCluster e2e-clusters-pl4bt/proxy-5g7nw to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pl4bt/proxy-5g7nw 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-7b56dbd58b-nwv8p has a restartCount > 0 (6)

requestserving.go:105: Created request serving nodepool clusters/51808892e4412988f476-mgmt-reqserving-dff2c requestserving.go:105: Created request serving nodepool clusters/51808892e4412988f476-mgmt-reqserving-kh4z4 requestserving.go:113: Created non request serving nodepool clusters/51808892e4412988f476-mgmt-non-reqserving-jsh6q requestserving.go:113: Created non request serving nodepool clusters/51808892e4412988f476-mgmt-non-reqserving-brfj6 requestserving.go:113: Created non request serving nodepool clusters/51808892e4412988f476-mgmt-non-reqserving-9szjf util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/51808892e4412988f476-mgmt-reqserving-dff2c in 3m15s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/51808892e4412988f476-mgmt-reqserving-kh4z4 in 48s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/51808892e4412988f476-mgmt-non-reqserving-jsh6q in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/51808892e4412988f476-mgmt-non-reqserving-brfj6 in 57s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/51808892e4412988f476-mgmt-non-reqserving-9szjf in 0s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-k4kd4/request-serving-isolation-msnlc in 17s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-msnlc util.go:2949: Successfully waited for HostedCluster e2e-clusters-k4kd4/request-serving-isolation-msnlc to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/51808892e4412988f476-mgmt-reqserving-dff2c requestserving.go:132: Tearing down custom nodepool clusters/51808892e4412988f476-mgmt-reqserving-kh4z4 requestserving.go:132: Tearing down custom nodepool clusters/51808892e4412988f476-mgmt-non-reqserving-jsh6q requestserving.go:132: Tearing down custom nodepool clusters/51808892e4412988f476-mgmt-non-reqserving-brfj6 requestserving.go:132: Tearing down custom nodepool clusters/51808892e4412988f476-mgmt-non-reqserving-9szjf hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k4kd4/request-serving-isolation-msnlc 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-request-serving-isolation-msnlc.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-msnlc.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-msnlc.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.219.118.118:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m10.15s util.go:565: Successfully waited for 3 nodes to become ready in 9m0s util.go:598: Successfully waited for HostedCluster e2e-clusters-k4kd4/request-serving-isolation-msnlc to rollout in 5m24s util.go:2949: Successfully waited for HostedCluster e2e-clusters-k4kd4/request-serving-isolation-msnlc to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k4kd4/request-serving-isolation-msnlc 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-574bbd9b86-sgdn6 has a restartCount > 0 (7)

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

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7qzh5/node-pool-fdnkm 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-8b7d7655d-6cpz6 has a restartCount > 0 (3)

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

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-968cp/node-pool-8s95v 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-794885858-89dh8 has a restartCount > 0 (3)

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

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mxmsm/control-plane-upgrade-ptchv 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-78db4d99d6-9tslk 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-mxmsm-control-plane-upgrade-ptchv/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-mxmsm-control-plane-upgrade-ptchv/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)