PR #9031 - 07-20 09:31

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-7k2tq/custom-config-t2vhv in 29s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster custom-config-t2vhv util.go:3158: Successfully waited for HostedCluster e2e-clusters-7k2tq/custom-config-t2vhv 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-7k2tq/custom-config-t2vhv 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-t2vhv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-t2vhv.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-t2vhv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.48.25.254:443: i/o timeout eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-t2vhv.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.83.59.134:443: i/o timeout util.go:384: Successfully waited for a successful connection to the guest API server in 2m24.175s util.go:583: Successfully waited for 2 nodes to become ready in 8m39s eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-7k2tq/hostedclusters/custom-config-t2vhv?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://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-7k2tq/hostedclusters/custom-config-t2vhv?timeout=5m0s": net/http: TLS handshake timeout util.go:620: Successfully waited for HostedCluster e2e-clusters-7k2tq/custom-config-t2vhv to rollout in 8m0s util.go:3158: Successfully waited for HostedCluster e2e-clusters-7k2tq/custom-config-t2vhv to have valid conditions in 0s

util.go:826: Leader election failure detected in container manager in pod capi-provider-855d56d9b6-v26wq util.go:829: Container control-plane-operator in pod control-plane-operator-55d75b6465-vwqwz has a restartCount > 0 (4) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-984b94dcb-hf859 has a restartCount > 0 (4)

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-tgtl9/private-ng9kj in 1m18s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster private-ng9kj util.go:3158: Failed to wait for HostedCluster e2e-clusters-tgtl9/private-ng9kj to have valid conditions in 2s: context deadline exceeded eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-tgtl9/private-ng9kj invalid at RV 104187 after 2s: eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=True, got ClusterVersionAvailable=False: FromClusterVersion eventually.go:228: - incorrect condition: wanted ClusterVersionSucceeding=True, got ClusterVersionSucceeding=False: ClusterOperatorDegraded(Cluster operator ingress is degraded) 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-tgtl9/private-ng9kj in 1m39s util.go:322: Successfully waited for kubeconfig secret to have data in 0s eventually.go:259: Failed to get **v1beta1.NodePool: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-tgtl9/nodepools?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost eventually.go:259: Failed to get **v1beta1.NodePool: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-tgtl9/nodepools?timeout=5m0s": net/http: TLS handshake timeout util.go:744: Failed to wait for NodePools for HostedCluster e2e-clusters-tgtl9/private-ng9kj to have all of their desired nodes in 30m0s: context deadline exceeded eventually.go:384: observed invalid **v1beta1.NodePool state after 30m0s eventually.go:401: - observed **v1beta1.NodePool e2e-clusters-tgtl9/private-ng9kj-us-east-1a invalid: expected 2 replicas, got 1 util.go:744: *v1beta1.NodePool e2e-clusters-tgtl9/private-ng9kj-us-east-1a conditions: util.go:744: AutoscalingEnabled=False: AsExpected util.go:744: UpdateManagementEnabled=True: AsExpected util.go:744: ValidReleaseImage=True: AsExpected(Using release image: registry.build01.ci.openshift.org/ci-op-xd6bcw90/release@sha256:4b518c40836889f3ceaa445a4fce2ad5bc068bf3a4826d2b9e6f71058f398c13) util.go:744: ValidArchPlatform=True: AsExpected util.go:744: ReconciliationActive=True: ReconciliationActive(Reconciliation active on resource) util.go:744: SupportedVersionSkew=True: AsExpected(Release image version is valid) util.go:744: ValidMachineConfig=True: AsExpected util.go:744: UpdatingConfig=True: AsExpected(Updating config in progress. Target config: 7d274c32) util.go:744: UpdatingVersion=True: AsExpected(Updating version in progress. Target version: 5.0.0-0.ci-2026-07-20-095241-test-ci-op-xd6bcw90-latest) util.go:744: ValidGeneratedPayload=True: AsExpected(Payload generated successfully) util.go:744: ReachedIgnitionEndpoint=True: AsExpected util.go:744: AllMachinesReady=True: AsExpected(All is well) util.go:744: AllNodesHealthy=False: NodeProvisioning(1 of 2 machines are not healthy Machine private-ng9kj-us-east-1a-5ksfv-w2r76: NodeProvisioning: Waiting for a node with matching ProviderID to exist ) util.go:744: ValidPlatformConfig=True: AsExpected(All is well) util.go:744: ValidPlatformImage=True: AsExpected(Bootstrap AMI is "ami-0fbc8be8796dc1df5") util.go:744: AWSSecurityGroupAvailable=True: AsExpected(NodePool has a default security group) util.go:744: ValidTuningConfig=True: AsExpected util.go:744: UpdatingPlatformMachineTemplate=True: AsExpected(platform machine template update in progress. Target template: private-ng9kj-us-east-1a-801a831c) util.go:744: AutorepairEnabled=False: AsExpected util.go:744: Ready=False: WaitingForAvailableMachines(Minimum availability requires 2 replicas, current 1 available)

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-9lnp2/private-j66n7 in 29s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster private-j66n7 util.go:3158: Successfully waited for HostedCluster e2e-clusters-9lnp2/private-j66n7 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-9lnp2/private-j66n7 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-9lnp2/private-j66n7 to have all of their desired nodes in 10m48s eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-9lnp2/hostedclusters/private-j66n7?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://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-9lnp2/hostedclusters/private-j66n7?timeout=5m0s": net/http: TLS handshake timeout util.go:620: Successfully waited for HostedCluster e2e-clusters-9lnp2/private-j66n7 to rollout in 8m30s util.go:3158: Successfully waited for HostedCluster e2e-clusters-9lnp2/private-j66n7 to have valid conditions in 0s

