[
https://issues.apache.org/jira/browse/CLOUDSTACK-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527074#comment-13527074
]
Koushik Das commented on CLOUDSTACK-595:
----------------------------------------
Hi Joe,
My bad missed out adding the details.
For Vmware, CS creates root volume in the Esx host with the display name of
root volume. I.e. if display name is ROOT-1 then the corresponding vmdk file is
named ROOT-1.vmdk. For system vm template upgrade and restoreVM command
scenarios, CS recreates the root volume with same properties as the old one and
also marks it for removal. At the host new ROOT-1.vmdk gets created and
overwrites the old one. Till this point everything is fine. But when the
storage cleanup thread runs (look at storage.cleanup.* global settings), it
tries to cleanup the old volume and as part of it remove the corresponding vmdk
file. This has the undesired effect of removing the vmdk file in use by the new
volume as both uses the same file name.
For other HVs problem is not there as disk filename is always a new UUID and
not CS display name. In Vmware the same approach is not used due to limitations
in length of vmdk file name. Refer to
http://bugs.cloudstack.org/browse/CS-16943 for details.
The fix is to make the vmdk filename unique. I have a fix ready and will send
out for review.
Thanks,
Koushik
> Recreate root volume scenarios doesn't work in vmware
> -----------------------------------------------------
>
> Key: CLOUDSTACK-595
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-595
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: pre-4.0.0, 4.0.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.0.1
>
>
> Affected scenarios:
> - System vm template upgrade
> - restoreVirtualMachine command
--
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
