Details
-
Bug
-
Resolution: Not a Bug
-
Critical
-
None
-
None
-
None
-
False
-
False
Description
Copying Bugzilla issue here - https://bugzilla.redhat.com/show_bug.cgi?id=2019972
Description of problem:
I used the "Add Hosts" tab to add another worker to the cluster using the assisted day-2 flow, and then waited for long minutes but the node's request to join the cluster never showed up in the UI. On the command line, you can see that the csr already exists.
Version-Release number of selected component (if applicable):
4.9.4
How reproducible:
100%
Steps to Reproduce:
1. Install a cluster with assisted installer.
2. If needed, update the cluster to the latest version 4.9.4.
3. Use the "Add Hosts" feature to create a day-2 iso and boot an additional node with it
4. Install the day-2 node
5. After the installation is finished, wait for the csr to appear in the UI under the "Nodes" section
Actual results:
The csr never shows up. I tried F5 many times.
Expected results:
The user should be able to approve the request to join the cluster using the UI.
Additional info:
From the CLI you can see that the csr exists already (from 12 minutes ago):
- oc get csr
NAME AGE SIGNERNAME REQUESTOR REQUESTEDDURATION CONDITION
csr-hz289 12m kubernetes.io/kube-apiserver-client-kubelet system:serviceaccount:openshift-machine-config-operator:node-bootstrapper <none> Pending
- oc describe csr csr-hz289
Name: csr-hz289
Labels: <none>
Annotations: <none>
CreationTimestamp: Wed, 03 Nov 2021 13:52:27 -0400
Requesting User: system:serviceaccount:openshift-machine-config-operator:node-bootstrapper
Signer: kubernetes.io/kube-apiserver-client-kubelet
Status: Pending
Subject:
Common Name: system:node:worker-0-3
Serial Number:
Organization: system:nodes
Events: <none>
Additional info: