cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2288) NPE while creating volume from snapshot when the primary storage is in maintenance state
Date Mon, 01 Jul 2013 21:25:29 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697206#comment-13697206
] 

ASF subversion and git services commented on CLOUDSTACK-2288:
-------------------------------------------------------------

Commit ffd5f1a777ac9af5b65b1fcd357684d7dafcce87 in branch refs/heads/vmsync from [~sanjay.tripathi]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ffd5f1a ]

CLOUDSTACK-2288: NPE while creating volume from snapshot when the primary storage is in maintenance
state.

Signed-off-by: Prasanna Santhanam <tsp@apache.org>

                
> NPE while creating volume from snapshot when the primary storage is in maintenance state
> ----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2288
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2288
>             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
>            Reporter: Sailaja Mada
>            Assignee: Sanjay Tripathi
>             Fix For: 4.2.0
>
>
> Setup: Advanced Networking Zone, Xen 6.1 , MS - RHEL 6.3 
> Steps:
> 1. Deploy instance as ROOT admin
> 2. Create the snapshot for the ROOT volume of this instance 
> 3. Put the only available primary storage to maintenance
> 4. Try to create the volume from this snapshot. 
> Observation:
> NPE while creating volume from snapshot when the primary storage is in maintenance state
> 2013-04-30 12:05:56,653 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null) ===END===
 10.144.6.19 -- GET  command=createVolume&response=json&sessionkey=mTrNgYbkndiHLZNAV%2BoAAzDOQFw%3D&snapshotid=79b17cda-71f7-4be9-9e7c-bedcb73a7106&name=newsnapvol1&_=1367303886423
> 2013-04-30 12:05:56,658 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-1:job-73)
Executing org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd for job-73
> 2013-04-30 12:05:56,755 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-1:job-73)
Storage pool garbage collector found 0 templates to clean up in storage pool: PS1
> 2013-04-30 12:05:56,767 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-1:job-73)
Secondary storage garbage collector found 0 templates to cleanup on secondary storage host:
nfs://10.102.192.100/cpg_vol/sailaja/masterxenss
> 2013-04-30 12:05:56,819 WARN  [cloud.storage.StorageManagerImpl] (Job-Executor-1:job-73)
Failed to cleanup snapshots for volume 15 due to can not find secondary storage VM agent for
data center 1
> 2013-04-30 12:05:56,840 WARN  [cloud.storage.StorageManagerImpl] (Job-Executor-1:job-73)
Failed to cleanup snapshots for volume 18 due to can not find secondary storage VM agent for
data center 1
> 2013-04-30 12:05:56,874 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-1:job-73)
Secondary storage garbage collector found 0 templates to cleanup on secondary storage host:
nfs://10.102.192.100/cpg_vol/sailaja/masterxenss
> 2013-04-30 12:05:56,890 DEBUG [allocator.impl.UserConcentratedAllocator] (Job-Executor-1:job-73)
There are no pods with enough memory/CPU capacity in zone Advzone1
> 2013-04-30 12:05:56,946 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-1:job-73)
Failed to create volume: 28
> 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:155)
>         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-04-30 12:05:57,019 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-1:job-73)
Complete async job-73, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text:
Failed to create a volume
> 2013-04-30 12:05:59,699 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) ===START===
 10.144.6.19 -- GET  command=queryAsyncJobResult&jobId=bdd08ea3-cf7f-4369-9778-c32e6267ffe1&response=json&sessionkey=mTrNgYbkndiHLZNAV%2BoAAzDOQFw%3D&_=1367303889729
> 2013-04-30 12:05:59,729 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-12:null)
Async job-73 completed
> 2013-04-30 12:05:59,747 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) ===END===
 10.144.6.19 -- GET  command=queryAsyncJobResult&jobId=bdd08ea3-cf7f-4369-9778-c32e6267ffe1&response=json&sessionkey=mTrNgYbkndiHLZNAV%2BoAAzDOQFw%3D&_=1367303889729

--
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

Mime
View raw message