Bug 1370480 - Incorrect name is used for default Azure provider during discovery
Summary: Incorrect name is used for default Azure provider during discovery
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: GA
: 5.6.2
Assignee: Bronagh Sorota
QA Contact: Jeff Teehan
URL:
Whiteboard:
Depends On: 1368507
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-26 12:57 UTC by Satoe Imaishi
Modified: 2022-07-09 07:52 UTC (History)
6 users (show)

Fixed In Version: 5.6.2.0
Doc Type: Bug Fix
Doc Text:
Previously, an incorrect name was used for default Azure provider during discovery. If there were no virtual machines in a provider and no EMSes in the DB, trying to create a default provider called "Azure-eastus” incorrectly set it to Azure-Azure-eastus. This caused a refresh failure because the region component of the provider name did not exist in the regions file. With this release, renaming the default region from Azure-Azure-east to Azure-east has fixed the issue.
Clone Of: 1368507
Environment:
Last Closed: 2016-10-04 14:32:30 UTC
Category: ---
Cloudforms Team: Azure
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1996 0 normal SHIPPED_LIVE Important: CFME 4.1 bug fixes and enhancement update 2016-10-04 18:26:13 UTC

Comment 2 Bronagh Sorota 2016-08-30 14:27:11 UTC 
https://github.com/ManageIQ/manageiq/pull/10629
Comment 3 Jeff Teehan 2016-09-21 05:16:23 UTC 
Had to remove all my vms, but it worked okay afterwards.  Moving this to verified using 5.6.2.0.20160913114355_70e9086 on 10.16.6.182  Also peek at code and it's pretty straight forward.
Comment 5 errata-xmlrpc 2016-10-04 14:32:30 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, 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://rhn.redhat.com/errata/RHSA-2016-1996.html
Note You need to log in before you can comment on or make changes to this bug.