PR #7450 - 01-09 13:49

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

149
Total Tests
98
Passed
32
Failed
19
Skipped

Failed Tests

TestAutoscaling
19m22.43s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-jbkfr/autoscaling-76snx in 31s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-76snx util.go:2949: Successfully waited for HostedCluster e2e-clusters-jbkfr/autoscaling-76snx to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
12m40.26s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jbkfr/autoscaling-76snx in 1m24s 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-76snx.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-76snx.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-76snx.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.200.115.168:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m29.025s util.go:565: Successfully waited for 1 nodes to become ready in 7m9s util.go:598: Successfully waited for HostedCluster e2e-clusters-jbkfr/autoscaling-76snx to rollout in 2m33s util.go:2949: Successfully waited for HostedCluster e2e-clusters-jbkfr/autoscaling-76snx to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jbkfr/autoscaling-76snx 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-77954979d8-lj6cm has a restartCount > 0 (6)
TestCreateCluster
26m37.6s
create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-4xkdp/create-cluster-pn9x7 in 55s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-pn9x7 util.go:2949: Successfully waited for HostedCluster e2e-clusters-4xkdp/create-cluster-pn9x7 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
19m13.27s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4xkdp/create-cluster-pn9x7 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-pn9x7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-pn9x7.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-pn9x7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.91.142.247:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m53.025s util.go:565: Successfully waited for 3 nodes to become ready in 7m45s util.go:598: Successfully waited for HostedCluster e2e-clusters-4xkdp/create-cluster-pn9x7 to rollout in 7m57s util.go:2949: Successfully waited for HostedCluster e2e-clusters-4xkdp/create-cluster-pn9x7 to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4xkdp/create-cluster-pn9x7 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-77cf57567c-tvskp has a restartCount > 0 (7)
TestCreateClusterCustomConfig
26m39.01s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-wcc9t/custom-config-gf82h in 1m2s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-gf82h util.go:2949: Successfully waited for HostedCluster e2e-clusters-wcc9t/custom-config-gf82h to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
18m59.26s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wcc9t/custom-config-gf82h 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-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.197.130.43:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.162.25.31:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.197.130.43:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.162.25.31:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.162.25.31:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.173.214.227:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.162.25.31:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.197.130.43:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.173.214.227:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.197.130.43:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.162.25.31:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.197.130.43:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.162.25.31:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gf82h.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.173.214.227:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m18.025s util.go:565: Successfully waited for 2 nodes to become ready in 7m21s util.go:598: Successfully waited for HostedCluster e2e-clusters-wcc9t/custom-config-gf82h to rollout in 7m12s util.go:2949: Successfully waited for HostedCluster e2e-clusters-wcc9t/custom-config-gf82h to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wcc9t/custom-config-gf82h 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-847b458bdd-s2b9l has a restartCount > 0 (7)
TestCreateClusterPrivate
24m51.36s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-8w252/private-jff57 in 19s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-jff57 util.go:2949: Successfully waited for HostedCluster e2e-clusters-8w252/private-jff57 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
17m51.22s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8w252/private-jff57 in 1m27s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-8w252/private-jff57 to have all of their desired nodes in 9m57s util.go:598: Successfully waited for HostedCluster e2e-clusters-8w252/private-jff57 to rollout in 6m27s util.go:2949: Successfully waited for HostedCluster e2e-clusters-8w252/private-jff57 to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
100ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8w252/private-jff57 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-84b4c9cf96-k672v has a restartCount > 0 (7)
TestCreateClusterPrivateWithRouteKAS
21m28.48s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-5k7vq/private-l4m29 in 20s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-l4m29 util.go:2949: Successfully waited for HostedCluster e2e-clusters-5k7vq/private-l4m29 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
15m15.14s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5k7vq/private-l4m29 in 1m27s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-5k7vq/private-l4m29 to have all of their desired nodes in 9m30s util.go:598: Successfully waited for HostedCluster e2e-clusters-5k7vq/private-l4m29 to rollout in 3m48s util.go:2949: Successfully waited for HostedCluster e2e-clusters-5k7vq/private-l4m29 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-5k7vq/private-l4m29 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-6fb995b97b-5l2k6 has a restartCount > 0 (6)
TestCreateClusterProxy
1h7m31.38s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-sclfv/proxy-czr8x in 36s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-czr8x util.go:2949: Successfully waited for HostedCluster e2e-clusters-sclfv/proxy-czr8x to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
15m3.24s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sclfv/proxy-czr8x in 1m24s 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-czr8x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-czr8x.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-czr8x.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.205.123.56: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 2 nodes to become ready in 8m9s util.go:598: Successfully waited for HostedCluster e2e-clusters-sclfv/proxy-czr8x to rollout in 3m39s util.go:2949: Successfully waited for HostedCluster e2e-clusters-sclfv/proxy-czr8x to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sclfv/proxy-czr8x 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-745694949b-2wm26 has a restartCount > 0 (6)
TestCreateClusterRequestServingIsolation
29m33.95s
requestserving.go:105: Created request serving nodepool clusters/c38608fdf50c5ba59b3a-mgmt-reqserving-v4qsd requestserving.go:105: Created request serving nodepool clusters/c38608fdf50c5ba59b3a-mgmt-reqserving-9wsh8 requestserving.go:113: Created non request serving nodepool clusters/c38608fdf50c5ba59b3a-mgmt-non-reqserving-hp6zm requestserving.go:113: Created non request serving nodepool clusters/c38608fdf50c5ba59b3a-mgmt-non-reqserving-wqzfq requestserving.go:113: Created non request serving nodepool clusters/c38608fdf50c5ba59b3a-mgmt-non-reqserving-s6jln util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/c38608fdf50c5ba59b3a-mgmt-reqserving-v4qsd in 3m30s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/c38608fdf50c5ba59b3a-mgmt-reqserving-9wsh8 in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/c38608fdf50c5ba59b3a-mgmt-non-reqserving-hp6zm in 24s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/c38608fdf50c5ba59b3a-mgmt-non-reqserving-wqzfq in 30s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/c38608fdf50c5ba59b3a-mgmt-non-reqserving-s6jln in 1m54s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-856l7/request-serving-isolation-d5zv5 in 16s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-d5zv5 util.go:2949: Successfully waited for HostedCluster e2e-clusters-856l7/request-serving-isolation-d5zv5 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/c38608fdf50c5ba59b3a-mgmt-reqserving-v4qsd requestserving.go:132: Tearing down custom nodepool clusters/c38608fdf50c5ba59b3a-mgmt-reqserving-9wsh8 requestserving.go:132: Tearing down custom nodepool clusters/c38608fdf50c5ba59b3a-mgmt-non-reqserving-hp6zm requestserving.go:132: Tearing down custom nodepool clusters/c38608fdf50c5ba59b3a-mgmt-non-reqserving-wqzfq requestserving.go:132: Tearing down custom nodepool clusters/c38608fdf50c5ba59b3a-mgmt-non-reqserving-s6jln hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
15m53.37s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-856l7/request-serving-isolation-d5zv5 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-d5zv5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-d5zv5.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-d5zv5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.208.129.145:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-d5zv5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.217.148.42:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-d5zv5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.208.129.145:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-d5zv5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.217.148.42:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 3m36.025s util.go:565: Successfully waited for 3 nodes to become ready in 6m18s util.go:598: Successfully waited for HostedCluster e2e-clusters-856l7/request-serving-isolation-d5zv5 to rollout in 4m6s util.go:2949: Successfully waited for HostedCluster e2e-clusters-856l7/request-serving-isolation-d5zv5 to have valid conditions in 15s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-856l7/request-serving-isolation-d5zv5 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-5f74f77b6d-6nrln has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
10m15.13s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-fbgm4/node-pool-cd7vw in 39s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-cd7vw util.go:2949: Successfully waited for HostedCluster e2e-clusters-fbgm4/node-pool-cd7vw to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
5m41.32s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fbgm4/node-pool-cd7vw in 1m51s 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-cd7vw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-cd7vw.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-cd7vw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.54.33.160:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-cd7vw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.88.219.13:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-cd7vw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.51.100.143:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-cd7vw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.88.219.13:443: connect: connection refused 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 25ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-fbgm4/node-pool-cd7vw to have valid conditions in 2m3s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fbgm4/node-pool-cd7vw 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-c857548-k8jgc has a restartCount > 0 (3)
TestNodePool/HostedCluster2
9m53.63s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-llwkp/node-pool-z5sqj in 14s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-z5sqj util.go:2949: Successfully waited for HostedCluster e2e-clusters-llwkp/node-pool-z5sqj to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
5m39.25s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-llwkp/node-pool-z5sqj 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-z5sqj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-z5sqj.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-z5sqj.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.225.147.194:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m19.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-llwkp/node-pool-z5sqj to have valid conditions in 2m42s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-llwkp/node-pool-z5sqj 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-669b4fc9dd-rh9b5 has a restartCount > 0 (3)
TestUpgradeControlPlane
56m41.55s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-q9cg5twv/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-q9cg5twv/release@sha256:1d37a56b4370720ea6dc0bdb6f86c60ab314df539f0a0cfd2ba5d156736c8115 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-dkwnp/control-plane-upgrade-b7vfp in 35s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-b7vfp util.go:2949: Successfully waited for HostedCluster e2e-clusters-dkwnp/control-plane-upgrade-b7vfp to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m0.7s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-dkwnp/control-plane-upgrade-b7vfp 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-q9cg5twv/release@sha256:1d37a56b4370720ea6dc0bdb6f86c60ab314df539f0a0cfd2ba5d156736c8115 util.go:598: Successfully waited for HostedCluster e2e-clusters-dkwnp/control-plane-upgrade-b7vfp to rollout in 0s
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-dkwnp/control-plane-upgrade-b7vfp 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-5f9964896d-t6mdn 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-dkwnp-control-plane-upgrade-b7vfp/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-dkwnp-control-plane-upgrade-b7vfp/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)