Using a long running CloudStack 3.0.3 deployment, I came up against a
StorageUnavailableException error when starting a VM that had been created in
the stopped state.
Any suggestions on how to narrow down the problem further?
Snippet from management server logs:
2012-07-17 12:04:19,107 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-81:job-2384) Checking if we need to prepare 2 volumes for
VM[User|1920fcd5-1633-4af8-9153-d48a5da94e1b]
2012-07-17 12:04:19,107 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-81:job-2384) Volume Vol[629|vm=192|DATADISK] is not recreatable!
Cannot recreate on storagepool: Pool[202|NetworkFilesystem]
2012-07-17 12:04:19,108 INFO [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-81:job-2384) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [Volume:629] is
unreachable: Volume is not recreatable, Unable to create
Vol[629|vm=192|DATADISK]
at
com.cloud.storage.StorageManagerImpl.prepare(StorageManagerImpl.java:3202)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:462)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2809)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1785)
at
com.cloud.event.ActionEventCallback.intercept(ActionEventCallback.java:32)
at com.cloud.api.commands.StartVMCmd.execute(StartVMCmd.java:119)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:134)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:427)
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)
