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

Bug 1946751

Summary: DAY2 Confusing event when trying to add hosts to a cluster that completed installation
Product: OpenShift Container Platform Reporter: fnar
Component: assisted-installerAssignee: Sarah Lavie <slavie>
assisted-installer sub component: assisted-service QA Contact: Yuri Obshansky <yobshans>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: alazar, aos-bugs, atraeger, lgamliel, mchernyk, vfarias
Version: 4.7Keywords: Reopened
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: All   
OS: All   
Whiteboard: AI-Team-Core
Fixed In Version: OCP-Metal-v1.0.19.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-27 22:57:48 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:
Attachments:
Description Flags
AI Cluster Error none

Description fnar 2021-04-06 19:04:47 UTC 
Created attachment 1769648 [details]
AI Cluster Error

Created attachment 1769648 [details]
AI Cluster Error

Description of problem:
AI does not allow addition/enlist of new nodes to an existing 3 nodes cluster, that prevents cluster scale from 3 nodes to 3 + 2 = 5 nodes.

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


How reproducible: Easy as described below.

Steps to Reproduce:
1.Create a 3 nodes AI cluster, get it up and running.
2.Bootstrap new worker nodes (4th & 5th node) with same iso image
3.See the error attached in snapshot picture.

Actual results:


Expected results:


Additional info:
Comment 1 mchernyk 2021-04-07 11:17:47 UTC 
It is an expected behavior. 

Day1 cluster is considered transient, so it's deliberately not used for scaling up an installed OS cluster. The correct way to add workers is to use "Add Hosts" tab of the cluster details page on cloud.redhat.com/openshift 

This tab is shown when OS cluster is healthy and has "Bare Metal" type ("Provider (Location)" column).
Comment 2 Ronnie Lazar 2021-04-07 15:57:12 UTC 
Now the user sees the standard event about not being able to register host in current state.
I think that in the case that we get a host registering when the cluster is already installed, we should display a different message in the event.
something along: "Cannot add host to a cluster that is already installed, please use the day2 cluster option" or something along these lines.

@avishay what do you think?
Comment 3 Avishay Traeger 2021-04-08 13:25:22 UTC 
Yes, a clearer event can help.  Allowing to add hosts to the day1 cluster would help even more :)
Comment 4 Sarah Lavie 2021-04-28 09:17:58 UTC 
solution was provided in this PR https://github.com/openshift/assisted-service/pull/1590/
Comment 5 mchernyk 2021-05-05 11:41:50 UTC 
Verified on staging
Assisted-ui-lib version:  1.5.19
assisted-service: v1.0.19.3
Comment 8 errata-xmlrpc 2021-07-27 22:57:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2438