PR #7404 - 01-09 10:13

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

149
Total Tests
98
Passed
32
Failed
19
Skipped

Failed Tests

TestAutoscaling
20m49.28s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-pkrn8/autoscaling-mxfjs in 35s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-mxfjs util.go:2949: Successfully waited for HostedCluster e2e-clusters-pkrn8/autoscaling-mxfjs to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
13m36.37s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pkrn8/autoscaling-mxfjs 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-autoscaling-mxfjs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-mxfjs.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-mxfjs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.229.206.222:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-mxfjs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.52.118.213:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-mxfjs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.89.150.237:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m1.025s util.go:565: Successfully waited for 1 nodes to become ready in 6m6s util.go:598: Successfully waited for HostedCluster e2e-clusters-pkrn8/autoscaling-mxfjs to rollout in 3m27s util.go:2949: Successfully waited for HostedCluster e2e-clusters-pkrn8/autoscaling-mxfjs to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pkrn8/autoscaling-mxfjs 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-6b845d49c6-7qjrk has a restartCount > 0 (6)
TestCreateCluster
26m16.71s
create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-256fq/create-cluster-7s4l9 in 35s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-7s4l9 util.go:2949: Successfully waited for HostedCluster e2e-clusters-256fq/create-cluster-7s4l9 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
19m2.36s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-256fq/create-cluster-7s4l9 in 1m54s 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-7s4l9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-7s4l9.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-7s4l9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.3.9.70:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-7s4l9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.203.201.183:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-7s4l9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.3.9.70:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-7s4l9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.203.201.183:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-7s4l9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.86.162.9:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 1m57.025s util.go:565: Successfully waited for 3 nodes to become ready in 7m45s util.go:598: Successfully waited for HostedCluster e2e-clusters-256fq/create-cluster-7s4l9 to rollout in 7m21s util.go:2949: Successfully waited for HostedCluster e2e-clusters-256fq/create-cluster-7s4l9 to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-256fq/create-cluster-7s4l9 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-7f5b988fc-7z4gm has a restartCount > 0 (7)
TestCreateClusterCustomConfig
26m7.02s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9n2dk/custom-config-md4xm in 53s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-md4xm util.go:2949: Successfully waited for HostedCluster e2e-clusters-9n2dk/custom-config-md4xm to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
18m47.33s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9n2dk/custom-config-md4xm 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-custom-config-md4xm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-md4xm.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-md4xm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.200.37:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-md4xm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.200.189.132:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-md4xm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.200.37:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-md4xm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.200.37:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m54.025s util.go:565: Successfully waited for 2 nodes to become ready in 7m0s util.go:598: Successfully waited for HostedCluster e2e-clusters-9n2dk/custom-config-md4xm to rollout in 7m12s util.go:2949: Successfully waited for HostedCluster e2e-clusters-9n2dk/custom-config-md4xm to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9n2dk/custom-config-md4xm 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-595d885ffb-s8ljr has a restartCount > 0 (7)
TestCreateClusterPrivate
22m28.3s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-f6kpw/private-p2jf7 in 33s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-p2jf7 util.go:2949: Successfully waited for HostedCluster e2e-clusters-f6kpw/private-p2jf7 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
16m0.15s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-f6kpw/private-p2jf7 in 1m33s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-f6kpw/private-p2jf7 to have all of their desired nodes in 9m51s util.go:598: Successfully waited for HostedCluster e2e-clusters-f6kpw/private-p2jf7 to rollout in 4m36s util.go:2949: Successfully waited for HostedCluster e2e-clusters-f6kpw/private-p2jf7 to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-f6kpw/private-p2jf7 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-6599fdc65b-rsxm2 has a restartCount > 0 (7)
TestCreateClusterPrivateWithRouteKAS
22m21.63s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-hj4xj/private-52hj2 in 34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-52hj2 util.go:2949: Successfully waited for HostedCluster e2e-clusters-hj4xj/private-52hj2 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
15m30.14s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hj4xj/private-52hj2 in 1m36s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-hj4xj/private-52hj2 to have all of their desired nodes in 9m39s util.go:598: Successfully waited for HostedCluster e2e-clusters-hj4xj/private-52hj2 to rollout in 3m45s util.go:2949: Successfully waited for HostedCluster e2e-clusters-hj4xj/private-52hj2 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-hj4xj/private-52hj2 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-7f6c8958d-zqbz6 has a restartCount > 0 (6)
TestCreateClusterProxy
23m7.72s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-ldcqw/proxy-9sdsq in 51s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-9sdsq util.go:2949: Successfully waited for HostedCluster e2e-clusters-ldcqw/proxy-9sdsq to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
15m17.33s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ldcqw/proxy-9sdsq 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-9sdsq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-9sdsq.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-9sdsq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.85.71.145:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-9sdsq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.209.18.62:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m21.025s util.go:565: Successfully waited for 2 nodes to become ready in 8m6s util.go:598: Successfully waited for HostedCluster e2e-clusters-ldcqw/proxy-9sdsq to rollout in 3m57s util.go:2949: Successfully waited for HostedCluster e2e-clusters-ldcqw/proxy-9sdsq to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ldcqw/proxy-9sdsq 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-b44cbbd7b-7x9hz has a restartCount > 0 (6)
TestCreateClusterRequestServingIsolation
28m57.48s
requestserving.go:105: Created request serving nodepool clusters/45a1bee2d186167d1e5c-mgmt-reqserving-668pb requestserving.go:105: Created request serving nodepool clusters/45a1bee2d186167d1e5c-mgmt-reqserving-ckxps requestserving.go:113: Created non request serving nodepool clusters/45a1bee2d186167d1e5c-mgmt-non-reqserving-vrj6x requestserving.go:113: Created non request serving nodepool clusters/45a1bee2d186167d1e5c-mgmt-non-reqserving-vv9p7 requestserving.go:113: Created non request serving nodepool clusters/45a1bee2d186167d1e5c-mgmt-non-reqserving-9k6gk util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/45a1bee2d186167d1e5c-mgmt-reqserving-668pb in 4m9s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/45a1bee2d186167d1e5c-mgmt-reqserving-ckxps in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/45a1bee2d186167d1e5c-mgmt-non-reqserving-vrj6x in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/45a1bee2d186167d1e5c-mgmt-non-reqserving-vv9p7 in 3s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/45a1bee2d186167d1e5c-mgmt-non-reqserving-9k6gk in 24s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-tpj7j/request-serving-isolation-zlsnw in 17s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-zlsnw util.go:2949: Successfully waited for HostedCluster e2e-clusters-tpj7j/request-serving-isolation-zlsnw to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/45a1bee2d186167d1e5c-mgmt-reqserving-668pb requestserving.go:132: Tearing down custom nodepool clusters/45a1bee2d186167d1e5c-mgmt-reqserving-ckxps requestserving.go:132: Tearing down custom nodepool clusters/45a1bee2d186167d1e5c-mgmt-non-reqserving-vrj6x requestserving.go:132: Tearing down custom nodepool clusters/45a1bee2d186167d1e5c-mgmt-non-reqserving-vv9p7 requestserving.go:132: Tearing down custom nodepool clusters/45a1bee2d186167d1e5c-mgmt-non-reqserving-9k6gk hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
17m5.36s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-tpj7j/request-serving-isolation-zlsnw in 1m45s 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-zlsnw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-zlsnw.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-zlsnw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.206.204.92:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m15.025s util.go:565: Successfully waited for 3 nodes to become ready in 8m48s util.go:598: Successfully waited for HostedCluster e2e-clusters-tpj7j/request-serving-isolation-zlsnw to rollout in 4m51s util.go:2949: Successfully waited for HostedCluster e2e-clusters-tpj7j/request-serving-isolation-zlsnw to have valid conditions in 21s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-tpj7j/request-serving-isolation-zlsnw 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-558fd475f6-nzrkz has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
10m15.85s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-grd67/node-pool-tm4sv in 33s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-tm4sv util.go:2949: Successfully waited for HostedCluster e2e-clusters-grd67/node-pool-tm4sv to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
5m40.34s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-grd67/node-pool-tm4sv 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-node-pool-tm4sv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-tm4sv.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-tm4sv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.91.110.181:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m26.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-grd67/node-pool-tm4sv to have valid conditions in 2m33s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-grd67/node-pool-tm4sv 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-78c78dc68-2sr2l has a restartCount > 0 (3)
TestNodePool/HostedCluster2
10m49.76s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-64cf8/node-pool-8fptn in 41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-8fptn util.go:2949: Successfully waited for HostedCluster e2e-clusters-64cf8/node-pool-8fptn to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
6m11.33s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-64cf8/node-pool-8fptn in 2m3s 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-8fptn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-8fptn.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-8fptn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.144.10.158:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8fptn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.213.76.243:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8fptn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.144.10.158:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8fptn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.144.10.158:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8fptn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.204.79.210:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8fptn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.144.10.158:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8fptn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.213.76.243:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8fptn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.204.79.210:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m18.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-64cf8/node-pool-8fptn to have valid conditions in 1m45s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-64cf8/node-pool-8fptn 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-75bb98d97b-mscnc has a restartCount > 0 (3)
TestUpgradeControlPlane
54m11.8s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-g7rnl14h/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-g7rnl14h/release@sha256:f7258d59249f2f8c743639f727537f97279a12f1b9fff33c7eda4a83dcbc5f8f hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9f7jd/control-plane-upgrade-wdwvw in 23s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-wdwvw util.go:2949: Successfully waited for HostedCluster e2e-clusters-9f7jd/control-plane-upgrade-wdwvw to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m0.54s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9f7jd/control-plane-upgrade-wdwvw 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-g7rnl14h/release@sha256:f7258d59249f2f8c743639f727537f97279a12f1b9fff33c7eda4a83dcbc5f8f util.go:598: Successfully waited for HostedCluster e2e-clusters-9f7jd/control-plane-upgrade-wdwvw to rollout in 0s
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9f7jd/control-plane-upgrade-wdwvw 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-7cb9f7966d-rqd2c 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-9f7jd-control-plane-upgrade-wdwvw/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-9f7jd-control-plane-upgrade-wdwvw/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)