[
https://issues.apache.org/jira/browse/CLOUDSTACK-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231454#comment-14231454
]
Rohit Yadav commented on CLOUDSTACK-5696:
-----------------------------------------
I tested this today with VM in isolated network/advanced zone using KVM and it
worked for me. VMSync kicked in shortly after VM was shutdown using virsh and
it transitioned the internal state first to stopped and then to starting. The
same thing happened when I did virsh destroy (like pulling plug). I see
something like this;
2014-12-02 18:42:12,061 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 1-4374: Processing Seq 1-4374: { Cmd ,
MgmtId: -1, via: 1, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.PingRoutingWithNwGroupsCommand":{"newGroupStates":{},"newStates":{"r-272-VM":"Stopped"},"_hostVmStateReport":{"v-2-VM":{"state":"PowerOn","host":"bluebox"},"s-1-VM":{"state":"PowerOn","host":"bluebox"},"i-2-326-VM":{"state":"PowerOn","host":"bluebox"}},"_gatewayAccessible":true,"_vnetAccessible":true,"hostType":"Routing","hostId":1,"wait":0}}]
}
2014-12-02 18:42:12,064 DEBUG [c.c.v.VirtualMachineManagerImpl]
(AgentManager-Handler-2:null) VM r-272-VM: cs state = Running and realState =
Stopped
2014-12-02 18:42:12,064 DEBUG [c.c.v.VirtualMachineManagerImpl]
(AgentManager-Handler-2:null) VM r-272-VM: cs state = Running and realState =
Stopped
2014-12-02 18:42:12,064 DEBUG [c.c.h.HighAvailabilityManagerImpl]
(AgentManager-Handler-2:null) VM does not require investigation so I'm marking
it as Stopped: VM[DomainRouter|r-272-VM]
2014-12-02 18:42:12,064 WARN [o.a.c.f.j.AsyncJobExecutionContext]
(AgentManager-Handler-2:null) Job is executed without a context, setup psudo
job for the executing thread
2014-12-02 18:42:12,132 DEBUG [c.c.c.CapacityManagerImpl]
(AgentManager-Handler-2:null) VM state transitted from :Running to Stopping
with event: StopRequestedvm's original host id: 1 new host id: 1 host id before
state transition: 1
> [Vmsync]- Stopped state of VM is not synced to CS when VM is stopped outside
> of CS.
> -----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5696
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5696
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Environment: Build from 4.3
> Reporter: Sangeetha Hariharan
> Assignee: Kelven Yang
> Priority: Critical
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> Pre Req:
> Have few Vms deployed using Cloudstack.
> Steps:
> Outside of Cloudstack ,Stop VM
> Vm continues to remain in "Running" state in CS , even though the change in
> state is detected.
> Following exception seen in management server logs:
> 2013-12-26 17:02:10,026 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (DirectAgent-77:ctx-c28d9506) VM i-3-8-MyTestVM: cs state = Running and realSt
> ate = Stopped
> 2013-12-26 17:02:10,027 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (DirectAgent-77:ctx-c28d9506) VM i-3-8-MyTestVM: cs state = Running and realSt
> ate = Stopped
> 2013-12-26 17:02:10,027 DEBUG [c.c.h.HighAvailabilityManagerImpl]
> (DirectAgent-77:ctx-c28d9506) VM does not require investigation so I'm marki
> ng it as Stopped: VM[User|TestVM-tiny-host-1ps-0-1]
> 2013-12-26 17:02:10,027 WARN [o.a.c.alerts] (DirectAgent-77:ctx-c28d9506)
> alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: null
> // message:: VM (name: TestVM-tiny-host-1ps-0-1, id: 8) stopped unexpectedly
> on host id:1, availability zone id:1, pod id:1
> 2013-12-26 17:02:10,032 DEBUG [c.c.h.HighAvailabilityManagerImpl]
> (DirectAgent-77:ctx-c28d9506) VM is not HA enabled so we're done.
> 2013-12-26 17:02:10,032 WARN [c.c.a.m.DirectAgentAttache]
> (DirectAgent-77:ctx-c28d9506) Seq 1-799145986: Exception caught
> java.lang.NullPointerException
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1235)
> at
> com.cloud.ha.HighAvailabilityManagerImpl.scheduleRestart(HighAvailabilityManagerImpl.java:346)
> at
> com.cloud.vm.VirtualMachineManagerImpl.compareState(VirtualMachineManagerImpl.java:2686)
> at
> com.cloud.vm.VirtualMachineManagerImpl.deltaSync(VirtualMachineManagerImpl.java:2320)
> at
> com.cloud.vm.VirtualMachineManagerImpl.processAnswers(VirtualMachineManagerImpl.java:2797)
> at com.cloud.agent.manager.AgentAttache.processAnswers(AgentAttache.java:296)
> at
> com.cloud.agent.manager.ClusteredDirectAgentAttache.processAnswers(ClusteredDirectAgentAttache.java:65)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:242)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 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:722)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
