Paul Angus created CLOUDSTACK-3502:
--------------------------------------
Summary: CloudStack will not allow migration of volumes of stopped
VMs
Key: CLOUDSTACK-3502
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3502
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: XenServer
Affects Versions: 4.2.0
Environment: XenServer 6.1 and XenServer 6.2
Reporter: Paul Angus
Fix For: 4.2.0
CloudStack will not allow migration of volumes of stopped VMs. The following
error is logged i
DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) ===START=== 10.0.0.33 --
GET
command=findStoragePoolsForMigration&id=88249ba7-7efc-458d-a5fb-dfe509f3be94&response=json&sessionkey=f1fhBLP6fTlE5Wun%2FBDzzbkAH4k%3D&_=1373630022341
INFO [cloud.server.ManagementServerImpl] (catalina-exec-18:null) Volume
Vol[20|vm=20|ROOT] isn't attached to any running vm. Only volumes attached to a
running VM can be migrated.
DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) ===START=== 10.0.0.33 --
GET
command=findStoragePoolsForMigration&id=0a3704cf-6a23-4c18-bf90-9fd701da2223&response=json&sessionkey=RKyZ0iBJcDk11IUG7pLJs57wgTE%3D&_=1373620893684
INFO [cloud.server.ManagementServerImpl] (catalina-exec-10:null) Volume
Vol[16|vm=16|ROOT] isn't attached to any running vm. Only volumes attached to a
running VM can be migrated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
