[
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N reopened CLOUDSTACK-2670:
-----------------------------------
Hi Min,
As per your comment, we only support volume live migration. But live volume
migration support has been added from xen6.1 onwards. If the user wanted to use
any xenserver prior to 6.1 live migration would not be supported from the
xenserver side and moving stopped vm's root volume would not be supported
because of the existing master code.
This is not expected behavior, hence reopening the bug.
> [Object_Store_Refactor] UI/API: migrate volume does not show the available
> primary storages within the cluster
> --------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: 4.2.0
> Environment: Latest build from object store branch:
> CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
> Reporter: Sanjeev N
> Assignee: Min Chen
> Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
> ================
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary
> storage in the cluster
> Result:
> ======
> migrate volume called findStoragePoolsFroMigration but the API returned blank
> response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.
--
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
