Bug 1916846
Summary: | Unable to provision OS in Azure when image definition is set to "Specialized" | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Chris Roberts <chrobert> |
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: | high | ||
Version: | 6.9.0 | CC: | ahumbe, gpadholi, jangerrit.kootstra, patalber |
Target Milestone: | Unspecified | Keywords: | MigratedToJIRA, PrioBumpGSS, Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-06-06 00:44:55 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: | |||
Attachments: |
Description
Chris Roberts
2021-01-15 16:36:41 UTC
Created attachment 1759161 [details]
Failed image creation with no version in Azure
Created attachment 1759162 [details]
Azure specialized image with no version
Created attachment 1759163 [details]
Azure specialized image with version
Created attachment 1759164 [details]
Specialized image created in Foreman
Created attachment 1759165 [details]
Specialized VM listed in Foreman
Looks like a bug currently with the Azure Ruby SDK: Opened an issue here: https://github.com/Azure/azure-sdk-for-ruby/issues/2824 Upstream bug assigned to chrobert Upstream bug assigned to chrobert 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. |