[
https://issues.apache.org/jira/browse/CLOUDSTACK-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N closed CLOUDSTACK-4946.
---------------------------------
Verified on latest 4.2.1 build with commit
8f76c49a994a630bfdd583c3515ac06c11c7c662
Restore VM to original root disk works fine. But restoring it to new template
fails. Created another bug to track this.
http://bugs-ccp.citrix.com/browse/CS-18519
> Restore VM with template id feature doesnt work on VMware
> ---------------------------------------------------------
>
> Key: CLOUDSTACK-4946
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4946
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Priority: Critical
> Fix For: 4.2.1
>
>
> To restore a VM to a different/original template, user can use
> restoreVirtualMachine API with templateId parameter or create the VM from a
> service offering that has isVolatile set to true and then reboot the VM.
> In 4.2 this functionality is not working as expected in a VMware environment.
> When a VM restore is called the VM is not restored to the right template,
> instead the VM continues to use the original template.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
