Bug 1908601

Summary:	Adding a data disk with 0 Gb size despite being removed
Product:	Red Hat Satellite	Reporter:	Alexey Masolov <amasolov>
Component:	Compute Resources - Azure	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Shweta Singh <shwsingh>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	ahumbe, ajambhul, bgajjava, chrobert, lstejska, rlavi, shwsingh
Target Milestone:	stream	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 00:44:51 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 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