cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajani Karuturi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-8598) CS reports volume migration as successful but the volume is not migrated in vCenter.
Date Wed, 12 Aug 2015 08:50:46 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajani Karuturi updated CLOUDSTACK-8598:
----------------------------------------
    Assignee:     (was: Likitha Shetty)

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

Mime
View raw message