https://github.com/ManageIQ/manageiq/pull/15164
I look at this.
Jeff, only managed images were added, not managed disks.
Added test case and tried again with Image. Created Managed image using https://docs.microsoft.com/en-us/azure/virtual-machines/windows/capture-image-resource PS C:\Users\Administrator.CFME-QE-VMM-AD> Get-AzureRmImage -ResourceGroupName Automation ResourceGroupName : Automation SourceVirtualMachine : Microsoft.Azure.Management.Compute.Models.SubResource StorageProfile : Microsoft.Azure.Management.Compute.Models.ImageStorageProfile ProvisioningState : Succeeded Id : /subscriptions/c9e72ccc-b20e-48bd-a0c8-879c6dbcbfbb/resourceGroups/Automation/providers/Microsoft.Compute/images/WS2016M I1 Name : WS2016MI1 Type : Microsoft.Compute/images Location : eastus2 Tags : {}
Tested with additional PR first. Should be in 5732.
Here's what I used: https://github.com/ManageIQ/manageiq/pull/15369
Two managed images. View this item WS2016MI1 azure 64 bit Region 623 View this item WS2016MI2a azure 64 bit Region 623 Moving to verified.
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:1601
Josh, that customer ticket 01869501 is going to hit this: https://bugzilla.redhat.com/show_bug.cgi?id=1470491 I should have caught that. It worked in LifeCycle provision and the image showed up in Catalog, but I didn't push it through. This bug is fixed. You should probably move that ticket to the new bug.