Bug 2041015 - The base domain did not updated when switch the provider credentials during create the cluster/cluster pool
Summary: The base domain did not updated when switch the provider credentials during c...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Console
Version: rhacm-2.4.z
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: rhacm-2.4.2
Assignee: Kevin Cormier
QA Contact: Hui Chen
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-15 07:43 UTC by Hui Chen
Modified: 2022-03-03 07:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-03 07:00:47 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.4.z+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 19153 0 None None None 2022-01-15 10:22:07 UTC
Red Hat Product Errata RHSA-2022:0735 0 None None None 2022-03-03 07:02:07 UTC

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


Note You need to log in before you can comment on or make changes to this bug.