Anurag Awasthi f9b61bc737 orchestration: Allow VM that has never started to have volumes attached (#3276) ... With this patch b766bf7 we started tracking disks in attaching state so that other attach request can fail gracefully. However this missed the case where disks were in allocated state but attach was requested. For the use case where users want to attach disk in allocated state but not ready, we need to have allocated-attaching transition as well. We must take care of returning to the original state - allocated or ready - when attach request has completed. For the use case of unstarted vm's the disk must proceed as follows - "Allocated" -> Attaching -> Allocated. When VM is started, the disk is "created" and pool is assigned. For the use case of started VMs it's more trivial and disk proceeds as follows - Ready -> Attaching -> Ready. Test this by creating a VM with "startvm=false", create a disk and try attaching it in allocated state. It would give an exception on latest 4.11 but will be fixed on this patch. Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>		2019-05-10 23:40:38 +05:30
..
com/cloud	orchestration: Allow VM that has never started to have volumes attached (#3276)	2019-05-10 23:40:38 +05:30
org/apache/cloudstack	api: don't throttle api discovery for listApis command (#2894)	2018-12-12 23:55:32 +05:30