Bug 1368507 - Incorrect name is used for default Azure provider during discovery
Summary: Incorrect name is used for default Azure provider during discovery
Keywords:
Status: CLOSED CURRENTRELEASE
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.7.0
Assignee: Bronagh Sorota
QA Contact: Jeff Teehan
URL:
Whiteboard: provider:azure:discover
Depends On:
Blocks: 1370480
TreeView+ depends on / blocked
 
Reported: 2016-08-19 15:20 UTC by Bronagh Sorota
Modified: 2019-12-16 06:25 UTC (History)
6 users (show)

Fixed In Version: 5.7.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1370480 (view as bug list)
Environment:
Last Closed: 2017-01-11 20:19:27 UTC
Category: ---
Cloudforms Team: Azure
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bronagh Sorota 2016-08-19 15:20:48 UTC 
Description of problem:

During Azure discovery, if there are no VMs in a provider and there are no EMSes in the DB, we try to create a default provider called "Azure-eastus". However, this is incorrectly being set to Azure-Azure-eastus which causes a refresh failure because the region component of the provider name does not exist in the regions file.

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


How reproducible:


Steps to Reproduce:
1. Ensure the provider has no VMs
2. Ensure there are no EMSes in the DB
3. Discover the Azure environment.

Actual results:
exception in the evm.log pointing to refresh post processing.


Expected results:
to see 1 or more Azure providers.


Additional info:
Comment 2 Bronagh Sorota 2016-08-22 15:21:24 UTC 
https://github.com/ManageIQ/manageiq/pull/10629
Comment 4 Jeff Teehan 2016-09-22 21:51:21 UTC 
This is working.  Funny, my client key expired since the 5.6 version of this bug and then neither were working until I figured out I needed a new key. 

Anyway, this is verified in 5.7.0.2 using my account with no VMs.

For what it's worth, my account is all West US, so defaulting to east doesn't really help much, but I understand we have to pick something.

Moving to verified.
Comment 5 Jeff Teehan 2016-09-22 21:52:55 UTC 
Missed a step.  Added test case.
Note You need to log in before you can comment on or make changes to this bug.