PR #6777 - 09-12 13:36

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

162
Total Tests
117
Passed
28
Failed
17
Skipped

Failed Tests

TestAutoscaling
23m8.77s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-4zg4r/autoscaling-xn9pf in 20s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-xn9pf util.go:2721: Successfully waited for HostedCluster e2e-clusters-4zg4r/autoscaling-xn9pf to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
14m56.75s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4zg4r/autoscaling-xn9pf in 1m39s util.go:276: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-xn9pf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-xn9pf.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-xn9pf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.221.116.196:443: i/o timeout util.go:330: Successfully waited for a successful connection to the guest API server in 1m33.45s util.go:513: Successfully waited for 1 nodes to become ready in 7m42s util.go:546: Successfully waited for HostedCluster e2e-clusters-4zg4r/autoscaling-xn9pf to rollout in 3m57s util.go:2721: Successfully waited for HostedCluster e2e-clusters-4zg4r/autoscaling-xn9pf to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4zg4r/autoscaling-xn9pf in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:755: Container kube-apiserver in pod kube-apiserver-67d7bd78d7-btldj has a restartCount > 0 (1)
TestCreateCluster
37m43.82s
create_cluster_test.go:1831: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-k4mzm/create-cluster-tqr9m in 1m14s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-tqr9m util.go:2721: Successfully waited for HostedCluster e2e-clusters-k4mzm/create-cluster-tqr9m to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
28m20.23s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k4mzm/create-cluster-tqr9m in 1m39s util.go:276: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-tqr9m.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-tqr9m.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-tqr9m.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 72.44.37.97:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-tqr9m.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.202.64.73:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-tqr9m.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.202.64.73:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-tqr9m.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.22.7.183:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-tqr9m.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 72.44.37.97:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-tqr9m.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.22.7.183:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m45.025s util.go:513: Successfully waited for 3 nodes to become ready in 24m51s util.go:546: Successfully waited for HostedCluster e2e-clusters-k4mzm/create-cluster-tqr9m to rollout in 0s util.go:2721: Successfully waited for HostedCluster e2e-clusters-k4mzm/create-cluster-tqr9m to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k4mzm/create-cluster-tqr9m in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:755: Container kube-apiserver in pod kube-apiserver-6985957777-npc98 has a restartCount > 0 (1)
TestCreateClusterCustomConfig
27m5.7s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-sfsbp/custom-config-rphb5 in 34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-rphb5 util.go:2721: Successfully waited for HostedCluster e2e-clusters-sfsbp/custom-config-rphb5 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
18m11.27s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sfsbp/custom-config-rphb5 in 1m18s util.go:276: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-rphb5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-rphb5.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-rphb5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.228.28.139:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-rphb5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.215.53.139:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-rphb5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.228.28.139:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 2m30.025s util.go:513: Successfully waited for 2 nodes to become ready in 6m15s util.go:546: Successfully waited for HostedCluster e2e-clusters-sfsbp/custom-config-rphb5 to rollout in 8m3s util.go:2721: Successfully waited for HostedCluster e2e-clusters-sfsbp/custom-config-rphb5 to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sfsbp/custom-config-rphb5 in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:755: Container kube-apiserver in pod kube-apiserver-c94db6767-wxkjg has a restartCount > 0 (1)
TestCreateClusterPrivate
33m44.4s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-zt88r/private-z87tm in 41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-z87tm util.go:2721: Successfully waited for HostedCluster e2e-clusters-zt88r/private-z87tm to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
25m30.2s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zt88r/private-z87tm in 1m42s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:643: Successfully waited for NodePools for HostedCluster e2e-clusters-zt88r/private-z87tm to have all of their desired nodes in 8m30s util.go:546: Successfully waited for HostedCluster e2e-clusters-zt88r/private-z87tm to rollout in 15m18s util.go:2721: Successfully waited for HostedCluster e2e-clusters-zt88r/private-z87tm to have valid conditions in 25ms
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
50ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zt88r/private-z87tm in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:755: Container kube-apiserver in pod kube-apiserver-85dcf79c4b-zmkt7 has a restartCount > 0 (1)
TestCreateClusterPrivateWithRouteKAS
26m30.84s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-c79wz/private-5l4vp in 40s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-5l4vp util.go:2721: Successfully waited for HostedCluster e2e-clusters-c79wz/private-5l4vp to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
18m45.14s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-c79wz/private-5l4vp in 1m33s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:643: Successfully waited for NodePools for HostedCluster e2e-clusters-c79wz/private-5l4vp to have all of their desired nodes in 16m42s util.go:546: Successfully waited for HostedCluster e2e-clusters-c79wz/private-5l4vp to rollout in 0s util.go:2721: Successfully waited for HostedCluster e2e-clusters-c79wz/private-5l4vp to have valid conditions in 0s
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster/EnsureNoCrashingPods
30.03s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-c79wz/private-5l4vp in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:755: Container kube-apiserver in pod kube-apiserver-7d77db6f9b-ktc45 has a restartCount > 0 (1)
TestCreateClusterProxy
39m34.35s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-8ns5c/proxy-wr52h in 1m29s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-wr52h util.go:2721: Successfully waited for HostedCluster e2e-clusters-8ns5c/proxy-wr52h to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
29m14.34s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8ns5c/proxy-wr52h in 1m42s util.go:276: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-wr52h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-wr52h.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-wr52h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.119.48:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-wr52h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.70.208.116:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-wr52h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.21.122.128:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-wr52h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.70.208.116:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-wr52h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.119.48:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-wr52h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.21.122.128:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-wr52h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.119.48:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 2m12.025s util.go:513: Successfully waited for 2 nodes to become ready in 19m24s util.go:546: Successfully waited for HostedCluster e2e-clusters-8ns5c/proxy-wr52h to rollout in 5m51s util.go:2721: Successfully waited for HostedCluster e2e-clusters-8ns5c/proxy-wr52h to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8ns5c/proxy-wr52h in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:755: Container kube-apiserver in pod kube-apiserver-5b6b6cb4fd-xwxsx has a restartCount > 0 (1)
TestCreateClusterRequestServingIsolation
26m4.38s
requestserving.go:105: Created request serving nodepool clusters/7c413d498004a37fed5c-mgmt-reqserving-9mm2m requestserving.go:105: Created request serving nodepool clusters/7c413d498004a37fed5c-mgmt-reqserving-8jvnl requestserving.go:113: Created non request serving nodepool clusters/7c413d498004a37fed5c-mgmt-non-reqserving-z2sn4 requestserving.go:113: Created non request serving nodepool clusters/7c413d498004a37fed5c-mgmt-non-reqserving-l8kmg requestserving.go:113: Created non request serving nodepool clusters/7c413d498004a37fed5c-mgmt-non-reqserving-c9294 util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/7c413d498004a37fed5c-mgmt-reqserving-9mm2m in 3m24s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/7c413d498004a37fed5c-mgmt-reqserving-8jvnl in 0s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/7c413d498004a37fed5c-mgmt-non-reqserving-z2sn4 in 45s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/7c413d498004a37fed5c-mgmt-non-reqserving-l8kmg in 50ms util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/7c413d498004a37fed5c-mgmt-non-reqserving-c9294 in 39s create_cluster_test.go:1974: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-7jcqp/request-serving-isolation-9x88h in 31s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-9x88h util.go:2721: Successfully waited for HostedCluster e2e-clusters-7jcqp/request-serving-isolation-9x88h to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/7c413d498004a37fed5c-mgmt-reqserving-9mm2m requestserving.go:132: Tearing down custom nodepool clusters/7c413d498004a37fed5c-mgmt-reqserving-8jvnl requestserving.go:132: Tearing down custom nodepool clusters/7c413d498004a37fed5c-mgmt-non-reqserving-z2sn4 requestserving.go:132: Tearing down custom nodepool clusters/7c413d498004a37fed5c-mgmt-non-reqserving-l8kmg requestserving.go:132: Tearing down custom nodepool clusters/7c413d498004a37fed5c-mgmt-non-reqserving-c9294 hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
13m0.87s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7jcqp/request-serving-isolation-9x88h in 1m30s util.go:276: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-9x88h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-9x88h.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-9x88h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.216.61.67:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-9x88h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.216.61.67:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m25.6s util.go:513: Successfully waited for 3 nodes to become ready in 6m15s util.go:546: Successfully waited for HostedCluster e2e-clusters-7jcqp/request-serving-isolation-9x88h to rollout in 3m45s util.go:2721: Successfully waited for HostedCluster e2e-clusters-7jcqp/request-serving-isolation-9x88h to have valid conditions in 0s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
50ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7jcqp/request-serving-isolation-9x88h in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:755: Container manager in pod capi-provider-5f6c76c875-m8hr5 has a restartCount > 0 (1) util.go:755: Container kube-apiserver in pod kube-apiserver-6c69c58c8c-bt884 has a restartCount > 0 (1) util.go:755: Container kube-apiserver in pod kube-apiserver-6c69c58c8c-v54zx has a restartCount > 0 (1)
TestNodePool
0s
TestNodePool/HostedCluster0
9m52.13s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-l2htc/node-pool-8lhqd in 1m9s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-8lhqd util.go:2721: Successfully waited for HostedCluster e2e-clusters-l2htc/node-pool-8lhqd to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
3m57.21s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-l2htc/node-pool-8lhqd in 1m24s util.go:276: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8lhqd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-8lhqd.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-8lhqd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.89.167.203:443: i/o timeout util.go:330: Successfully waited for a successful connection to the guest API server in 1m28.05s util.go:513: Successfully waited for 0 nodes to become ready in 25ms util.go:2721: Successfully waited for HostedCluster e2e-clusters-l2htc/node-pool-8lhqd to have valid conditions in 1m0s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-l2htc/node-pool-8lhqd in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:755: Container kube-apiserver in pod kube-apiserver-b8c94d6b4-tf5zf has a restartCount > 0 (1)
TestNodePool/HostedCluster2
10m46.52s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-4pz76/node-pool-strqd in 1m11s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-strqd util.go:2721: Successfully waited for HostedCluster e2e-clusters-4pz76/node-pool-strqd to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
4m14.31s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4pz76/node-pool-strqd in 1m39s util.go:276: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-strqd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-strqd.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-strqd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.221.70.102:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-strqd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.222.84.189:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-strqd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.221.70.102:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-strqd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.222.84.189:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-strqd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.221.70.102:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m42.025s util.go:513: Successfully waited for 0 nodes to become ready in 0s util.go:2721: Successfully waited for HostedCluster e2e-clusters-4pz76/node-pool-strqd to have valid conditions in 48s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4pz76/node-pool-strqd in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:755: Container kube-apiserver in pod kube-apiserver-64fbfc9458-kqwnd has a restartCount > 0 (1)