Bug 1830860

Summary:	Refactor loading regions based on subscription dynamically
Product:	Red Hat Satellite	Reporter:	Aditi Puntambekar <apuntamb>
Component:	Compute Resources - Azure	Assignee:	Aditi Puntambekar <apuntamb>
Status:	CLOSED ERRATA	QA Contact:	vijsingh
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	bkearney, egolov
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_azure_rm-2.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 13:02:11 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:
Bug Depends On:
Bug Blocks:	1841472

Description Aditi Puntambekar 2020-05-04 06:58:30 UTC

Description of problem:
Currently, all the Azure regions were hardcoded into the model.
But, since available regions depend on the subscription id of azure,
it's best suited to display regions dynamically.

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


How reproducible:


Steps to Reproduce:
1. Click on Create Compute Resource
2. Select Azure Resource Manager

Actual results:
All the regions are listed under Region (since hardcoded).

Expected results:
Regions available for selected subscription must be listed.

Additional info:

Comment 7 vijsingh 2020-07-20 08:43:13 UTC


Verified.

Version Tested:  Satellite-6.8.0 Snap 9.0

Steps followed:

 Create CR using AzureRM


Observation:

 1. Able to load regions 
 2. Regions are loading based on Subscription

Comment 10 errata-xmlrpc 2020-10-27 13:02:11 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: Satellite 6.8 release), 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-2020:4366