You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Steve Searles <ss...@zimcom.net> on 2015/04/01 15:52:22 UTC
Trouble Attaching Volume
I am having trouble attaching a volume to an existing VM. Adding an extra volume during the instance creation works fine. It does not seem to matter what state the VM is in eg. stopped or running I receive the same error. Anyone know what this means? I can not find any further information on "Message: Unable to find the VM to execute AttachVolumeCommand”, ‘
Cloudstack 4.4.2
Vmware 5.5
Any help would be appreciated.
INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca job-484/job-485) Add job-485 into job monitoring
INFO [c.c.s.VolumeApiServiceImpl] (Work-Job-Executor-1:ctx-4e1f0aca job-484/job-485 ctx-3e014d23) Trying to attaching volume 175 to vm instance:154, update async job-485 progress status
ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca job-484/job-485 ctx-3e014d23) Invocation exception, caused by: com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to Exception: java.lang.Exception
Message: Unable to find the VM to execute AttachVolumeCommand, vmName: i-2-154-VM
INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca job-484/job-485 ctx-3e014d23) Rethrow exception com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to Exception: java.lang.Exception
Message: Unable to find the VM to execute AttachVolumeCommand, vmName: i-2-154-VM
ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-1:ctx-4e1f0aca job-484/job-485) Unable to complete AsyncJobVO {id:485, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd: com.cloud.storage.VmWorkAttachVolume, cmdInfo: rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAJp0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAK8, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 345049815164, completeMsid: null, lastUpdated: null, lastPolled: null, created: Wed Apr 01 09:47:24 EDT 2015}, job origin:484
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to Exception: java.lang.Exception
Message: Unable to find the VM to execute AttachVolumeCommand, vmName: i-2-154-VM
at com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2110)
at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1247)
at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1091)
at com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2476)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2511)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy183.handleVmWorkJob(Unknown Source)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
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 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
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)
INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca job-484/job-485) Remove job-485 from job monitoring
-Steven Searles
RE: Trouble Attaching Volume
Posted by Somesh Naidu <So...@citrix.com>.
Yitao, that may be because VM sync for VMware was fixed in later versions, partially in 4.2 and further enhancements in 4.3.
Somesh
CloudPlatform Escalations
Citrix Systems, Inc.
-----Original Message-----
From: Yitao Jiang [mailto:willierjyt@gmail.com]
Sent: Friday, April 03, 2015 2:00 AM
To: users@cloudstack.apache.org
Subject: Re: Trouble Attaching Volume
But obviously ACS4.1.0 with vmware hypervisor and fc-san storage , the
mechanism not working for me.
---
Thanks,
Yitao(依涛 姜)
jiangyt.github.io
On Fri, Apr 3, 2015 at 1:14 PM, Koushik Das <ko...@citrix.com> wrote:
> There is already a vm-sync mechanism to synchronise states between
> hypervisor and CS DB. When VMs get moved from one host to another outside
> of CS, vm-sync is supposed to update the DB with the new host id.
>
>
> On 03-Apr-2015, at 7:13 AM, Yitao Jiang <wi...@gmail.com> wrote:
>
> > Synchronisation work need to be done. I will do some hacking when i am
> free.
> > On Apr 2, 2015 10:27 PM, "Steve Searles" <ss...@zimcom.net> wrote:
> >
> >> That was it. Thanks!. What is the best practice for DRS and HA with
> >> vmware for use with Cloudstack? Disabled?
> >>
> >> Steven Searles
> >>
> >>
> >>
> >> On Apr 2, 2015, at 2:17 AM, Sanjeev N <sanjeev@apache.org<mailto:
> >> sanjeev@apache.org>> wrote:
> >>
> >> Also make sure that vm is actually running on the host
> >>
> >> On Thu, Apr 2, 2015 at 6:11 AM, Yitao Jiang <willierjyt@gmail.com
> <mailto:
> >> willierjyt@gmail.com>> wrote:
> >>
> >> I met the same issue before. Cause under vmware cluster ha enabled, so
> the
> >> vm mirgrated among hosts. You can check the host which vm lives in cloud
> >> databases, and compare to the actual host, if mismatchrd, changing the
> db
> >> table, thrn all works fine.
> >> On Apr 1, 2015 9:52 PM, "Steve Searles" <ssearles@zimcom.net<mailto:
> >> ssearles@zimcom.net>> wrote:
> >>
> >> I am having trouble attaching a volume to an existing VM. Adding an
> >> extra
> >> volume during the instance creation works fine. It does not seem to
> >> matter
> >> what state the VM is in eg. stopped or running I receive the same error.
> >> Anyone know what this means? I can not find any further information on
> >> "Message: Unable to find the VM to execute AttachVolumeCommand”, ‘
> >>
> >>
> >> Cloudstack 4.4.2
> >> Vmware 5.5
> >>
> >>
> >>
> >> Any help would be appreciated.
> >>
> >>
> >> INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485) Add job-485 into job monitoring
> >> INFO [c.c.s.VolumeApiServiceImpl] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485 ctx-3e014d23) Trying to attaching volume 175 to vm
> >> instance:154, update async job-485 progress status
> >> ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485 ctx-3e014d23) Invocation exception, caused by:
> >> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> >> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> >> Exception: java.lang.Exception
> >> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> >> i-2-154-VM
> >>
> >> INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485 ctx-3e014d23) Rethrow exception
> >> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> >> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> >> Exception: java.lang.Exception
> >> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> >> i-2-154-VM
> >>
> >> ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485) Unable to complete AsyncJobVO {id:485, userId: 2,
> >> accountId: 2, instanceType: null, instanceId: null, cmd:
> >> com.cloud.storage.VmWorkAttachVolume, cmdInfo:
> >>
> >>
> >>
> rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAJp0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAK8,
> >> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> >> result: null, initMsid: 345049815164, completeMsid: null, lastUpdated:
> >> null, lastPolled: null, created: Wed Apr 01 09:47:24 EDT 2015}, job
> >> origin:484
> >> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> >> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> >> Exception: java.lang.Exception
> >> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> >> i-2-154-VM
> >>
> >> at
> >>
> >>
> >>
> com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2110)
> >> at
> >>
> >>
> >>
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1247)
> >> at
> >>
> >>
> >>
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1091)
> >> at
> >>
> >>
> >>
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2476)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> >>
> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >> at
> >>
> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> at java.lang.reflect.Method.invoke(Method.java:606)
> >> at
> >>
> >>
> >>
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> >> at
> >>
> >>
> >>
> com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2511)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> >>
> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >> at
> >>
> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> at java.lang.reflect.Method.invoke(Method.java:606)
> >> at
> >>
> >>
> >>
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> >> at
> >>
> >>
> >>
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> >> at
> >>
> >>
> >>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> >> at
> >>
> >>
> >>
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> >> at
> >>
> >>
> >>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> >> at
> >>
> >>
> >>
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> >> at com.sun.proxy.$Proxy183.handleVmWorkJob(Unknown Source)
> >> at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> >> at
> >>
> >>
> >>
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
> >> 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
> >>
> >>
> >>
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
> >> at
> >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> >> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> >> 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)
> >> INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485) Remove job-485 from job monitoring
> >>
> >>
> >> -Steven Searles
> >>
> >>
> >>
> >>
> >>
>
>
Re: Trouble Attaching Volume
Posted by Yitao Jiang <wi...@gmail.com>.
But obviously ACS4.1.0 with vmware hypervisor and fc-san storage , the
mechanism not working for me.
---
Thanks,
Yitao(依涛 姜)
jiangyt.github.io
On Fri, Apr 3, 2015 at 1:14 PM, Koushik Das <ko...@citrix.com> wrote:
> There is already a vm-sync mechanism to synchronise states between
> hypervisor and CS DB. When VMs get moved from one host to another outside
> of CS, vm-sync is supposed to update the DB with the new host id.
>
>
> On 03-Apr-2015, at 7:13 AM, Yitao Jiang <wi...@gmail.com> wrote:
>
> > Synchronisation work need to be done. I will do some hacking when i am
> free.
> > On Apr 2, 2015 10:27 PM, "Steve Searles" <ss...@zimcom.net> wrote:
> >
> >> That was it. Thanks!. What is the best practice for DRS and HA with
> >> vmware for use with Cloudstack? Disabled?
> >>
> >> Steven Searles
> >>
> >>
> >>
> >> On Apr 2, 2015, at 2:17 AM, Sanjeev N <sanjeev@apache.org<mailto:
> >> sanjeev@apache.org>> wrote:
> >>
> >> Also make sure that vm is actually running on the host
> >>
> >> On Thu, Apr 2, 2015 at 6:11 AM, Yitao Jiang <willierjyt@gmail.com
> <mailto:
> >> willierjyt@gmail.com>> wrote:
> >>
> >> I met the same issue before. Cause under vmware cluster ha enabled, so
> the
> >> vm mirgrated among hosts. You can check the host which vm lives in cloud
> >> databases, and compare to the actual host, if mismatchrd, changing the
> db
> >> table, thrn all works fine.
> >> On Apr 1, 2015 9:52 PM, "Steve Searles" <ssearles@zimcom.net<mailto:
> >> ssearles@zimcom.net>> wrote:
> >>
> >> I am having trouble attaching a volume to an existing VM. Adding an
> >> extra
> >> volume during the instance creation works fine. It does not seem to
> >> matter
> >> what state the VM is in eg. stopped or running I receive the same error.
> >> Anyone know what this means? I can not find any further information on
> >> "Message: Unable to find the VM to execute AttachVolumeCommand”, ‘
> >>
> >>
> >> Cloudstack 4.4.2
> >> Vmware 5.5
> >>
> >>
> >>
> >> Any help would be appreciated.
> >>
> >>
> >> INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485) Add job-485 into job monitoring
> >> INFO [c.c.s.VolumeApiServiceImpl] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485 ctx-3e014d23) Trying to attaching volume 175 to vm
> >> instance:154, update async job-485 progress status
> >> ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485 ctx-3e014d23) Invocation exception, caused by:
> >> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> >> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> >> Exception: java.lang.Exception
> >> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> >> i-2-154-VM
> >>
> >> INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485 ctx-3e014d23) Rethrow exception
> >> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> >> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> >> Exception: java.lang.Exception
> >> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> >> i-2-154-VM
> >>
> >> ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485) Unable to complete AsyncJobVO {id:485, userId: 2,
> >> accountId: 2, instanceType: null, instanceId: null, cmd:
> >> com.cloud.storage.VmWorkAttachVolume, cmdInfo:
> >>
> >>
> >>
> rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAJp0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAK8,
> >> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> >> result: null, initMsid: 345049815164, completeMsid: null, lastUpdated:
> >> null, lastPolled: null, created: Wed Apr 01 09:47:24 EDT 2015}, job
> >> origin:484
> >> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> >> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> >> Exception: java.lang.Exception
> >> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> >> i-2-154-VM
> >>
> >> at
> >>
> >>
> >>
> com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2110)
> >> at
> >>
> >>
> >>
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1247)
> >> at
> >>
> >>
> >>
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1091)
> >> at
> >>
> >>
> >>
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2476)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> >>
> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >> at
> >>
> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> at java.lang.reflect.Method.invoke(Method.java:606)
> >> at
> >>
> >>
> >>
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> >> at
> >>
> >>
> >>
> com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2511)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> >>
> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >> at
> >>
> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> at java.lang.reflect.Method.invoke(Method.java:606)
> >> at
> >>
> >>
> >>
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> >> at
> >>
> >>
> >>
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> >> at
> >>
> >>
> >>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> >> at
> >>
> >>
> >>
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> >> at
> >>
> >>
> >>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> >> at
> >>
> >>
> >>
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> >> at com.sun.proxy.$Proxy183.handleVmWorkJob(Unknown Source)
> >> at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> >> at
> >>
> >>
> >>
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
> >> 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
> >>
> >>
> >>
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
> >> at
> >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> >> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> >> 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)
> >> INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
> >> job-484/job-485) Remove job-485 from job monitoring
> >>
> >>
> >> -Steven Searles
> >>
> >>
> >>
> >>
> >>
>
>
Re: Trouble Attaching Volume
Posted by Koushik Das <ko...@citrix.com>.
There is already a vm-sync mechanism to synchronise states between hypervisor and CS DB. When VMs get moved from one host to another outside of CS, vm-sync is supposed to update the DB with the new host id.
On 03-Apr-2015, at 7:13 AM, Yitao Jiang <wi...@gmail.com> wrote:
> Synchronisation work need to be done. I will do some hacking when i am free.
> On Apr 2, 2015 10:27 PM, "Steve Searles" <ss...@zimcom.net> wrote:
>
>> That was it. Thanks!. What is the best practice for DRS and HA with
>> vmware for use with Cloudstack? Disabled?
>>
>> Steven Searles
>>
>>
>>
>> On Apr 2, 2015, at 2:17 AM, Sanjeev N <sanjeev@apache.org<mailto:
>> sanjeev@apache.org>> wrote:
>>
>> Also make sure that vm is actually running on the host
>>
>> On Thu, Apr 2, 2015 at 6:11 AM, Yitao Jiang <willierjyt@gmail.com<mailto:
>> willierjyt@gmail.com>> wrote:
>>
>> I met the same issue before. Cause under vmware cluster ha enabled, so the
>> vm mirgrated among hosts. You can check the host which vm lives in cloud
>> databases, and compare to the actual host, if mismatchrd, changing the db
>> table, thrn all works fine.
>> On Apr 1, 2015 9:52 PM, "Steve Searles" <ssearles@zimcom.net<mailto:
>> ssearles@zimcom.net>> wrote:
>>
>> I am having trouble attaching a volume to an existing VM. Adding an
>> extra
>> volume during the instance creation works fine. It does not seem to
>> matter
>> what state the VM is in eg. stopped or running I receive the same error.
>> Anyone know what this means? I can not find any further information on
>> "Message: Unable to find the VM to execute AttachVolumeCommand”, ‘
>>
>>
>> Cloudstack 4.4.2
>> Vmware 5.5
>>
>>
>>
>> Any help would be appreciated.
>>
>>
>> INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
>> job-484/job-485) Add job-485 into job monitoring
>> INFO [c.c.s.VolumeApiServiceImpl] (Work-Job-Executor-1:ctx-4e1f0aca
>> job-484/job-485 ctx-3e014d23) Trying to attaching volume 175 to vm
>> instance:154, update async job-485 progress status
>> ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
>> job-484/job-485 ctx-3e014d23) Invocation exception, caused by:
>> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
>> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
>> Exception: java.lang.Exception
>> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
>> i-2-154-VM
>>
>> INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
>> job-484/job-485 ctx-3e014d23) Rethrow exception
>> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
>> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
>> Exception: java.lang.Exception
>> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
>> i-2-154-VM
>>
>> ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-1:ctx-4e1f0aca
>> job-484/job-485) Unable to complete AsyncJobVO {id:485, userId: 2,
>> accountId: 2, instanceType: null, instanceId: null, cmd:
>> com.cloud.storage.VmWorkAttachVolume, cmdInfo:
>>
>>
>> rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAJp0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAK8,
>> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
>> result: null, initMsid: 345049815164, completeMsid: null, lastUpdated:
>> null, lastPolled: null, created: Wed Apr 01 09:47:24 EDT 2015}, job
>> origin:484
>> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
>> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
>> Exception: java.lang.Exception
>> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
>> i-2-154-VM
>>
>> at
>>
>>
>> com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2110)
>> at
>>
>>
>> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1247)
>> at
>>
>>
>> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1091)
>> at
>>
>>
>> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2476)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>>
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>>
>>
>> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
>> at
>>
>>
>> com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2511)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>>
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>>
>>
>> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
>> at
>>
>>
>> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
>> at
>>
>>
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
>> at
>>
>>
>> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
>> at
>>
>>
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
>> at
>>
>>
>> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
>> at com.sun.proxy.$Proxy183.handleVmWorkJob(Unknown Source)
>> at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
>> at
>>
>>
>> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
>> 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
>>
>>
>> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> 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)
>> INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
>> job-484/job-485) Remove job-485 from job monitoring
>>
>>
>> -Steven Searles
>>
>>
>>
>>
>>
Re: Trouble Attaching Volume
Posted by Yitao Jiang <wi...@gmail.com>.
Synchronisation work need to be done. I will do some hacking when i am free.
On Apr 2, 2015 10:27 PM, "Steve Searles" <ss...@zimcom.net> wrote:
> That was it. Thanks!. What is the best practice for DRS and HA with
> vmware for use with Cloudstack? Disabled?
>
> Steven Searles
>
>
>
> On Apr 2, 2015, at 2:17 AM, Sanjeev N <sanjeev@apache.org<mailto:
> sanjeev@apache.org>> wrote:
>
> Also make sure that vm is actually running on the host
>
> On Thu, Apr 2, 2015 at 6:11 AM, Yitao Jiang <willierjyt@gmail.com<mailto:
> willierjyt@gmail.com>> wrote:
>
> I met the same issue before. Cause under vmware cluster ha enabled, so the
> vm mirgrated among hosts. You can check the host which vm lives in cloud
> databases, and compare to the actual host, if mismatchrd, changing the db
> table, thrn all works fine.
> On Apr 1, 2015 9:52 PM, "Steve Searles" <ssearles@zimcom.net<mailto:
> ssearles@zimcom.net>> wrote:
>
> I am having trouble attaching a volume to an existing VM. Adding an
> extra
> volume during the instance creation works fine. It does not seem to
> matter
> what state the VM is in eg. stopped or running I receive the same error.
> Anyone know what this means? I can not find any further information on
> "Message: Unable to find the VM to execute AttachVolumeCommand”, ‘
>
>
> Cloudstack 4.4.2
> Vmware 5.5
>
>
>
> Any help would be appreciated.
>
>
> INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485) Add job-485 into job monitoring
> INFO [c.c.s.VolumeApiServiceImpl] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485 ctx-3e014d23) Trying to attaching volume 175 to vm
> instance:154, update async job-485 progress status
> ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485 ctx-3e014d23) Invocation exception, caused by:
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> Exception: java.lang.Exception
> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> i-2-154-VM
>
> INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485 ctx-3e014d23) Rethrow exception
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> Exception: java.lang.Exception
> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> i-2-154-VM
>
> ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485) Unable to complete AsyncJobVO {id:485, userId: 2,
> accountId: 2, instanceType: null, instanceId: null, cmd:
> com.cloud.storage.VmWorkAttachVolume, cmdInfo:
>
>
> rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAJp0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAK8,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 345049815164, completeMsid: null, lastUpdated:
> null, lastPolled: null, created: Wed Apr 01 09:47:24 EDT 2015}, job
> origin:484
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> Exception: java.lang.Exception
> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> i-2-154-VM
>
> at
>
>
> com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2110)
> at
>
>
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1247)
> at
>
>
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1091)
> at
>
>
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2476)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
>
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
>
>
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
>
>
> com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2511)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
>
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
>
>
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
>
>
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
>
>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
>
>
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
>
>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
>
>
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy183.handleVmWorkJob(Unknown Source)
> at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> at
>
>
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
> 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
>
>
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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)
> INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485) Remove job-485 from job monitoring
>
>
> -Steven Searles
>
>
>
>
>
Re: Trouble Attaching Volume
Posted by Steve Searles <ss...@zimcom.net>.
That was it. Thanks!. What is the best practice for DRS and HA with vmware for use with Cloudstack? Disabled?
Steven Searles
On Apr 2, 2015, at 2:17 AM, Sanjeev N <sa...@apache.org>> wrote:
Also make sure that vm is actually running on the host
On Thu, Apr 2, 2015 at 6:11 AM, Yitao Jiang <wi...@gmail.com>> wrote:
I met the same issue before. Cause under vmware cluster ha enabled, so the
vm mirgrated among hosts. You can check the host which vm lives in cloud
databases, and compare to the actual host, if mismatchrd, changing the db
table, thrn all works fine.
On Apr 1, 2015 9:52 PM, "Steve Searles" <ss...@zimcom.net>> wrote:
I am having trouble attaching a volume to an existing VM. Adding an
extra
volume during the instance creation works fine. It does not seem to
matter
what state the VM is in eg. stopped or running I receive the same error.
Anyone know what this means? I can not find any further information on
"Message: Unable to find the VM to execute AttachVolumeCommand”, ‘
Cloudstack 4.4.2
Vmware 5.5
Any help would be appreciated.
INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
job-484/job-485) Add job-485 into job monitoring
INFO [c.c.s.VolumeApiServiceImpl] (Work-Job-Executor-1:ctx-4e1f0aca
job-484/job-485 ctx-3e014d23) Trying to attaching volume 175 to vm
instance:154, update async job-485 progress status
ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
job-484/job-485 ctx-3e014d23) Invocation exception, caused by:
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
Exception: java.lang.Exception
Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
i-2-154-VM
INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
job-484/job-485 ctx-3e014d23) Rethrow exception
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
Exception: java.lang.Exception
Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
i-2-154-VM
ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-1:ctx-4e1f0aca
job-484/job-485) Unable to complete AsyncJobVO {id:485, userId: 2,
accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.storage.VmWorkAttachVolume, cmdInfo:
rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAJp0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAK8,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
result: null, initMsid: 345049815164, completeMsid: null, lastUpdated:
null, lastPolled: null, created: Wed Apr 01 09:47:24 EDT 2015}, job
origin:484
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
Exception: java.lang.Exception
Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
i-2-154-VM
at
com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2110)
at
com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1247)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1091)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2476)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2511)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy183.handleVmWorkJob(Unknown Source)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
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
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
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)
INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
job-484/job-485) Remove job-485 from job monitoring
-Steven Searles
Re: Trouble Attaching Volume
Posted by Sanjeev N <sa...@apache.org>.
Also make sure that vm is actually running on the host
On Thu, Apr 2, 2015 at 6:11 AM, Yitao Jiang <wi...@gmail.com> wrote:
> I met the same issue before. Cause under vmware cluster ha enabled, so the
> vm mirgrated among hosts. You can check the host which vm lives in cloud
> databases, and compare to the actual host, if mismatchrd, changing the db
> table, thrn all works fine.
> On Apr 1, 2015 9:52 PM, "Steve Searles" <ss...@zimcom.net> wrote:
>
> > I am having trouble attaching a volume to an existing VM. Adding an
> extra
> > volume during the instance creation works fine. It does not seem to
> matter
> > what state the VM is in eg. stopped or running I receive the same error.
> > Anyone know what this means? I can not find any further information on
> > "Message: Unable to find the VM to execute AttachVolumeCommand”, ‘
> >
> >
> > Cloudstack 4.4.2
> > Vmware 5.5
> >
> >
> >
> > Any help would be appreciated.
> >
> >
> > INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
> > job-484/job-485) Add job-485 into job monitoring
> > INFO [c.c.s.VolumeApiServiceImpl] (Work-Job-Executor-1:ctx-4e1f0aca
> > job-484/job-485 ctx-3e014d23) Trying to attaching volume 175 to vm
> > instance:154, update async job-485 progress status
> > ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
> > job-484/job-485 ctx-3e014d23) Invocation exception, caused by:
> > com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> > test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> > Exception: java.lang.Exception
> > Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> > i-2-154-VM
> >
> > INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
> > job-484/job-485 ctx-3e014d23) Rethrow exception
> > com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> > test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> > Exception: java.lang.Exception
> > Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> > i-2-154-VM
> >
> > ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-1:ctx-4e1f0aca
> > job-484/job-485) Unable to complete AsyncJobVO {id:485, userId: 2,
> > accountId: 2, instanceType: null, instanceId: null, cmd:
> > com.cloud.storage.VmWorkAttachVolume, cmdInfo:
> >
> rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAJp0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAK8,
> > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> > result: null, initMsid: 345049815164, completeMsid: null, lastUpdated:
> > null, lastPolled: null, created: Wed Apr 01 09:47:24 EDT 2015}, job
> > origin:484
> > com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> > test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> > Exception: java.lang.Exception
> > Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> > i-2-154-VM
> >
> > at
> >
> com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2110)
> > at
> >
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1247)
> > at
> >
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1091)
> > at
> >
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2476)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:606)
> > at
> >
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> > at
> >
> com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2511)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:606)
> > at
> >
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> > at
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> > at
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> > at
> >
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> > at
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> > at
> >
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> > at com.sun.proxy.$Proxy183.handleVmWorkJob(Unknown Source)
> > at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> > at
> >
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
> > 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
> >
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
> > at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> > 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)
> > INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
> > job-484/job-485) Remove job-485 from job monitoring
> >
> >
> > -Steven Searles
> >
> >
>
Re: Trouble Attaching Volume
Posted by Yitao Jiang <wi...@gmail.com>.
I met the same issue before. Cause under vmware cluster ha enabled, so the
vm mirgrated among hosts. You can check the host which vm lives in cloud
databases, and compare to the actual host, if mismatchrd, changing the db
table, thrn all works fine.
On Apr 1, 2015 9:52 PM, "Steve Searles" <ss...@zimcom.net> wrote:
> I am having trouble attaching a volume to an existing VM. Adding an extra
> volume during the instance creation works fine. It does not seem to matter
> what state the VM is in eg. stopped or running I receive the same error.
> Anyone know what this means? I can not find any further information on
> "Message: Unable to find the VM to execute AttachVolumeCommand”, ‘
>
>
> Cloudstack 4.4.2
> Vmware 5.5
>
>
>
> Any help would be appreciated.
>
>
> INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485) Add job-485 into job monitoring
> INFO [c.c.s.VolumeApiServiceImpl] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485 ctx-3e014d23) Trying to attaching volume 175 to vm
> instance:154, update async job-485 progress status
> ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485 ctx-3e014d23) Invocation exception, caused by:
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> Exception: java.lang.Exception
> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> i-2-154-VM
>
> INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485 ctx-3e014d23) Rethrow exception
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> Exception: java.lang.Exception
> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> i-2-154-VM
>
> ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485) Unable to complete AsyncJobVO {id:485, userId: 2,
> accountId: 2, instanceType: null, instanceId: null, cmd:
> com.cloud.storage.VmWorkAttachVolume, cmdInfo:
> rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAJp0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAAAAAAAAK8,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 345049815164, completeMsid: null, lastUpdated:
> null, lastPolled: null, created: Wed Apr 01 09:47:24 EDT 2015}, job
> origin:484
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
> test-cvg to VM RESIZE-TEST-2012; AttachVolumeCommand failed due to
> Exception: java.lang.Exception
> Message: Unable to find the VM to execute AttachVolumeCommand, vmName:
> i-2-154-VM
>
> at
> com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2110)
> at
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1247)
> at
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1091)
> at
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2476)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
> com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2511)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy183.handleVmWorkJob(Unknown Source)
> at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
> 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
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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)
> INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-1:ctx-4e1f0aca
> job-484/job-485) Remove job-485 from job monitoring
>
>
> -Steven Searles
>
>