util.go:826: Leader election failure detected in container manager in pod capi-provider-7c84d646b9-frnfb util.go:829: Container control-plane-operator in pod control-plane-operator-6f5b69fcbb-zsxj6 has a restartCount > 0 (4) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-c6b95586c-pk66t has a restartCount > 0 (4)

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-mvrr5/proxy-hn7k6 in 27s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster proxy-hn7k6 util.go:3158: Successfully waited for HostedCluster e2e-clusters-mvrr5/proxy-hn7k6 to have valid conditions in 0s hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called

journals.go:308: Error copying machine journals to artifacts directory: exit status 1 hypershift_framework.go:591: Destroyed cluster. Namespace: e2e-clusters-mvrr5, name: proxy-hn7k6 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

util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mvrr5/proxy-hn7k6 in 42.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-hn7k6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-hn7k6.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-hn7k6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.210.213.110:443: i/o timeout eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-hn7k6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.199.150.124:443: i/o timeout util.go:384: Successfully waited for a successful connection to the guest API server in 2m36.075s util.go:583: Successfully waited for 2 nodes to become ready in 9m3s util.go:620: Successfully waited for HostedCluster e2e-clusters-mvrr5/proxy-hn7k6 to rollout in 3m4.3s util.go:3158: Successfully waited for HostedCluster e2e-clusters-mvrr5/proxy-hn7k6 to have valid conditions in 925ms

util.go:1920: failed to ensure guest webhooks validated, violating webhook test-webhook was not deleted: context deadline exceeded

util.go:942: failed to get pods in namespace e2e-clusters-mvrr5-proxy-hn7k6: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/api/v1/namespaces/e2e-clusters-mvrr5-proxy-hn7k6/pods?labelSelector=app%3Dopenshift-apiserver&timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost Unexpected error: <*rest.wrapPreviousError | 0xc0076abca0>: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/api/v1/namespaces/e2e-clusters-mvrr5-proxy-hn7k6/pods?labelSelector=app%3Dopenshift-apiserver&timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost { currentErr: <*url.Error | 0xc007849080>{ Op: "Get", URL: "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/api/v1/namespaces/e2e-clusters-mvrr5-proxy-hn7k6/pods?labelSelector=app%3Dopenshift-apiserver&timeout=5m0s", Err: <http.tlsHandshakeTimeoutError>{}, }, previousError: <*errors.errorString | 0xc00614eb10>{ s: "http2: client connection lost", }, } occurred

