[
https://issues.apache.org/jira/browse/CLOUDSTACK-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Likitha Shetty reopened CLOUDSTACK-5122:
----------------------------------------
During upgrade from 4.1 system vms don't come up with 'ROOT-x-y.vmdk not found'
exception.
Log details are:
INFO [vmware.resource.VmwareResource] (DirectAgent-5:10.102.192.23) Configure
VNC port for VM s-1-VM, port: 5919, host: 10.102.192.23
WARN [vmware.resource.VmwareResource] (DirectAgent-5:10.102.192.23)
StartCommand failed due to Exception: java.lang.RuntimeException
Message: File []/vmfs/volumes/35ade0f8-0714a521/s-1-VM/ROOT-1-1.vmdk was not
found
java.lang.RuntimeException: File
[]/vmfs/volumes/35ade0f8-0714a521/s-1-VM/ROOT-1-1.vmdk was not found
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:411)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:856)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2966)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:513)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-5:null) Seq 1-607780939:
Cancelling because one of the answers is false and it is stop on error.
> [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)
