PR #7355 - 01-09 19:56

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

149
Total Tests
98
Passed
32
Failed
19
Skipped

Failed Tests

TestAutoscaling
21m30.52s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-fk2z9/autoscaling-z2592 in 37s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-z2592 util.go:2949: Successfully waited for HostedCluster e2e-clusters-fk2z9/autoscaling-z2592 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
14m35.42s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fk2z9/autoscaling-z2592 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-z2592.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-z2592.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-z2592.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.85.95.116:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m33.125s util.go:565: Successfully waited for 1 nodes to become ready in 7m36s util.go:598: Successfully waited for HostedCluster e2e-clusters-fk2z9/autoscaling-z2592 to rollout in 3m48s util.go:2949: Successfully waited for HostedCluster e2e-clusters-fk2z9/autoscaling-z2592 to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fk2z9/autoscaling-z2592 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-74f965f8b5-mqvtc has a restartCount > 0 (6)
TestCreateCluster
25m23.52s
create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-d4kn2/create-cluster-9sml6 in 48s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-9sml6 util.go:2949: Successfully waited for HostedCluster e2e-clusters-d4kn2/create-cluster-9sml6 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
17m57.33s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-d4kn2/create-cluster-9sml6 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-create-cluster-9sml6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-9sml6.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-9sml6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.84.48.195:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m22.025s util.go:565: Successfully waited for 3 nodes to become ready in 7m57s util.go:598: Successfully waited for HostedCluster e2e-clusters-d4kn2/create-cluster-9sml6 to rollout in 6m36s util.go:2949: Successfully waited for HostedCluster e2e-clusters-d4kn2/create-cluster-9sml6 to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-d4kn2/create-cluster-9sml6 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-5f86f45ddb-q48kd has a restartCount > 0 (7)
TestCreateClusterCustomConfig
25m19.84s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-g58sl/custom-config-mmtz4 in 46s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-mmtz4 util.go:2949: Successfully waited for HostedCluster e2e-clusters-g58sl/custom-config-mmtz4 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
18m50.25s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-g58sl/custom-config-mmtz4 in 1m45s 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-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-mmtz4.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-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.171.61.247:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.222.45.139:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.192.77:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.192.77:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.222.45.139:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.192.77:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.222.45.139:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.192.77:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.171.61.247:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.222.45.139:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.171.61.247:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.222.45.139:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.171.61.247:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.192.77:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-mmtz4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.171.61.247:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m45.025s util.go:565: Successfully waited for 2 nodes to become ready in 6m24s util.go:598: Successfully waited for HostedCluster e2e-clusters-g58sl/custom-config-mmtz4 to rollout in 7m51s util.go:2949: Successfully waited for HostedCluster e2e-clusters-g58sl/custom-config-mmtz4 to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-g58sl/custom-config-mmtz4 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-6d7f848c5c-rncp4 has a restartCount > 0 (7)
TestCreateClusterPrivate
24m49.14s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-t6579/private-9bxsb in 23s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-9bxsb util.go:2949: Successfully waited for HostedCluster e2e-clusters-t6579/private-9bxsb to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
17m30.17s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-t6579/private-9bxsb in 1m48.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-t6579/private-9bxsb to have all of their desired nodes in 9m33s util.go:598: Successfully waited for HostedCluster e2e-clusters-t6579/private-9bxsb to rollout in 6m9s util.go:2949: Successfully waited for HostedCluster e2e-clusters-t6579/private-9bxsb to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-t6579/private-9bxsb 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-7b7d9ffd4f-5zb6s has a restartCount > 0 (7)
TestCreateClusterPrivateWithRouteKAS
23m34.1s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-cdcvt/private-qmskj in 17s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-qmskj util.go:2949: Successfully waited for HostedCluster e2e-clusters-cdcvt/private-qmskj to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
17m0.14s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cdcvt/private-qmskj in 1m15s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-cdcvt/private-qmskj to have all of their desired nodes in 9m51s util.go:598: Successfully waited for HostedCluster e2e-clusters-cdcvt/private-qmskj to rollout in 5m24s util.go:2949: Successfully waited for HostedCluster e2e-clusters-cdcvt/private-qmskj 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-cdcvt/private-qmskj 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-7d57f6c68f-wn9kz has a restartCount > 0 (7)
TestCreateClusterProxy
1h7m42.35s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-m6b6b/proxy-7wlfb in 44s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-7wlfb util.go:2949: Successfully waited for HostedCluster e2e-clusters-m6b6b/proxy-7wlfb to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
15m41.24s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m6b6b/proxy-7wlfb in 2m12s 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-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-7wlfb.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-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.90.154.155:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.172.211.77:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.170.150.3:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.90.154.155:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.90.154.155:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.172.211.77:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.90.154.155:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.170.150.3:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.90.154.155:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.172.211.77:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.170.150.3:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-7wlfb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.90.154.155:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m27.025s util.go:565: Successfully waited for 2 nodes to become ready in 6m54s util.go:598: Successfully waited for HostedCluster e2e-clusters-m6b6b/proxy-7wlfb to rollout in 4m3s util.go:2949: Successfully waited for HostedCluster e2e-clusters-m6b6b/proxy-7wlfb to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m6b6b/proxy-7wlfb 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-7699c7bc9c-7p5dd has a restartCount > 0 (6)
TestCreateClusterRequestServingIsolation
30m18.9s
requestserving.go:105: Created request serving nodepool clusters/d3c19824067a1b84ab7f-mgmt-reqserving-hqvmd requestserving.go:105: Created request serving nodepool clusters/d3c19824067a1b84ab7f-mgmt-reqserving-zfhsx requestserving.go:113: Created non request serving nodepool clusters/d3c19824067a1b84ab7f-mgmt-non-reqserving-jbntb requestserving.go:113: Created non request serving nodepool clusters/d3c19824067a1b84ab7f-mgmt-non-reqserving-qvjp5 requestserving.go:113: Created non request serving nodepool clusters/d3c19824067a1b84ab7f-mgmt-non-reqserving-tcl9m util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/d3c19824067a1b84ab7f-mgmt-reqserving-hqvmd in 3m48s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/d3c19824067a1b84ab7f-mgmt-reqserving-zfhsx in 100ms util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/d3c19824067a1b84ab7f-mgmt-non-reqserving-jbntb in 1m15s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/d3c19824067a1b84ab7f-mgmt-non-reqserving-qvjp5 in 100ms util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/d3c19824067a1b84ab7f-mgmt-non-reqserving-tcl9m in 3s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-6f6kh/request-serving-isolation-pj7pm in 13s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-pj7pm util.go:2949: Successfully waited for HostedCluster e2e-clusters-6f6kh/request-serving-isolation-pj7pm to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/d3c19824067a1b84ab7f-mgmt-reqserving-hqvmd requestserving.go:132: Tearing down custom nodepool clusters/d3c19824067a1b84ab7f-mgmt-reqserving-zfhsx requestserving.go:132: Tearing down custom nodepool clusters/d3c19824067a1b84ab7f-mgmt-non-reqserving-jbntb requestserving.go:132: Tearing down custom nodepool clusters/d3c19824067a1b84ab7f-mgmt-non-reqserving-qvjp5 requestserving.go:132: Tearing down custom nodepool clusters/d3c19824067a1b84ab7f-mgmt-non-reqserving-tcl9m hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
18m43.4s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-6f6kh/request-serving-isolation-pj7pm 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-request-serving-isolation-pj7pm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-pj7pm.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-pj7pm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.27.153.153:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m5.125s util.go:565: Successfully waited for 3 nodes to become ready in 8m24s util.go:598: Successfully waited for HostedCluster e2e-clusters-6f6kh/request-serving-isolation-pj7pm to rollout in 7m33s util.go:2949: Successfully waited for HostedCluster e2e-clusters-6f6kh/request-serving-isolation-pj7pm to have valid conditions in 0s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-6f6kh/request-serving-isolation-pj7pm 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-54698dd9bf-qtzm5 has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
10m20.92s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-8dg6f/node-pool-wdlft in 42s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-wdlft util.go:2949: Successfully waited for HostedCluster e2e-clusters-8dg6f/node-pool-wdlft to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
5m41.46s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8dg6f/node-pool-wdlft in 1m39s 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-wdlft.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-wdlft.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-wdlft.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.162.80.186:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-wdlft.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.200.13.201:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m42.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-8dg6f/node-pool-wdlft to have valid conditions in 2m15s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
110ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8dg6f/node-pool-wdlft 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-85754d4d49-44mr2 has a restartCount > 0 (2)
TestNodePool/HostedCluster2
10m20.93s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9dbjq/node-pool-k6c4n in 40s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-k6c4n util.go:2949: Successfully waited for HostedCluster e2e-clusters-9dbjq/node-pool-k6c4n to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
6m11.29s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9dbjq/node-pool-k6c4n 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-node-pool-k6c4n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-k6c4n.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-k6c4n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.1.189.17:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m36.025s util.go:565: Successfully waited for 0 nodes to become ready in 25ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-9dbjq/node-pool-k6c4n to have valid conditions in 3m0s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9dbjq/node-pool-k6c4n 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-54bf76c457-94j4k has a restartCount > 0 (3)
TestUpgradeControlPlane
54m54.23s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-tm64446s/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-tm64446s/release@sha256:50365db2594de25387ca67b64923a54c986224e6baee868a768dcaac1e2bc1cf hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-8k48d/control-plane-upgrade-q74bp in 35s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-q74bp util.go:2949: Successfully waited for HostedCluster e2e-clusters-8k48d/control-plane-upgrade-q74bp to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m0.63s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8k48d/control-plane-upgrade-q74bp 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-tm64446s/release@sha256:50365db2594de25387ca67b64923a54c986224e6baee868a768dcaac1e2bc1cf util.go:598: Successfully waited for HostedCluster e2e-clusters-8k48d/control-plane-upgrade-q74bp to rollout in 0s
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8k48d/control-plane-upgrade-q74bp 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-655bc8c549-dh5fs has a restartCount > 0 (8)
TestUpgradeControlPlane/Main/Wait_for_control_plane_components_to_complete_rollout
30m0s
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-8k48d-control-plane-upgrade-q74bp/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-8k48d-control-plane-upgrade-q74bp/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)