requestserving.go:105: Created request serving nodepool clusters/3468c9060c-mgmt-reqserving-g96sk requestserving.go:105: Created request serving nodepool clusters/3468c9060c-mgmt-reqserving-mr67x requestserving.go:113: Created non request serving nodepool clusters/3468c9060c-mgmt-non-reqserving-glkp8 requestserving.go:113: Created non request serving nodepool clusters/3468c9060c-mgmt-non-reqserving-5w2pd requestserving.go:113: Created non request serving nodepool clusters/3468c9060c-mgmt-non-reqserving-4gvcl util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/3468c9060c-mgmt-reqserving-g96sk in 3m48s util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/3468c9060c-mgmt-reqserving-mr67x in 6s util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/3468c9060c-mgmt-non-reqserving-glkp8 in 36s util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/3468c9060c-mgmt-non-reqserving-5w2pd in 100ms util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/3468c9060c-mgmt-non-reqserving-4gvcl in 39s create_cluster_test.go:299: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-x4r4z/request-serving-isolation-jpv9p in 15s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster request-serving-isolation-jpv9p util.go:3158: Successfully waited for HostedCluster e2e-clusters-x4r4z/request-serving-isolation-jpv9p to have valid conditions in 0s hypershift_framework.go:349: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/3468c9060c-mgmt-reqserving-g96sk requestserving.go:132: Tearing down custom nodepool clusters/3468c9060c-mgmt-reqserving-mr67x requestserving.go:132: Tearing down custom nodepool clusters/3468c9060c-mgmt-non-reqserving-glkp8 requestserving.go:132: Tearing down custom nodepool clusters/3468c9060c-mgmt-non-reqserving-5w2pd requestserving.go:132: Tearing down custom nodepool clusters/3468c9060c-mgmt-non-reqserving-4gvcl hypershift_framework.go:327: skipping teardown, already called

util.go:826: Leader election failure detected in container manager in pod capi-provider-5c9f4f5ffb-txkbq util.go:829: Container control-plane-operator in pod control-plane-operator-7b89c7bb96-jfsts has a restartCount > 0 (4) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-fb8b686b-bkljg has a restartCount > 0 (4)

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-ht72f/karpenter-upgrade-control-plane-t7nd4 in 45s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster karpenter-upgrade-control-plane-t7nd4 util.go:3158: Successfully waited for HostedCluster e2e-clusters-ht72f/karpenter-upgrade-control-plane-t7nd4 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-ht72f/karpenter-upgrade-control-plane-t7nd4 in 1m6s 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-t7nd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-karpenter-upgrade-control-plane-t7nd4.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-t7nd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.55.239.135:443: i/o timeout eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-karpenter-upgrade-control-plane-t7nd4.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.30.7.245:443: i/o timeout util.go:384: Successfully waited for a successful connection to the guest API server in 2m22.175s util.go:583: Successfully waited for 2 nodes to become ready in 8m21s util.go:620: Successfully waited for HostedCluster e2e-clusters-ht72f/karpenter-upgrade-control-plane-t7nd4 to rollout in 3m0.1s eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-ht72f/hostedclusters/karpenter-upgrade-control-plane-t7nd4?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://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-ht72f/hostedclusters/karpenter-upgrade-control-plane-t7nd4?timeout=5m0s": net/http: TLS handshake timeout util.go:3158: Successfully waited for HostedCluster e2e-clusters-ht72f/karpenter-upgrade-control-plane-t7nd4 to have valid conditions in 5m36s

