PR #7445 - 01-09 07:39

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

149
Total Tests
98
Passed
32
Failed
19
Skipped

Failed Tests

TestAutoscaling
24m27.76s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-k5nnn/autoscaling-hjh5w in 27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-hjh5w util.go:2949: Successfully waited for HostedCluster e2e-clusters-k5nnn/autoscaling-hjh5w to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
17m16.41s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k5nnn/autoscaling-hjh5w 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-autoscaling-hjh5w.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-hjh5w.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-hjh5w.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.206.219.50:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m23.175s util.go:565: Successfully waited for 1 nodes to become ready in 7m30s util.go:598: Successfully waited for HostedCluster e2e-clusters-k5nnn/autoscaling-hjh5w to rollout in 6m45s util.go:2949: Successfully waited for HostedCluster e2e-clusters-k5nnn/autoscaling-hjh5w to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k5nnn/autoscaling-hjh5w 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-68f5fd45bb-dj69v has a restartCount > 0 (7)
TestCreateCluster
28m2.84s
create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-sr2d9/create-cluster-98sbs in 49s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-98sbs util.go:2949: Successfully waited for HostedCluster e2e-clusters-sr2d9/create-cluster-98sbs to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
20m11.35s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sr2d9/create-cluster-98sbs 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-create-cluster-98sbs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-98sbs.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-98sbs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.194.170.100:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-98sbs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.194.214.147:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-98sbs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.212.199.157:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 1m45.1s util.go:565: Successfully waited for 3 nodes to become ready in 8m51s util.go:598: Successfully waited for HostedCluster e2e-clusters-sr2d9/create-cluster-98sbs to rollout in 7m57s util.go:2949: Successfully waited for HostedCluster e2e-clusters-sr2d9/create-cluster-98sbs to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sr2d9/create-cluster-98sbs 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-6b4cb455b7-mc2lg has a restartCount > 0 (7)
TestCreateClusterCustomConfig
25m20.29s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-rckww/custom-config-9rtjj in 34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-9rtjj util.go:2949: Successfully waited for HostedCluster e2e-clusters-rckww/custom-config-9rtjj to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
18m44.36s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-rckww/custom-config-9rtjj in 1m42s 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-9rtjj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-9rtjj.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-9rtjj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.198.161.159:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9rtjj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.84.198.231:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9rtjj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.55.248.215:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9rtjj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.55.248.215:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9rtjj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.84.198.231:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9rtjj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.55.248.215:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9rtjj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.84.198.231:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9rtjj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.198.161.159:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-9rtjj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.55.248.215:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m42.025s util.go:565: Successfully waited for 2 nodes to become ready in 6m51s util.go:598: Successfully waited for HostedCluster e2e-clusters-rckww/custom-config-9rtjj to rollout in 7m24s util.go:2949: Successfully waited for HostedCluster e2e-clusters-rckww/custom-config-9rtjj to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-rckww/custom-config-9rtjj 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-68764879fd-lnmhn has a restartCount > 0 (7)
TestCreateClusterPrivate
23m50.17s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-mxqd6/private-frdsw in 1m5s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-frdsw util.go:2949: Successfully waited for HostedCluster e2e-clusters-mxqd6/private-frdsw to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
15m48.22s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mxqd6/private-frdsw in 1m24s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-mxqd6/private-frdsw to have all of their desired nodes in 10m21s util.go:598: Successfully waited for HostedCluster e2e-clusters-mxqd6/private-frdsw to rollout in 4m3s util.go:2949: Successfully waited for HostedCluster e2e-clusters-mxqd6/private-frdsw to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
70ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mxqd6/private-frdsw 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-db9d75c5d-sz98k has a restartCount > 0 (7)
TestCreateClusterPrivateWithRouteKAS
22m39.02s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-sgn8n/private-pprrs in 51s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-pprrs util.go:2949: Successfully waited for HostedCluster e2e-clusters-sgn8n/private-pprrs to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
15m30.15s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sgn8n/private-pprrs 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-sgn8n/private-pprrs to have all of their desired nodes in 9m27s util.go:598: Successfully waited for HostedCluster e2e-clusters-sgn8n/private-pprrs to rollout in 3m57s util.go:2949: Successfully waited for HostedCluster e2e-clusters-sgn8n/private-pprrs to have valid conditions in 0s
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster/EnsureNoCrashingPods
30.03s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sgn8n/private-pprrs 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-57784ddb54-7lmmb has a restartCount > 0 (6)
TestCreateClusterProxy
23m55.6s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-jbfnn/proxy-vn4q8 in 29s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-vn4q8 util.go:2949: Successfully waited for HostedCluster e2e-clusters-jbfnn/proxy-vn4q8 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
15m26.28s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jbfnn/proxy-vn4q8 in 1m54s 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-vn4q8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-vn4q8.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-vn4q8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.217.122.158:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-vn4q8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.21.61.178:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-vn4q8.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.237.50.229:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m0.05s util.go:565: Successfully waited for 2 nodes to become ready in 7m54s util.go:598: Successfully waited for HostedCluster e2e-clusters-jbfnn/proxy-vn4q8 to rollout in 3m33s util.go:2949: Successfully waited for HostedCluster e2e-clusters-jbfnn/proxy-vn4q8 to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jbfnn/proxy-vn4q8 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-7bf669b4cd-6dj22 has a restartCount > 0 (6)
TestCreateClusterRequestServingIsolation
30m3.21s
requestserving.go:105: Created request serving nodepool clusters/205b0160580332549d60-mgmt-reqserving-4xx6h requestserving.go:105: Created request serving nodepool clusters/205b0160580332549d60-mgmt-reqserving-7n98r requestserving.go:113: Created non request serving nodepool clusters/205b0160580332549d60-mgmt-non-reqserving-zgsf8 requestserving.go:113: Created non request serving nodepool clusters/205b0160580332549d60-mgmt-non-reqserving-zx55h requestserving.go:113: Created non request serving nodepool clusters/205b0160580332549d60-mgmt-non-reqserving-k7dbx util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/205b0160580332549d60-mgmt-reqserving-4xx6h in 3m24s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/205b0160580332549d60-mgmt-reqserving-7n98r in 36s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/205b0160580332549d60-mgmt-non-reqserving-zgsf8 in 3s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/205b0160580332549d60-mgmt-non-reqserving-zx55h in 57s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/205b0160580332549d60-mgmt-non-reqserving-k7dbx in 100ms create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9lscj/request-serving-isolation-cgfkg in 17s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-cgfkg util.go:2949: Successfully waited for HostedCluster e2e-clusters-9lscj/request-serving-isolation-cgfkg to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/205b0160580332549d60-mgmt-reqserving-4xx6h requestserving.go:132: Tearing down custom nodepool clusters/205b0160580332549d60-mgmt-reqserving-7n98r requestserving.go:132: Tearing down custom nodepool clusters/205b0160580332549d60-mgmt-non-reqserving-zgsf8 requestserving.go:132: Tearing down custom nodepool clusters/205b0160580332549d60-mgmt-non-reqserving-zx55h requestserving.go:132: Tearing down custom nodepool clusters/205b0160580332549d60-mgmt-non-reqserving-k7dbx hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
17m12.47s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9lscj/request-serving-isolation-cgfkg 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-cgfkg.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-cgfkg.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-cgfkg.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.218.59.150:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m16.025s util.go:565: Successfully waited for 3 nodes to become ready in 8m39s util.go:598: Successfully waited for HostedCluster e2e-clusters-9lscj/request-serving-isolation-cgfkg to rollout in 5m39s util.go:2949: Successfully waited for HostedCluster e2e-clusters-9lscj/request-serving-isolation-cgfkg to have valid conditions in 0s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
50ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9lscj/request-serving-isolation-cgfkg 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-949ccd486-8d88b has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
10m22.52s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-r86z5/node-pool-sdm4g in 41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-sdm4g util.go:2949: Successfully waited for HostedCluster e2e-clusters-r86z5/node-pool-sdm4g to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
5m41.37s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-r86z5/node-pool-sdm4g 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-sdm4g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-sdm4g.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-sdm4g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.50.199.246:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-sdm4g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.1.233.71:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m30.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-r86z5/node-pool-sdm4g to have valid conditions in 2m33s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-r86z5/node-pool-sdm4g 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-54c56bdc58-pv5g8 has a restartCount > 0 (3)
TestNodePool/HostedCluster2
10m22.82s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-g7dnn/node-pool-8ffkn in 58s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-8ffkn util.go:2949: Successfully waited for HostedCluster e2e-clusters-g7dnn/node-pool-8ffkn to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
5m39.24s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-g7dnn/node-pool-8ffkn in 1m57s 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-8ffkn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-8ffkn.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-8ffkn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.225.184.92:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8ffkn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.213.255.1:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8ffkn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.225.184.92:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8ffkn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.213.255.1:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-8ffkn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.173.235.1:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m19.05s util.go:565: Successfully waited for 0 nodes to become ready in 25ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-g7dnn/node-pool-8ffkn to have valid conditions in 1m18s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-g7dnn/node-pool-8ffkn 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-79d4cb56f4-jxmqd has a restartCount > 0 (2)
TestUpgradeControlPlane
53m53.91s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-r7wlfncg/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-r7wlfncg/release@sha256:e3c5f081ca9fe52ba24b92e82a856ba88b1c99480c42355ed6ebc7922d64f4d6 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-4pmc5/control-plane-upgrade-87kz4 in 16s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-87kz4 util.go:2949: Successfully waited for HostedCluster e2e-clusters-4pmc5/control-plane-upgrade-87kz4 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m0.56s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4pmc5/control-plane-upgrade-87kz4 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-r7wlfncg/release@sha256:e3c5f081ca9fe52ba24b92e82a856ba88b1c99480c42355ed6ebc7922d64f4d6 util.go:598: Successfully waited for HostedCluster e2e-clusters-4pmc5/control-plane-upgrade-87kz4 to rollout in 0s
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4pmc5/control-plane-upgrade-87kz4 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-87c8c7b8b-mc8rm has a restartCount > 0 (7)
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-4pmc5-control-plane-upgrade-87kz4/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-4pmc5-control-plane-upgrade-87kz4/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)