PR #7181 - 01-09 13:16

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

149
Total Tests
98
Passed
32
Failed
19
Skipped

Failed Tests

TestAutoscaling
20m18.38s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-qj9c7/autoscaling-l7gg9 in 47s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-l7gg9 util.go:2949: Successfully waited for HostedCluster e2e-clusters-qj9c7/autoscaling-l7gg9 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
13m16.32s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qj9c7/autoscaling-l7gg9 in 2m27s 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-l7gg9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-l7gg9.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-l7gg9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.184.58:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m38.1s util.go:565: Successfully waited for 1 nodes to become ready in 6m30s util.go:598: Successfully waited for HostedCluster e2e-clusters-qj9c7/autoscaling-l7gg9 to rollout in 2m36s util.go:2949: Successfully waited for HostedCluster e2e-clusters-qj9c7/autoscaling-l7gg9 to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qj9c7/autoscaling-l7gg9 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-8697dd7d44-2d4bl has a restartCount > 0 (6)
TestCreateCluster
23m23.78s
create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-wbb5b/create-cluster-qhvp6 in 42s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-qhvp6 util.go:2949: Successfully waited for HostedCluster e2e-clusters-wbb5b/create-cluster-qhvp6 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
15m48.42s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wbb5b/create-cluster-qhvp6 in 1m57s 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-qhvp6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-qhvp6.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-qhvp6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.209.206.115:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m40.15s util.go:565: Successfully waited for 3 nodes to become ready in 7m48s util.go:598: Successfully waited for HostedCluster e2e-clusters-wbb5b/create-cluster-qhvp6 to rollout in 4m18s util.go:2949: Successfully waited for HostedCluster e2e-clusters-wbb5b/create-cluster-qhvp6 to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wbb5b/create-cluster-qhvp6 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-7c4cc856df-v2vvv has a restartCount > 0 (6)
TestCreateClusterCustomConfig
26m27.24s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-zjq98/custom-config-hzfzs in 34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-hzfzs util.go:2949: Successfully waited for HostedCluster e2e-clusters-zjq98/custom-config-hzfzs to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
19m50.24s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zjq98/custom-config-hzfzs in 2m42s 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-hzfzs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-hzfzs.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-hzfzs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.201.70.5:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-hzfzs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.201.70.5:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-hzfzs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.193.5.215:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-hzfzs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.91.150.150:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-hzfzs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.193.5.215:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m12.025s util.go:565: Successfully waited for 2 nodes to become ready in 7m36s util.go:598: Successfully waited for HostedCluster e2e-clusters-zjq98/custom-config-hzfzs to rollout in 7m15s util.go:2949: Successfully waited for HostedCluster e2e-clusters-zjq98/custom-config-hzfzs to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zjq98/custom-config-hzfzs 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-7d445d49f6-pzv88 has a restartCount > 0 (7)
TestCreateClusterPrivate
21m28.86s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-zptr2/private-bk9qr in 40s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-bk9qr util.go:2949: Successfully waited for HostedCluster e2e-clusters-zptr2/private-bk9qr to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
14m54.14s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zptr2/private-bk9qr in 2m15s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-zptr2/private-bk9qr to have all of their desired nodes in 9m30s util.go:598: Successfully waited for HostedCluster e2e-clusters-zptr2/private-bk9qr to rollout in 3m9s util.go:2949: Successfully waited for HostedCluster e2e-clusters-zptr2/private-bk9qr to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zptr2/private-bk9qr 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-7b7c466bb4-2zshr has a restartCount > 0 (6)
TestCreateClusterPrivateWithRouteKAS
26m23.41s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-hmj8p/private-v5xtc in 29s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-v5xtc util.go:2949: Successfully waited for HostedCluster e2e-clusters-hmj8p/private-v5xtc to have valid conditions in 25ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
20m21.24s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hmj8p/private-v5xtc in 2m24s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-hmj8p/private-v5xtc to have all of their desired nodes in 9m27s util.go:598: Successfully waited for HostedCluster e2e-clusters-hmj8p/private-v5xtc to rollout in 8m0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-hmj8p/private-v5xtc to have valid conditions in 0s
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster/EnsureNoCrashingPods
30.02s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hmj8p/private-v5xtc 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-5ccb844b7b-nkvzt has a restartCount > 0 (7)
TestCreateClusterProxy
28m47.94s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-24jzf/proxy-n4xnn in 44s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-n4xnn util.go:2949: Successfully waited for HostedCluster e2e-clusters-24jzf/proxy-n4xnn to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
20m54.22s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-24jzf/proxy-n4xnn in 2m30s 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-n4xnn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-n4xnn.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-n4xnn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.153.164.158:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m31.025s util.go:565: Successfully waited for 2 nodes to become ready in 8m0s util.go:598: Successfully waited for HostedCluster e2e-clusters-24jzf/proxy-n4xnn to rollout in 8m48s util.go:2949: Successfully waited for HostedCluster e2e-clusters-24jzf/proxy-n4xnn to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-24jzf/proxy-n4xnn 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-55bcbd76dd-n2tpr has a restartCount > 0 (8)
TestCreateClusterRequestServingIsolation
28m29.95s
requestserving.go:105: Created request serving nodepool clusters/32a98837e71cfa8f664a-mgmt-reqserving-vf686 requestserving.go:105: Created request serving nodepool clusters/32a98837e71cfa8f664a-mgmt-reqserving-ttckg requestserving.go:113: Created non request serving nodepool clusters/32a98837e71cfa8f664a-mgmt-non-reqserving-r7rcr requestserving.go:113: Created non request serving nodepool clusters/32a98837e71cfa8f664a-mgmt-non-reqserving-7s4bv requestserving.go:113: Created non request serving nodepool clusters/32a98837e71cfa8f664a-mgmt-non-reqserving-9qnzk util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/32a98837e71cfa8f664a-mgmt-reqserving-vf686 in 3m24s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/32a98837e71cfa8f664a-mgmt-reqserving-ttckg in 3s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/32a98837e71cfa8f664a-mgmt-non-reqserving-r7rcr in 33s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/32a98837e71cfa8f664a-mgmt-non-reqserving-7s4bv in 36s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/32a98837e71cfa8f664a-mgmt-non-reqserving-9qnzk in 3s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-mmq2j/request-serving-isolation-rrnsx in 14s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-rrnsx util.go:2949: Successfully waited for HostedCluster e2e-clusters-mmq2j/request-serving-isolation-rrnsx to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/32a98837e71cfa8f664a-mgmt-reqserving-vf686 requestserving.go:132: Tearing down custom nodepool clusters/32a98837e71cfa8f664a-mgmt-reqserving-ttckg requestserving.go:132: Tearing down custom nodepool clusters/32a98837e71cfa8f664a-mgmt-non-reqserving-r7rcr requestserving.go:132: Tearing down custom nodepool clusters/32a98837e71cfa8f664a-mgmt-non-reqserving-7s4bv requestserving.go:132: Tearing down custom nodepool clusters/32a98837e71cfa8f664a-mgmt-non-reqserving-9qnzk hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
16m55.33s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mmq2j/request-serving-isolation-rrnsx 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-request-serving-isolation-rrnsx.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-rrnsx.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-rrnsx.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.206.107.234:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-rrnsx.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.172.152.207:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m50.025s util.go:565: Successfully waited for 3 nodes to become ready in 8m6s util.go:598: Successfully waited for HostedCluster e2e-clusters-mmq2j/request-serving-isolation-rrnsx to rollout in 5m15s util.go:2949: Successfully waited for HostedCluster e2e-clusters-mmq2j/request-serving-isolation-rrnsx to have valid conditions in 0s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mmq2j/request-serving-isolation-rrnsx 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-7598477768-btl85 has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
10m20.6s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-bjmhw/node-pool-2x8w4 in 41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-2x8w4 util.go:2949: Successfully waited for HostedCluster e2e-clusters-bjmhw/node-pool-2x8w4 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
6m8.42s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bjmhw/node-pool-2x8w4 in 2m0s 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-2x8w4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-2x8w4.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-2x8w4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.49.117.195:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-2x8w4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.199.106.152:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m45.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-bjmhw/node-pool-2x8w4 to have valid conditions in 2m18s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bjmhw/node-pool-2x8w4 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-5cd6669768-jvl2d has a restartCount > 0 (3)
TestNodePool/HostedCluster2
9m40.99s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-8kff8/node-pool-tz2t4 in 21s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-tz2t4 util.go:2949: Successfully waited for HostedCluster e2e-clusters-8kff8/node-pool-tz2t4 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
6m29.25s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8kff8/node-pool-tz2t4 in 2m30s 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-tz2t4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-tz2t4.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-tz2t4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.211.106.254:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m21.05s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-8kff8/node-pool-tz2t4 to have valid conditions in 2m33s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8kff8/node-pool-tz2t4 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-7548f96d9b-5ppmb has a restartCount > 0 (3)
TestUpgradeControlPlane
54m25.4s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-tj940dgg/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-tj940dgg/release@sha256:8f10c2ff1cba524c2f0facbaa0f72a77e73444b082783a3bb05a6d4dd822035b hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-zwjkw/control-plane-upgrade-7c8dw in 38s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-7c8dw util.go:2949: Successfully waited for HostedCluster e2e-clusters-zwjkw/control-plane-upgrade-7c8dw to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m0.68s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zwjkw/control-plane-upgrade-7c8dw 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-tj940dgg/release@sha256:8f10c2ff1cba524c2f0facbaa0f72a77e73444b082783a3bb05a6d4dd822035b util.go:598: Successfully waited for HostedCluster e2e-clusters-zwjkw/control-plane-upgrade-7c8dw to rollout in 0s
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zwjkw/control-plane-upgrade-7c8dw 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-5f484b848d-nn47n 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-zwjkw-control-plane-upgrade-7c8dw/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-zwjkw-control-plane-upgrade-7c8dw/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)