Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-42710

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

XMLWordPrintable

    • Moderate
    • None
    • Installer Sprint 260, Installer Sprint 261
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, when you used the Agent-based Installer to install a cluster, the `assisted-installer-controller` timed out of the installation process, depending on whether `assisted-service` was unavailable on the rendezvous host. This event caused the cluster installation to fail during CSR approval checks. With this release, an update to `assisted-installer-controller` ensures that the controller does not time out if the `assisted-service` is unavailable. The CSR approval check now works as expected.
      ====
      * Previously, when you used the Agent-based Installer to install a cluster, `assisted-installer-controller` timed out or exited the installation process depending on whether `assisted-service` was unavailable on the rendezvous host. This situation caused the cluster installation to fail during CSR approval checks. With this release, an update to `assisted-installer-controller` ensures that the controller does not timeout or exit if `assisted-service` is unavailable. The CSR approval check now works as expected. (link:https://issues.redhat.com/browse/OCPBUGS-42710[*OCPBUGS-42710*])
      Show
      Previously, when you used the Agent-based Installer to install a cluster, the `assisted-installer-controller` timed out of the installation process, depending on whether `assisted-service` was unavailable on the rendezvous host. This event caused the cluster installation to fail during CSR approval checks. With this release, an update to `assisted-installer-controller` ensures that the controller does not time out if the `assisted-service` is unavailable. The CSR approval check now works as expected. ==== * Previously, when you used the Agent-based Installer to install a cluster, `assisted-installer-controller` timed out or exited the installation process depending on whether `assisted-service` was unavailable on the rendezvous host. This situation caused the cluster installation to fail during CSR approval checks. With this release, an update to `assisted-installer-controller` ensures that the controller does not timeout or exit if `assisted-service` is unavailable. The CSR approval check now works as expected. (link: https://issues.redhat.com/browse/OCPBUGS-42710 [* OCPBUGS-42710 *])
    • Bug Fix
    • Done

      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

              rwsu1@redhat.com Richard Su
              openshift-crt-jira-prow OpenShift Prow Bot
              Manoj Hans Manoj Hans
              Aidan Reilly Aidan Reilly
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: