[jira] [Created] (CLOUDSTACK-5694) Xenserver - When VM is deleted outside of CS , VM state is not being synced to CS.

["Sangeetha Hariharan (JIRA)" <ji...@apache.org>]

Sangeetha Hariharan created CLOUDSTACK-5694:
-----------------------------------------------

             Summary: Xenserver - When VM is deleted outside of CS , VM state is not being synced to CS.
                 Key: CLOUDSTACK-5694
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5694
             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
            Priority: Critical
             Fix For: 4.3.0


[Vmsync]- xenserver - When VM is deleted outside of CS , VM state is not being synced to CS.

PreReq:
Have few Vms deployed using Cloudstack.
Steps:
Outside of Cloudstack , Destroy an existing VM. ( stop the VM and then delete the VM from xencenter.

There is an attempt made to stop the VM in CS that fails.
Should the expected behavior be to stop the VM and then destroy it in the CS?

Following exception seen in management server:

2013-12-26 20:14:42,543 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-342:ctx-433f534a) The VM is now missing marking it as Stopped i-3-3-MyTestVM
2013-12-26 20:14:42,543 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-342:ctx-433f534a) Seq 1-1141178372: Response Received:
2013-12-26 20:14:42,543 DEBUG [c.c.a.t.Request] (DirectAgent-342:ctx-433f534a) Seq 1-1141178372: Processing: { Ans: , MgmtId: 112516401760401, via: 1, Ver: v1, Flags: 10, [{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":1,"_newStates":{"i-3-3-MyTestVM":{"t":"157f5d61-037f-44eb-ae3d-0cd082d3cff0","u":"Stopped"}},"_isExecuted":false,"result":true,"wait":0}}] }
2013-12-26 20:14:42,547 DEBUG [c.c.v.VirtualMachineManagerImpl] (DirectAgent-342:ctx-433f534a) VM i-3-3-MyTestVM: cs state = Running and realState = Stopped
2013-12-26 20:14:42,547 DEBUG [c.c.v.VirtualMachineManagerImpl] (DirectAgent-342:ctx-433f534a) VM i-3-3-MyTestVM: cs state = Running and realState = Stopped
2013-12-26 20:14:42,547 DEBUG [c.c.h.HighAvailabilityManagerImpl] (DirectAgent-342:ctx-433f534a) VM does not require investigation so I'm marking it as Stopped: VM[User|TestVM-1]
2013-12-26 20:14:42,547 WARN [o.a.c.alerts] (DirectAgent-342:ctx-433f534a) alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: VM (name: TestVM-1, id: 3) stopped unexpectedly on host id:2, availability zone id:1, pod id:1
2013-12-26 20:14:42,551 DEBUG [c.c.h.HighAvailabilityManagerImpl] (DirectAgent-342:ctx-433f534a) VM is not HA enabled so we're done.
2013-12-26 20:14:42,551 WARN [c.c.a.m.DirectAgentAttache] (DirectAgent-342:ctx-433f534a) Seq 1-1141178372: 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.1.5#6160)