[
https://issues.apache.org/jira/browse/CLOUDSTACK-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720482#comment-13720482
]
manasaveloori commented on CLOUDSTACK-3628:
-------------------------------------------
After the data volume migration from shared to local storage is failed,I tried
to attach that data volume to a VM.
Observed the following exception
pi.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }
2013-07-26 18:06:58,969 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-10:null) SeqA 2-665: Sending Seq 2-665: { Ans: , MgmtId:
6805241462820, via: 2, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
2013-07-26 18:06:59,120 ERROR [storage.resource.VmwareStorageProcessor]
(DirectAgent-185:10.147.40.29) AttachVolumeCommand failed due to Exception:
java.lang.RuntimeException
Message: File
[]/vmfs/volumes/e7681efe-8090fb9d/99c66d6c067046acb264109cb8923872.vmdk was not
found
java.lang.RuntimeException: File
[]/vmfs/volumes/e7681efe-8090fb9d/99c66d6c067046acb264109cb8923872.vmdk was not
found
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.attachDisk(VirtualMachineMO.java:1006)
at
com.cloud.storage.resource.VmwareStorageProcessor.attachVolume(VmwareStorageProcessor.java:1172)
at
com.cloud.storage.resource.VmwareStorageProcessor.attachVolume(VmwareStorageProcessor.java:1125)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:129)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:55)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:566)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
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:679)
2013-07-26 18:06:59,122 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2092040602: Response Received:
2013-07-26 18:06:59,123 DEBUG [agent.transport.Request] (DirectAgent-185:null)
Seq 1-2092040602: Processing: { Ans: , MgmtId: 6805241462820, via: 1, Ver: v1,
Flags: 10,
[{"org.apache.cloudstack.storage.command.AttachAnswer":{"result":false,"details":"AttachVolumeCommand
failed due to Exception: java.lang.RuntimeException\nMessage: File
[]/vmfs/volumes/e7681efe-8090fb9d/99c66d6c067046acb264109cb8923872.vmdk was not
found\n","wait":0}}] }
2013-07-26 18:06:59,123 DEBUG [agent.transport.Request] (Job-Executor-57:job-57
= [ 03b298b5-a8ca-452f-8d89-d12b17e5a5c0 ]) Seq 1-2092040602: Received: { Ans:
, MgmtId: 6805241462820, via: 1, Ver: v1, Flags: 10, { AttachAnswer } }
2013-07-26 18:06:59,136 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-57:job-57 = [ 03b298b5-a8ca-452f-8d89-d12b17e5a5c0 ]) Unexpected
exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume:
shared to VM: sharedVMw; AttachVolumeCommand failed due to Exception:
java.lang.RuntimeException
Message: File
[]/vmfs/volumes/e7681efe-8090fb9d/99c66d6c067046acb264109cb8923872.vmdk was not
found
at
com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1701)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1908)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
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:679)
2013-07-26 18:06:59,140 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-57:job-57 = [ 03b298b5-a8ca-452f-8d89-d12b17e5a5c0 ]) Complete
async job-57 = [ 03b298b5-a8ca-452f-8d89-d12b17e5a5c0 ], jobStatus: 2,
resultCode: 530, result: Error Code: 530 Error text: Failed to attach volume:
shared to VM: sharedVMw; AttachVolumeCommand failed due to Exception:
java.lang.RuntimeException
Message: File
[]/vmfs/volumes/e7681efe-8090fb9d/99c66d6c067046acb264109cb8923872.vmdk was not
found
2013-07-26 18:06:59,945 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null)
===START=== 10.252.192.69 -- GET
command=queryAsyncJobResult&jobId=b443da8d-f463-400b-be6c-3904a32143d8&response=json&sessionkey=GEujwYnERF5hO10HFUmjOyCbyP0%3D&_=1374822766165
2013-07-26 18:06:59,980 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null)
===END=== 10.252.192.69 -- GET
command=queryAsyncJobResult&jobId=b443da8d-f463-400b-be6c-3904a32143d8&response=json&sessionkey=GEujwYnERF5hO10HFUmjOyCbyP0%3D&_=1374822766165
2013-07-26 18:07:00,559 DEBUG [cloud.server.StatsCollector]
(StatsCollector-2:null) StorageCollector is running..
> [Storage]Migration of data disk from Shared primary to shared/local primary
> storage is throwing NPE.
> ----------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3628
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3628
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.2.0
> Environment: 4.2 build
> Reporter: manasaveloori
> Assignee: Koushik Das
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log, management-server.zip
>
>
> Steps:
> 1. Have a CS with advanced zone and VMware hypervisor.
> 2. Create 2 shared cluster wide primary storage and a local storage.
> 3. Create a data volume using shared storage.
> 4. Try to migrate the volume to another primary or local storage.
> Observed NPE:
> 013-07-18 18:45:00,999 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
> ===START=== 10.252.192.69 -- GET
> command=migrateVolume&storageid=0f38bade-9d99-4391-a9f4-d63f948d908e&volumeid=a9266985-b526-4f81-9692-1b4180d09659&response=json&sessionkey=%2BaQLExaoaIr64YjXYR008EoMPkw%3D&_=1374133787585
> 2013-07-18 18:45:01,057 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-1:null) submit async job-107 = [
> 7f2a997f-f241-465c-a641-3930020b4ce8 ], details: AsyncJobVO {id:107, userId:
> 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","sessionkey":"+aQLExaoaIr64YjXYR008EoMPkw\u003d","cmdEventType":"VOLUME.MIGRATE","ctxUserId":"2","storageid":"0f38bade-9d99-4391-a9f4-d63f948d908e","httpmethod":"GET","volumeid":"a9266985-b526-4f81-9692-1b4180d09659","_":"1374133787585","ctxAccountId":"2","ctxStartEventId":"327"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7562229448750,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-18 18:45:01,061 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
> ===END=== 10.252.192.69 -- GET
> command=migrateVolume&storageid=0f38bade-9d99-4391-a9f4-d63f948d908e&volumeid=a9266985-b526-4f81-9692-1b4180d09659&response=json&sessionkey=%2BaQLExaoaIr64YjXYR008EoMPkw%3D&_=1374133787585
> 2013-07-18 18:45:01,065 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-34:job-107 = [ 7f2a997f-f241-465c-a641-3930020b4ce8 ])
> Executing org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for
> job-107 = [ 7f2a997f-f241-465c-a641-3930020b4ce8 ]
> 2013-07-18 18:45:01,097 DEBUG [storage.volume.VolumeServiceImpl]
> (Job-Executor-34:job-107 = [ 7f2a997f-f241-465c-a641-3930020b4ce8 ]) Failed
> to copy volumejava.lang.NullPointerException
> 2013-07-18 18:45:01,097 ERROR [cloud.storage.VolumeManagerImpl]
> (Job-Executor-34:job-107 = [ 7f2a997f-f241-465c-a641-3930020b4ce8 ]) migrate
> volume failed:java.lang.NullPointerException
> 2013-07-18 18:45:01,100 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-34:job-107 = [ 7f2a997f-f241-465c-a641-3930020b4ce8 ]) Complete
> async job-107 = [ 7f2a997f-f241-465c-a641-3930020b4ce8 ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Failed to migrate volume
> 2013-07-18 18:45:01,449 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-11:null) SeqA 2-4: Processing Seq 2-4: { Cmd , MgmtId:
> -1, via: 2, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2013-07-18 18:45:01,457 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-11:null) SeqA 2-4: Sending Seq 2-4: { Ans: , MgmtId:
> 7562229448750, via: 2, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2013-07-18 18:45:03,248 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-3:null) StorageCollector is running...
> 2013-07-18 18:45:03,936 DEBUG [agent.transport.Request]
> (StatsCollector-3:null) Seq 3-357564436: Received: { Ans: , MgmtId: 75622294
> Attached the MS logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
