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-5122) [VMware] System VMs are getting recreated with old template after upgrading to 4.2
Date Sun, 10 Nov 2013 18:11:17 GMT

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

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

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

CLOUDSTACK-5122. System VMs are getting recreated with old template after upgrading to 4.2.
In VMware during VM start the existing disk information is used to configure the VMs. So even
if a new disk is created using the new template VM continues to use the old disk.
Once the old root disk is marked for destroy force expunge it and sync the new disk into the
VM folder before VM start


> [VMware] System VMs are getting recreated with old template after upgrading to 4.2
> ----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5122
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5122
>             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
>
>
> Steps:
> 1. Configure Adv zone with VMware
> 2. Deploy 2 VM's and then register 4.2 template
> 3. Upgraded to 4.2
> 4. Restart System VM;s and Router
> Observation:
> System VM's are getting recreated with old templates only
> Workaround :
> 1. Destroy SSVM/CPVM then these VMs gets created with new template
> 2. Stop Router VM, Destroy Router VM
> 3. Restart Network or Deploy new VM on this guest network. Now Router also gets created
with new template



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message