Failed Tests
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-4gqcd/autoscaling-j87ps in 28s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster autoscaling-j87ps
util.go:3158: Successfully waited for HostedCluster e2e-clusters-4gqcd/autoscaling-j87ps 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-4gqcd/autoscaling-j87ps in 48s
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-j87ps.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-j87ps.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-j87ps.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.159.134.180:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m17.025s
util.go:583: Successfully waited for 1 nodes to become ready in 8m21s
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-4gqcd/hostedclusters/autoscaling-j87ps?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-4gqcd/hostedclusters/autoscaling-j87ps?timeout=5m0s": net/http: TLS handshake timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-4gqcd/hostedclusters/autoscaling-j87ps?timeout=5m0s": dial tcp 98.95.248.9:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-4gqcd/hostedclusters/autoscaling-j87ps?timeout=5m0s": dial tcp 98.95.248.9:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-4gqcd/autoscaling-j87ps to rollout in 9m18s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-4gqcd/autoscaling-j87ps to have valid conditions in 3s
util.go:829: Container manager in pod capi-provider-6946798988-snbwm has a restartCount > 0 (3)
util.go:829: Container manager in pod cluster-api-88f67dcb5-w7zdq has a restartCount > 0 (4)
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-648f49886c-64cx9 has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-6c57555764-kzwrs has a restartCount > 0 (6)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-5fd8f54889-mg5pz has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-6f6868c4bd-wtnsd has a restartCount > 0 (6)
create_cluster_test.go:47: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-lb26n/create-cluster-lslsm in 45s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster create-cluster-lslsm
util.go:3158: Successfully waited for HostedCluster e2e-clusters-lb26n/create-cluster-lslsm to have valid conditions in 75ms
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-lb26n/create-cluster-lslsm in 1m24s
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-lslsm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-lslsm.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-lslsm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.211.25.195:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-lslsm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.49.179.23:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-lslsm.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.211.25.195:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m27.05s
util.go:583: Successfully waited for 3 nodes to become ready in 7m54s
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-lb26n/hostedclusters/create-cluster-lslsm?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-lb26n/hostedclusters/create-cluster-lslsm?timeout=5m0s": net/http: TLS handshake timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-lb26n/hostedclusters/create-cluster-lslsm?timeout=5m0s": dial tcp 98.95.248.9:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-lb26n/hostedclusters/create-cluster-lslsm?timeout=5m0s": dial tcp 98.95.248.9:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-lb26n/create-cluster-lslsm to rollout in 9m6s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-lb26n/create-cluster-lslsm to have valid conditions in 3s
util.go:826: Leader election failure detected in container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-54557b9d98-zbtrv
util.go:826: Leader election failure detected in container manager in pod capi-provider-66f9dcdcb-ksknk
util.go:829: Container manager in pod cluster-api-5c96d87fdd-phjcf has a restartCount > 0 (3)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-669df66c9c-fqdjz
util.go:829: Container control-plane-operator in pod control-plane-operator-676dd8d69b-9ghdd has a restartCount > 0 (6)
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-78b5895fbc-z6p27
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-5bfccb8f7c-fqpmm has a restartCount > 0 (6)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-wcltm/custom-config-hgghv in 35s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster custom-config-hgghv
util.go:3158: Successfully waited for HostedCluster e2e-clusters-wcltm/custom-config-hgghv to have valid conditions in 25ms
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-wcltm/custom-config-hgghv 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-custom-config-hgghv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-hgghv.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-hgghv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.175.60.40:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-hgghv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 32.197.69.78:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m18.05s
util.go:583: Successfully waited for 2 nodes to become ready in 8m9s
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-wcltm/hostedclusters/custom-config-hgghv?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-wcltm/hostedclusters/custom-config-hgghv?timeout=5m0s": net/http: TLS handshake timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-wcltm/hostedclusters/custom-config-hgghv?timeout=5m0s": dial tcp 98.95.248.9:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-wcltm/custom-config-hgghv to rollout in 8m36s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-wcltm/custom-config-hgghv 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-6c7ccb8fcd-g9h7k
util.go:826: Leader election failure detected in container manager in pod capi-provider-fbf5cd556-r6hgb
util.go:829: Container manager in pod cluster-api-57d86cdd47-6xjlk has a restartCount > 0 (4)
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-674588949-w2ngp has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-76f96694cb-qffs5 has a restartCount > 0 (6)
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-59b55f7c9f-rzw2l
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-855c5bcb9d-hrf4x has a restartCount > 0 (6)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-6jn4r/ha-break-glass-creds-9wb75 in 24s
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
journals.go:79: No machines associated with infra id ha-break-glass-creds-9wb75 were found. Skipping journal dump.
hypershift_framework.go:591: Destroyed cluster. Namespace: e2e-clusters-6jn4r, name: ha-break-glass-creds-9wb75
hypershift_framework.go:613: Failed to dump cluster: failed to dump hosted cluster: failed to dump cluster: the server is currently unable to handle the request
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-74ngw/private-gbn96 in 21s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster private-gbn96
util.go:3158: Successfully waited for HostedCluster e2e-clusters-74ngw/private-gbn96 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-74ngw/private-gbn96 in 39s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
util.go:744: Successfully waited for NodePools for HostedCluster e2e-clusters-74ngw/private-gbn96 to have all of their desired nodes in 10m30s
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-74ngw/hostedclusters/private-gbn96?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-74ngw/hostedclusters/private-gbn96?timeout=5m0s": net/http: TLS handshake timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-74ngw/hostedclusters/private-gbn96?timeout=5m0s": dial tcp 98.95.248.9:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-74ngw/hostedclusters/private-gbn96?timeout=5m0s": dial tcp 98.95.248.9:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-74ngw/hostedclusters/private-gbn96?timeout=5m0s": dial tcp 98.95.248.9:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-74ngw/hostedclusters/private-gbn96?timeout=5m0s": dial tcp 98.95.248.9:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-74ngw/hostedclusters/private-gbn96?timeout=5m0s": dial tcp 98.95.248.9:6443: connect: connection refused
util.go:620: Successfully waited for HostedCluster e2e-clusters-74ngw/private-gbn96 to rollout in 9m36s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-74ngw/private-gbn96 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-dccb46bbf-h9q4m
util.go:826: Leader election failure detected in container manager in pod capi-provider-7fbf487699-qbjtw
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-6565745d8f-m56bw has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-79d78d8f67-2vc2b has a restartCount > 0 (6)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-57c4484c8f-2dppn has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-69b684dc7d-f8c2r has a restartCount > 0 (6)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-kmqt9/private-nsdc4 in 23s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster private-nsdc4
util.go:3158: Successfully waited for HostedCluster e2e-clusters-kmqt9/private-nsdc4 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-kmqt9/private-nsdc4 in 54s
util.go:322: Successfully waited for kubeconfig secret to have data in 0s
util.go:744: Successfully waited for NodePools for HostedCluster e2e-clusters-kmqt9/private-nsdc4 to have all of their desired nodes in 10m21s
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-kmqt9/hostedclusters/private-nsdc4?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-kmqt9/hostedclusters/private-nsdc4?timeout=5m0s": net/http: TLS handshake timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-kmqt9/hostedclusters/private-nsdc4?timeout=5m0s": dial tcp 98.95.248.9:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-kmqt9/private-nsdc4 to rollout in 8m54s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-kmqt9/private-nsdc4 to have valid conditions in 0s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-58fd7677f8-4lzcm has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-55bcd6cdc5-2zskj
util.go:829: Container manager in pod cluster-api-5c97fb6889-zb9gp has a restartCount > 0 (3)
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-556c97f5b9-v8qkd has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-5fb8c6d87c-tgh89 has a restartCount > 0 (6)
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-867dcddd55-4wlb5
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-ff4ffc4d7-gnz7g has a restartCount > 0 (6)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-2lfk5/proxy-wn27g in 36s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster proxy-wn27g
util.go:3158: Successfully waited for HostedCluster e2e-clusters-2lfk5/proxy-wn27g 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-2lfk5/proxy-wn27g in 1m0.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-proxy-wn27g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-wn27g.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-wn27g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.216.84.158:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-wn27g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.172.140.94:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-wn27g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.216.84.158:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m48.05s
util.go:583: Successfully waited for 2 nodes to become ready in 8m54s
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-2lfk5/hostedclusters/proxy-wn27g?timeout=5m0s": net/http: TLS handshake timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-2lfk5/hostedclusters/proxy-wn27g?timeout=5m0s": dial tcp 98.95.248.9:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-2lfk5/hostedclusters/proxy-wn27g?timeout=5m0s": dial tcp 98.95.248.9:6443: connect: connection refused
util.go:620: Successfully waited for HostedCluster e2e-clusters-2lfk5/proxy-wn27g to rollout in 7m51s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-2lfk5/proxy-wn27g to have valid conditions in 9.025s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-6fff657bdd-bbz5h has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-769db69b5c-76d8g
util.go:829: Container manager in pod cluster-api-58546f6696-kdr6c has a restartCount > 0 (4)
util.go:829: Container control-plane-operator in pod control-plane-operator-86c77b988b-9pz54 has a restartCount > 0 (6)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-5f848778ff-69km2 has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-745d4df77-zgbxc has a restartCount > 0 (6)
requestserving.go:105: Created request serving nodepool clusters/54e853e9a8-mgmt-reqserving-flt2q
requestserving.go:105: Created request serving nodepool clusters/54e853e9a8-mgmt-reqserving-4bmjs
requestserving.go:113: Created non request serving nodepool clusters/54e853e9a8-mgmt-non-reqserving-4gshz
requestserving.go:113: Created non request serving nodepool clusters/54e853e9a8-mgmt-non-reqserving-c8n5d
requestserving.go:113: Created non request serving nodepool clusters/54e853e9a8-mgmt-non-reqserving-p99j7
util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/54e853e9a8-mgmt-reqserving-flt2q in 4m0s
util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/54e853e9a8-mgmt-reqserving-4bmjs in 33s
util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/54e853e9a8-mgmt-non-reqserving-4gshz in 0s
util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/54e853e9a8-mgmt-non-reqserving-c8n5d in 100ms
util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/54e853e9a8-mgmt-non-reqserving-p99j7 in 2m21.05s
create_cluster_test.go:299: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-fhdxz/request-serving-isolation-zr7ns in 13s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster request-serving-isolation-zr7ns
util.go:3158: Successfully waited for HostedCluster e2e-clusters-fhdxz/request-serving-isolation-zr7ns to have valid conditions in 0s
hypershift_framework.go:349: skipping postTeardown()
requestserving.go:132: Tearing down custom nodepool clusters/54e853e9a8-mgmt-reqserving-flt2q
requestserving.go:132: Tearing down custom nodepool clusters/54e853e9a8-mgmt-reqserving-4bmjs
requestserving.go:132: Tearing down custom nodepool clusters/54e853e9a8-mgmt-non-reqserving-4gshz
requestserving.go:132: Tearing down custom nodepool clusters/54e853e9a8-mgmt-non-reqserving-c8n5d
requestserving.go:132: Tearing down custom nodepool clusters/54e853e9a8-mgmt-non-reqserving-p99j7
hypershift_framework.go:327: skipping teardown, already called
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fhdxz/request-serving-isolation-zr7ns 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-request-serving-isolation-zr7ns.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-zr7ns.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-zr7ns.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.57.207.187:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m8.025s
util.go:583: Successfully waited for 3 nodes to become ready in 17m33s
util.go:620: Successfully waited for HostedCluster e2e-clusters-fhdxz/request-serving-isolation-zr7ns to rollout in 7m24.025s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-fhdxz/request-serving-isolation-zr7ns to have valid conditions in 7m45s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-7fbb7d556d-xjffn has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-6d5646d5d9-4tv6r
util.go:829: Container manager in pod cluster-api-7f47484dc4-2chtq has a restartCount > 0 (4)
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-66fc84cb99-jmdqv
util.go:829: Container control-plane-operator in pod control-plane-operator-c7d54d98b-d4ktr has a restartCount > 0 (6)
util.go:829: Container control-plane-pki-operator in pod control-plane-pki-operator-6755889746-68p7b has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-9f87dc7d9-ps9ns
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-684cc89cdd-r97zp has a restartCount > 0 (6)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-cxxv9/karpenter-7zpgz in 48s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster karpenter-7zpgz
util.go:3158: Successfully waited for HostedCluster e2e-clusters-cxxv9/karpenter-7zpgz 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-cxxv9/karpenter-7zpgz in 1m51s
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-7zpgz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-karpenter-7zpgz.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-7zpgz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.211.212.33:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-karpenter-7zpgz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 98.84.224.81:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 1m55.125s
util.go:583: Successfully waited for 2 nodes to become ready in 8m9s
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-cxxv9/hostedclusters/karpenter-7zpgz?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-cxxv9/hostedclusters/karpenter-7zpgz?timeout=5m0s": net/http: TLS handshake timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-cxxv9/hostedclusters/karpenter-7zpgz?timeout=5m0s": dial tcp 98.95.248.9:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-cxxv9/karpenter-7zpgz to rollout in 8m36s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-cxxv9/karpenter-7zpgz to have valid conditions in 9s
util.go:826: Leader election failure detected in container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-5fdd858b87-8dsz7
util.go:826: Leader election failure detected in container manager in pod capi-provider-5f6b9b8798-hjtp8
util.go:829: Container manager in pod cluster-api-85f4746896-znk68 has a restartCount > 0 (3)
util.go:829: Container control-plane-operator in pod control-plane-operator-6ccffcccb6-nnf82 has a restartCount > 0 (6)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-57977df987-2dj92 has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-747c575499-jzhtk has a restartCount > 0 (6)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-ndnj7/karpenter-upgrade-control-plane-wgnfv in 41s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster karpenter-upgrade-control-plane-wgnfv
util.go:3158: Successfully waited for HostedCluster e2e-clusters-ndnj7/karpenter-upgrade-control-plane-wgnfv 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-ndnj7/karpenter-upgrade-control-plane-wgnfv in 4m24s
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-wgnfv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF
util.go:384: Successfully waited for a successful connection to the guest API server in 22.3s
util.go:583: Successfully waited for 2 nodes to become ready in 8m12s
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-ndnj7/hostedclusters/karpenter-upgrade-control-plane-wgnfv?timeout=5m0s": dial tcp 98.95.248.9:6443: i/o timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-ndnj7/hostedclusters/karpenter-upgrade-control-plane-wgnfv?timeout=5m0s": dial tcp 98.95.248.9:6443: connect: connection refused
util.go:620: Successfully waited for HostedCluster e2e-clusters-ndnj7/karpenter-upgrade-control-plane-wgnfv to rollout in 18m30s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-ndnj7/karpenter-upgrade-control-plane-wgnfv to have valid conditions in 0s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-d8668fbfc-bgj8m has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-5794fdb58b-pg4qz
util.go:829: Container manager in pod cluster-api-d7c7dff5c-d47gb has a restartCount > 0 (3)
util.go:829: Container control-plane-operator in pod control-plane-operator-c496986bd-jkhcb has a restartCount > 0 (6)
util.go:826: Leader election failure detected in container control-plane-pki-operator in pod control-plane-pki-operator-5c57c8dcd7-gtxnj
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-59598bf776-4xzcb
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-89589cbf5-98x52 has a restartCount > 0 (6)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-87bnd/node-pool-mgncs in 1m28s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-mgncs
util.go:3158: Failed to wait for HostedCluster e2e-clusters-87bnd/node-pool-mgncs to have valid conditions in 2s: context deadline exceeded
eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-87bnd/node-pool-mgncs invalid at RV 154040 after 2s:
eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.0.0-0.ci-2026-07-20-100126-test-ci-op-t78bpv8z-latest)
eventually.go:228: - incorrect condition: wanted ControlPlaneConnectionAvailable=Unknown, got ControlPlaneConnectionAvailable=True: AsExpected(All is well)
eventually.go:228: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion
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-20-100126-test-ci-op-t78bpv8z-latest)
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-87bnd/node-pool-mgncs in 25ms
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_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-87bnd/node-pool-mgncs-test-ntomachineconfig-inplace in 5m30s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-ntomachineconfig-inplace to have correct status in 0s
util.go:499: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-ntomachineconfig-inplace to start config update in 15s
util.go:515: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-ntomachineconfig-inplace to finish config update in 3m40s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-mgncs-test-ntomachineconfig-inplace to be ready in 25s
util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-ntomachineconfig-inplace in 0s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-ntomachineconfig-inplace to have correct status in 4m30s
util.go:845: couldn't stream pod log; pod namespace: e2e-clusters-87bnd-node-pool-mgncs, pod name: aws-ebs-csi-driver-operator-9ffbc7cc5-h44fc, error: Get "https://10.0.1.167:10250/containerLogs/e2e-clusters-87bnd-node-pool-mgncs/aws-ebs-csi-driver-operator-9ffbc7cc5-h44fc/aws-ebs-csi-driver-operator?previous=true&tailLines=10": read tcp 10.129.5.41:44660->172.30.86.84:8090: read: connection timed out
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-9ffbc7cc5-h44fc has a restartCount > 0 (2)
util.go:845: couldn't stream pod log; pod namespace: e2e-clusters-87bnd-node-pool-mgncs, pod name: capi-provider-768b496fcf-g9hbg, error: Get "https://10.0.1.167:10250/containerLogs/e2e-clusters-87bnd-node-pool-mgncs/capi-provider-768b496fcf-g9hbg/manager?previous=true&tailLines=10": dial tcp 172.30.86.84:8090: connect: connection refused
util.go:829: Container manager in pod capi-provider-768b496fcf-g9hbg has a restartCount > 0 (1)
util.go:845: couldn't stream pod log; pod namespace: e2e-clusters-87bnd-node-pool-mgncs, pod name: cluster-api-6cdcfb78f8-sw8j4, error: Get "https://10.0.1.167:10250/containerLogs/e2e-clusters-87bnd-node-pool-mgncs/cluster-api-6cdcfb78f8-sw8j4/manager?previous=true&tailLines=10": dial tcp 172.30.86.84:8090: connect: connection refused
util.go:829: Container manager in pod cluster-api-6cdcfb78f8-sw8j4 has a restartCount > 0 (3)
util.go:845: couldn't stream pod log; pod namespace: e2e-clusters-87bnd-node-pool-mgncs, pod name: cluster-storage-operator-84678969c8-jfhtk, error: Get "https://10.0.1.167:10250/containerLogs/e2e-clusters-87bnd-node-pool-mgncs/cluster-storage-operator-84678969c8-jfhtk/cluster-storage-operator?previous=true&tailLines=10": dial tcp 172.30.86.84:8090: connect: connection refused
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-84678969c8-jfhtk has a restartCount > 0 (2)
util.go:845: couldn't stream pod log; pod namespace: e2e-clusters-87bnd-node-pool-mgncs, pod name: control-plane-operator-78cfc89-cpqv2, error: Get "https://10.0.1.167:10250/containerLogs/e2e-clusters-87bnd-node-pool-mgncs/control-plane-operator-78cfc89-cpqv2/control-plane-operator?previous=true&tailLines=10": dial tcp 172.30.86.84:8090: connect: connection refused
util.go:829: Container control-plane-operator in pod control-plane-operator-78cfc89-cpqv2 has a restartCount > 0 (6)
util.go:845: couldn't stream pod log; pod namespace: e2e-clusters-87bnd-node-pool-mgncs, pod name: csi-snapshot-controller-operator-7d76847676-kbbdh, error: Get "https://10.0.1.167:10250/containerLogs/e2e-clusters-87bnd-node-pool-mgncs/csi-snapshot-controller-operator-7d76847676-kbbdh/csi-snapshot-controller-operator?previous=true&tailLines=10": dial tcp 172.30.86.84:8090: connect: connection refused
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-7d76847676-kbbdh has a restartCount > 0 (1)
util.go:845: couldn't stream pod log; pod namespace: e2e-clusters-87bnd-node-pool-mgncs, pod name: hosted-cluster-config-operator-69c58f6848-254mt, error: Get "https://10.0.1.167:10250/containerLogs/e2e-clusters-87bnd-node-pool-mgncs/hosted-cluster-config-operator-69c58f6848-254mt/hosted-cluster-config-operator?previous=true&tailLines=10": dial tcp 172.30.86.84:8090: connect: connection refused
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-69c58f6848-254mt has a restartCount > 0 (6)
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-87bnd/node-pool-mgncs-test-ntomachineconfig-replace in 5m48s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-ntomachineconfig-replace to have correct status in 0s
util.go:499: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-ntomachineconfig-replace to start config update in 15s
util.go:515: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-ntomachineconfig-replace to finish config update in 12m10.375s
nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-mgncs-test-ntomachineconfig-replace to be ready in 0s
util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-ntomachineconfig-replace in 0s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-ntomachineconfig-replace to have correct status in 0s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-9ffbc7cc5-h44fc has a restartCount > 0 (2)
util.go:829: Container manager in pod capi-provider-768b496fcf-g9hbg has a restartCount > 0 (6)
util.go:829: Container manager in pod cluster-api-6cdcfb78f8-sw8j4 has a restartCount > 0 (3)
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-84678969c8-jfhtk has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-78cfc89-cpqv2 has a restartCount > 0 (11)
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-7d76847676-kbbdh
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-69c58f6848-254mt has a restartCount > 0 (6)
nodepool_nto_performanceprofile_test.go:59: Starting test NTOPerformanceProfileTest
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-87bnd/node-pool-mgncs-test-ntoperformanceprofile 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_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-87bnd/node-pool-mgncs-test-machineconfig in 5m36s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-machineconfig to have correct status in 0s
util.go:499: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-machineconfig to start config update in 15s
util.go:515: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-machineconfig to finish config update in 14m40s
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-87bnd/node-pool-mgncs-test-machineconfig in 0s
nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-87bnd/node-pool-mgncs-test-machineconfig to have correct status in 0s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-9ffbc7cc5-h44fc has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-768b496fcf-g9hbg
util.go:829: Container manager in pod cluster-api-6cdcfb78f8-sw8j4 has a restartCount > 0 (3)
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-84678969c8-jfhtk has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-78cfc89-cpqv2 has a restartCount > 0 (12)
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-7d76847676-kbbdh
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-69c58f6848-254mt has a restartCount > 0 (6)
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-2c8fs/scale-from-zero-q4k4g in 14s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster scale-from-zero-q4k4g
util.go:3158: Successfully waited for HostedCluster e2e-clusters-2c8fs/scale-from-zero-q4k4g 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-2c8fs/scale-from-zero-q4k4g in 48s
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-q4k4g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-scale-from-zero-q4k4g.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-q4k4g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.1.252.229:443: i/o timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-scale-from-zero-q4k4g.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 32.194.41.21:443: i/o timeout
util.go:384: Successfully waited for a successful connection to the guest API server in 2m18.025s
util.go:583: Successfully waited for 1 nodes to become ready in 8m6s
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-2c8fs/hostedclusters/scale-from-zero-q4k4g?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-2c8fs/hostedclusters/scale-from-zero-q4k4g?timeout=5m0s": net/http: TLS handshake timeout
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-2c8fs/hostedclusters/scale-from-zero-q4k4g?timeout=5m0s": dial tcp 98.95.248.9:6443: connect: connection refused
eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://ac009b8f01c484f4f8aca246e58d43dc-35d7b75c2316ccf2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-2c8fs/hostedclusters/scale-from-zero-q4k4g?timeout=5m0s": dial tcp 98.95.248.9:6443: i/o timeout
util.go:620: Successfully waited for HostedCluster e2e-clusters-2c8fs/scale-from-zero-q4k4g to rollout in 9m48s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-2c8fs/scale-from-zero-q4k4g to have valid conditions in 3s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-74c56975c6-zq9js has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-665749cf8-8vwhw
util.go:826: Leader election failure detected in container cluster-storage-operator in pod cluster-storage-operator-79d87f6f4d-t7vbl
util.go:829: Container control-plane-operator in pod control-plane-operator-5fcd5f5bdf-j2757 has a restartCount > 0 (6)
util.go:829: Container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-f56665b8d-xl29q has a restartCount > 0 (2)
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-6cbc5d6497-vsvgz has a restartCount > 0 (6)
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-t78bpv8z/release@sha256:62c295e9a2002d9928cc152c9009094f02fe056f6ff894ce2bcdb4450490e29c, toImage: registry.build01.ci.openshift.org/ci-op-t78bpv8z/release@sha256:098a5e98219d92ccfa238330966476d8e8eb2e4258d92241869da33728677af4
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-k9r99/control-plane-upgrade-wcx5p in 58s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-wcx5p
util.go:3158: Successfully waited for HostedCluster e2e-clusters-k9r99/control-plane-upgrade-wcx5p 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-k9r99/control-plane-upgrade-wcx5p in 5m39s
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-wcx5p.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF
util.go:384: Successfully waited for a successful connection to the guest API server in 13.5s
util.go:583: Successfully waited for 2 nodes to become ready in 14m18s
util.go:620: Successfully waited for HostedCluster e2e-clusters-k9r99/control-plane-upgrade-wcx5p to rollout in 3m12s
util.go:3158: Successfully waited for HostedCluster e2e-clusters-k9r99/control-plane-upgrade-wcx5p to have valid conditions in 3m48s
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-77555b79bb-9m4h2 has a restartCount > 0 (2)
util.go:826: Leader election failure detected in container manager in pod capi-provider-86d7fbb4cf-qggkk
util.go:829: Container manager in pod cluster-api-584f987df4-dhpfh has a restartCount > 0 (4)
util.go:829: Container cluster-storage-operator in pod cluster-storage-operator-7c4456d6-xjvtr has a restartCount > 0 (2)
util.go:829: Container control-plane-operator in pod control-plane-operator-6468f8f445-5xrpk has a restartCount > 0 (6)
util.go:826: Leader election failure detected in container control-plane-pki-operator in pod control-plane-pki-operator-868fbd6c7f-sthk9
util.go:826: Leader election failure detected in container csi-snapshot-controller-operator in pod csi-snapshot-controller-operator-57ffdbb67b-jwj5c
util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-5987dc6cbd-fqcw5 has a restartCount > 0 (6)