Bug 1830860 - Refactor loading regions based on subscription dynamically
Summary: Refactor loading regions based on subscription dynamically
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - Azure
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: Aditi Puntambekar
QA Contact: vijsingh
URL:
Whiteboard:
Depends On:
Blocks: 1841472
TreeView+ depends on / blocked
 
Reported: 2020-05-04 06:58 UTC by Aditi Puntambekar
Modified: 2020-10-27 13:02 UTC (History)
2 users (show)

Fixed In Version: tfm-rubygem-foreman_azure_rm-2.1.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:02:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 29222 0 Normal Closed Dynamically load `regions` based on subscription 2020-10-28 17:38:24 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:02:24 UTC

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
Note You need to log in before you can comment on or make changes to this bug.