Bug 1737564

Summary: [RFE] Support custom images on Azure
Product: Red Hat Satellite Reporter: Bryan Kearney <bkearney>
Component: Compute Resources - AzureAssignee: Aditi Puntambekar <apuntamb>
Status: CLOSED ERRATA QA Contact: vijsingh
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: apatel, apuntamb, egolov, mawerner, sokeeffe
Target Milestone: 6.8.0Keywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_azure_rm-2.1.0 Doc Type: Enhancement
Doc Text:
You can now create your own images and use them as a basis for hosts that you can provision in Azure.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:59:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1827584, 1841472    

Description Bryan Kearney 2019-08-05 16:23:18 UTC
Customers would like to create their own images and use them as a basis for hosts which they provision in Azure. This means integrating with the shared image galleries.

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/shared-image-galleries

Comment 7 Bryan Kearney 2020-05-14 12:01:01 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27407 has been resolved.

Comment 8 vijsingh 2020-07-20 08:41:07 UTC
Verified.

Version Tested:  Satellite-6.8.0 Snap 9.0

Steps followed:

 Create Image under AzureRM CR


Observation:

 1. Able to create/edit/delete the BYOS image under AzureRM CR
 2. Able to create VM using same .

Comment 11 errata-xmlrpc 2020-10-27 12:59:02 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 (Important: Satellite 6.8 release), 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-2020:4366