cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Likitha Shetty (JIRA)" <>
Subject [jira] [Assigned] (CLOUDSTACK-6043) VMware detaching volume fails if volume has snapshots
Date Fri, 25 Jul 2014 10:16:38 GMT


Likitha Shetty reassigned CLOUDSTACK-6043:

    Assignee: Likitha Shetty  (was: Kelven Yang)

> VMware detaching volume fails if volume has snapshots
> -----------------------------------------------------
>                 Key: CLOUDSTACK-6043
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware, Volumes
>    Affects Versions: 4.3.0
>            Reporter: Chris Suich
>            Assignee: Likitha Shetty
>              Labels: vmware, volumes
>             Fix For: 4.4.0
> When detaching VMware volumes, a call is first made to the hypervisor to remove all snapshots
for that volume. After this happens, the path for the volume potentially changes, but isn't
updated in the ACS DB, which causes problems when the call is made to actually detach the
> For example, if the volume has a single snapshot, then the current path would be something
like VOLUME-00001.vmdk which is a delta disk for VOLUME.vmdk. Once the snapshot is deleted,
VOLUME-00001.vmdk is coalesced into VOLUME.vmdk, which becomes the active path. However, ACS
still believes the correct path is VOLUME-00001.vmdk which causes the detach to fail.

This message was sent by Atlassian JIRA

View raw message