Description of problem:
When creating a new content host, a second disk with size of 0 is added automatically and there is no way to remove it via compute profile, we remove it, save and once we reopen the compute profile, the disk is back there.

Version-Release number of selected component (if applicable):
tested on 6.13, but I believe all of them will face the same behavior

How reproducible:
100%

Steps to Reproduce:
1. Create the connection to azure (compute resource and compute profile)
2.
3.

Actual results:
Here we can already see the issue, once the compute profile gets created and you save it, if you reopen, you can see a new disk, size of 0

Expected results:
No additional disk, unless added by the customer.

Additional info: