Failed Tests
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-ggw84/autoscaling-bv9mb in 28s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster autoscaling-bv9mb
util.go:3158: Successfully waited for HostedCluster e2e-clusters-ggw84/autoscaling-bv9mb to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ggw84/autoscaling-bv9mb in 1m9s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-bv9mb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-bv9mb.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-bv9mb.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.219.141.175:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m14.05s
util.go:583: Successfully waited for 1 nodes to become ready in 9m36s
eventually.go:105: Failed to get *v1beta1.HostedCluster: unexpected error when reading response body. Please retry. Original error: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-ggw84/hostedclusters/autoscaling-bv9mb?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-ggw84/hostedclusters/autoscaling-bv9mb?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-ggw84/hostedclusters/autoscaling-bv9mb?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-ggw84/autoscaling-bv9mb to rollout in 8m15.3s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-ggw84/autoscaling-bv9mb to have valid conditions in 0s
util.go:826: Leader election failure detected in container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-785bf8ff54-jv4cc
util.go:826: Leader election failure detected in container manager in pod capi-provider-6f68cc6566-qxl44
util.go:829: Container manager in pod cluster-api-6845d5d4cc-hxb96 has a restartCount > 0 (3)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-8497b99675-ll7st
util.go:829: Container control-plane-operator in pod control-plane-operator-84d6f6846d-v4nbc has a restartCount > 0 (5)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-cf965cb68-5bm4p has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-f54855f7c-bv8gj has a restartCount > 0 (5)
create_cluster_test.go:47: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-zxcdp/create-cluster-vltt7 in 49s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster create-cluster-vltt7
util.go:3158: Successfully waited for HostedCluster e2e-clusters-zxcdp/create-cluster-vltt7 to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zxcdp/create-cluster-vltt7 in 1m15s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-vltt7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-vltt7.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-vltt7.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.216.44.15:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m39.025s
util.go:583: Successfully waited for 3 nodes to become ready in 8m24s
eventually.go:105: Failed to get *v1beta1.HostedCluster: unexpected error when reading response body. Please retry. Original error: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-zxcdp/hostedclusters/create-cluster-vltt7?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-zxcdp/hostedclusters/create-cluster-vltt7?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-zxcdp/hostedclusters/create-cluster-vltt7?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
util.go:620: Successfully waited for HostedCluster e2e-clusters-zxcdp/create-cluster-vltt7 to rollout in 7m33s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-zxcdp/create-cluster-vltt7 to have valid conditions in 0s
util.go:826: Leader election failure detected in container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-75bc858f49-vjs8m
util.go:826: Leader election failure detected in container manager in pod capi-provider-65b9dcb7d9-56hm7
util.go:829: Container manager in pod cluster-api-5c59ddcf9c-s9tl6 has a restartCount > 0 (3)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-6b6dffb985-b9r56
util.go:829: Container control-plane-operator in pod control-plane-operator-7d947d8cc9-5cxjh has a restartCount > 0 (5)
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-85c447858-4k66h
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-8574bc4965-lvz4q has a restartCount > 0 (5)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-mfg2p/custom-config-xgzbd in 11s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster custom-config-xgzbd
util.go:3158: Successfully waited for HostedCluster e2e-clusters-mfg2p/custom-config-xgzbd to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mfg2p/custom-config-xgzbd in 51s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-xgzbd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-xgzbd.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-xgzbd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.84.161.154:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-xgzbd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 23.20.15.150:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m33.175s
util.go:583: Successfully waited for 2 nodes to become ready in 8m33s
eventually.go:105: Failed to get *v1beta1.HostedCluster: unexpected error when reading response body. Please retry. Original error: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-mfg2p/hostedclusters/custom-config-xgzbd?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-mfg2p/custom-config-xgzbd to rollout in 8m33s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-mfg2p/custom-config-xgzbd to have valid conditions in 0s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-68995bcbb4-2s445 has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-79f6f7d48f-5ck9n
util.go:829: Container manager in pod cluster-api-7bf7dbb69-9vch2 has a restartCount > 0 (4)
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-568c944bc6-5dkwg has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-55c4f6f548-pzgb9 has a restartCount > 0 (5)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-6f788bd49-kv9gc has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-5fc785df67-8b8g8 has a restartCount > 0 (5)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-tvrsj/private-jdkcf in 16s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster private-jdkcf
util.go:3158: Successfully waited for HostedCluster e2e-clusters-tvrsj/private-jdkcf to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-tvrsj/private-jdkcf in 57s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:259: Failed to get **v1beta1.NodePool: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-tvrsj/nodepools?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused - error from a previous attempt: http2: client connection lost
eventually.go:259: Failed to get **v1beta1.NodePool: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-tvrsj/nodepools?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
eventually.go:259: Failed to get **v1beta1.NodePool: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-tvrsj/nodepools?timeout=5m0s": net/http: TLS handshake timeout
eventually.go:259: Failed to get **v1beta1.NodePool: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-tvrsj/nodepools?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
eventually.go:259: Failed to get **v1beta1.NodePool: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-tvrsj/nodepools?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
eventually.go:259: Failed to get **v1beta1.NodePool: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-tvrsj/nodepools?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
util.go:744: Successfully waited for NodePools for HostedCluster e2e-clusters-tvrsj/private-jdkcf to have all of their desired nodes in 19m45.025s
util.go:620: Successfully waited for HostedCluster e2e-clusters-tvrsj/private-jdkcf to rollout in 30s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-tvrsj/private-jdkcf to have valid conditions in 0s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-5f78995fbc-97gtj has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-798746947-skxtd
util.go:829: Container manager in pod cluster-api-6cc7795895-86p8g has a restartCount > 0 (4)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-59c5fccb66-d4vcz
util.go:829: Container control-plane-operator in pod control-plane-operator-895cc7875-6hd5w has a restartCount > 0 (5)
util.go:826: Leader election failure detected in container control-plane-pki-operator in pod control-plane-pki-operator-676f595775-qttbw
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-54bbc488cc-fvgsz has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-6fd58fb5f8-4x6kq has a restartCount > 0 (5)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-kpqvg/private-t9vvs in 37s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster private-t9vvs
util.go:3158: Successfully waited for HostedCluster e2e-clusters-kpqvg/private-t9vvs to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-kpqvg/private-t9vvs in 1m42s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:259: Failed to get **v1beta1.NodePool: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-kpqvg/nodepools?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout - error from a previous attempt: http2: client connection lost
eventually.go:259: Failed to get **v1beta1.NodePool: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-kpqvg/nodepools?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
util.go:744: Successfully waited for NodePools for HostedCluster e2e-clusters-kpqvg/private-t9vvs to have all of their desired nodes in 18m45s
util.go:620: Successfully waited for HostedCluster e2e-clusters-kpqvg/private-t9vvs to rollout in 27s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-kpqvg/private-t9vvs to have valid conditions in 0s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-fbbc4d9bf-v69rl has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-776f9f49f-2cqlc
util.go:829: Container manager in pod cluster-api-6dcdfc8858-86wft has a restartCount > 0 (4)
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-59549bb8fc-dxm46 has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-679547475-xtzkw has a restartCount > 0 (5)
util.go:826: Leader election failure detected in container control-plane-pki-operator in pod control-plane-pki-operator-644bdff665-d6spt
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-74c759ff68-cwrnk has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-74fd94d9c7-vmv5l has a restartCount > 0 (5)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-krg4f/proxy-qtrjs in 25s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster proxy-qtrjs
util.go:3158: Successfully waited for HostedCluster e2e-clusters-krg4f/proxy-qtrjs to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-krg4f/proxy-qtrjs in 1m3s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-qtrjs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-qtrjs.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-qtrjs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.86.124.184:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-qtrjs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.1.173.94:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m21.05s
util.go:583: Successfully waited for 2 nodes to become ready in 9m15s
eventually.go:105: Failed to get *v1beta1.HostedCluster: unexpected error when reading response body. Please retry. Original error: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-krg4f/hostedclusters/proxy-qtrjs?timeout=5m0s": net/http: TLS handshake timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-krg4f/hostedclusters/proxy-qtrjs?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-krg4f/proxy-qtrjs to rollout in 7m45s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-krg4f/proxy-qtrjs to have valid conditions in 0s
util.go:826: Leader election failure detected in container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-7c8db59757-b794p
util.go:826: Leader election failure detected in container manager in pod capi-provider-84d78ccf68-9ntf7
util.go:829: Container manager in pod cluster-api-65448fcf6b-p4nqx has a restartCount > 0 (3)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-756b5fc847-stf8q
util.go:829: Container control-plane-operator in pod control-plane-operator-68965f9646-tp9nm has a restartCount > 0 (5)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-6c97dd6698-s62nv has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-5749cc54f9-q6fqj has a restartCount > 0 (5)
requestserving.go:105: Created request serving nodepool clusters/40bdbc0d73-mgmt-reqserving-wqj4k
requestserving.go:105: Created request serving nodepool clusters/40bdbc0d73-mgmt-reqserving-cccbd
requestserving.go:113: Created non request serving nodepool clusters/40bdbc0d73-mgmt-non-reqserving-d9wmf
requestserving.go:113: Created non request serving nodepool clusters/40bdbc0d73-mgmt-non-reqserving-nnmmg
requestserving.go:113: Created non request serving nodepool clusters/40bdbc0d73-mgmt-non-reqserving-fx6lx
util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/40bdbc0d73-mgmt-reqserving-wqj4k in 4m0s
util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/40bdbc0d73-mgmt-reqserving-cccbd in 36s
util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/40bdbc0d73-mgmt-non-reqserving-d9wmf in 18s
util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/40bdbc0d73-mgmt-non-reqserving-nnmmg in 15.45s
util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/40bdbc0d73-mgmt-non-reqserving-fx6lx in 100ms
create_cluster_test.go:299: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-js25b/request-serving-isolation-j7vt6 in 17s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster request-serving-isolation-j7vt6
util.go:3158: Successfully waited for HostedCluster e2e-clusters-js25b/request-serving-isolation-j7vt6 to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
requestserving.go:132: Tearing down custom nodepool clusters/40bdbc0d73-mgmt-reqserving-wqj4k
requestserving.go:132: Tearing down custom nodepool clusters/40bdbc0d73-mgmt-reqserving-cccbd
requestserving.go:132: Tearing down custom nodepool clusters/40bdbc0d73-mgmt-non-reqserving-d9wmf
requestserving.go:132: Tearing down custom nodepool clusters/40bdbc0d73-mgmt-non-reqserving-nnmmg
requestserving.go:132: Tearing down custom nodepool clusters/40bdbc0d73-mgmt-non-reqserving-fx6lx
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-js25b/request-serving-isolation-j7vt6 in 54s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-j7vt6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-j7vt6.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-j7vt6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.2.77.16:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-j7vt6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.49.72.14:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m46.025s
util.go:583: Successfully waited for 3 nodes to become ready in 11m3s
util.go:620: Successfully waited for HostedCluster e2e-clusters-js25b/request-serving-isolation-j7vt6 to rollout in 3m30s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-js25b/request-serving-isolation-j7vt6 to have valid conditions in 3m18s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-548b75f6c9-8kvzl has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-b9b84ffb9-9l4pj
util.go:829: Container manager in pod cluster-api-677555d586-tldj2 has a restartCount > 0 (4)
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-d7f84586-gmb9w has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-86cb87b4b-878l6 has a restartCount > 0 (5)
util.go:829: Container control-plane-pki-operator in pod control-plane-pki-operator-64f5797f5d-4bs7g has a restartCount > 0 (2)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-7fc5c68577-dwdch has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-7f6bb87697-r92h9 has a restartCount > 0 (5)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-mp7qz/karpenter-7zq7s in 30s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster karpenter-7zq7s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-mp7qz/karpenter-7zq7s to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mp7qz/karpenter-7zq7s in 1m12.025s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-karpenter-7zq7s.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-karpenter-7zq7s.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-karpenter-7zq7s.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.227.138.176:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m32.125s
util.go:583: Successfully waited for 2 nodes to become ready in 8m48s
eventually.go:105: Failed to get *v1beta1.HostedCluster: unexpected error when reading response body. Please retry. Original error: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-mp7qz/hostedclusters/karpenter-7zq7s?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-mp7qz/hostedclusters/karpenter-7zq7s?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-mp7qz/hostedclusters/karpenter-7zq7s?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-mp7qz/karpenter-7zq7s to rollout in 6m6s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-mp7qz/karpenter-7zq7s to have valid conditions in 0s
util.go:1920: failed to ensure guest webhooks validated, violating webhook test-webhook was not deleted: context deadline exceeded
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-6975bb7c94-xrhhk has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-b47cf6bf-xgnnd
util.go:829: Container manager in pod cluster-api-9bb87df45-fbqfg has a restartCount > 0 (3)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-7cb4d67f4c-9884j
util.go:829: Container control-plane-operator in pod control-plane-operator-64948f5c5-szlcq has a restartCount > 0 (4)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-7546cdf84d-fddb6 has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-9cff495db-jbxbw has a restartCount > 0 (4)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-kn76z/karpenter-upgrade-control-plane-6ds5z in 21s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster karpenter-upgrade-control-plane-6ds5z
util.go:3158: Successfully waited for HostedCluster e2e-clusters-kn76z/karpenter-upgrade-control-plane-6ds5z to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-kn76z/karpenter-upgrade-control-plane-6ds5z in 1m9s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-karpenter-upgrade-control-plane-6ds5z.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-karpenter-upgrade-control-plane-6ds5z.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-karpenter-upgrade-control-plane-6ds5z.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.49.230.97:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m24.1s
util.go:583: Successfully waited for 2 nodes to become ready in 8m45s
eventually.go:105: Failed to get *v1beta1.HostedCluster: unexpected error when reading response body. Please retry. Original error: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-kn76z/hostedclusters/karpenter-upgrade-control-plane-6ds5z?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-kn76z/hostedclusters/karpenter-upgrade-control-plane-6ds5z?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-kn76z/hostedclusters/karpenter-upgrade-control-plane-6ds5z?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
util.go:620: Successfully waited for HostedCluster e2e-clusters-kn76z/karpenter-upgrade-control-plane-6ds5z to rollout in 8m9s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-kn76z/karpenter-upgrade-control-plane-6ds5z to have valid conditions in 2m0s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-54d4867bdf-jkcxj has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-55df4fb699-qgxrj
util.go:829: Container manager in pod cluster-api-68d8666f4-l5xth has a restartCount > 0 (3)
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-748bc7d46b-pvcs8 has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-bb49bd566-5vv65 has a restartCount > 0 (5)
util.go:826: Leader election failure detected in container control-plane-pki-operator in pod control-plane-pki-operator-5d4678978c-9h7dk
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-74876446f8-tkx8k has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-6f9f8545bb-8lppf has a restartCount > 0 (5)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-klmwb/node-pool-kc7n9 in 35s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-kc7n9
util.go:3158: Failed to wait for HostedCluster e2e-clusters-klmwb/node-pool-kc7n9 to have valid conditions in 2s: context deadline exceeded
eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-klmwb/node-pool-kc7n9 invalid at RV 150592 after 2s:
eventually.go:228: - incorrect condition: wanted DataPlaneConnectionAvailable=Unknown, got DataPlaneConnectionAvailable=True: AsExpected(All is well)
eventually.go:228: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 5.0.0-0.ci-2026-07-01-155731-test-ci-op-h9ftnvfx-latest)
eventually.go:228: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion
eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.0.0-0.ci-2026-07-01-155731-test-ci-op-h9ftnvfx-latest)
eventually.go:228: - incorrect condition: wanted ControlPlaneConnectionAvailable=Unknown, got ControlPlaneConnectionAvailable=True: AsExpected(All is well)
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-klmwb/node-pool-kc7n9 in 0s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
util.go:384: Successfully waited for a successful connection to the guest API server in 0s
nodepool_imagetype_test.go:51: Starting test NodePoolImageTypeTest
nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning
nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef
nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted
eventually.go:259: Failed to get **v1.Node: context deadline exceeded
util.go:583: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-imagetype in 45m0s: context deadline exceeded
eventually.go:384: observed invalid **v1.Node state after 45m0s
eventually.go:401: - observed **v1.Node collection invalid: expected 1 nodes, got 0
nodepool_kms_root_volume_test.go:43: Starting test KMSRootVolumeTest
nodepool_kms_root_volume_test.go:55: retrieved KMS ARN: arn:aws:kms:us-east-1:820196288204:key/d3cdd9e0-3fd1-47a4-a559-72ae3672c5a6
nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning
nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef
nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted
util.go:583: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-kms-root-volume in 45m0s: context deadline exceeded
eventually.go:384: observed invalid **v1.Node state after 45m0s
eventually.go:401: - observed **v1.Node collection invalid: expected 1 nodes, got 0
nodepool_mirrorconfigs_test.go:60: Starting test MirrorConfigsTest
nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning
nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef
nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted
util.go:583: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-mirrorconfigs in 45m0s: context deadline exceeded
eventually.go:384: observed invalid **v1.Node state after 45m0s
eventually.go:401: - observed **v1.Node collection invalid: expected 1 nodes, got 0
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest
nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning
nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef
nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted
util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-inplace in 8m24.85s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-inplace to have correct status in 0s
util.go:499: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-inplace to start config update in 15s
util.go:515: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-inplace to finish config update in 5m0s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-kc7n9-test-ntomachineconfig-inplace to be ready in 5s
util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-inplace in 25ms
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-inplace to have correct status in 0s
util.go:826: Leader election failure detected in container manager in pod capi-provider-54755c74f6-f2pqk
util.go:829: Container manager in pod cluster-api-d47754574-482gb has a restartCount > 0 (3)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-6cd8dcf95-swjpm
util.go:829: Container control-plane-operator in pod control-plane-operator-7464fd55fb-r2dj7 has a restartCount > 0 (5)
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-6cfd49456b-5wp4j
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest
nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning
nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef
nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted
util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-replace in 8m59.675s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-replace to have correct status in 0s
util.go:499: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-replace to start config update in 15s
util.go:515: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-replace to finish config update in 10m0s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-kc7n9-test-ntomachineconfig-replace to be ready in 0s
util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-replace in 0s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-ntomachineconfig-replace to have correct status in 0s
util.go:826: Leader election failure detected in container manager in pod capi-provider-54755c74f6-f2pqk
util.go:829: Container manager in pod cluster-api-d47754574-482gb has a restartCount > 0 (3)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-6cd8dcf95-swjpm
util.go:829: Container control-plane-operator in pod control-plane-operator-7464fd55fb-r2dj7 has a restartCount > 0 (5)
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-6cfd49456b-5wp4j
nodepool_machineconfig_test.go:54: Starting test NodePoolMachineconfigRolloutTest
nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning
nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef
nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted
util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-machineconfig in 8m17.375s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-machineconfig to have correct status in 0s
util.go:499: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-machineconfig to start config update in 15s
util.go:515: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-machineconfig to finish config update in 7m40s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/machineconfig-update-checker-replace to be ready in 0s
util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-machineconfig in 0s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-machineconfig to have correct status in 0s
util.go:826: Leader election failure detected in container manager in pod capi-provider-54755c74f6-f2pqk
util.go:829: Container manager in pod cluster-api-d47754574-482gb has a restartCount > 0 (3)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-6cd8dcf95-swjpm
util.go:829: Container control-plane-operator in pod control-plane-operator-7464fd55fb-r2dj7 has a restartCount > 0 (5)
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-6cfd49456b-5wp4j
nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning
nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef
nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted
util.go:583: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-rolling-upgrade in 45m0s: context deadline exceeded
eventually.go:384: observed invalid **v1.Node state after 45m0s
eventually.go:401: - observed **v1.Node collection invalid: expected 2 nodes, got 0
nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning
nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef
nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted
util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-spot-termination in 5m15s
eventually.go:105: Failed to get *v1beta1.NodePool: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-klmwb/nodepools/node-pool-kc7n9-test-spot-termination?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
nodepool_test.go:431: Failed to wait for NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-spot-termination to have correct status in 20m0s: context deadline exceeded
eventually.go:225: observed *v1beta1.NodePool e2e-clusters-klmwb/node-pool-kc7n9-test-spot-termination invalid at RV 103305 after 20m0s: incorrect condition: wanted ReachedIgnitionEndpoint=True, got ReachedIgnitionEndpoint=False: ignitionNotReached
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-vl225/scale-from-zero-9s9rr in 15s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster scale-from-zero-9s9rr
util.go:3158: Successfully waited for HostedCluster e2e-clusters-vl225/scale-from-zero-9s9rr to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vl225/scale-from-zero-9s9rr in 57s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-scale-from-zero-9s9rr.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-scale-from-zero-9s9rr.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-scale-from-zero-9s9rr.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.173.7.236:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m11.175s
util.go:583: Successfully waited for 1 nodes to become ready in 9m15s
eventually.go:105: Failed to get *v1beta1.HostedCluster: unexpected error when reading response body. Please retry. Original error: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-vl225/hostedclusters/scale-from-zero-9s9rr?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-vl225/hostedclusters/scale-from-zero-9s9rr?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-vl225/hostedclusters/scale-from-zero-9s9rr?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-vl225/hostedclusters/scale-from-zero-9s9rr?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-vl225/hostedclusters/scale-from-zero-9s9rr?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-vl225/hostedclusters/scale-from-zero-9s9rr?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-vl225/scale-from-zero-9s9rr to rollout in 8m9s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-vl225/scale-from-zero-9s9rr to have valid conditions in 0s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-8785d44f9-4n9jg has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-58f8df456-vjpvl
util.go:829: Container manager in pod cluster-api-6f4d8cf4dc-cjc29 has a restartCount > 0 (4)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-697d7cbc57-zd5rt
util.go:829: Container control-plane-operator in pod control-plane-operator-7c668bd49c-mzk59 has a restartCount > 0 (5)
util.go:826: Leader election failure detected in container control-plane-pki-operator in pod control-plane-pki-operator-5cd46c65d7-hbdq4
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-6784c8dcb-fwpdv
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-6cc6b58c45-mqrtk has a restartCount > 0 (5)
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-h9ftnvfx/release@sha256:c3475f3d282465a4768ca25743059cb718393a39fb90bd5c37459a48eee5418e, toImage: registry.build01.ci.openshift.org/ci-op-h9ftnvfx/release@sha256:18ed94d2ec9af482efeb41c77b23a6898c7d64eb9417a939ab3f194273c07632
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-jd2ht/control-plane-upgrade-xw6fp in 19s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-xw6fp
util.go:3158: Successfully waited for HostedCluster e2e-clusters-jd2ht/control-plane-upgrade-xw6fp to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jd2ht/control-plane-upgrade-xw6fp in 1m9s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-control-plane-upgrade-xw6fp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-control-plane-upgrade-xw6fp.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-control-plane-upgrade-xw6fp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.60.160.170:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-control-plane-upgrade-xw6fp.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.60.160.232:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m6.075s
util.go:583: Successfully waited for 2 nodes to become ready in 8m54s
eventually.go:105: Failed to get *v1beta1.HostedCluster: unexpected error when reading response body. Please retry. Original error: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-jd2ht/hostedclusters/control-plane-upgrade-xw6fp?timeout=5m0s": dial tcp 32.195.163.46:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a12359bb72d3a4b2ba504ee2186599bd-2e9227f54293ffd0.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-jd2ht/hostedclusters/control-plane-upgrade-xw6fp?timeout=5m0s": dial tcp 32.195.163.46:6443: connect: connection refused
util.go:620: Successfully waited for HostedCluster e2e-clusters-jd2ht/control-plane-upgrade-xw6fp to rollout in 8m3s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-jd2ht/control-plane-upgrade-xw6fp to have valid conditions in 3m18s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-6f665787cc-rk6w4 has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-7f8c88bb7d-kp4c5
util.go:829: Container manager in pod cluster-api-75bf5d4cb5-2qqb8 has a restartCount > 0 (3)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-7858458f89-r79z5
util.go:829: Container control-plane-operator in pod control-plane-operator-75bb86d95c-98jcq has a restartCount > 0 (5)
util.go:829: Container control-plane-pki-operator in pod control-plane-pki-operator-857fbc47d5-944mw has a restartCount > 0 (2)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-7f55bf7fb9-4cw72 has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-9b4f54df5-ts2ns has a restartCount > 0 (5)