Bug 2102247

Summary:	Not able to deploy Virtual machine from satellite to Azure with BYOS images
Product:	Red Hat Satellite	Reporter:	dprabhu
Component:	Compute Resources - Azure	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.9.7	CC:	dsinglet, jbhatia, lstejska
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 12:23:22 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:

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.

Comment 7 Brad Buckingham 2024-01-09 20:58:59 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 10 Brad Buckingham 2024-02-07 17:44:46 UTC

Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional discussion; however, it may be closed in a future iteration.

Comment 12 Eric Helms 2024-06-06 12:23:22 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 13 Red Hat Bugzilla 2024-10-05 04:25:25 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days