PR #6745 - 09-12 11:02

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

139
Total Tests
91
Passed
31
Failed
17
Skipped

Failed Tests

TestAutoscaling
37m13.12s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-xbcjr/autoscaling-d6xz6 in 21s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-d6xz6 util.go:2687: Successfully waited for HostedCluster e2e-clusters-xbcjr/autoscaling-d6xz6 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
29m8.26s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xbcjr/autoscaling-d6xz6 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-autoscaling-d6xz6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-d6xz6.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-d6xz6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.170.110.68:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-d6xz6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.209.251.47:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-d6xz6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.198.50.110:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m48.025s util.go:513: Successfully waited for 1 nodes to become ready in 18m57s util.go:546: Successfully waited for HostedCluster e2e-clusters-xbcjr/autoscaling-d6xz6 to rollout in 6m48s util.go:2687: Successfully waited for HostedCluster e2e-clusters-xbcjr/autoscaling-d6xz6 to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xbcjr/autoscaling-d6xz6 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-7c74dc6b66-wq6vc has a restartCount > 0 (1)
TestCreateCluster
30m59.85s
create_cluster_test.go:1831: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-pvwzt/create-cluster-5zlvn in 54s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-5zlvn util.go:2687: Successfully waited for HostedCluster e2e-clusters-pvwzt/create-cluster-5zlvn to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
23m6.23s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pvwzt/create-cluster-5zlvn 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-create-cluster-5zlvn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-5zlvn.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-5zlvn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.72.108.31:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-5zlvn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.55.31.30:443: i/o timeout util.go:330: Successfully waited for a successful connection to the guest API server in 1m58.025s util.go:513: Successfully waited for 3 nodes to become ready in 19m45s util.go:546: Successfully waited for HostedCluster e2e-clusters-pvwzt/create-cluster-5zlvn to rollout in 0s util.go:2687: Successfully waited for HostedCluster e2e-clusters-pvwzt/create-cluster-5zlvn to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pvwzt/create-cluster-5zlvn 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-698c687484-vgsk9 has a restartCount > 0 (1)
TestCreateClusterCustomConfig
28m36.11s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-4dkfg/custom-config-2bzrf in 38s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-2bzrf util.go:2687: Successfully waited for HostedCluster e2e-clusters-4dkfg/custom-config-2bzrf to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
19m44.28s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4dkfg/custom-config-2bzrf 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-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-2bzrf.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-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.210.206.127:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.229.220.146:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.229.220.146:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.210.206.127:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.229.220.146:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.210.206.127:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.229.220.146:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.210.206.127:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.229.220.146:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.210.206.127:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.88.126.247:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.210.206.127:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.229.220.146:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-2bzrf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.88.126.247: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 7m21s util.go:546: Successfully waited for HostedCluster e2e-clusters-4dkfg/custom-config-2bzrf to rollout in 7m45s util.go:2687: Successfully waited for HostedCluster e2e-clusters-4dkfg/custom-config-2bzrf to have valid conditions in 25ms
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4dkfg/custom-config-2bzrf 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-6fd66f994b-db59v has a restartCount > 0 (1)
TestCreateClusterPrivate
28m43.94s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-t46wf/private-9fptf in 15s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-9fptf util.go:2687: Successfully waited for HostedCluster e2e-clusters-t46wf/private-9fptf to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
19m9.22s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-t46wf/private-9fptf in 1m27s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:643: Successfully waited for NodePools for HostedCluster e2e-clusters-t46wf/private-9fptf to have all of their desired nodes in 16m18s util.go:546: Successfully waited for HostedCluster e2e-clusters-t46wf/private-9fptf to rollout in 1m24s util.go:2687: Successfully waited for HostedCluster e2e-clusters-t46wf/private-9fptf to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-t46wf/private-9fptf 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-687c769544-ddxbn has a restartCount > 0 (1)
TestCreateClusterPrivateWithRouteKAS
30m25.18s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-wp7sj/private-nn2tf in 34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-nn2tf util.go:2687: Successfully waited for HostedCluster e2e-clusters-wp7sj/private-nn2tf to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
22m39.16s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wp7sj/private-nn2tf in 1m18s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:643: Successfully waited for NodePools for HostedCluster e2e-clusters-wp7sj/private-nn2tf to have all of their desired nodes in 19m21s util.go:546: Successfully waited for HostedCluster e2e-clusters-wp7sj/private-nn2tf to rollout in 1m30s util.go:2687: Successfully waited for HostedCluster e2e-clusters-wp7sj/private-nn2tf 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-wp7sj/private-nn2tf 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-66bb7484fd-2j4rk has a restartCount > 0 (1)
TestCreateClusterProxy
23m9.39s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-5k25w/proxy-tqxqz in 56s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-tqxqz util.go:2687: Successfully waited for HostedCluster e2e-clusters-5k25w/proxy-tqxqz to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
13m50.34s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5k25w/proxy-tqxqz 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-proxy-tqxqz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-tqxqz.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-tqxqz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.86.141.208:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-tqxqz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.235.117.250:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-tqxqz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.205.70.247:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-tqxqz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.86.141.208:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-tqxqz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.235.117.250:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-tqxqz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.205.70.247:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-tqxqz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.235.117.250: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 2 nodes to become ready in 5m54s util.go:546: Successfully waited for HostedCluster e2e-clusters-5k25w/proxy-tqxqz to rollout in 4m6s util.go:2687: Successfully waited for HostedCluster e2e-clusters-5k25w/proxy-tqxqz to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5k25w/proxy-tqxqz 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-d5c5c48fb-ptmp4 has a restartCount > 0 (1)
TestCreateClusterRequestServingIsolation
28m17.73s
requestserving.go:105: Created request serving nodepool clusters/c37773f77a3c4ea9ad7f-mgmt-reqserving-4bzlg requestserving.go:105: Created request serving nodepool clusters/c37773f77a3c4ea9ad7f-mgmt-reqserving-rld86 requestserving.go:113: Created non request serving nodepool clusters/c37773f77a3c4ea9ad7f-mgmt-non-reqserving-qlng4 requestserving.go:113: Created non request serving nodepool clusters/c37773f77a3c4ea9ad7f-mgmt-non-reqserving-fks9b requestserving.go:113: Created non request serving nodepool clusters/c37773f77a3c4ea9ad7f-mgmt-non-reqserving-q8wtq util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/c37773f77a3c4ea9ad7f-mgmt-reqserving-4bzlg in 3m48s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/c37773f77a3c4ea9ad7f-mgmt-reqserving-rld86 in 100ms util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/c37773f77a3c4ea9ad7f-mgmt-non-reqserving-qlng4 in 3s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/c37773f77a3c4ea9ad7f-mgmt-non-reqserving-fks9b in 1m12.025s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/c37773f77a3c4ea9ad7f-mgmt-non-reqserving-q8wtq in 3s create_cluster_test.go:1974: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-s6695/request-serving-isolation-nl4lw in 11s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-nl4lw util.go:2687: Successfully waited for HostedCluster e2e-clusters-s6695/request-serving-isolation-nl4lw to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/c37773f77a3c4ea9ad7f-mgmt-reqserving-4bzlg requestserving.go:132: Tearing down custom nodepool clusters/c37773f77a3c4ea9ad7f-mgmt-reqserving-rld86 requestserving.go:132: Tearing down custom nodepool clusters/c37773f77a3c4ea9ad7f-mgmt-non-reqserving-qlng4 requestserving.go:132: Tearing down custom nodepool clusters/c37773f77a3c4ea9ad7f-mgmt-non-reqserving-fks9b requestserving.go:132: Tearing down custom nodepool clusters/c37773f77a3c4ea9ad7f-mgmt-non-reqserving-q8wtq hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
15m5.27s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-s6695/request-serving-isolation-nl4lw in 2m3s 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-nl4lw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-nl4lw.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-nl4lw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 174.129.11.157:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-nl4lw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 174.129.11.157:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-nl4lw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.206.187.145:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-nl4lw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 174.129.11.157:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-nl4lw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.206.187.145:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 2m6.025s util.go:513: Successfully waited for 3 nodes to become ready in 6m3s util.go:546: Successfully waited for HostedCluster e2e-clusters-s6695/request-serving-isolation-nl4lw to rollout in 4m0s util.go:2687: Successfully waited for HostedCluster e2e-clusters-s6695/request-serving-isolation-nl4lw to have valid conditions in 48s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-s6695/request-serving-isolation-nl4lw 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-68cf87d65b-jv8vn has a restartCount > 0 (1) util.go:755: Container kube-apiserver in pod kube-apiserver-68cf87d65b-kbwpd has a restartCount > 0 (1)
TestNodePool
0s
TestNodePool/HostedCluster0
9m20.98s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-lxx2k/node-pool-pc4h9 in 43s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-pc4h9 util.go:2687: Successfully waited for HostedCluster e2e-clusters-lxx2k/node-pool-pc4h9 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
4m4.18s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lxx2k/node-pool-pc4h9 in 1m21s 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-pc4h9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-pc4h9.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-pc4h9.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.86.71.247:443: i/o timeout util.go:330: Successfully waited for a successful connection to the guest API server in 1m32.025s util.go:513: Successfully waited for 0 nodes to become ready in 0s util.go:2687: Successfully waited for HostedCluster e2e-clusters-lxx2k/node-pool-pc4h9 to have valid conditions in 1m6s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lxx2k/node-pool-pc4h9 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-595f785c94-zd9fr has a restartCount > 0 (1)
TestNodePool/HostedCluster2
11m16.64s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-dpr4w/node-pool-mznln in 21s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-mznln util.go:2687: Successfully waited for HostedCluster e2e-clusters-dpr4w/node-pool-mznln to have valid conditions in 25ms hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
4m47.28s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-dpr4w/node-pool-mznln 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-mznln.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-mznln.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-mznln.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.234.219.218:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-mznln.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.28.152:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-mznln.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.234.219.218:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-mznln.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.28.152:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-mznln.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.86.143.220:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-mznln.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.28.152: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 0 nodes to become ready in 25ms util.go:2687: Successfully waited for HostedCluster e2e-clusters-dpr4w/node-pool-mznln to have valid conditions in 1m15s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-dpr4w/node-pool-mznln 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-86f6d677c6-b2qgq has a restartCount > 0 (1)
TestUpgradeControlPlane
40m3.78s
control_plane_upgrade_test.go:27: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-qnx9wvb2/release@sha256:64e94a8a52a548f07ab4c8acd53c21c7d3d980460125c9bf6b0fdc67b8e2511b, toImage: registry.build01.ci.openshift.org/ci-op-qnx9wvb2/release@sha256:1dd95d6345ea1e7ecefe93d04a1cf17cf645c4f01a3ae8278723adaa0f82c8e2 hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-hrtx5/control-plane-upgrade-zwjh7 in 25s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-zwjh7 util.go:2687: Successfully waited for HostedCluster e2e-clusters-hrtx5/control-plane-upgrade-zwjh7 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestUpgradeControlPlane/Main
16m40.66s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hrtx5/control-plane-upgrade-zwjh7 in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:330: Successfully waited for a successful connection to the guest API server in 0s control_plane_upgrade_test.go:49: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-qnx9wvb2/release@sha256:1dd95d6345ea1e7ecefe93d04a1cf17cf645c4f01a3ae8278723adaa0f82c8e2 util.go:546: Successfully waited for HostedCluster e2e-clusters-hrtx5/control-plane-upgrade-zwjh7 to rollout in 0s
TestUpgradeControlPlane/Main/Verifying_featureGate_status_has_entries_for_the_same_versions_as_clusterVersion
30ms
control_plane_upgrade_test.go:100: version 4.21.0-0.ci-2025-09-11-160443 found in ClusterVersion history but missing in FeatureGate status control_plane_upgrade_test.go:103: Expected the same number of entries in FeatureGate status (1) as in ClusterVersion history (2) Expected <int>: 1 to equal <int>: 2