util.go:826: Leader election failure detected in container manager in pod capi-provider-5d4cf9bdf5-bjq5n util.go:829: Container control-plane-operator in pod control-plane-operator-686dbfc7c6-tsf6m has a restartCount > 0 (4) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-55c9db4ccc-mjcd8 has a restartCount > 0 (4)

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-425dv/node-pool-clxfp in 10s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-clxfp util.go:3158: Failed to wait for HostedCluster e2e-clusters-425dv/node-pool-clxfp to have valid conditions in 2s: context deadline exceeded eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-425dv/node-pool-clxfp invalid at RV 143296 after 2s: eventually.go:228: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 5.0.0-0.ci-2026-07-20-095241-test-ci-op-xd6bcw90-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-20-095241-test-ci-op-xd6bcw90-latest) eventually.go:228: - incorrect condition: wanted DataPlaneConnectionAvailable=Unknown, got DataPlaneConnectionAvailable=True: AsExpected(All is well) 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-425dv/node-pool-clxfp 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_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-425dv/node-pool-clxfp-test-ntomachineconfig-inplace in 6m39s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-test-ntomachineconfig-inplace to have correct status in 0s util.go:499: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-test-ntomachineconfig-inplace to start config update in 15s eventually.go:105: Failed to get *v1beta1.NodePool: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-425dv/nodepools/node-pool-clxfp-test-ntomachineconfig-inplace?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost eventually.go:105: Failed to get *v1beta1.NodePool: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-425dv/nodepools/node-pool-clxfp-test-ntomachineconfig-inplace?timeout=5m0s": net/http: TLS handshake timeout util.go:515: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-test-ntomachineconfig-inplace to finish config update in 8m0s nodepool_machineconfig_test.go:165: Successfully waited for all pods in the DaemonSet kube-system/node-pool-clxfp-test-ntomachineconfig-inplace to be ready in 20s util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-425dv/node-pool-clxfp-test-ntomachineconfig-inplace in 0s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-test-ntomachineconfig-inplace to have correct status in 0s

util.go:826: Leader election failure detected in container manager in pod capi-provider-6f48d4949c-xk26d util.go:829: Container control-plane-operator in pod control-plane-operator-6478f79d6b-wpnwb has a restartCount > 0 (4) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-bc7964ddf-8mwnr has a restartCount > 0 (4)

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-425dv/node-pool-clxfp-test-ntomachineconfig-replace in 6m3s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-test-ntomachineconfig-replace to have correct status in 0s util.go:499: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-test-ntomachineconfig-replace to start config update in 15s eventually.go:105: Failed to get *v1beta1.NodePool: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-425dv/nodepools/node-pool-clxfp-test-ntomachineconfig-replace?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost eventually.go:105: Failed to get *v1beta1.NodePool: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-425dv/nodepools/node-pool-clxfp-test-ntomachineconfig-replace?timeout=5m0s": net/http: TLS handshake timeout util.go:515: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-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-clxfp-test-ntomachineconfig-replace to be ready in 0s util.go:583: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-425dv/node-pool-clxfp-test-ntomachineconfig-replace in 0s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-test-ntomachineconfig-replace to have correct status in 0s

util.go:826: Leader election failure detected in container manager in pod capi-provider-6f48d4949c-xk26d util.go:829: Container control-plane-operator in pod control-plane-operator-6478f79d6b-wpnwb has a restartCount > 0 (4) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-bc7964ddf-8mwnr has a restartCount > 0 (4)

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-425dv/node-pool-clxfp-test-machineconfig in 5m15s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-test-machineconfig to have correct status in 0s util.go:499: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-test-machineconfig to start config update in 15s eventually.go:105: Failed to get *v1beta1.NodePool: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-425dv/nodepools/node-pool-clxfp-test-machineconfig?timeout=5m0s": net/http: TLS handshake timeout - error from a previous attempt: http2: client connection lost eventually.go:105: Failed to get *v1beta1.NodePool: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-425dv/nodepools/node-pool-clxfp-test-machineconfig?timeout=5m0s": net/http: TLS handshake timeout util.go:515: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-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-425dv/node-pool-clxfp-test-machineconfig in 0s nodepool_test.go:431: Successfully waited for NodePool e2e-clusters-425dv/node-pool-clxfp-test-machineconfig to have correct status in 0s

