Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1327723 - Azure - Default Credentials valid - Refresh status failed
Azure - Default Credentials valid - Refresh status failed
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.5.0
Unspecified Unspecified
urgent Severity urgent
: GA
: 5.5.4
Assigned To: Daniel Berger
Jeff Teehan
azure
: ZStream
Depends On: 1326436
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-15 14:17 EDT by John Prause
Modified: 2017-08-29 21:16 EDT (History)
8 users (show)

See Also:
Fixed In Version: 5.5.4.0
Doc Type: Bug Fix
Doc Text:
When adding an Azure provider with a custom Linux image, an image parsing issue for Azure caused the refresh status to fail if the container path did not contain "Microsoft.Compute". The operation now takes only the directory name plus the base name, ignores the .vhd and Azure GUID extensions from the Azure image name, and no longer assumes "Microsoft.Compute" is part of the path.
Story Points: ---
Clone Of: 1326436
Environment:
Last Closed: 2016-05-31 09:42:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1101 normal SHIPPED_LIVE CFME 5.5.4 bug fixes and enhancement update 2016-05-31 13:40:10 EDT

  None (edit)
Comment 3 Jeff Teehan 2016-04-29 15:04:46 EDT
I ran the template against the vm that was consistently failing for me and it went through okay.  I'll move this to verified for 5.4.4, but will keep an eye on this issue.
Comment 5 errata-xmlrpc 2016-05-31 09:42:39 EDT
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/RHBA-2016:1101

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