You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sailaja Mada (JIRA)" <ji...@apache.org> on 2013/07/09 13:11:48 UTC
[jira] [Updated] (CLOUDSTACK-3418) Failed to update snapshot state
with NPE while creating the snpashot when Primary Storage is in Prepare
Maintanance state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sailaja Mada updated CLOUDSTACK-3418:
-------------------------------------
Attachment: management-server.log
apilog.log
> Failed to update snapshot state with NPE while creating the snpashot when Primary Storage is in Prepare Maintanance state
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3418
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3418
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Sailaja Mada
> Attachments: apilog.log, management-server.log
>
>
> Setup: VMWARE with Cluster Primary storage and Zone primary storage
> Steps:
> 1. Configure VMWARE Adv Zone with cluster level primary storage and Zone level primary storage
> 2. Move the Cluster level primary storage to Maintenance state . When its in Prepare Maintenance state, tried to create snapshot for the ROOT volume.
> Observation:
> Failed to update snapshot state with NPE while creating the snpashot when Primary Storage is in Prepare Maintenance state
> 2013-07-09 16:24:55,983 WARN [storage.snapshot.SnapshotManagerImpl] (Job-Executor-29:job-49) Storage unavailable
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1] is unreachable: Unable to send command to the pool 1 due to there is no enabled hosts up in this cluster
> at com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:1071)
> at com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:1096)
> at com.cloud.storage.snapshot.SnapshotManagerImpl.sendToPool(SnapshotManagerImpl.java:219)
> at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copySnapshot(AncientDataMotionStrategy.java:785)
> at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:497)
> at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:59)
> at org.apache.cloudstack.storage.snapshot.strategy.AncientSnapshotStrategy.backupSnapshot(AncientSnapshotStrategy.java:425)
> at com.cloud.storage.snapshot.SnapshotManagerImpl.backupSnapshot(SnapshotManagerImpl.java:360)
> at com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:302)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.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-07-09 16:24:55,987 DEBUG [snapshot.strategy.AncientSnapshotStrategy] (Job-Executor-29:job-49) Failed to update snapshot state
> java.lang.NullPointerException
> at org.apache.cloudstack.storage.snapshot.strategy.AncientSnapshotStrategy.copySnapshotAsyncCallback(AncientSnapshotStrategy.java:468)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:125)
> at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:26)
> at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:103)
> at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:505)
> at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:59)
> at org.apache.cloudstack.storage.snapshot.strategy.AncientSnapshotStrategy.backupSnapshot(AncientSnapshotStrategy.java:425)
> at com.cloud.storage.snapshot.SnapshotManagerImpl.backupSnapshot(SnapshotManagerImpl.java:360)
> at com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:302)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.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-07-09 16:24:56,014 INFO [user.snapshot.CreateSnapshotCmd] (Job-Executor-29:job-49) VOLSS: backupSnapshotCmd finishes:1373367296014
--
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