Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Normal
Fix Version/s: None
Affects Version/s: 4.16
Component/s: Installer / Agent based installation
Labels:
- triaged

Severity:
Moderate
Regression:
None
Sprint:
Installer Sprint 261
sprint_count:
1
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
Cause: Using the agent based installer, the assisted-installer-controller starts or restarts when assisted-service is unreachable on the rendezvous host. The rendezvous host may have rebooted or there is a connectivity issue.

Consequence: Because assisted-service cannot be reached, assisted-installer-controller times out and exits without waiting for cluster installation to finish and approving CSRs. Because CSRs are not being approved, the third master node and workers cannot join the cluster after the rendezvous host reboots.

Fix: The assisted-installer-controller has been updated so that it does not exit if it fails to connect to assisted-service. It will attempt to find the information it needs from the initialized cluster and then wait for cluster installation to complete and approve CSRs.

Result: CSRs for nodes are approved and they join the cluster. Cluster installation completes.

Show
Cause: Using the agent based installer, the assisted-installer-controller starts or restarts when assisted-service is unreachable on the rendezvous host. The rendezvous host may have rebooted or there is a connectivity issue. Consequence: Because assisted-service cannot be reached, assisted-installer-controller times out and exits without waiting for cluster installation to finish and approving CSRs. Because CSRs are not being approved, the third master node and workers cannot join the cluster after the rendezvous host reboots. Fix: The assisted-installer-controller has been updated so that it does not exit if it fails to connect to assisted-service. It will attempt to find the information it needs from the initialized cluster and then wait for cluster installation to complete and approve CSRs. Result: CSRs for nodes are approved and they join the cluster. Cluster installation completes.
Release Note Type:
Bug Fix
Release Note Status:
In Progress
RH Private Keywords:
Target Version:

4.16.z
Target Backport Versions:

4.17.z, 4.16.z

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

This is a clone of issue ~~OCPBUGS-42839~~. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-38466. The following is the description of the original issue:
—
Description of problem:

- One node [ rendezvous]   is failed to add the cluster and there are some pending CSR's.

- omc get csr 
NAME                                                            AGE   SIGNERNAME                                    REQUESTOR                                                                   REQUESTEDDURATION   CONDITION
csr-44qjs                                                       21m   kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-machine-config-operator:node-bootstrapper   <none>              Pending
csr-9n9hc                                                       5m    kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-machine-config-operator:node-bootstrapper   <none>              Pending
csr-9xw24                                                       1h    kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-machine-config-operator:node-bootstrapper   <none>              Pending
csr-brm6f                                                       1h    kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-machine-config-operator:node-bootstrapper   <none>              Pending
csr-dz75g                                                       36m   kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-machine-config-operator:node-bootstrapper   <none>              Pending
csr-l8c7v                                                       1h    kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-machine-config-operator:node-bootstrapper   <none>              Pending
csr-mv7w5                                                       52m   kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-machine-config-operator:node-bootstrapper   <none>              Pending
csr-v6pgd                                                       1h    kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-machine-config-operator:node-bootstrapper   <none>              Pending

In order to complete the installation, cu needs to approve the those CSR's manually.

Steps to Reproduce:

   agent-based installation.

Actual results:

    CSR's are in pending state.

Expected results:

    CSR's should approved automatically

Additional info:

Logs : https://drive.google.com/drive/folders/1UCgC6oMx28k-_WXy8w1iN_t9h9rtmnfo?usp=sharing

clones

OCPBUGS-42839 Rendezvous node is failed to add the cluster due to some pending CSR's.

Closed

duplicates

OCPBUGS-42710 Rendezvous node is failed to add the cluster due to some pending CSR's.

Closed

is blocked by

OCPBUGS-42839 Rendezvous node is failed to add the cluster due to some pending CSR's.

Closed

links to

openshift/assisted-installer#934: [release-4.16] OCPBUGS-43377: Allow controller to continue when assisted-service

Assignee:: Richard Su

Reporter:: OpenShift Prow Bot

QA Contact:: Manoj Hans

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024/10/15 4:25 PM

Updated:: 2024/10/17 10:02 PM

Resolved:: 2024/10/17 10:02 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates