manasaveloori created CLOUDSTACK-3628:
-----------------------------------------
Summary: [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
Priority: Critical
Fix For: 4.2.0
Attachments: 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
