PR #7404 - 01-09 13:17

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

149
Total Tests
98
Passed
32
Failed
19
Skipped

Failed Tests

TestAutoscaling
19m32s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-pgzh4/autoscaling-gf8jp in 17s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-gf8jp util.go:2949: Successfully waited for HostedCluster e2e-clusters-pgzh4/autoscaling-gf8jp to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
13m2.45s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pgzh4/autoscaling-gf8jp 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-autoscaling-gf8jp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-gf8jp.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-gf8jp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.30.137.244:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m39.125s util.go:565: Successfully waited for 1 nodes to become ready in 7m12s util.go:598: Successfully waited for HostedCluster e2e-clusters-pgzh4/autoscaling-gf8jp to rollout in 2m24s util.go:2949: Successfully waited for HostedCluster e2e-clusters-pgzh4/autoscaling-gf8jp to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pgzh4/autoscaling-gf8jp 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-59968cb696-k5pvm has a restartCount > 0 (6)
TestCreateCluster
28m52.48s
create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-q4hwc/create-cluster-g8nct in 55s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-g8nct util.go:2949: Successfully waited for HostedCluster e2e-clusters-q4hwc/create-cluster-g8nct to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
21m3.27s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-q4hwc/create-cluster-g8nct 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-create-cluster-g8nct.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-g8nct.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-g8nct.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.173.143.193:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m31.05s util.go:565: Successfully waited for 3 nodes to become ready in 8m3s util.go:598: Successfully waited for HostedCluster e2e-clusters-q4hwc/create-cluster-g8nct to rollout in 9m48s util.go:2949: Successfully waited for HostedCluster e2e-clusters-q4hwc/create-cluster-g8nct to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-q4hwc/create-cluster-g8nct 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-696bdcccd5-9kp89 has a restartCount > 0 (8)
TestCreateClusterCustomConfig
25m28.42s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-cxnqp/custom-config-fm76v in 42s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-fm76v util.go:2949: Successfully waited for HostedCluster e2e-clusters-cxnqp/custom-config-fm76v to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
19m8.25s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cxnqp/custom-config-fm76v 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-custom-config-fm76v.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-fm76v.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-fm76v.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 184.73.108.17:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-fm76v.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.148.84:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-fm76v.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.148.84:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-fm76v.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 184.73.108.17:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-fm76v.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.148.84:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m21.025s util.go:565: Successfully waited for 2 nodes to become ready in 7m33s util.go:598: Successfully waited for HostedCluster e2e-clusters-cxnqp/custom-config-fm76v to rollout in 7m27s util.go:2949: Successfully waited for HostedCluster e2e-clusters-cxnqp/custom-config-fm76v to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cxnqp/custom-config-fm76v 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-6d55c6889b-j4d27 has a restartCount > 0 (7)
TestCreateClusterPrivate
21m33.4s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-7w7dz/private-m68k6 in 22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-m68k6 util.go:2949: Successfully waited for HostedCluster e2e-clusters-7w7dz/private-m68k6 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
15m6.22s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7w7dz/private-m68k6 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-7w7dz/private-m68k6 to have all of their desired nodes in 9m48s util.go:598: Successfully waited for HostedCluster e2e-clusters-7w7dz/private-m68k6 to rollout in 3m39s util.go:2949: Successfully waited for HostedCluster e2e-clusters-7w7dz/private-m68k6 to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7w7dz/private-m68k6 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-58c76ffbd4-cn7gv has a restartCount > 0 (6)
TestCreateClusterPrivateWithRouteKAS
24m33.82s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-cfw5l/private-q75lg in 21s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-q75lg util.go:2949: Successfully waited for HostedCluster e2e-clusters-cfw5l/private-q75lg to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
18m9.12s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cfw5l/private-q75lg in 1m30s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-cfw5l/private-q75lg to have all of their desired nodes in 9m45s util.go:598: Successfully waited for HostedCluster e2e-clusters-cfw5l/private-q75lg to rollout in 6m24s util.go:2949: Successfully waited for HostedCluster e2e-clusters-cfw5l/private-q75lg 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-cfw5l/private-q75lg 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-6bb9fddd6d-zrxcq has a restartCount > 0 (7)
TestCreateClusterProxy
25m35.36s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-xhj56/proxy-xft28 in 1m9s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-xft28 util.go:2949: Successfully waited for HostedCluster e2e-clusters-xhj56/proxy-xft28 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
17m8.26s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xhj56/proxy-xft28 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-proxy-xft28.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-xft28.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-xft28.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.203.102.147:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-xft28.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.203.102.147:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-xft28.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.3.109.53:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-xft28.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.203.102.147:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 1m39.05s util.go:565: Successfully waited for 2 nodes to become ready in 8m21s util.go:598: Successfully waited for HostedCluster e2e-clusters-xhj56/proxy-xft28 to rollout in 5m21s util.go:2949: Successfully waited for HostedCluster e2e-clusters-xhj56/proxy-xft28 to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xhj56/proxy-xft28 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-674d4f79d4-8mxt6 has a restartCount > 0 (7)
TestCreateClusterRequestServingIsolation
29m50.43s
requestserving.go:105: Created request serving nodepool clusters/7085d61ff2a62a1133ee-mgmt-reqserving-h788n requestserving.go:105: Created request serving nodepool clusters/7085d61ff2a62a1133ee-mgmt-reqserving-rfkkl requestserving.go:113: Created non request serving nodepool clusters/7085d61ff2a62a1133ee-mgmt-non-reqserving-zjj7b requestserving.go:113: Created non request serving nodepool clusters/7085d61ff2a62a1133ee-mgmt-non-reqserving-qcrjk requestserving.go:113: Created non request serving nodepool clusters/7085d61ff2a62a1133ee-mgmt-non-reqserving-r5pp9 util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/7085d61ff2a62a1133ee-mgmt-reqserving-h788n in 4m12s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/7085d61ff2a62a1133ee-mgmt-reqserving-rfkkl in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/7085d61ff2a62a1133ee-mgmt-non-reqserving-zjj7b in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/7085d61ff2a62a1133ee-mgmt-non-reqserving-qcrjk in 3s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/7085d61ff2a62a1133ee-mgmt-non-reqserving-r5pp9 in 57s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-ll6vl/request-serving-isolation-kd4g8 in 33s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-kd4g8 util.go:2949: Successfully waited for HostedCluster e2e-clusters-ll6vl/request-serving-isolation-kd4g8 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/7085d61ff2a62a1133ee-mgmt-reqserving-h788n requestserving.go:132: Tearing down custom nodepool clusters/7085d61ff2a62a1133ee-mgmt-reqserving-rfkkl requestserving.go:132: Tearing down custom nodepool clusters/7085d61ff2a62a1133ee-mgmt-non-reqserving-zjj7b requestserving.go:132: Tearing down custom nodepool clusters/7085d61ff2a62a1133ee-mgmt-non-reqserving-qcrjk requestserving.go:132: Tearing down custom nodepool clusters/7085d61ff2a62a1133ee-mgmt-non-reqserving-r5pp9 hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
17m32.36s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ll6vl/request-serving-isolation-kd4g8 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-kd4g8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-kd4g8.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-kd4g8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.89.115.121:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-kd4g8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.161.187.249:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m42.125s util.go:565: Successfully waited for 3 nodes to become ready in 7m51s util.go:598: Successfully waited for HostedCluster e2e-clusters-ll6vl/request-serving-isolation-kd4g8 to rollout in 5m27s util.go:2949: Successfully waited for HostedCluster e2e-clusters-ll6vl/request-serving-isolation-kd4g8 to have valid conditions in 48s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ll6vl/request-serving-isolation-kd4g8 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-5cb6f47bc6-dn8lm has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
10m7.99s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-jbh9x/node-pool-ltj8n in 25s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-ltj8n util.go:2949: Successfully waited for HostedCluster e2e-clusters-jbh9x/node-pool-ltj8n to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
5m41.4s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jbh9x/node-pool-ltj8n 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-node-pool-ltj8n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-ltj8n.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-ltj8n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.50.97.79:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m36.175s util.go:565: Successfully waited for 0 nodes to become ready in 50ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-jbh9x/node-pool-ltj8n to have valid conditions in 2m27s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jbh9x/node-pool-ltj8n 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-6b88f9f684-nk7rc has a restartCount > 0 (3)
TestNodePool/HostedCluster2
10m8.19s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-wg5fc/node-pool-kt9g6 in 29s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-kt9g6 util.go:2949: Successfully waited for HostedCluster e2e-clusters-wg5fc/node-pool-kt9g6 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
5m41.23s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wg5fc/node-pool-kt9g6 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-node-pool-kt9g6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-kt9g6.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-kt9g6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.203.149.72:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m27.05s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-wg5fc/node-pool-kt9g6 to have valid conditions in 2m36s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wg5fc/node-pool-kt9g6 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-76dd8fb9b8-6kqj8 has a restartCount > 0 (3)
TestUpgradeControlPlane
53m32.42s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-knv7dmtw/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-knv7dmtw/release@sha256:e38dc0a11ee9cb116d71a991fdfba27d8cb2fe78560f5875cbaa1cf1ee3717e9 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-677jv/control-plane-upgrade-8zlb6 in 34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-8zlb6 util.go:2949: Successfully waited for HostedCluster e2e-clusters-677jv/control-plane-upgrade-8zlb6 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m0.65s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-677jv/control-plane-upgrade-8zlb6 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-knv7dmtw/release@sha256:e38dc0a11ee9cb116d71a991fdfba27d8cb2fe78560f5875cbaa1cf1ee3717e9 util.go:598: Successfully waited for HostedCluster e2e-clusters-677jv/control-plane-upgrade-8zlb6 to rollout in 0s
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-677jv/control-plane-upgrade-8zlb6 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-7b88477dd4-9hq98 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: rate: Wait(n=1) would exceed context deadline 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-677jv-control-plane-upgrade-8zlb6/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-677jv-control-plane-upgrade-8zlb6/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)