util.go:826: Leader election failure detected in container manager in pod capi-provider-6f48d4949c-xk26d util.go:829: Container control-plane-operator in pod control-plane-operator-6478f79d6b-wpnwb has a restartCount > 0 (4) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-bc7964ddf-8mwnr has a restartCount > 0 (4)

hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-fjptc/scale-from-zero-pbbsq in 29s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster scale-from-zero-pbbsq util.go:3158: Successfully waited for HostedCluster e2e-clusters-fjptc/scale-from-zero-pbbsq 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-fjptc/scale-from-zero-pbbsq 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-scale-from-zero-pbbsq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-scale-from-zero-pbbsq.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-pbbsq.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.235.209.43:443: i/o timeout util.go:384: Successfully waited for a successful connection to the guest API server in 1m39.05s util.go:583: Successfully waited for 1 nodes to become ready in 9m42s eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-fjptc/hostedclusters/scale-from-zero-pbbsq?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://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-fjptc/hostedclusters/scale-from-zero-pbbsq?timeout=5m0s": net/http: TLS handshake timeout util.go:620: Successfully waited for HostedCluster e2e-clusters-fjptc/scale-from-zero-pbbsq to rollout in 7m48s util.go:3158: Successfully waited for HostedCluster e2e-clusters-fjptc/scale-from-zero-pbbsq to have valid conditions in 0s

util.go:826: Leader election failure detected in container manager in pod capi-provider-845dcd8bf-sptfd util.go:829: Container control-plane-operator in pod control-plane-operator-5756fccd9b-xjhf5 has a restartCount > 0 (4) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-6fb564fc68-nl7bs has a restartCount > 0 (4)

control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-xd6bcw90/release@sha256:62c295e9a2002d9928cc152c9009094f02fe056f6ff894ce2bcdb4450490e29c, toImage: registry.build01.ci.openshift.org/ci-op-xd6bcw90/release@sha256:4b518c40836889f3ceaa445a4fce2ad5bc068bf3a4826d2b9e6f71058f398c13 hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-jwd74/control-plane-upgrade-5hm8s in 51s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-5hm8s util.go:3158: Successfully waited for HostedCluster e2e-clusters-jwd74/control-plane-upgrade-5hm8s 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-jwd74/control-plane-upgrade-5hm8s in 1m12s 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-5hm8s.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-control-plane-upgrade-5hm8s.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-5hm8s.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.231.118.170:443: i/o timeout util.go:384: Successfully waited for a successful connection to the guest API server in 2m50.05s util.go:583: Successfully waited for 2 nodes to become ready in 7m51s util.go:620: Successfully waited for HostedCluster e2e-clusters-jwd74/control-plane-upgrade-5hm8s to rollout in 3m24s eventually.go:105: Failed to get *v1beta1.HostedCluster: Get "https://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-jwd74/hostedclusters/control-plane-upgrade-5hm8s?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://a1236fc887e0f4570b0ecf24dd9a57d2-d434534e3e0ef9d2.elb.us-east-1.amazonaws.com:6443/apis/hypershift.openshift.io/v1beta1/namespaces/e2e-clusters-jwd74/hostedclusters/control-plane-upgrade-5hm8s?timeout=5m0s": net/http: TLS handshake timeout util.go:3158: Successfully waited for HostedCluster e2e-clusters-jwd74/control-plane-upgrade-5hm8s to have valid conditions in 5m0s

util.go:826: Leader election failure detected in container manager in pod capi-provider-57888c459c-n5dlt util.go:829: Container control-plane-operator in pod control-plane-operator-6bff78c45c-9n2zr has a restartCount > 0 (4) util.go:829: Container hosted-cluster-config-operator in pod hosted-cluster-config-operator-848db7c954-z89ct has a restartCount > 0 (4)