Bug 1468703 - Azure refresh fails if provider has no orchestration stacks
Summary: Azure refresh fails if provider has no orchestration stacks
Keywords:
Status: CLOSED ERRATA
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.8.1
Assignee: Bronagh Sorota
QA Contact: Leo Khomenko
URL:
Whiteboard:
Depends On: 1467405
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-07 16:52 UTC by Satoe Imaishi
Modified: 2022-07-09 08:42 UTC (History)
9 users (show)

Fixed In Version: 5.8.1.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1467405
Environment:
Last Closed: 2017-08-02 17:34:22 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1758 0 normal SHIPPED_LIVE Important: Red Hat CloudForms security, bug fix, and enhancement update 2017-08-02 21:23:43 UTC

Comment 2 CFME Bot 2017-07-07 16:58:19 UTC
New commit detected on ManageIQ/manageiq-providers-azure/fine:
https://github.com/ManageIQ/manageiq-providers-azure/commit/0bea1a1b12325dfb3cbc9630158369cb72214fc8

commit 0bea1a1b12325dfb3cbc9630158369cb72214fc8
Author:     Greg Blomquist <blomquisg>
AuthorDate: Tue Jun 27 16:27:31 2017 -0400
Commit:     Satoe Imaishi <simaishi>
CommitDate: Fri Jul 7 12:52:27 2017 -0400

    Merge pull request #84 from djberg96/orchestration_stack_fix
    
    Handle possibility of no orchestration stacks
    (cherry picked from commit cb8acf4422799d9861f4e43a9c07d7038fbe7405)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1468703

 .../providers/azure/cloud_manager/refresh_parser.rb       | 15 ++++++++++-----
 .../providers/azure/cloud_manager/refresher_spec.rb       | 15 +++++++++++++++
 2 files changed, 25 insertions(+), 5 deletions(-)

Comment 5 errata-xmlrpc 2017-08-02 17:34:22 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://access.redhat.com/errata/RHSA-2017:1758


Note You need to log in before you can comment on or make changes to this bug.