PR #6802 - 09-12 17:24

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

162
Total Tests
117
Passed
28
Failed
17
Skipped

Failed Tests

TestAutoscaling
25m39.32s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-fnsdv/autoscaling-vn69q in 52s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-vn69q util.go:2721: Successfully waited for HostedCluster e2e-clusters-fnsdv/autoscaling-vn69q to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
16m50.45s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fnsdv/autoscaling-vn69q 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-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-vn69q.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-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.200.201.152:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.226.81.175:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.200.201.152:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.72.224:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.200.201.152:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.72.224:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.200.201.152:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.72.224:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.226.81.175:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.200.201.152:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-vn69q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.226.81.175:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 2m42.05s util.go:513: Successfully waited for 1 nodes to become ready in 8m15s util.go:546: Successfully waited for HostedCluster e2e-clusters-fnsdv/autoscaling-vn69q to rollout in 4m12s util.go:2721: Successfully waited for HostedCluster e2e-clusters-fnsdv/autoscaling-vn69q to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fnsdv/autoscaling-vn69q 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-7fdcf45998-2595s has a restartCount > 0 (1)
TestCreateCluster
25m37.62s
create_cluster_test.go:1831: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-twnr4/create-cluster-bwq2p in 1m6s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-bwq2p util.go:2721: Successfully waited for HostedCluster e2e-clusters-twnr4/create-cluster-bwq2p to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
15m53.25s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-twnr4/create-cluster-bwq2p 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-create-cluster-bwq2p.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-bwq2p.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-bwq2p.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.81.186.170:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-bwq2p.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.231.7.254:443: i/o timeout util.go:330: Successfully waited for a successful connection to the guest API server in 1m48.05s util.go:513: Successfully waited for 3 nodes to become ready in 6m54s util.go:546: Successfully waited for HostedCluster e2e-clusters-twnr4/create-cluster-bwq2p to rollout in 5m42s util.go:2721: Successfully waited for HostedCluster e2e-clusters-twnr4/create-cluster-bwq2p to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-twnr4/create-cluster-bwq2p 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-84cb7f8f66-dltl5 has a restartCount > 0 (1)
TestCreateClusterCustomConfig
27m15.1s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-frxb8/custom-config-xh2rn in 24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-xh2rn util.go:2721: Successfully waited for HostedCluster e2e-clusters-frxb8/custom-config-xh2rn to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
18m38.25s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-frxb8/custom-config-xh2rn 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-custom-config-xh2rn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-xh2rn.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-xh2rn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.59.39:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-xh2rn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.196.148.130:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-xh2rn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.59.39:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-xh2rn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.93.245.191:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-xh2rn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.59.39:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-xh2rn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.93.245.191:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-xh2rn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.196.148.130:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-xh2rn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.59.39:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 2m27.025s util.go:513: Successfully waited for 2 nodes to become ready in 6m51s util.go:546: Successfully waited for HostedCluster e2e-clusters-frxb8/custom-config-xh2rn to rollout in 7m51s util.go:2721: Successfully waited for HostedCluster e2e-clusters-frxb8/custom-config-xh2rn to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-frxb8/custom-config-xh2rn 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-76d4b76b7b-kctkg has a restartCount > 0 (1)
TestCreateClusterPrivate
44m41.96s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-r7cdd/private-5xvzc in 22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-5xvzc util.go:2721: Successfully waited for HostedCluster e2e-clusters-r7cdd/private-5xvzc to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
36m12.16s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-r7cdd/private-5xvzc in 1m36s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:643: Successfully waited for NodePools for HostedCluster e2e-clusters-r7cdd/private-5xvzc to have all of their desired nodes in 21m36s util.go:546: Successfully waited for HostedCluster e2e-clusters-r7cdd/private-5xvzc to rollout in 13m0s util.go:2721: Successfully waited for HostedCluster e2e-clusters-r7cdd/private-5xvzc to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-r7cdd/private-5xvzc 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-66c56d94f6-xsrwt has a restartCount > 0 (1)
TestCreateClusterPrivateWithRouteKAS
32m51.74s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-7jb9t/private-7dl7s in 22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-7dl7s util.go:2721: Successfully waited for HostedCluster e2e-clusters-7jb9t/private-7dl7s to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
25m3.13s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7jb9t/private-7dl7s in 1m36s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:643: Successfully waited for NodePools for HostedCluster e2e-clusters-7jb9t/private-7dl7s to have all of their desired nodes in 20m33s util.go:546: Successfully waited for HostedCluster e2e-clusters-7jb9t/private-7dl7s to rollout in 2m24s util.go:2721: Successfully waited for HostedCluster e2e-clusters-7jb9t/private-7dl7s 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-7jb9t/private-7dl7s 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-7bbcdf8cd4-bvgt8 has a restartCount > 0 (1)
TestCreateClusterProxy
41m14.06s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-6nmzb/proxy-t7zd6 in 49s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-t7zd6 util.go:2721: Successfully waited for HostedCluster e2e-clusters-6nmzb/proxy-t7zd6 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
31m56.23s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-6nmzb/proxy-t7zd6 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-proxy-t7zd6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-t7zd6.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-t7zd6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.208.198.50:443: i/o timeout util.go:330: Successfully waited for a successful connection to the guest API server in 1m38.925s util.go:513: Successfully waited for 2 nodes to become ready in 20m27s util.go:546: Successfully waited for HostedCluster e2e-clusters-6nmzb/proxy-t7zd6 to rollout in 8m15s util.go:2721: Successfully waited for HostedCluster e2e-clusters-6nmzb/proxy-t7zd6 to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-6nmzb/proxy-t7zd6 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-bd9484689-92c4t has a restartCount > 0 (1)
TestCreateClusterRequestServingIsolation
27m9.92s
requestserving.go:105: Created request serving nodepool clusters/54a428bd9993911366b6-mgmt-reqserving-cj9lp requestserving.go:105: Created request serving nodepool clusters/54a428bd9993911366b6-mgmt-reqserving-c2z57 requestserving.go:113: Created non request serving nodepool clusters/54a428bd9993911366b6-mgmt-non-reqserving-8q2n6 requestserving.go:113: Created non request serving nodepool clusters/54a428bd9993911366b6-mgmt-non-reqserving-bp2hv requestserving.go:113: Created non request serving nodepool clusters/54a428bd9993911366b6-mgmt-non-reqserving-8mblf util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/54a428bd9993911366b6-mgmt-reqserving-cj9lp in 3m0s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/54a428bd9993911366b6-mgmt-reqserving-c2z57 in 39s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/54a428bd9993911366b6-mgmt-non-reqserving-8q2n6 in 36s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/54a428bd9993911366b6-mgmt-non-reqserving-bp2hv in 0s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/54a428bd9993911366b6-mgmt-non-reqserving-8mblf in 3s create_cluster_test.go:1974: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-7dl4v/request-serving-isolation-4jvq8 in 22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-4jvq8 util.go:2721: Successfully waited for HostedCluster e2e-clusters-7dl4v/request-serving-isolation-4jvq8 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/54a428bd9993911366b6-mgmt-reqserving-cj9lp requestserving.go:132: Tearing down custom nodepool clusters/54a428bd9993911366b6-mgmt-reqserving-c2z57 requestserving.go:132: Tearing down custom nodepool clusters/54a428bd9993911366b6-mgmt-non-reqserving-8q2n6 requestserving.go:132: Tearing down custom nodepool clusters/54a428bd9993911366b6-mgmt-non-reqserving-bp2hv requestserving.go:132: Tearing down custom nodepool clusters/54a428bd9993911366b6-mgmt-non-reqserving-8mblf hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
14m23.3s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7dl4v/request-serving-isolation-4jvq8 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-request-serving-isolation-4jvq8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-4jvq8.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-4jvq8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.211.164.4:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-4jvq8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.229.199.28:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-4jvq8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.173.103.185:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-4jvq8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.229.199.28:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-4jvq8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.173.103.185:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-4jvq8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.229.199.28:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-4jvq8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.211.164.4:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-4jvq8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.173.103.185:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m36.025s util.go:513: Successfully waited for 3 nodes to become ready in 7m15s util.go:546: Successfully waited for HostedCluster e2e-clusters-7dl4v/request-serving-isolation-4jvq8 to rollout in 3m33s util.go:2721: Successfully waited for HostedCluster e2e-clusters-7dl4v/request-serving-isolation-4jvq8 to have valid conditions in 0s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7dl4v/request-serving-isolation-4jvq8 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-f4ddfd655-j26nt has a restartCount > 0 (1) util.go:755: Container kube-apiserver in pod kube-apiserver-f4ddfd655-wmgl5 has a restartCount > 0 (1)
TestNodePool
0s
TestNodePool/HostedCluster0
11m52.42s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-2jls6/node-pool-rzqn7 in 38s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-rzqn7 util.go:2721: Successfully waited for HostedCluster e2e-clusters-2jls6/node-pool-rzqn7 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
6m23.31s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2jls6/node-pool-rzqn7 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-rzqn7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-rzqn7.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-rzqn7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.224.35:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-rzqn7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.224.35:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-rzqn7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.88.118.96:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-rzqn7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.224.35:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-rzqn7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.231.238.170:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-rzqn7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.224.35:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m57.05s util.go:513: Successfully waited for 0 nodes to become ready in 0s util.go:2721: Successfully waited for HostedCluster e2e-clusters-2jls6/node-pool-rzqn7 to have valid conditions in 2m42s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2jls6/node-pool-rzqn7 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-6c566477c-ktm8s has a restartCount > 0 (1)
TestNodePool/HostedCluster2
12m4.68s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-hb7kk/node-pool-27xs5 in 36s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-27xs5 util.go:2721: Successfully waited for HostedCluster e2e-clusters-hb7kk/node-pool-27xs5 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
6m23.43s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hb7kk/node-pool-27xs5 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-node-pool-27xs5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-27xs5.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-27xs5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.200.9.144:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-27xs5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.160.45.150:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-27xs5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.160.45.150:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-27xs5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.200.9.144:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-27xs5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.54.39.161:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m42.05s util.go:513: Successfully waited for 0 nodes to become ready in 25ms util.go:2721: Successfully waited for HostedCluster e2e-clusters-hb7kk/node-pool-27xs5 to have valid conditions in 2m54s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hb7kk/node-pool-27xs5 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-7dbcbd6b5c-wtdz7 has a restartCount > 0 (1)