Bug 1377416 - Unknown Error while refreshing Azure
Summary: Unknown Error while refreshing Azure
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
urgent
urgent
Target Milestone: GA
: 5.6.2
Assignee: Bronagh Sorota
QA Contact: Jeff Teehan
URL:
Whiteboard:
Depends On: 1376468
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 15:46 UTC by Satoe Imaishi
Modified: 2022-07-09 07:55 UTC (History)
10 users (show)

Fixed In Version: 5.6.2.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1376468
Environment:
Last Closed: 2016-10-04 14:40:10 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-2016:1996 0 normal SHIPPED_LIVE Important: CFME 4.1 bug fixes and enhancement update 2016-10-04 18:26:13 UTC

Comment 3 CFME Bot 2016-09-20 18:31:10 UTC
New commit detected on ManageIQ/manageiq/darga:
https://github.com/ManageIQ/manageiq/commit/734c563fc8154b1309fd6baf2910faeaa115ff8f

commit 734c563fc8154b1309fd6baf2910faeaa115ff8f
Author:     Bronagh Sorota <bsorota>
AuthorDate: Tue Sep 20 11:08:53 2016 -0400
Commit:     Bronagh Sorota <bsorota>
CommitDate: Tue Sep 20 11:08:53 2016 -0400

    Bump Azure-armrest gem version from 0.2.9 to 0.2.10 on Darga branch
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1377416

 gems/pending/Gemfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 4 Jeff Teehan 2016-09-26 17:46:11 UTC
Verified that 0.2.10 was indeed installed.  Checked the code.  Looks pretty simple, we just catch any exceptions and go to the next storage account.

It's not actually possible to create a storage account with no keys, and you can't delete them, so this is being marked as verified based on the changes alone.

Comment 6 errata-xmlrpc 2016-10-04 14:40:10 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.