PR #7446 - 01-09 11:17

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

149
Total Tests
98
Passed
32
Failed
19
Skipped

Failed Tests

TestAutoscaling
22m44.76s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9g8pt/autoscaling-l6765 in 20s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-l6765 util.go:2949: Successfully waited for HostedCluster e2e-clusters-9g8pt/autoscaling-l6765 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
16m10.35s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9g8pt/autoscaling-l6765 in 1m27s 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-l6765.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-l6765.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-l6765.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.171.136.31:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-l6765.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.207.173.69:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 2m14.025s util.go:565: Successfully waited for 1 nodes to become ready in 6m36s util.go:598: Successfully waited for HostedCluster e2e-clusters-9g8pt/autoscaling-l6765 to rollout in 5m48s util.go:2949: Successfully waited for HostedCluster e2e-clusters-9g8pt/autoscaling-l6765 to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9g8pt/autoscaling-l6765 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-549558454d-bcr4t has a restartCount > 0 (7)
TestCreateCluster
23m45.18s
create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-7v7cp/create-cluster-jvw7q in 46s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-jvw7q util.go:2949: Successfully waited for HostedCluster e2e-clusters-7v7cp/create-cluster-jvw7q to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
15m59.37s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7v7cp/create-cluster-jvw7q in 2m3s 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-jvw7q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-jvw7q.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-jvw7q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.208.77.112:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-jvw7q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.208.77.112:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-jvw7q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.194.155.217:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-jvw7q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.208.77.112:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-jvw7q.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.194.155.217:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m9.025s util.go:565: Successfully waited for 3 nodes to become ready in 7m45s util.go:598: Successfully waited for HostedCluster e2e-clusters-7v7cp/create-cluster-jvw7q to rollout in 3m57s util.go:2949: Successfully waited for HostedCluster e2e-clusters-7v7cp/create-cluster-jvw7q to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7v7cp/create-cluster-jvw7q 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-7c79774897-kjnd7 has a restartCount > 0 (6)
TestCreateClusterCustomConfig
25m5.91s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-btz8n/custom-config-ck5mf in 21s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-ck5mf util.go:2949: Successfully waited for HostedCluster e2e-clusters-btz8n/custom-config-ck5mf to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
17m59.26s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-btz8n/custom-config-ck5mf 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-custom-config-ck5mf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-ck5mf.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-ck5mf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.165.24.163:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-ck5mf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.211.2.94:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-ck5mf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.165.24.163:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-ck5mf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.211.2.94:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-ck5mf.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.165.24.163:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m12.025s util.go:565: Successfully waited for 2 nodes to become ready in 7m0s util.go:598: Successfully waited for HostedCluster e2e-clusters-btz8n/custom-config-ck5mf to rollout in 7m9s util.go:2949: Successfully waited for HostedCluster e2e-clusters-btz8n/custom-config-ck5mf to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-btz8n/custom-config-ck5mf 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-67f46cf75b-dvh7b has a restartCount > 0 (7)
TestCreateClusterPrivate
24m12.53s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-xnxc2/private-n7km7 in 42s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-n7km7 util.go:2949: Successfully waited for HostedCluster e2e-clusters-xnxc2/private-n7km7 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
17m21.23s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xnxc2/private-n7km7 in 1m24.025s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-xnxc2/private-n7km7 to have all of their desired nodes in 10m48s util.go:598: Successfully waited for HostedCluster e2e-clusters-xnxc2/private-n7km7 to rollout in 5m9s util.go:2949: Successfully waited for HostedCluster e2e-clusters-xnxc2/private-n7km7 to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xnxc2/private-n7km7 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-6bd5474468-98h46 has a restartCount > 0 (7)
TestCreateClusterPrivateWithRouteKAS
23m2.34s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-f76c8/private-k7tc2 in 34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-k7tc2 util.go:2949: Successfully waited for HostedCluster e2e-clusters-f76c8/private-k7tc2 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
15m42.15s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-f76c8/private-k7tc2 in 2m6s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-f76c8/private-k7tc2 to have all of their desired nodes in 9m30s util.go:598: Successfully waited for HostedCluster e2e-clusters-f76c8/private-k7tc2 to rollout in 3m36s util.go:2949: Successfully waited for HostedCluster e2e-clusters-f76c8/private-k7tc2 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-f76c8/private-k7tc2 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-7559596476-r2rb6 has a restartCount > 0 (6)
TestCreateClusterProxy
22m23.39s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-vr676/proxy-whmcw in 55s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-whmcw util.go:2949: Successfully waited for HostedCluster e2e-clusters-vr676/proxy-whmcw to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
14m56.28s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vr676/proxy-whmcw in 2m24s 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-whmcw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.234.6.109:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-whmcw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.234.6.109:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-whmcw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.198.151.211:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-whmcw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.234.6.109:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 1m48.05s util.go:565: Successfully waited for 2 nodes to become ready in 6m45s util.go:598: Successfully waited for HostedCluster e2e-clusters-vr676/proxy-whmcw to rollout in 3m54s util.go:2949: Successfully waited for HostedCluster e2e-clusters-vr676/proxy-whmcw to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vr676/proxy-whmcw 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-77d78c9fb4-xjr68 has a restartCount > 0 (6)
TestCreateClusterRequestServingIsolation
28m53.19s
requestserving.go:105: Created request serving nodepool clusters/9b489db1c90c6a6bc02a-mgmt-reqserving-5p4ft requestserving.go:105: Created request serving nodepool clusters/9b489db1c90c6a6bc02a-mgmt-reqserving-hvd68 requestserving.go:113: Created non request serving nodepool clusters/9b489db1c90c6a6bc02a-mgmt-non-reqserving-qm9vq requestserving.go:113: Created non request serving nodepool clusters/9b489db1c90c6a6bc02a-mgmt-non-reqserving-2qf5b requestserving.go:113: Created non request serving nodepool clusters/9b489db1c90c6a6bc02a-mgmt-non-reqserving-rhk8s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/9b489db1c90c6a6bc02a-mgmt-reqserving-5p4ft in 4m57s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/9b489db1c90c6a6bc02a-mgmt-reqserving-hvd68 in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/9b489db1c90c6a6bc02a-mgmt-non-reqserving-qm9vq in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/9b489db1c90c6a6bc02a-mgmt-non-reqserving-2qf5b in 100ms util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/9b489db1c90c6a6bc02a-mgmt-non-reqserving-rhk8s in 27s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-qvcxv/request-serving-isolation-f8rcm in 42s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-f8rcm util.go:2949: Successfully waited for HostedCluster e2e-clusters-qvcxv/request-serving-isolation-f8rcm to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/9b489db1c90c6a6bc02a-mgmt-reqserving-5p4ft requestserving.go:132: Tearing down custom nodepool clusters/9b489db1c90c6a6bc02a-mgmt-reqserving-hvd68 requestserving.go:132: Tearing down custom nodepool clusters/9b489db1c90c6a6bc02a-mgmt-non-reqserving-qm9vq requestserving.go:132: Tearing down custom nodepool clusters/9b489db1c90c6a6bc02a-mgmt-non-reqserving-2qf5b requestserving.go:132: Tearing down custom nodepool clusters/9b489db1c90c6a6bc02a-mgmt-non-reqserving-rhk8s hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
15m40.32s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qvcxv/request-serving-isolation-f8rcm in 1m27s 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-f8rcm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-f8rcm.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-f8rcm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.165.28.18:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-f8rcm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.219.181.157:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-f8rcm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.158.123.27:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-f8rcm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.219.181.157:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-f8rcm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.165.28.18:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 3m59.025s util.go:565: Successfully waited for 3 nodes to become ready in 5m36s util.go:598: Successfully waited for HostedCluster e2e-clusters-qvcxv/request-serving-isolation-f8rcm to rollout in 4m33s util.go:2949: Successfully waited for HostedCluster e2e-clusters-qvcxv/request-serving-isolation-f8rcm to have valid conditions in 0s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qvcxv/request-serving-isolation-f8rcm 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-78547d986d-4tnh6 has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
8m56.58s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-m4f6m/node-pool-4fcwm in 25s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-4fcwm util.go:2949: Successfully waited for HostedCluster e2e-clusters-m4f6m/node-pool-4fcwm to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
5m42.29s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m4f6m/node-pool-4fcwm 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-node-pool-4fcwm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-4fcwm.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-4fcwm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.195.76.228:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-4fcwm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.89.238.164:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m43.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-m4f6m/node-pool-4fcwm to have valid conditions in 2m12s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m4f6m/node-pool-4fcwm 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-85999dc8dd-2dlg5 has a restartCount > 0 (4)
TestNodePool/HostedCluster2
10m8.53s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-64hgm/node-pool-ds9js in 19s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-ds9js util.go:2949: Successfully waited for HostedCluster e2e-clusters-64hgm/node-pool-ds9js to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
5m42.57s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-64hgm/node-pool-ds9js 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-node-pool-ds9js.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-ds9js.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-ds9js.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.238.14.61:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m16.15s util.go:565: Successfully waited for 0 nodes to become ready in 25ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-64hgm/node-pool-ds9js to have valid conditions in 2m39s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-64hgm/node-pool-ds9js 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-5b8fdb95cb-4gd9w has a restartCount > 0 (2)
TestUpgradeControlPlane
51m39.96s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-s61qv8wl/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-s61qv8wl/release@sha256:0de63e62f6be0b61ecf88a5a2add956190faef04c0d7f465dfbdd3afea436530 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-xsxx8/control-plane-upgrade-8p2rz in 24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-8p2rz util.go:2949: Successfully waited for HostedCluster e2e-clusters-xsxx8/control-plane-upgrade-8p2rz to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m0.79s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xsxx8/control-plane-upgrade-8p2rz 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-s61qv8wl/release@sha256:0de63e62f6be0b61ecf88a5a2add956190faef04c0d7f465dfbdd3afea436530 util.go:598: Successfully waited for HostedCluster e2e-clusters-xsxx8/control-plane-upgrade-8p2rz to rollout in 0s
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xsxx8/control-plane-upgrade-8p2rz 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-5455c8956d-sr78s 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-xsxx8-control-plane-upgrade-8p2rz/cluster-network-operator invalid: incorrect condition: wanted RolloutComplete=True, got RolloutComplete=False: WaitingForOperands(deployment cloud-network-config-controller is not ready) util.go:638: *v1beta1.ControlPlaneComponent e2e-clusters-xsxx8-control-plane-upgrade-8p2rz/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)