PR #6779 - 09-12 08:15

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

162
Total Tests
117
Passed
28
Failed
17
Skipped

Failed Tests

TestAutoscaling
40m35.13s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-fpfkg/autoscaling-sgvxg in 22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-sgvxg util.go:2721: Successfully waited for HostedCluster e2e-clusters-fpfkg/autoscaling-sgvxg to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
33m0.61s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fpfkg/autoscaling-sgvxg in 1m33s 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-sgvxg.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-sgvxg.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-sgvxg.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.202.172.15:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-sgvxg.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.212.135.250:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-sgvxg.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.202.172.15:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m58.25s util.go:513: Successfully waited for 1 nodes to become ready in 17m54s util.go:546: Successfully waited for HostedCluster e2e-clusters-fpfkg/autoscaling-sgvxg to rollout in 11m30s util.go:2721: Successfully waited for HostedCluster e2e-clusters-fpfkg/autoscaling-sgvxg to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
70ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fpfkg/autoscaling-sgvxg 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-69c454dc85-j7j67 has a restartCount > 0 (1)
TestCreateCluster
24m5.45s
create_cluster_test.go:1831: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-lcb7v/create-cluster-zrxvn in 46s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-zrxvn util.go:2721: Successfully waited for HostedCluster e2e-clusters-lcb7v/create-cluster-zrxvn to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
14m44.46s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lcb7v/create-cluster-zrxvn 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-create-cluster-zrxvn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-zrxvn.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-zrxvn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.214.72.82:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-zrxvn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.205.43.132:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-zrxvn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.214.72.82:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 2m9.025s util.go:513: Successfully waited for 3 nodes to become ready in 7m0s util.go:546: Successfully waited for HostedCluster e2e-clusters-lcb7v/create-cluster-zrxvn to rollout in 4m0s util.go:2721: Successfully waited for HostedCluster e2e-clusters-lcb7v/create-cluster-zrxvn to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
100ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lcb7v/create-cluster-zrxvn 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-5b5d575b79-snxz2 has a restartCount > 0 (1)
TestCreateClusterCustomConfig
39m50.62s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-x6v2b/custom-config-f24mn in 31s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-f24mn util.go:2721: Successfully waited for HostedCluster e2e-clusters-x6v2b/custom-config-f24mn to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
31m53.33s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-x6v2b/custom-config-f24mn in 1m51s 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-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-f24mn.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-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.210.145.67:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.203.175.166:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.210.145.67:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.203.175.166:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.210.145.67:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.203.175.166:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.210.145.67:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.203.175.166:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.201.180.36:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.203.175.166:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.210.145.67:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.201.180.36:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.210.145.67:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.203.175.166:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.210.145.67:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f24mn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.201.180.36:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 2m57.025s util.go:513: Successfully waited for 2 nodes to become ready in 20m12s util.go:546: Successfully waited for HostedCluster e2e-clusters-x6v2b/custom-config-f24mn to rollout in 6m48s util.go:2721: Successfully waited for HostedCluster e2e-clusters-x6v2b/custom-config-f24mn to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-x6v2b/custom-config-f24mn 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-f5c76994f-tllbp has a restartCount > 0 (1)
TestCreateClusterPrivate
20m39.09s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-wg7lr/private-vzldf in 33s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-vzldf util.go:2721: Successfully waited for HostedCluster e2e-clusters-wg7lr/private-vzldf to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
13m42.14s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wg7lr/private-vzldf in 1m51s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:643: Successfully waited for NodePools for HostedCluster e2e-clusters-wg7lr/private-vzldf to have all of their desired nodes in 8m6s util.go:546: Successfully waited for HostedCluster e2e-clusters-wg7lr/private-vzldf to rollout in 3m45s util.go:2721: Successfully waited for HostedCluster e2e-clusters-wg7lr/private-vzldf to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wg7lr/private-vzldf 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-6fdd884ffc-q74pr has a restartCount > 0 (1)
TestCreateClusterPrivateWithRouteKAS
28m44.75s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-qssmg/private-rp9m2 in 40s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-rp9m2 util.go:2721: Successfully waited for HostedCluster e2e-clusters-qssmg/private-rp9m2 to have valid conditions in 25ms hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
20m54.13s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qssmg/private-rp9m2 in 1m45s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:643: Successfully waited for NodePools for HostedCluster e2e-clusters-qssmg/private-rp9m2 to have all of their desired nodes in 16m42s util.go:546: Successfully waited for HostedCluster e2e-clusters-qssmg/private-rp9m2 to rollout in 1m57s util.go:2721: Successfully waited for HostedCluster e2e-clusters-qssmg/private-rp9m2 to have valid conditions in 0s
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster/EnsureNoCrashingPods
30.02s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qssmg/private-rp9m2 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-75b7f4d68f-b766d has a restartCount > 0 (1)
TestCreateClusterProxy
25m11.45s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-pbdcg/proxy-f74kd in 25s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-f74kd util.go:2721: Successfully waited for HostedCluster e2e-clusters-pbdcg/proxy-f74kd to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
14m27.78s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pbdcg/proxy-f74kd in 1m54s 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-f74kd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-f74kd.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-f74kd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.238.94.132:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-f74kd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.193.221.111:443: i/o timeout util.go:330: Successfully waited for a successful connection to the guest API server in 1m46.5s util.go:513: Successfully waited for 2 nodes to become ready in 6m30s util.go:546: Successfully waited for HostedCluster e2e-clusters-pbdcg/proxy-f74kd to rollout in 4m12s util.go:2721: Successfully waited for HostedCluster e2e-clusters-pbdcg/proxy-f74kd to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pbdcg/proxy-f74kd 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-678cf8b68c-pbv68 has a restartCount > 0 (1)
TestCreateClusterRequestServingIsolation
26m45.51s
requestserving.go:105: Created request serving nodepool clusters/6dc34741c61cdcd32c19-mgmt-reqserving-kfrhn requestserving.go:105: Created request serving nodepool clusters/6dc34741c61cdcd32c19-mgmt-reqserving-zvl8t requestserving.go:113: Created non request serving nodepool clusters/6dc34741c61cdcd32c19-mgmt-non-reqserving-q8r2n requestserving.go:113: Created non request serving nodepool clusters/6dc34741c61cdcd32c19-mgmt-non-reqserving-q9jc4 requestserving.go:113: Created non request serving nodepool clusters/6dc34741c61cdcd32c19-mgmt-non-reqserving-fcgrd util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/6dc34741c61cdcd32c19-mgmt-reqserving-kfrhn in 3m36s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/6dc34741c61cdcd32c19-mgmt-reqserving-zvl8t in 27s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/6dc34741c61cdcd32c19-mgmt-non-reqserving-q8r2n in 54s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/6dc34741c61cdcd32c19-mgmt-non-reqserving-q9jc4 in 100ms util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/6dc34741c61cdcd32c19-mgmt-non-reqserving-fcgrd in 100ms create_cluster_test.go:1974: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-t94t4/request-serving-isolation-xtzf2 in 22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-xtzf2 util.go:2721: Successfully waited for HostedCluster e2e-clusters-t94t4/request-serving-isolation-xtzf2 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/6dc34741c61cdcd32c19-mgmt-reqserving-kfrhn requestserving.go:132: Tearing down custom nodepool clusters/6dc34741c61cdcd32c19-mgmt-reqserving-zvl8t requestserving.go:132: Tearing down custom nodepool clusters/6dc34741c61cdcd32c19-mgmt-non-reqserving-q8r2n requestserving.go:132: Tearing down custom nodepool clusters/6dc34741c61cdcd32c19-mgmt-non-reqserving-q9jc4 requestserving.go:132: Tearing down custom nodepool clusters/6dc34741c61cdcd32c19-mgmt-non-reqserving-fcgrd hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
14m5.36s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-t94t4/request-serving-isolation-xtzf2 in 1m33s 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-xtzf2.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-xtzf2.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-xtzf2.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.224.180.40:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-xtzf2.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.215.106.25:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-xtzf2.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.224.180.40:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m45.05s util.go:513: Successfully waited for 3 nodes to become ready in 6m21s util.go:546: Successfully waited for HostedCluster e2e-clusters-t94t4/request-serving-isolation-xtzf2 to rollout in 3m51s util.go:2721: Successfully waited for HostedCluster e2e-clusters-t94t4/request-serving-isolation-xtzf2 to have valid conditions in 30s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-t94t4/request-serving-isolation-xtzf2 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-6bb848c96-85qbl has a restartCount > 0 (1) util.go:755: Container kube-apiserver in pod kube-apiserver-6bb848c96-jbp55 has a restartCount > 0 (1)
TestNodePool
0s
TestNodePool/HostedCluster0
11m34.26s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-bqkkz/node-pool-xck5n in 17s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-xck5n util.go:2721: Successfully waited for HostedCluster e2e-clusters-bqkkz/node-pool-xck5n to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
6m9.35s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bqkkz/node-pool-xck5n in 1m51s 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-xck5n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-xck5n.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-xck5n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.198.236.23:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-xck5n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.208.163.2:443: i/o timeout util.go:330: Successfully waited for a successful connection to the guest API server in 1m40.025s util.go:513: Successfully waited for 0 nodes to become ready in 0s util.go:2721: Successfully waited for HostedCluster e2e-clusters-bqkkz/node-pool-xck5n to have valid conditions in 2m33s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bqkkz/node-pool-xck5n 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-7767bc979-vpsv4 has a restartCount > 0 (1)
TestNodePool/HostedCluster2
11m30.36s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-2tpkn/node-pool-bxsvd in 22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-bxsvd util.go:2721: Successfully waited for HostedCluster e2e-clusters-2tpkn/node-pool-bxsvd to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
6m11.21s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2tpkn/node-pool-bxsvd in 1m36s 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-bxsvd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-bxsvd.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-bxsvd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.22.178.44:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-bxsvd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.200.87.60:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-bxsvd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.242.8.65:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-bxsvd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.200.87.60:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m57.025s util.go:513: Successfully waited for 0 nodes to become ready in 0s util.go:2721: Successfully waited for HostedCluster e2e-clusters-2tpkn/node-pool-bxsvd to have valid conditions in 2m33s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2tpkn/node-pool-bxsvd 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-865cb5b5f5-wbgv6 has a restartCount > 0 (1)