You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2013/10/28 08:56:30 UTC
[jira] [Resolved] (CLOUDSTACK-4946) Restore VM with template id
feature doesnt work on VMware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Likitha Shetty resolved CLOUDSTACK-4946.
----------------------------------------
Resolution: Fixed
> 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)