Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
The Azure BYOS-image host provisioning fails with error:
`Creating a virtual machine from Marketplace image or a custom image sourced from a Marketplace image requires Plan information in the request`

Version-Release number of selected component (if applicable):
Satellite 6.10 snap 11

How reproducible:
Always reproducible from Satellite but host provisioning using BYOS image from Azure UI works as expected.

Steps to Reproduce:
1. Create Azure CR in satellite.
2. Create a BYOS image in the Azure CR created above.
3. Attempt to provision a Host on the Azure CR using the BYOS image.

Actual results:
The host provisioning based on BYOS image fails on Azure fails with error:
`Creating a virtual machine from Marketplace image or a custom image sourced from a Marketplace image requires Plan information in the request`

Expected results:
The host can be provisioned on Azure using BYOS image successfully.

Additional info:

In 6.10 snap 10 (and before QE shifted the resources from SATQE resource group and pay-as-you-go subscription), it failed with error :
`Timed out reading data from server`.

The same issue was observed in Satellite 6.10 - Snap 12 as well!

Closing this as a duplicate of a bug - #1937960.

*** This bug has been marked as a duplicate of bug 1937960 ***