[
https://issues.apache.org/jira/browse/CLOUDSTACK-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831311#comment-13831311
]
ASF subversion and git services commented on CLOUDSTACK-5122:
-------------------------------------------------------------
Commit 8b0a46502a749f1665a76c0b0de2c2595f09eff0 in branch refs/heads/4.3 from
[~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8b0a465 ]
CLOUDSTACK-5122. [VMware] During upgrade from 4.1 system vms don't come up with
'ROOT-x-y VMDK file not found' exception.
During VM start, if VM already exists and CS finds a matching disk in storage
for each of the existing disk then the VM is reconfigured with VM's existing
disk information. This existing disk information for a VM is got from vCenter.
CS checks if a matching disk exists in storage by checking if there is a disk
in storage whose name atleast partially matches with the name of the existing
disk.
Post 4.1, Volume path has been changed to ROOT-<instanceId> from
ROOT-<instanceId>-<volumeId>. Hence in case of an upgraded setup (pre 4.1 to
4.2) during search for an existing disk in storage even though
ROOT-<instanceId>-<volumeId> has been deleted, CS does a postive match of the
old existing disk because of the partial match with the new disk
ROOT-<instanceId> that exists in storage. And so when VM is being powered on by
vCenter it looks for ROOT-<instanceId>-<volumeId> and fails to power on.
Solution - While looking for a VM's matching disk in storage, instead of
checking if a disk with a partial match exists check if a disk with the exact
name exists.
> [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.3.0
>
>
> 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)
