You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Srikanteswararao Talluri (JIRA)" <ji...@apache.org> on 2013/05/02 12:40:15 UTC
[jira] [Created] (CLOUDSTACK-2305) NPE: not able to create volume
from snapshot
Srikanteswararao Talluri created CLOUDSTACK-2305:
----------------------------------------------------
Summary: NPE: not able to create volume from snapshot
Key: CLOUDSTACK-2305
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2305
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Volumes
Affects Versions: 4.2.0
Environment: KVM deployment with zone wide primary storage
Reporter: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.2.0
1. Create a volume on zone wide primary storage
2. attach it to a VM
3. Create snapshot of that volume
4. create a volume from the above snapshot
===START=== 10.252.241.40 -- GET command=createVolume&response=json&sessionkey=d0EygWD080kDM0o4S4kPsTY6vHw%3D&snapshotid=27f88a61-3501-4e52-b8f1-89072dd31f50&name=fromzatc&_=1367490347398
2013-05-02 21:21:54,576 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-18:null) submit async job-129, details: AsyncJobVO {id:129, userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId: 40, cmd: org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd, cmdOriginator: null, cmdInfo: {"id":"40","response":"json","sessionkey":"d0EygWD080kDM0o4S4kPsTY6vHw\u003d","ctxUserId":"2","snapshotid":"27f88a61-3501-4e52-b8f1-89072dd31f50","name":"fromzatc","_":"1367490347398","ctxAccountId":"2","ctxStartEventId":"421"}, cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160, completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-02 21:21:54,580 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) ===END=== 10.252.241.40 -- GET command=createVolume&response=json&sessionkey=d0EygWD080kDM0o4S4kPsTY6vHw%3D&snapshotid=27f88a61-3501-4e52-b8f1-89072dd31f50&name=fromzatc&_=1367490347398
2013-05-02 21:21:54,583 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-98:job-129) Executing org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd for job-129
2013-05-02 21:21:54,637 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-98:job-129) Storage pool garbage collector found 0 templates to clean up in storage pool: primary
2013-05-02 21:21:54,643 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-98:job-129) Storage pool garbage collector found 0 templates to clean up in storage pool: clus
2013-05-02 21:21:54,649 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-98:job-129) Storage pool garbage collector found 0 templates to clean up in storage pool: Rack1Pod1Host24 Local Storage
2013-05-02 21:21:54,651 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-98:job-129) Storage pool garbage collector found 0 templates to clean up in storage pool: primary2
2013-05-02 21:21:54,653 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-98:job-129) Storage pool garbage collector found 0 templates to clean up in storage pool: clus2
2013-05-02 21:21:54,658 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-98:job-129) Secondary storage garbage collector found 0 templates to cleanup on secondary storage host: nfs://10.147.28.7/export/home/talluri/kvms
2013-05-02 21:21:54,669 WARN [cloud.storage.StorageManagerImpl] (Job-Executor-98:job-129) Failed to cleanup snapshots for volume 3 due to can not find secondary storage VM agent for data center 1
2013-05-02 21:21:54,674 WARN [cloud.storage.StorageManagerImpl] (Job-Executor-98:job-129) Failed to cleanup snapshots for volume 5 due to can not find secondary storage VM agent for data center 1
2013-05-02 21:21:54,680 WARN [cloud.storage.StorageManagerImpl] (Job-Executor-98:job-129) Failed to cleanup snapshots for volume 34 due to can not find secondary storage VM agent for data center 1
2013-05-02 21:21:54,697 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-98:job-129) Secondary storage garbage collector found 0 templates to cleanup on secondary storage host: nfs://10.147.28.7/export/home/talluri/kvms
2013-05-02 21:21:54,705 DEBUG [allocator.impl.UserConcentratedAllocator] (Job-Executor-98:job-129) There are no pods with enough memory/CPU capacity in zone zwps
2013-05-02 21:21:54,710 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-98:job-129) Failed to create volume: 40
java.lang.NullPointerException
at com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:537)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:597)
at com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:1014)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:180)
at org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd.execute(CreateVolumeCmd.java:168)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:164)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
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-05-02 21:21:54,746 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-98:job-129) Complete async job-129, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to create a volume
--
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