You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "manasaveloori (JIRA)" <ji...@apache.org> on 2013/07/18 11:34:56 UTC

[jira] [Commented] (CLOUDSTACK-3630) [Storage]No option for migration of local data volume.

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712163#comment-13712163 ] 

manasaveloori commented on CLOUDSTACK-3630:
-------------------------------------------

Devdeep

As per your comments when I try to migrate the instance (which is created using compute offering with storage as local)  to  another  storage pool on second host it is throwing exception as Volumes cannot be migrated.

ed: 0, total: 17169539072; new used: 1073741824,reserved:0; movedfromreserved: false,moveToReserveredfalse
2013-07-18 20:17:42,024 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-47:job-119 = [ 326823ea-b4a6-4c47-99c8-ea84af62099d ]) Unexpected exception while executing org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to migrated vm VM[User|localvm1] along with its volumes. Snapshots are being created on a volume. Volumes cannot be migrated now.
        at com.cloud.storage.VolumeManagerImpl.migrateVolumes(VolumeManagerImpl.java:2260)
        at com.cloud.vm.VirtualMachineManagerImpl.migrateWithStorage(VirtualMachineManagerImpl.java:1701)
        at com.cloud.vm.UserVmManagerImpl.migrateVirtualMachineWithVolume(UserVmManagerImpl.java:4039)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd.execute(MigrateVirtualMachineWithVolumeCmd.java:137)
        at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
        at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:679)
2013-07-18 20:17:42,058 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-47:job-119 = [ 326823ea-b4a6-4c47-99c8-ea84af62099d ]) Complete async job-119 = [ 326823ea-b4a6-4c47-99c8-ea84af62099d ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to migrated vm VM[User|localvm1] along with its volumes. Snapshots are being created on a volume. Volumes cannot be migrated now.



                
> [Storage]No option for migration of local data volume.
> ------------------------------------------------------
>
>                 Key: CLOUDSTACK-3630
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3630
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.2.0
>         Environment: latest 4.2 build
>            Reporter: manasaveloori
>            Assignee: Devdeep Singh
>             Fix For: 4.2.0
>
>         Attachments: storage.jpg
>
>
> Steps:
> 1.	Have a CS with advanced zone with VMware hypervisor..
> 2.	Have 1 local and 1 cluster wide primary storages.
> 3.	Create a Data disk using local primary storage.
> Observed that there is no option to migrate the created local data disk.
> Attached the screen shot for the same.

--
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