Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2058990

Summary:	No CSR request for a new Day-2 node in the OpenShift console
Product:	OpenShift Container Platform	Reporter:	Lital Alon <lalon>
Component:	Console Metal3 Plugin	Assignee:	Jiri Tomasek <jtomasek>
Status:	CLOSED DUPLICATE	QA Contact:	Yanping Zhang <yanpzhan>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.10-rc3	CC:	aos-bugs, mchernyk, rawagner, rfreiman, spadgett, tjelinek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-02 07:59:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lital Alon 2022-02-27 14:25:39 UTC

Description of problem:
Finalization instructions for adding a day2 node using Assited-Installer states that a user should open OpenShift Console and approve added node on the "Compute->Nodes" page, but neither new node nor its CSR is displayed on this page

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Deploy a day1 OpenShift cluster using Assisted Installer Cloud
2. Add a day2 host to the deployed cluster
3. Wait until the new node is in the installed state, and open "Compute->Nodes" page of the OpenShift console.

Actual results:
1. No record for the added node appears on the "Compute->Nodes" page
2. CSR request for the new node never appears on the page, but after some time appears in the output of CLI "oc get csr" command

Expected results:
An entry for the newly added node is shown, along with a CSR request for this node. a user can approve the CSR request.


Additional info:

Comment 7 Tomas Jelinek 2022-03-02 07:59:29 UTC

The https://bugzilla.redhat.com/show_bug.cgi?id=2019972 is tracking the fix for 4.10. The 4.9 version is tacked here: https://bugzilla.redhat.com/show_bug.cgi?id=2033712 (in post).
Marking this BZ as duplicate.

*** This bug has been marked as a duplicate of bug 2033712 ***

Comment 8 Red Hat Bugzilla 2023-09-15 01:22:27 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days