This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 1908601 - Adding a data disk with 0 Gb size despite being removed
Summary: Adding a data disk with 0 Gb size despite being removed
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - Azure
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: stream
Assignee: satellite6-bugs
QA Contact: Shweta Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-17 06:53 UTC by Alexey Masolov
Modified: 2024-10-05 04:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 00:44:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32061 0 Normal New Unwanted additional disk with 0Gb size is always created in compute profiles 2024-03-16 05:55:10 UTC
Github theforeman foreman_azure_rm pull 108 0 None Merged Fixes #32270 - Implement custom size for OS disk 2024-03-16 05:59:26 UTC
Red Hat Issue Tracker   SAT-23990 0 None Migrated None 2024-06-06 00:44:50 UTC
Red Hat Knowledge Base (Solution) 6827171 0 None None None 2022-03-18 09:11:14 UTC

Description Alexey Masolov 2020-12-17 06:53:08 UTC 
Description of problem:
While using a compute profile with no data disk (Azure adds an OS disk by default, so everything we add to a compute profile is considered as a data disk) Satellite keeps adding a data disk with 0Gb size. Provisioning fails while calling Azure API because it doesn't accept 0 size. 

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

How reproducible:
100%

Steps to Reproduce:
1. Remove all storage disk in a compute profile for Azure
2. Add a new host in Satellite
3. the VM tab will have a new data disk with 0 size.
4. If you click provision then it will fail at some point. 

Actual results:
Error message while provisioning

Expected results:
If no disk specified in a compute profile then Satellite shouldn't add a data disk.

Additional info:
Comment 4 Shweta Singh 2024-04-17 13:16:01 UTC 
Verified.

Version Tested: Satellite Stream Snap 54.0

Verification Steps:
1. Create an Azure Compute Resource and remove all storage disk in a compute profile.
2. Add a new host to the Satellite

Observation:
Host provisioned successfully without adding any data disk.
Comment 5 Eric Helms 2024-06-06 00:44:51 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 6 Red Hat Bugzilla 2024-10-05 04:25:05 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.