[
https://issues.apache.org/jira/browse/CLOUDSTACK-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716057#comment-13716057
]
ASF subversion and git services commented on CLOUDSTACK-3708:
-------------------------------------------------------------
Commit 0760a5197b47a66ec5fbf77419d88922279c7138 in branch refs/heads/4.2 from
[~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0760a51 ]
CLOUDSTACK-3708, Migration of a volume attached to a running instance isn't
working (Storage motion).
The request to migrate was coming till ancient data motion strategy but wasn't
worked on and forwarded
to the resource. The code probably got removed by a bad merge. Bringing it back.
> [Regression] Migration of volume from one storage pool to another isn't
> working
> -------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3708
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3708
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Reporter: Devdeep Singh
> Assignee: Devdeep Singh
> Priority: Blocker
> Fix For: 4.2.0
>
>
> 1. Create a setup on a hypervisor that supports storage migratio, e.g
> XenServer 6.1 or 6.2 or Vmware 5.1.
> 2. Create a cluster and add atleast 2 primary storage pools to the cluster.
> 3. Deploy an instance.
> 4. Try migrating volume of a running instance to another storage pool in the
> cluster.
> It fails and storage migration doesn't work. This is a regression and the
> feature used to work earlier.
--
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
