Bug 1467405 - Azure refresh fails if provider has no orchestration stacks
Summary: Azure refresh fails if provider has no orchestration stacks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: 5.9.0
Assignee: Bronagh Sorota
QA Contact: Leo Khomenko
URL:
Whiteboard:
: 1467929 (view as bug list)
Depends On:
Blocks: 1468606 1468703
TreeView+ depends on / blocked
 
Reported: 2017-07-03 16:57 UTC by Daniel Berger
Modified: 2018-03-06 15:29 UTC (History)
10 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1468606 1468703 (view as bug list)
Environment:
Last Closed: 2018-03-06 15:29:14 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Daniel Berger 2017-07-03 16:57:31 UTC 
Description of problem:

If there are no orchestration stacks for a given Azure provider, a refresh will fail.

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

5.8

How reproducible:

Always, if provider has no orchestration stacks.

Steps to Reproduce:
1. Add an Azure cloud provider
2. Remove any orchestration stacks if present
3. Refresh provider

Actual results:

undefined method 'each' for nil:NilClass

Expected results:

Refresh is successful

Additional info:

This was already addressed on master.

https://github.com/ManageIQ/manageiq-providers-azure/pull/84
Comment 2 Bronagh Sorota 2017-07-05 16:41:49 UTC 
https://github.com/ManageIQ/manageiq-providers-azure/pull/84
Comment 3 Bronagh Sorota 2017-07-05 16:45:07 UTC 
*** Bug 1467929 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.