PR #6809 - 09-12 18:10

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

139
Total Tests
91
Passed
31
Failed
17
Skipped

Failed Tests

TestAutoscaling
33m1.79s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-2rjv7/autoscaling-g8ks2 in 1m1s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-g8ks2 util.go:2721: Successfully waited for HostedCluster e2e-clusters-2rjv7/autoscaling-g8ks2 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
24m14.37s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2rjv7/autoscaling-g8ks2 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-g8ks2.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-g8ks2.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-g8ks2.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.120.226:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-g8ks2.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.209.76.105:443: i/o timeout util.go:330: Successfully waited for a successful connection to the guest API server in 2m9.025s util.go:513: Successfully waited for 1 nodes to become ready in 16m36s util.go:546: Successfully waited for HostedCluster e2e-clusters-2rjv7/autoscaling-g8ks2 to rollout in 3m48s util.go:2721: Successfully waited for HostedCluster e2e-clusters-2rjv7/autoscaling-g8ks2 to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2rjv7/autoscaling-g8ks2 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-6b5bf7bfb7-mq8pd has a restartCount > 0 (1)
TestCreateCluster
23m3s
create_cluster_test.go:1831: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-k7xqb/create-cluster-zln7n in 51s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-zln7n util.go:2721: Successfully waited for HostedCluster e2e-clusters-k7xqb/create-cluster-zln7n to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
14m23.34s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k7xqb/create-cluster-zln7n 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-create-cluster-zln7n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-zln7n.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-zln7n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.204.173.2:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-zln7n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.204.173.2:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m33.025s util.go:513: Successfully waited for 3 nodes to become ready in 7m6s util.go:546: Successfully waited for HostedCluster e2e-clusters-k7xqb/create-cluster-zln7n to rollout in 3m57s util.go:2721: Successfully waited for HostedCluster e2e-clusters-k7xqb/create-cluster-zln7n to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k7xqb/create-cluster-zln7n 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-75877669c4-khwt5 has a restartCount > 0 (1)
TestCreateClusterCustomConfig
33m10.52s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-xtkms/custom-config-9n95g in 40s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-9n95g util.go:2721: Successfully waited for HostedCluster e2e-clusters-xtkms/custom-config-9n95g to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
25m32.35s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xtkms/custom-config-9n95g 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-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-9n95g.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-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.219.164.168:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.213.200.181:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.237.254.60:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.213.200.181:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.237.254.60:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.219.164.168:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.237.254.60:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.219.164.168:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.237.254.60:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.219.164.168:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.237.254.60:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.219.164.168:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.237.254.60:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.219.164.168:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.237.254.60:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.213.200.181:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.237.254.60:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9n95g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.219.164.168:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 3m36.025s util.go:513: Successfully waited for 2 nodes to become ready in 15m9s util.go:546: Successfully waited for HostedCluster e2e-clusters-xtkms/custom-config-9n95g to rollout in 5m9s util.go:2721: Successfully waited for HostedCluster e2e-clusters-xtkms/custom-config-9n95g to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xtkms/custom-config-9n95g in 0s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:755: Container bootstrap in pod kube-apiserver-7f547c96d8-46x8k has a restartCount > 0 (1) util.go:755: Container kube-apiserver in pod kube-apiserver-7f547c96d8-46x8k has a restartCount > 0 (2)
TestCreateClusterPrivate
31m38.95s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-5rwt9/private-bxhpx in 38s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-bxhpx util.go:2721: Successfully waited for HostedCluster e2e-clusters-5rwt9/private-bxhpx to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
24m3.16s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5rwt9/private-bxhpx 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-5rwt9/private-bxhpx to have all of their desired nodes in 21m6s util.go:546: Successfully waited for HostedCluster e2e-clusters-5rwt9/private-bxhpx to rollout in 1m24s util.go:2721: Successfully waited for HostedCluster e2e-clusters-5rwt9/private-bxhpx to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
60ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5rwt9/private-bxhpx 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-7746977556-n9qpq has a restartCount > 0 (1)
TestCreateClusterPrivateWithRouteKAS
34m2.88s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-2mdxg/private-ntzg9 in 41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-ntzg9 util.go:2721: Successfully waited for HostedCluster e2e-clusters-2mdxg/private-ntzg9 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
25m51.15s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2mdxg/private-ntzg9 in 1m48s util.go:276: Successfully waited for kubeconfig secret to have data in 0s util.go:643: Successfully waited for NodePools for HostedCluster e2e-clusters-2mdxg/private-ntzg9 to have all of their desired nodes in 19m21s util.go:546: Successfully waited for HostedCluster e2e-clusters-2mdxg/private-ntzg9 to rollout in 4m12s util.go:2721: Successfully waited for HostedCluster e2e-clusters-2mdxg/private-ntzg9 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-2mdxg/private-ntzg9 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-5f9558688d-lh8wb has a restartCount > 0 (1)
TestCreateClusterProxy
24m57.93s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-wmb2f/proxy-nmm7x in 37s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-nmm7x util.go:2721: Successfully waited for HostedCluster e2e-clusters-wmb2f/proxy-nmm7x to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
14m38.37s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wmb2f/proxy-nmm7x 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-proxy-nmm7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-nmm7x.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-nmm7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.204.147.163:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-nmm7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.215.58.4:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-nmm7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.204.147.163:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-nmm7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.81.144.150:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-nmm7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.204.147.163:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-nmm7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.81.144.150:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-nmm7x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.204.147.163:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 2m15.025s util.go:513: Successfully waited for 2 nodes to become ready in 6m21s util.go:546: Successfully waited for HostedCluster e2e-clusters-wmb2f/proxy-nmm7x to rollout in 4m18s util.go:2721: Successfully waited for HostedCluster e2e-clusters-wmb2f/proxy-nmm7x to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wmb2f/proxy-nmm7x 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-848f79f49c-cn6qr has a restartCount > 0 (1)
TestCreateClusterRequestServingIsolation
27m3.18s
requestserving.go:105: Created request serving nodepool clusters/3cb1a3f7acd9fcba7ae8-mgmt-reqserving-wrs6r requestserving.go:105: Created request serving nodepool clusters/3cb1a3f7acd9fcba7ae8-mgmt-reqserving-4dfxj requestserving.go:113: Created non request serving nodepool clusters/3cb1a3f7acd9fcba7ae8-mgmt-non-reqserving-wvmbt requestserving.go:113: Created non request serving nodepool clusters/3cb1a3f7acd9fcba7ae8-mgmt-non-reqserving-rrj9v requestserving.go:113: Created non request serving nodepool clusters/3cb1a3f7acd9fcba7ae8-mgmt-non-reqserving-jbpkl util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/3cb1a3f7acd9fcba7ae8-mgmt-reqserving-wrs6r in 3m24s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/3cb1a3f7acd9fcba7ae8-mgmt-reqserving-4dfxj in 30s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/3cb1a3f7acd9fcba7ae8-mgmt-non-reqserving-wvmbt in 3s util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/3cb1a3f7acd9fcba7ae8-mgmt-non-reqserving-rrj9v in 100ms util.go:513: Successfully waited for 1 nodes to become ready for NodePool clusters/3cb1a3f7acd9fcba7ae8-mgmt-non-reqserving-jbpkl in 1m12s create_cluster_test.go:1974: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-hx8fh/request-serving-isolation-wwdgk in 24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-wwdgk util.go:2721: Successfully waited for HostedCluster e2e-clusters-hx8fh/request-serving-isolation-wwdgk to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/3cb1a3f7acd9fcba7ae8-mgmt-reqserving-wrs6r requestserving.go:132: Tearing down custom nodepool clusters/3cb1a3f7acd9fcba7ae8-mgmt-reqserving-4dfxj requestserving.go:132: Tearing down custom nodepool clusters/3cb1a3f7acd9fcba7ae8-mgmt-non-reqserving-wvmbt requestserving.go:132: Tearing down custom nodepool clusters/3cb1a3f7acd9fcba7ae8-mgmt-non-reqserving-rrj9v requestserving.go:132: Tearing down custom nodepool clusters/3cb1a3f7acd9fcba7ae8-mgmt-non-reqserving-jbpkl hypershift_framework.go:220: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
14m23.29s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hx8fh/request-serving-isolation-wwdgk in 1m45.025s 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-wwdgk.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-wwdgk.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-wwdgk.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.144.66.177:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-wwdgk.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.41.17:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-wwdgk.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.197.2.131:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-wwdgk.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.87.41.17: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 6m48s util.go:546: Successfully waited for HostedCluster e2e-clusters-hx8fh/request-serving-isolation-wwdgk to rollout in 3m36s util.go:2721: Successfully waited for HostedCluster e2e-clusters-hx8fh/request-serving-isolation-wwdgk to have valid conditions in 0s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hx8fh/request-serving-isolation-wwdgk 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-7d8596bd7-5bss2 has a restartCount > 0 (1) util.go:755: Container kube-apiserver in pod kube-apiserver-7d8596bd7-dv4q7 has a restartCount > 0 (1)
TestNodePool
0s
TestNodePool/HostedCluster0
9m51.43s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-hrz9w/node-pool-lh699 in 48s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-lh699 util.go:2721: Successfully waited for HostedCluster e2e-clusters-hrz9w/node-pool-lh699 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
4m8.22s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hrz9w/node-pool-lh699 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-lh699.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-lh699.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-lh699.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.204.236.159:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-lh699.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.88.129.102:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-lh699.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.204.236.159:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-lh699.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.88.129.102:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-lh699.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.204.236.159:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-lh699.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.223.17.131:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 1m48.05s util.go:513: Successfully waited for 0 nodes to become ready in 0s util.go:2721: Successfully waited for HostedCluster e2e-clusters-hrz9w/node-pool-lh699 to have valid conditions in 36s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hrz9w/node-pool-lh699 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-8487df5c6b-nfbn2 has a restartCount > 0 (1)
TestNodePool/HostedCluster2
10m40.56s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-b7pcv/node-pool-d8pfc in 59s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-d8pfc util.go:2721: Successfully waited for HostedCluster e2e-clusters-b7pcv/node-pool-d8pfc to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
4m50.2s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b7pcv/node-pool-d8pfc in 1m45s 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-d8pfc.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-d8pfc.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-d8pfc.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.201.137.247:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-d8pfc.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.214.186.225:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-d8pfc.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.223.201.244:443: connect: connection refused util.go:330: Successfully waited for a successful connection to the guest API server in 2m3.025s util.go:513: Successfully waited for 0 nodes to become ready in 0s util.go:2721: Successfully waited for HostedCluster e2e-clusters-b7pcv/node-pool-d8pfc to have valid conditions in 57s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b7pcv/node-pool-d8pfc 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-566b855646-4dvnw has a restartCount > 0 (1)
TestUpgradeControlPlane
41m18.53s
control_plane_upgrade_test.go:27: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-lgpxqw2d/release@sha256:64e94a8a52a548f07ab4c8acd53c21c7d3d980460125c9bf6b0fdc67b8e2511b, toImage: registry.build01.ci.openshift.org/ci-op-lgpxqw2d/release@sha256:a03ac0168da8a807c75f06d4202d345c3867c3aaae53f214f171d6059518dab4 hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-xc549/control-plane-upgrade-l8tv9 in 57s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-l8tv9 util.go:2721: Successfully waited for HostedCluster e2e-clusters-xc549/control-plane-upgrade-l8tv9 to have valid conditions in 0s hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestUpgradeControlPlane/Main
17m50.66s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xc549/control-plane-upgrade-l8tv9 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-lgpxqw2d/release@sha256:a03ac0168da8a807c75f06d4202d345c3867c3aaae53f214f171d6059518dab4 util.go:546: Successfully waited for HostedCluster e2e-clusters-xc549/control-plane-upgrade-l8tv9 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