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:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	ajambhul, bgajjava, chrobert, lstejska
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused	Flags:	ajambhul: needinfo? (chrobert)
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:		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: