Bug 2041015

Summary:	The base domain did not updated when switch the provider credentials during create the cluster/cluster pool
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	Hui Chen <huichen>
Component:	Console	Assignee:	Kevin Cormier <kcormier>
Status:	CLOSED ERRATA	QA Contact:	Hui Chen <huichen>
Severity:	medium	Docs Contact:	Christopher Dawson <cdawson>
Priority:	medium
Version:	rhacm-2.4.z	CC:	dho, dhuynh, huichen, rislam
Target Milestone:	---	Keywords:	Regression
Target Release:	rhacm-2.4.2	Flags:	bot-tracker-sync: rhacm-2.4.z+
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-03 07:00:47 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 Hui Chen 2022-01-15 07:43:21 UTC

Description of problem:

I have 2 AWS cloud credentials created, and each of credentials have the different basedomain, when I create the cluster/cluster pool, I select the one of the credentials, then go to the cluster details, the base domain info was same with the credentials, then I back to Infrastructure provider by click the Back button or the left nav tree, and select any other credentials from the Infrastructure provider credential dropdown list, go to Cluster details by click Next, I found that the basedomain did not updated with the new credentials.

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

How reproducible:


Steps to Reproduce:
1.Create 2 credentials with different basedomain configured
2.in Cluster page or clusterpool page, click the create cluster/create clusterpool
3.select the one of credentials we create before and check the basedomain info in cluster details page.
4.Back to Infrastructure providers page and select another credentials
5.go to cluster details page by click Next button and check the basedomain.

Actual results:
the basedomain did not updated when we select another one.

Expected results:
the basedomain should be updated when we select another one.

Additional info:

Comment 5 errata-xmlrpc 2022-03-03 07:00:47 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.4.2 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:0735