Bug 2102247 - Not able to deploy Virtual machine from satellite to Azure with BYOS images
Summary: Not able to deploy Virtual machine from satellite to Azure with BYOS images
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - Azure
Version: 6.9.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-29 14:08 UTC by dprabhu
Modified: 2023-08-11 19:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19525 0 None None None 2023-08-11 19:10:38 UTC

Description dprabhu 2022-06-29 14:08:39 UTC 
Description of problem:

Not able to deploy VMs from RH Satellite to Azure with BYOS images. 


Additional info:

Version-Release number of selected component (if applicable):
satellite-6.9.7-1.el7sat.noarch



How reproducible:

Steps to Reproduce:

1. Hosts-->All hosts

2. Create Host

3. Fill all new host details 

4. Before click on "Submit" button, I login to Azure portal

5. Open Azure CLI

6. Accept image terms with command as below:

az vm image terms accept --urn redhat:rhel-byos:rhel-lvm86-gen2:latest

7. Click on "Submit" button 


Actual results:

"Creating a virtual machine from Marketplace image or a custom image sourced from a Marketplace image requires Plan information in the request"


Expected results:

VM should deploy on azure using BYOS images without errors

Additional info:

Customer has applied the solution from "https://access.redhat.com/solutions/6961347"  but it is not working. 

"https://bugzilla.redhat.com/show_bug.cgi?id=1937960"  bugzilla was for the same issue and provided "https://access.redhat.com/solutions/6961347" solution but it is not working.
Note You need to log in before you can comment on or make changes to this bug.