PR #7139 - 01-09 16:41

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

149
Total Tests
98
Passed
32
Failed
19
Skipped

Failed Tests

TestAutoscaling
20m23.5s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-fkjqz/autoscaling-2xj4z in 24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-2xj4z util.go:2949: Successfully waited for HostedCluster e2e-clusters-fkjqz/autoscaling-2xj4z to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
13m9.37s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fkjqz/autoscaling-2xj4z 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-autoscaling-2xj4z.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-2xj4z.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-2xj4z.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.163.92.70:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m7.05s util.go:565: Successfully waited for 1 nodes to become ready in 7m51s util.go:598: Successfully waited for HostedCluster e2e-clusters-fkjqz/autoscaling-2xj4z to rollout in 2m27s util.go:2949: Successfully waited for HostedCluster e2e-clusters-fkjqz/autoscaling-2xj4z to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fkjqz/autoscaling-2xj4z 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-85f5994d8d-vklts has a restartCount > 0 (6)
TestCreateCluster
27m46.38s
create_cluster_test.go:2612: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-zvn9r/create-cluster-tzrm9 in 41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-tzrm9 util.go:2949: Successfully waited for HostedCluster e2e-clusters-zvn9r/create-cluster-tzrm9 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
20m6.42s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zvn9r/create-cluster-tzrm9 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-create-cluster-tzrm9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-tzrm9.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-tzrm9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.221.134.159:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m34.175s util.go:565: Successfully waited for 3 nodes to become ready in 7m54s util.go:598: Successfully waited for HostedCluster e2e-clusters-zvn9r/create-cluster-tzrm9 to rollout in 8m42s util.go:2949: Successfully waited for HostedCluster e2e-clusters-zvn9r/create-cluster-tzrm9 to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zvn9r/create-cluster-tzrm9 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-566b6986b5-zxc46 has a restartCount > 0 (7)
TestCreateClusterCustomConfig
26m15.77s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-8zbsb/custom-config-7s8rq in 41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-7s8rq util.go:2949: Successfully waited for HostedCluster e2e-clusters-8zbsb/custom-config-7s8rq to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
19m26.27s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8zbsb/custom-config-7s8rq 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-custom-config-7s8rq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-7s8rq.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-7s8rq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.90.18.36:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7s8rq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.195.241.41:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7s8rq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.195.241.41:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7s8rq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.90.18.36:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7s8rq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.195.241.41:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m24.025s util.go:565: Successfully waited for 2 nodes to become ready in 8m9s util.go:598: Successfully waited for HostedCluster e2e-clusters-8zbsb/custom-config-7s8rq to rollout in 7m24s util.go:2949: Successfully waited for HostedCluster e2e-clusters-8zbsb/custom-config-7s8rq to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8zbsb/custom-config-7s8rq 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-59f7698448-78h7v has a restartCount > 0 (7)
TestCreateClusterPrivate
22m45.68s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-vrnk2/private-7d28f in 38s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-7d28f util.go:2949: Successfully waited for HostedCluster e2e-clusters-vrnk2/private-7d28f to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
16m27.16s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vrnk2/private-7d28f in 1m24s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-vrnk2/private-7d28f to have all of their desired nodes in 9m54s util.go:598: Successfully waited for HostedCluster e2e-clusters-vrnk2/private-7d28f to rollout in 5m9s util.go:2949: Successfully waited for HostedCluster e2e-clusters-vrnk2/private-7d28f to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vrnk2/private-7d28f 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-b65499464-phr6v has a restartCount > 0 (7)
TestCreateClusterPrivateWithRouteKAS
22m48.71s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9mmdn/private-h5db6 in 37s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-h5db6 util.go:2949: Successfully waited for HostedCluster e2e-clusters-9mmdn/private-h5db6 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
15m21.16s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9mmdn/private-h5db6 in 1m24s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-9mmdn/private-h5db6 to have all of their desired nodes in 9m48s util.go:598: Successfully waited for HostedCluster e2e-clusters-9mmdn/private-h5db6 to rollout in 3m39s util.go:2949: Successfully waited for HostedCluster e2e-clusters-9mmdn/private-h5db6 to have valid conditions in 0s
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster/EnsureNoCrashingPods
30.03s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9mmdn/private-h5db6 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-59f75fd4bd-d8kkk has a restartCount > 0 (6)
TestCreateClusterProxy
1h6m19.97s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-kcbvk/proxy-lr2k6 in 45s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-lr2k6 util.go:2949: Successfully waited for HostedCluster e2e-clusters-kcbvk/proxy-lr2k6 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
15m16.36s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-kcbvk/proxy-lr2k6 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-proxy-lr2k6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-lr2k6.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-lr2k6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.230.33.186:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-lr2k6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.1.146.190:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 1m56.025s util.go:565: Successfully waited for 2 nodes to become ready in 7m48s util.go:598: Successfully waited for HostedCluster e2e-clusters-kcbvk/proxy-lr2k6 to rollout in 3m39s util.go:2949: Successfully waited for HostedCluster e2e-clusters-kcbvk/proxy-lr2k6 to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-kcbvk/proxy-lr2k6 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-6867b6bd5b-4t8xw has a restartCount > 0 (6)
TestCreateClusterRequestServingIsolation
27m44.69s
requestserving.go:105: Created request serving nodepool clusters/c6d5e8653af0e2c5e40a-mgmt-reqserving-4rmcv requestserving.go:105: Created request serving nodepool clusters/c6d5e8653af0e2c5e40a-mgmt-reqserving-hcsn9 requestserving.go:113: Created non request serving nodepool clusters/c6d5e8653af0e2c5e40a-mgmt-non-reqserving-qtx5g requestserving.go:113: Created non request serving nodepool clusters/c6d5e8653af0e2c5e40a-mgmt-non-reqserving-8rkm4 requestserving.go:113: Created non request serving nodepool clusters/c6d5e8653af0e2c5e40a-mgmt-non-reqserving-5xzcg util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/c6d5e8653af0e2c5e40a-mgmt-reqserving-4rmcv in 3m54s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/c6d5e8653af0e2c5e40a-mgmt-reqserving-hcsn9 in 100ms util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/c6d5e8653af0e2c5e40a-mgmt-non-reqserving-qtx5g in 21s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/c6d5e8653af0e2c5e40a-mgmt-non-reqserving-8rkm4 in 42s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/c6d5e8653af0e2c5e40a-mgmt-non-reqserving-5xzcg in 75ms create_cluster_test.go:2790: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-pnczs/request-serving-isolation-8zngp in 59s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-8zngp util.go:2949: Successfully waited for HostedCluster e2e-clusters-pnczs/request-serving-isolation-8zngp to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/c6d5e8653af0e2c5e40a-mgmt-reqserving-4rmcv requestserving.go:132: Tearing down custom nodepool clusters/c6d5e8653af0e2c5e40a-mgmt-reqserving-hcsn9 requestserving.go:132: Tearing down custom nodepool clusters/c6d5e8653af0e2c5e40a-mgmt-non-reqserving-qtx5g requestserving.go:132: Tearing down custom nodepool clusters/c6d5e8653af0e2c5e40a-mgmt-non-reqserving-8rkm4 requestserving.go:132: Tearing down custom nodepool clusters/c6d5e8653af0e2c5e40a-mgmt-non-reqserving-5xzcg hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
15m11.77s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pnczs/request-serving-isolation-8zngp 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-request-serving-isolation-8zngp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-8zngp.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-8zngp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 23.23.77.91:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-8zngp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.217.133.228:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-8zngp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.175.221.20:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-8zngp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 23.23.77.91:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-8zngp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.175.221.20:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 3m27.475s util.go:565: Successfully waited for 3 nodes to become ready in 6m12s util.go:598: Successfully waited for HostedCluster e2e-clusters-pnczs/request-serving-isolation-8zngp to rollout in 3m45.025s util.go:2949: Successfully waited for HostedCluster e2e-clusters-pnczs/request-serving-isolation-8zngp to have valid conditions in 0s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pnczs/request-serving-isolation-8zngp 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-5d68d8c6cb-tqkcs has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
10m10.45s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-6kpqk/node-pool-t7xvg in 20s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-t7xvg util.go:2949: Successfully waited for HostedCluster e2e-clusters-6kpqk/node-pool-t7xvg to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
5m45.38s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-6kpqk/node-pool-t7xvg in 1m42.025s 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-t7xvg.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-t7xvg.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-t7xvg.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.2.194.215:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m28.075s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-6kpqk/node-pool-t7xvg to have valid conditions in 2m30s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-6kpqk/node-pool-t7xvg 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-55866d8f9b-8l7kt has a restartCount > 0 (3)
TestNodePool/HostedCluster2
10m7.93s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-2twv4/node-pool-4bv5s in 23s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-4bv5s util.go:2949: Successfully waited for HostedCluster e2e-clusters-2twv4/node-pool-4bv5s to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
5m40.37s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2twv4/node-pool-4bv5s 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-node-pool-4bv5s.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-4bv5s.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-4bv5s.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.234.19.202:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m35.025s util.go:565: Successfully waited for 0 nodes to become ready in 25ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-2twv4/node-pool-4bv5s to have valid conditions in 2m42s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2twv4/node-pool-4bv5s 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-6cbdb6db68-jtzx7 has a restartCount > 0 (4)
TestUpgradeControlPlane
55m25.58s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-v0nmqb5g/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-v0nmqb5g/release@sha256:7be0b01440d1843fdb9111b9e004de27fda819823a4732b86f3366a1a9e266fe hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-mndp4/control-plane-upgrade-g94jj in 35s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-g94jj util.go:2949: Successfully waited for HostedCluster e2e-clusters-mndp4/control-plane-upgrade-g94jj to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m0.83s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mndp4/control-plane-upgrade-g94jj 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-v0nmqb5g/release@sha256:7be0b01440d1843fdb9111b9e004de27fda819823a4732b86f3366a1a9e266fe util.go:598: Successfully waited for HostedCluster e2e-clusters-mndp4/control-plane-upgrade-g94jj to rollout in 0s
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mndp4/control-plane-upgrade-g94jj 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-684697c876-b2tdw has a restartCount > 0 (8)
TestUpgradeControlPlane/Main/Wait_for_control_plane_components_to_complete_rollout
30m0s
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-mndp4-control-plane-upgrade-g94jj/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-mndp4-control-plane-upgrade-g94jj/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)