[
https://issues.apache.org/jira/browse/CLOUDSTACK-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14607962#comment-14607962
]
ASF GitHub Bot commented on CLOUDSTACK-8598:
--------------------------------------------
GitHub user likitha opened a pull request:
https://github.com/apache/cloudstack/pull/543
CLOUDSTACK-8598. CS reports volume migration as successful but the vo…
…lume is not migrated in vCenter..
For the following disk operations - migration, snapshot creation, resize,
detach and template creation, CS should do an exact disk match between volume
path and vCenter disk name.
If the exact matching fails to find a disk, CS should fall back to the old
method of partial matching on a trimmed disk.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/likitha/cloudstack CLOUDSTACK-8598
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/543.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #543
----
commit f5db6a81f83ee42e7a557c0c099ea3463857c554
Author: Likitha Shetty <[email protected]>
Date: 2015-04-09T05:25:12Z
CLOUDSTACK-8598. CS reports volume migration as successful but the volume
is not migrated in vCenter..
For the following disk operations - migration, snapshot creation, resize,
detach and template creation, CS should do an exact disk match between volume
path and vCenter disk name.
If the exact matching fails to find a disk, CS should fall back to the old
method of partial matching on a trimmed disk.
----
> CS reports volume migration as successful but the volume is not migrated in
> vCenter.
> ------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8598
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8598
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Fix For: 4.6.0
>
>
> +Steps to reproduce+
> 1. Deploy a VMware setup with 1 cluster, 2 hosts H1,H2 and 2 primary storages
> P1,P2
> 2. Deploy a VM V1 on H1, such that ROOT is on P1 and data vol is on P2
> 3. Migrate V1 to H2 ,ROOT to P2 and data vol to P1 using
> migrateVirtualMachineWithVolume API.
> 4. Attach another data disk to V1
> 5. Now migrate V1 to H1, data1 to P2, data2 to P2 and ROOT to P1.
> 6. Again Migrate V1 to H2, data1 to P1, data2 to P1 and ROOT to P2
> Observed that data volume doesn't get migrated in step 8, but DB is updated
> and migration operation is reported as successful.
> Same issue observed with other operations that involve disk look up. For e.g.
> creating volume snapshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
