cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7201) migrate volume with live migrate = true allows migration across cluster or fails with NPE
Date Wed, 30 Jul 2014 07:30:38 GMT

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

ASF subversion and git services commented on CLOUDSTACK-7201:
-------------------------------------------------------------

Commit fc14fe1132d03ad8828faf434989d3cd394d023b in cloudstack's branch refs/heads/master from
[~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fc14fe1 ]

CLOUDSTACK-7201. Before initating  out live volume migration to a pool check that if the
destination pool is a cluster wide pool, it should be in the same cluster as the vm to
which the volume is attached.


> migrate volume with live migrate = true allows migration across cluster or fails with
NPE
> -----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7201
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7201
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Devdeep Singh
>            Assignee: Devdeep Singh
>            Priority: Critical
>
> migrate volume with livemigrate=true allows migrating the volume across clusters in case
of Hyper-V.
> In case of XS, we are throwing an NPE although the migration correctly fails.
> Steps:
> =====
> 0. Create a set up with at least 2 clusters
> 1. Deploy a VM with data disk
> 2. As admin, while VM is running migrate volume to another shared pool in another cluster
> (cloudmonkey)
> > migrate volume livemigrate=true storageid=<id of pool in another cluster>
volumeid=<id of ROOT or DATA disk>
> Expected Result:
> ============
> This shouldn't be allowed, we should fail the API with proper error message, allowing
us to migrate volume only to storage pool within the same cluster, unless it is a zone wide
storage pool. (If we want to achieve across cluster migration, we should use migrateVitualMachine
with storage live migration)
> Result in Hyper-V
> =============
> We end up with the volume migrated to another cluster storage pool while the VM is running
off the original cluster storage pool. We should not allow this to happen.
> Result in XS 6.2
> ============
> Migration correctly fails with error message but we also throw an NPE.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message