Bug 1826340

Summary: [RFE] Ability to provision a VM using Red Hat Gold BYOS images
Product: Red Hat Satellite Reporter: vijsingh
Component: Compute Resources - AzureAssignee: Aditi Puntambekar <apuntamb>
Status: CLOSED ERRATA QA Contact: vijsingh
Severity: medium Docs Contact:
Priority: unspecified    
Version: UnspecifiedCC: aludwar, apuntamb, egolov, jsenkyri, jswanson, kgaikwad, ktordeur, pcreech, pdwyer, smutkule
Target Milestone: 6.8.0Keywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_azure_rm-2.1.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 13:01:20 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: 1841472    

Description vijsingh 2020-04-21 13:20:15 UTC 
Description of problem:

Unable to provision a VM using Red Hat Gold BYOS images

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1. Under AzureRm CR , Create an image using 'Azure BYOS (Gold Images)' URN
2. Try provision a VM using same image.


Actual results:

Fails with error code: VMMarketplaceInvalidinput 


Expected results:

VM should provision using Red Hat Gold BYOS images
Additional info:
Comment 4 Bryan Kearney 2020-06-09 12:01:59 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29819 has been resolved.
Comment 6 Aditi Puntambekar 2020-06-23 12:11:28 UTC 
*** Bug 1849807 has been marked as a duplicate of this bug. ***
Comment 7 vijsingh 2020-07-20 06:52:22 UTC 
Verified.

Version Tested:  Satellite-6.8.0 Snap 9.0

Steps followed:

 Create Image under AzureRM CR


Observation:

 Able to create/edit/delete the BYOS image under AzureRM CR
Comment 10 errata-xmlrpc 2020-10-27 13:01:20 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