Bug 2030002

Summary: Console UI enabled SNO UI Options not displayed during cluster creating
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Thuy Nguyen <thnguyen>
Component: Cluster LifecycleAssignee: Randy Bruno-Piverger <rbrunopi>
Status: CLOSED ERRATA QA Contact: Hui Chen <huichen>
Severity: high Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.3.zCC: izhang, jtalton, kcormier, yuhe
Target Milestone: ---Flags: bot-tracker-sync: rhacm-2.3.z+
Target Release: rhacm-2.3.6   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-22 21:58:13 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 Thuy Nguyen 2021-12-07 19:10:19 UTC
Description of the problem: Console UI enabled SNO UI Options not displayed during cluster creating 

Release version: ACM 2.3.4

Operator snapshot version: 

OCP version: OCP 4.9.4

Browser Info: Firefox 78.15.0esr (64-bit)

Steps to reproduce:
1. Enable SNO UI options

oc patch configmap console-config -n <acm_namespace> --patch '{"data":{"singleNodeOpenshift":"enabled"}}'

2. Creating a cluster on AWS from ACM UI

Actual results:
No SNO UI option displayed after selecting release image >4.8

Expected results:
SNO UI option seen

Additional info:

Comment 1 ian zhang 2021-12-08 14:41:36 UTC
hi Thuy,

just want to make sure we are on the same page, when you do this test, which documentation are you following? Can you please share the link for the documentation?

Comment 3 ian zhang 2021-12-08 20:08:48 UTC
Hi James,

Can you please take a look at this one? 

It seems the SNO option is turned on at 2.4, but it's not working on 2.3 even we patched the configmap of console-config.

Comment 4 ian zhang 2021-12-13 14:30:23 UTC
Hi Thuy,

Can you please follow up the instruction at https://github.com/open-cluster-management/backlog/issues/18354#issuecomment-991848880

It seems we were following a wrong one...

Comment 5 Thuy Nguyen 2022-01-11 14:54:41 UTC
Info provided in the associated GH issue https://github.com/stolostron/backlog/issues/18354

Comment 6 bot-tracker-sync 2022-01-26 22:49:06 UTC
G2Bsync 1022634015 comment 
 KevinFCormier Wed, 26 Jan 2022 21:48:49 UTC 
 G2Bsync @thuyn-581 thnguyen please verify. Thanks.

Comment 7 Thuy Nguyen 2022-02-03 21:34:51 UTC
Validated on ACM 2.3.6-RC1. Closing.

Comment 14 errata-xmlrpc 2022-02-22 21:58:13 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 (Important: Red Hat Advanced Cluster Management 2.3.6 security updates and bug fixes), 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-2022:0595

Comment 19 Red Hat Bugzilla 2023-09-15 01:17:57 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days