Bug 1932430 - RHACM missing Canadian regions for Azure Provider
Summary: RHACM missing Canadian regions for Azure Provider
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: rhacm-2.1.5
Assignee: cahl
QA Contact: Derek Ho
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-24 15:25 UTC by Filipe
Modified: 2024-06-14 00:29 UTC (History)
2 users (show)

Fixed In Version: 2.1.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-24 12:57:56 UTC
Target Upstream Version:
Embargoed:
gghezzo: rhacm-2.1.z+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 9848 0 None None None 2021-02-24 18:18:36 UTC
Red Hat Product Errata RHSA-2021:0980 0 None None None 2021-03-24 12:59:46 UTC

Description Filipe 2021-02-24 15:25:54 UTC
Description of problem:
Customers are unable to select a Canadian region on Azure Cloud when trying to deploy an Openshift cluster via rhacm or when trying to create an Azure Provider.

Version-Release number of selected component (if applicable):
RHACM 2.1.3 and 2.1.4

How reproducible:

From the RHACM console, Create an Azure Provider and when prompt to select a region, there is no Canadian Region / Zones available from the drop down list

Actual results:

Since there is no Canadian region available, customers are forced to use other regions to deploy an Openshift Cluster

Expected results:

We should be able to Select a Canadian Region ( canadacentral or canadaeast ) to deploy an Openshift cluster or create a new Azure Provider.

Additional info:

An issue is also created in Github : https://github.com/open-cluster-management/backlog/issues/9701

Comment 3 Mike Ng 2021-02-25 19:52:45 UTC
G2Bsync 786145023 comment 
 chrisahl Thu, 25 Feb 2021 19:26:37 UTC 
 G2Bsync 
 Fixed in 2.1.5

Comment 9 errata-xmlrpc 2021-03-24 12:57:56 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: Red Hat Advanced Cluster Management 2.1.5 security and bug fix 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:0980


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