Description of the problem: From the Advance Cluster Management console, create a new OCP cluster on AWS. There is no problem to selected the cluster to be created in AWS Sydney region (ap-southeast-2), as such "control plane pool" and "worker pools 1" are created in the same region. However, when creating more worker pools, the drop-down menu shows the us-east-1 availability zones instead of ap-southeast-2 zones. Release version: 2.4.1 OCP version: reproduced - ACM 2.4.1 on OCP 4.9.21 hub cluster Steps to reproduce: 1. From ACM console, Clusters, click "Create cluster" 2. Change Node pool region to another region - ap-southeast-2 3. There is no issue for Control plane pool and worker pool 1 to choose ap-southeast-2 zones 4. click Add worker pool 5. in Worker pool 2 Zones, it can only select us-east-1 zones instead of ap-southeast-2 zones. type "ap" in Select zone search, "no results found" Actual results: in Worker pool 2 Zones, it can only select us-east-1 zone. Expected results: It should be like Worker pool 1, to be able to select the right region. Additional info: It might be similar to the previous ACM v1.0 bug - 1821806 https://bugzilla.redhat.com/show_bug.cgi?id=1821806
G2Bsync 1043181034 comment mark-nc Thu, 17 Feb 2022 16:52:32 UTC G2Bsync Yes, we have reproduced this bug on Advanced Cluster Management v2.4.2 running on OCP v4.9.7. When creating a cluster on AWS when you get to the third step of the create cluster wizard for node pools, if you change the region, the zones list for control plane pool and worker pool 1 reflect the new region. If you add any additional worker pools, however, the zones list for the new worker pool will reflect the original region and not the new region the user specified. This appears to be a case of the UI working off an out of date cached value for the region when adding the fields for the new worker pool.
Verified with v2.4.5-FC0
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: Red Hat Advanced Cluster Management 2.4.5 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:5201