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/07/03 08:56:20 UTC

[jira] [Closed] (CLOUDSTACK-2598) [Automation] NPE: not able to create volume from snapshot

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Srikanteswararao Talluri closed CLOUDSTACK-2598.
------------------------------------------------

    Resolution: Fixed

Not hitting this issue anymore
                
>  [Automation] NPE: not able to create volume from snapshot
> ----------------------------------------------------------
>
>                 Key: CLOUDSTACK-2598
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2598
>             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
>             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=queryAsyncJobResult&jobId=c7be4361-1b65-41e3-8b49-feefa88cc16c&response=json&sessionkey=d0EygWD080kDM0o4S4kPsTY6vHw%3D&_=1367490347930
> 2013-05-02 21:21:55,074 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) ===END=== 10.252.241.40 -- GET command=queryAsyncJobResult&jobId=c7be4361-1b65-41e3-8b49-feefa88cc16c&response=json&sessionkey=d0EygWD080kDM0o4S4kPsTY6vHw%3D&_=1367490347930
> 2013-05-02 21:21:55,439 DEBUG [storage.snapshot.SnapshotManagerImpl] (Job-Executor-94:job-125) Retrying...
> 2013-05-02 21:21:55,442 WARN [storage.snapshot.SnapshotManagerImpl] (Job-Executor-94:job-125) Storage unavailable
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:4] is unreachable: Unable to send command to the pool 4 due to there is no enabled hosts up in this cluster
>         at com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:1056)
>         at com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:1081)
>         at com.cloud.storage.snapshot.SnapshotManagerImpl.sendToPool(SnapshotManagerImpl.java:218)
>         at org.apache.cloudstack.storage.datastore.driver.CloudStackPrimaryDataStoreDriverImpl.takeSnapshot(CloudStackPrimaryDataStoreDriverImpl.java:304)
>         at org.apache.cloudstack.storage.snapshot.strategy.AncientSnapshotStrategy.createSnapshotOnPrimary(AncientSnapshotStrategy.java:302)
>         at org.apache.cloudstack.storage.snapshot.strategy.AncientSnapshotStrategy.takeSnapshot(AncientSnapshotStrategy.java:395)
>         at com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:287)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:167)
>         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:55,564 DEBUG [agent.transport.Request] (Job-Executor-94:job-125) Seq 1-1888748249: Sending { Cmd , MgmtId: 7566222426160, via: 1, Ver: v1, Flags: 100011, [{"BackupSnapshotCommand":{"isVolumeInactive":false,"vmName"
> I am not able to reproduce this one

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