Alena Prokharchyk created CLOUDSTACK-5597:
---------------------------------------------
Summary: attachVolume shouldn't create the volume on the primary
storage if the vm's root volume is not created yet
Key: CLOUDSTACK-5597
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5597
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.3.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
Fix For: 4.4.0
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.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
