[ https://issues.apache.org/jira/browse/CLOUDSTACK-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213503#comment-14213503 ]
Kishan Kavala commented on CLOUDSTACK-7530: ------------------------------------------- 2014-11-15 15:23:19,364 INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-97:ctx-cf13ccba job-31/job-613) Remove job-613 from job monitoring 2014-11-15 15:23:19,366 DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-98:ctx-619c9467 job-480/job-615 ctx-9751a4a7) VM is already stopped: VM[DomainRouter|r-127-VM] 2014-11-15 15:23:19,366 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-98:ctx-619c9467 job-480/job-615 ctx-9751a4a7) Done executing VM work job: com.cloud.vm.VmWorkStop{"cleanup":false,"userId":1,"accountId":1,"vmId":127,"handlerName":"VirtualMachineManagerImpl"} 2014-11-15 15:23:19,366 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-98:ctx-619c9467 job-480/job-615 ctx-9751a4a7) Complete async job-615, jobStatus: SUCCEEDED, resultCode: 0, result: null 2014-11-15 15:23:19,366 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-98:ctx-619c9467 job-480/job-615 ctx-9751a4a7) Publish async job-615 complete on message bus 2014-11-15 15:23:19,366 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-98:ctx-619c9467 job-480/job-615 ctx-9751a4a7) Wake up jobs related to job-615 2014-11-15 15:23:19,366 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-98:ctx-619c9467 job-480/job-615 ctx-9751a4a7) Update db status for job-615 2014-11-15 15:23:19,367 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-98:ctx-619c9467 job-480/job-615 ctx-9751a4a7) Wake up jobs joined with job-615 and disjoin all subjobs created from job- 615 2014-11-15 15:23:19,430 DEBUG [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-98:ctx-619c9467 job-480/job-615) Done with run of VM work job: com.cloud.vm.VmWorkStop for VM 127, job origin: 480 2014-11-15 15:23:19,430 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-98:ctx-619c9467 job-480/job-615) Done executing com.cloud.vm.VmWorkStop for job-615 2014-11-15 15:23:19,451 DEBUG [o.a.c.e.o.NetworkOrchestrator] (RouterMonitor-1:ctx-b081e6ea) Starting network Ntwk[204|Guest|8]... 2014-11-15 15:23:19,451 DEBUG [o.a.c.e.o.NetworkOrchestrator] (RouterMonitor-1:ctx-b081e6ea) Network id=204 is already implemented 2014-11-15 15:23:19,452 DEBUG [o.a.c.e.o.NetworkOrchestrator] (RouterMonitor-1:ctx-b081e6ea) Starting network Ntwk[202|Control|3]... 2014-11-15 15:23:19,453 DEBUG [o.a.c.e.o.NetworkOrchestrator] (RouterMonitor-1:ctx-b081e6ea) Network id=202 is already implemented 2014-11-15 15:23:19,453 DEBUG [o.a.c.e.o.NetworkOrchestrator] (RouterMonitor-1:ctx-b081e6ea) Starting network Ntwk[200|Public|1]... 2014-11-15 15:23:19,454 DEBUG [o.a.c.e.o.NetworkOrchestrator] (RouterMonitor-1:ctx-b081e6ea) Network id=200 is already implemented 2014-11-15 15:23:19,455 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:ctx-b081e6ea) Starting router VM[DomainRouter|r-127-VM] > [LXC] router VMs are not migrating to other cluster if we put its original > host into maintenance > ------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-7530 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7530 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM > Affects Versions: 4.5.0 > Reporter: shweta agarwal > Assignee: Kishan Kavala > Fix For: 4.5.0 > > > Repro steps: > Create a Zone with two LXC clusters each having one host > Launch a VM in this cluster > Put LXC host to maintenance which has router VM > Bug; > Router VM does not migrates to other available host in another cluster > Expected Result: > Router VM should migrate to other host in the 2nd cluster > Additional info to support my case : > 1. When i started manually router vm it started in other cluster without issue > 2. Other system vm like CPVM and SSVM in similar situation moves/recreated > for one cluster to another cluster . -- This message was sent by Atlassian JIRA (v6.3.4#6332)