[ https://issues.apache.org/jira/browse/CLOUDSTACK-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102566#comment-14102566 ]
Sudha Ponnaganti commented on CLOUDSTACK-6043: ---------------------------------------------- Chris, Do you agree with this assessment thanks /sudha > VMware detaching volume fails if volume has snapshots > ----------------------------------------------------- > > Key: CLOUDSTACK-6043 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6043 > 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 volume. > 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 (v6.2#6252)