Suresh Kumar Anaparti created CLOUDSTACK-9185:
-------------------------------------------------
Summary: [VMware DRS] VM sync failed with exception due to
out-of-band changes
Key: CLOUDSTACK-9185
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9185
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server, VMware
Affects Versions: 4.5.2
Reporter: Suresh Kumar Anaparti
1. Configure VMware advanced zone
2. Create a cluster with 2 hosts
3. Enable the DRS in the cluster from vCenter
4. Configure the DRS rule – VMs grouped together for SSVM and Router VM
5. Make sure both SSVM and Router VM are on the same host
6. Migrate Router VM from CloudStack to another host
7. Check the VM states
Actual result:
After vm migrated to another host successfully, DRS on background moves back
Router VM back to original host as per DRS rule(VMs together) configured.
CS identifed our-of-band change and failed with below exception:
2015-11-24 00:45:06,298 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-343:ctx-4d811a39) (logid:46ceb8da) VM state report. host:
5, vm id: 48, power state: PowerOn
2015-11-24 00:45:06,304 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-343:ctx-4d811a39) (logid:46ceb8da) VM state report is
updated. host: 5, vm id: 48, power state: PowerOn
2015-11-24 00:45:06,313 INFO [c.c.v.VirtualMachineManagerImpl]
(DirectAgentCronJob-343:ctx-4d811a39) (logid:46ceb8da) Detected out of band VM
migration from host 1 to host 5
2015-11-24 00:45:06,324 ERROR [o.a.c.f.m.MessageDispatcher]
(DirectAgentCronJob-343:ctx-4d811a39) (logid:46ceb8da) Unexpected exception
when calling
com.cloud.vm.ClusteredVirtualMachineManagerImpl.HandlePowerStateReport
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor228.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.cloudstack.framework.messagebus.MessageDispatcher.dispatch(MessageDispatcher.java:75)
at
org.apache.cloudstack.framework.messagebus.MessageDispatcher.onPublishMessage(MessageDispatcher.java:45)
at
org.apache.cloudstack.framework.messagebus.MessageBusBase$SubscriptionNode.notifySubscribers(MessageBusBase.java:441)
at
org.apache.cloudstack.framework.messagebus.MessageBusBase.publish(MessageBusBase.java:178)
at
com.cloud.vm.VirtualMachinePowerStateSyncImpl.processReport(VirtualMachinePowerStateSyncImpl.java:87)
at
com.cloud.vm.VirtualMachinePowerStateSyncImpl.processHostVmStatePingReport(VirtualMachinePowerStateSyncImpl.java:70)
at
com.cloud.vm.VirtualMachineManagerImpl.processCommands(VirtualMachineManagerImpl.java:2840)
at
com.cloud.agent.manager.AgentManagerImpl.handleCommands(AgentManagerImpl.java:309)
at
com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(DirectAgentAttache.java:192)
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.runAndReset(FutureTask.java:304)
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:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.util.concurrent.RejectedExecutionException: Task
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@4b366ec2
rejected from
java.util.concurrent.ScheduledThreadPoolExecutor@7f5b2a5e[Terminated, pool size
= 0, active threads = 0, queued tasks = 0, completed tasks = 1]
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821)
at
java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:325)
... 32 more
2015-11-24 00:45:06,326 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgentCronJob-343:ctx-4d811a39) (logid:46ceb8da) Unable to complete the
ping task
java.lang.RuntimeException: InvocationTargetException when invoking event
handler for subject: vm.powerstate
at
org.apache.cloudstack.framework.messagebus.MessageDispatcher.dispatch(MessageDispatcher.java:84)
at
org.apache.cloudstack.framework.messagebus.MessageDispatcher.onPublishMessage(MessageDispatcher.java:45)
at
org.apache.cloudstack.framework.messagebus.MessageBusBase$SubscriptionNode.notifySubscribers(MessageBusBase.java:441)
at
org.apache.cloudstack.framework.messagebus.MessageBusBase.publish(MessageBusBase.java:178)
at
com.cloud.vm.VirtualMachinePowerStateSyncImpl.processReport(VirtualMachinePowerStateSyncImpl.java:87)
at
com.cloud.vm.VirtualMachinePowerStateSyncImpl.processHostVmStatePingReport(VirtualMachinePowerStateSyncImpl.java:70)
at
com.cloud.vm.VirtualMachineManagerImpl.processCommands(VirtualMachineManagerImpl.java:2840)
at
com.cloud.agent.manager.AgentManagerImpl.handleCommands(AgentManagerImpl.java:309)
at
com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(DirectAgentAttache.java:192)
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.runAndReset(FutureTask.java:304)
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:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2015-11-24 00:45:06,989 DEBUG [c.c.s.StatsCollector]
(StatsCollector-3:ctx-c3c9615d) (logid:158be315) AutoScaling Monitor is
running...
2015-11-24 00:45:10,102 INFO [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-2b3f6b75) (logid:5862f424) Begin cleanup expired
async-jobs
2015-11-24 00:45:10,112 INFO [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-2b3f6b75) (logid:5862f424) End cleanup expired
async-jobs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
