cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4946) Restore VM with template id feature doesnt work on VMware
Date Mon, 28 Oct 2013 07:52:30 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806608#comment-13806608
] 

ASF subversion and git services commented on CLOUDSTACK-4946:
-------------------------------------------------------------

Commit 1a3f394730e92bb80388a9f78aa83bbc513b451f in branch refs/heads/4.2 from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1a3f394 ]

CLOUDSTACK-4946. VM Restore with template id/Volatile VM feature doesnt work on VMware
When a ROOT volume is created from base template, if a folder already exists for the ROOT
volume's VM then replace the old ROOT disk files with the new one.


> 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)

Mime
View raw message