PR #7355 - 01-09 18:26

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

149
Total Tests
98
Passed
32
Failed
19
Skipped

Failed Tests

TestAutoscaling
21m29.52s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-mlqn5/autoscaling-sjjr7 in 33s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-sjjr7 util.go:2949: Successfully waited for HostedCluster e2e-clusters-mlqn5/autoscaling-sjjr7 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
14m30.4s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mlqn5/autoscaling-sjjr7 in 1m21s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-sjjr7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-sjjr7.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-sjjr7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.218.23.47:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m28.1s util.go:565: Successfully waited for 1 nodes to become ready in 7m42s util.go:598: Successfully waited for HostedCluster e2e-clusters-mlqn5/autoscaling-sjjr7 to rollout in 3m54s util.go:2949: Successfully waited for HostedCluster e2e-clusters-mlqn5/autoscaling-sjjr7 to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mlqn5/autoscaling-sjjr7 in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-5fb444d74c-jptd8 has a restartCount > 0 (6)
TestCreateCluster
23m27.64s
create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-g7thl/create-cluster-q8j7z in 40s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-q8j7z util.go:2949: Successfully waited for HostedCluster e2e-clusters-g7thl/create-cluster-q8j7z to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
15m49.29s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-g7thl/create-cluster-q8j7z in 1m36s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-q8j7z.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-q8j7z.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-q8j7z.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.2.108.62:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-q8j7z.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.26.120.95:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m31.95s util.go:565: Successfully waited for 3 nodes to become ready in 8m24s util.go:598: Successfully waited for HostedCluster e2e-clusters-g7thl/create-cluster-q8j7z to rollout in 4m12s util.go:2949: Successfully waited for HostedCluster e2e-clusters-g7thl/create-cluster-q8j7z to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-g7thl/create-cluster-q8j7z in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-996765bc6-thqgd has a restartCount > 0 (6)
TestCreateClusterCustomConfig
25m22.97s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-jgt42/custom-config-7wpl8 in 17s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-7wpl8 util.go:2949: Successfully waited for HostedCluster e2e-clusters-jgt42/custom-config-7wpl8 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
18m50.27s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jgt42/custom-config-7wpl8 in 1m30s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-7wpl8.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-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.71.80.186:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.233.193.235:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.71.80.186:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.82.90.63:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.71.80.186:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.233.193.235:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.71.80.186:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.233.193.235:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.71.80.186:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.233.193.235:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.71.80.186:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.82.90.63:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.233.193.235:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.82.90.63:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.233.193.235:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.71.80.186:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-7wpl8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.233.193.235:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 3m9.025s util.go:565: Successfully waited for 2 nodes to become ready in 6m54s util.go:598: Successfully waited for HostedCluster e2e-clusters-jgt42/custom-config-7wpl8 to rollout in 7m12s util.go:2949: Successfully waited for HostedCluster e2e-clusters-jgt42/custom-config-7wpl8 to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jgt42/custom-config-7wpl8 in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-5df6897b99-zbmfr has a restartCount > 0 (7)
TestCreateClusterPrivate
27m42.42s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-bhjhb/private-7mnrm in 54s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-7mnrm util.go:2949: Successfully waited for HostedCluster e2e-clusters-bhjhb/private-7mnrm to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
20m3.32s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bhjhb/private-7mnrm in 1m36s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-bhjhb/private-7mnrm to have all of their desired nodes in 10m9s util.go:598: Successfully waited for HostedCluster e2e-clusters-bhjhb/private-7mnrm to rollout in 8m18s util.go:2949: Successfully waited for HostedCluster e2e-clusters-bhjhb/private-7mnrm to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bhjhb/private-7mnrm in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-74784dd5bc-r65nc has a restartCount > 0 (8)
TestCreateClusterPrivateWithRouteKAS
21m37.55s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-45xwz/private-hpv59 in 27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-hpv59 util.go:2949: Successfully waited for HostedCluster e2e-clusters-45xwz/private-hpv59 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
14m51.22s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-45xwz/private-hpv59 in 1m39s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-45xwz/private-hpv59 to have all of their desired nodes in 9m18s util.go:598: Successfully waited for HostedCluster e2e-clusters-45xwz/private-hpv59 to rollout in 3m24s util.go:2949: Successfully waited for HostedCluster e2e-clusters-45xwz/private-hpv59 to have valid conditions in 0s
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster/EnsureNoCrashingPods
30.02s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-45xwz/private-hpv59 in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-59fdbbb65f-xm48m has a restartCount > 0 (6)
TestCreateClusterProxy
23m48.83s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-mc9rk/proxy-cwdqp in 39s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-cwdqp util.go:2949: Successfully waited for HostedCluster e2e-clusters-mc9rk/proxy-cwdqp to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
15m42.39s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mc9rk/proxy-cwdqp in 1m36.025s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-cwdqp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-cwdqp.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-cwdqp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.49.111.115:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m13.15s util.go:565: Successfully waited for 2 nodes to become ready in 8m42s util.go:598: Successfully waited for HostedCluster e2e-clusters-mc9rk/proxy-cwdqp to rollout in 4m6s util.go:2949: Successfully waited for HostedCluster e2e-clusters-mc9rk/proxy-cwdqp to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mc9rk/proxy-cwdqp in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-85cf4f6c99-crjff has a restartCount > 0 (6)
TestCreateClusterRequestServingIsolation
29m48.75s
requestserving.go:105: Created request serving nodepool clusters/3789b8817c6daff55c8e-mgmt-reqserving-z7h69 requestserving.go:105: Created request serving nodepool clusters/3789b8817c6daff55c8e-mgmt-reqserving-zbkr5 requestserving.go:113: Created non request serving nodepool clusters/3789b8817c6daff55c8e-mgmt-non-reqserving-pcpqk requestserving.go:113: Created non request serving nodepool clusters/3789b8817c6daff55c8e-mgmt-non-reqserving-mns2z requestserving.go:113: Created non request serving nodepool clusters/3789b8817c6daff55c8e-mgmt-non-reqserving-ptmlb util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/3789b8817c6daff55c8e-mgmt-reqserving-z7h69 in 4m0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/3789b8817c6daff55c8e-mgmt-reqserving-zbkr5 in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/3789b8817c6daff55c8e-mgmt-non-reqserving-pcpqk in 1m0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/3789b8817c6daff55c8e-mgmt-non-reqserving-mns2z in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/3789b8817c6daff55c8e-mgmt-non-reqserving-ptmlb in 3s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-8xrkj/request-serving-isolation-klqkf in 16s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-klqkf util.go:2949: Successfully waited for HostedCluster e2e-clusters-8xrkj/request-serving-isolation-klqkf to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/3789b8817c6daff55c8e-mgmt-reqserving-z7h69 requestserving.go:132: Tearing down custom nodepool clusters/3789b8817c6daff55c8e-mgmt-reqserving-zbkr5 requestserving.go:132: Tearing down custom nodepool clusters/3789b8817c6daff55c8e-mgmt-non-reqserving-pcpqk requestserving.go:132: Tearing down custom nodepool clusters/3789b8817c6daff55c8e-mgmt-non-reqserving-mns2z requestserving.go:132: Tearing down custom nodepool clusters/3789b8817c6daff55c8e-mgmt-non-reqserving-ptmlb hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
17m27.31s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8xrkj/request-serving-isolation-klqkf in 1m33s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-klqkf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-klqkf.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-klqkf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.209.219.121:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m46.025s util.go:565: Successfully waited for 3 nodes to become ready in 8m21s util.go:598: Successfully waited for HostedCluster e2e-clusters-8xrkj/request-serving-isolation-klqkf to rollout in 4m21s util.go:2949: Successfully waited for HostedCluster e2e-clusters-8xrkj/request-serving-isolation-klqkf to have valid conditions in 1m21s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8xrkj/request-serving-isolation-klqkf in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-556d58756c-8hmmq has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
10m14.65s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-t4l88/node-pool-n8882 in 29s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-n8882 util.go:2949: Successfully waited for HostedCluster e2e-clusters-t4l88/node-pool-n8882 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
5m44.21s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-t4l88/node-pool-n8882 in 1m36s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-n8882.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-n8882.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-n8882.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.223.251.160:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m33.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-t4l88/node-pool-n8882 to have valid conditions in 2m30s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-t4l88/node-pool-n8882 in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-76768b6875-sp8kg has a restartCount > 0 (4)
TestNodePool/HostedCluster2
8m57.25s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-gf52z/node-pool-9kpvh in 18s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-9kpvh util.go:2949: Successfully waited for HostedCluster e2e-clusters-gf52z/node-pool-9kpvh to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
5m47.33s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-gf52z/node-pool-9kpvh in 1m33s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-9kpvh.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-9kpvh.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-9kpvh.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.20.213.90:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m36.1s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-gf52z/node-pool-9kpvh to have valid conditions in 2m33s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-gf52z/node-pool-9kpvh in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-5997f8fc7f-r6sxd has a restartCount > 0 (4)
TestUpgradeControlPlane
55m43.12s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-fhgh54bi/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-fhgh54bi/release@sha256:8b25e51379816e3942bbc181c81972c36b7f7fb3051672f4553e98ff007dda65 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-wqskc/control-plane-upgrade-jg4js in 39s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-jg4js util.go:2949: Successfully waited for HostedCluster e2e-clusters-wqskc/control-plane-upgrade-jg4js to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m0.73s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wqskc/control-plane-upgrade-jg4js in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:363: Successfully waited for a successful connection to the guest API server in 0s control_plane_upgrade_test.go:52: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-fhgh54bi/release@sha256:8b25e51379816e3942bbc181c81972c36b7f7fb3051672f4553e98ff007dda65 util.go:598: Successfully waited for HostedCluster e2e-clusters-wqskc/control-plane-upgrade-jg4js to rollout in 0s
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wqskc/control-plane-upgrade-jg4js in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-7ffbb44979-5cw7h has a restartCount > 0 (8)
TestUpgradeControlPlane/Main/Wait_for_control_plane_components_to_complete_rollout
30m0s
eventually.go:258: Failed to get **v1beta1.ControlPlaneComponent: client rate limiter Wait returned an error: context deadline exceeded util.go:638: Failed to wait for control plane components to complete rollout in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1beta1.ControlPlaneComponent state after 30m0s eventually.go:400: - observed **v1beta1.ControlPlaneComponent e2e-clusters-wqskc-control-plane-upgrade-jg4js/cluster-network-operator invalid: eventually.go:403: - incorrect condition: wanted RolloutComplete=True, got RolloutComplete=False: WaitingForOperands(deployment cloud-network-config-controller is not ready) eventually.go:403: - component cluster-network-operator is still on version 4.22.0-0.ci-2026-01-08-185312 util.go:638: *v1beta1.ControlPlaneComponent e2e-clusters-wqskc-control-plane-upgrade-jg4js/cluster-network-operator conditions: util.go:638: Available=True: AsExpected(Deployment cluster-network-operator is available) util.go:638: RolloutComplete=False: WaitingForOperands(deployment cloud-network-config-controller is not ready)