[CLOUDSTACK-5597] attachVolume shouldn't create the volume on the primary storage if the vm's root volume is not created yet

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.3.0
• Fix Version/s: 4.4.0
• Component/s: Management Server
• Security Level: Public (Anyone can view this level - this is the default.)
• Assignee: Alena Prokharchyk
• Reporter: Alena Prokharchyk
• Created: 20/Dec/13 21:15
• Updated: 26/Nov/14 18:41
• Resolved: 20/Dec/13 21:39

Description

In cloudStack you can deploy a vm w/o actually starting it on the backend (startVm=false parameter should be passed to deployVm call to trigger this behavior). When vm is not started during the original deployment, its ROOT volume is not created either. It stays in Allocated state in the DB.

Bug: when try to attach data disk to such a vm, current CS code creates it on the primary storage.

The fix should be: when check to see if the volume needs to be created on the primary storage, validate the Vm's Root volume state. And if its Allocated, don't create it.