You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2013/06/14 10:26:20 UTC
[jira] [Created] (CLOUDSTACK-3005) Upgrade from 2.2.14 to 4.1.0
failed with "Storage volume not found: no storage vol with matching name"
Wei Zhou created CLOUDSTACK-3005:
------------------------------------
Summary: Upgrade from 2.2.14 to 4.1.0 failed with "Storage volume not found: no storage vol with matching name"
Key: CLOUDSTACK-3005
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3005
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.1.0
Reporter: Wei Zhou
Assignee: Wei Zhou
Priority: Blocker
Fix For: 4.1.1, 4.2.0
After upgrade from 2.2.14 to 4.1.0, the systemvm are running, and I can also add seconday storage.
An exception raises when I create a new virtual machine.
2013-06-14 09:38:34,373 DEBUG [agent.transport.Request] (Job-Executor-1:job-20) Seq 2-1571029023: Sending { Cmd , MgmtId: 90520747364525, via: 2, Ver: v1, Flags: 100111, [{"storage.CreateCommand":{"volId":28,"pool":{"id":200,"uuid":"72301816-c94a-3ad4-a1fd-7a1749c56171","host":"192.168.103.1","path":"/storage/da-upgr-01-primary","port":2049,"type":"NetworkFilesystem"},"diskCharacteristics":{"size":42949672960,"tags":[],"type":"ROOT","name":"ROOT-26","useLocalStorage":false,"recreatable":true,"diskOfferingId":1,"volumeId":28,"hyperType":"KVM"},"templateUrl":"/mnt/72301816-c94a-3ad4-a1fd-7a1749c56171/ea12c801-9fe6-491c-81d7-9d60d409d4c8","wait":0}}] }
2013-06-14 09:38:34,434 DEBUG [agent.transport.Request] (AgentManager-Handler-2:null) Seq 2-1571029023: Processing: { Ans: , MgmtId: 90520747364525, via: 2, Ver: v1, Flags: 110, [{"storage.CreateAnswer":{"requestTemplateReload":false,"result":false,"details":"Exception: com.cloud.utils.exception.CloudRuntimeException\nMessage: org.libvirt.LibvirtException: Storage volume not found: no storage vol with matching name '/mnt/72301816-c94a-3ad4-a1fd-7a1749c56171/ea12c801-9fe6-491c-81d7-9d60d409d4c8'\nStack: com.cloud.utils.exception.CloudRuntimeException: org.libvirt.LibvirtException: Storage volume not found: no storage vol with matching name '/mnt/72301816-c94a-3ad4-a1fd-7a1749c56171/ea12c801-9fe6-491c-81d7-9d60d409d4c8'\n\tat com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getVolume(LibvirtStorageAdaptor.java:90)\n\tat com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getPhysicalDisk(LibvirtStorageAdaptor.java:437)\n\tat com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.getPhysicalDisk(LibvirtStoragePool.java:123)\n\tat com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:1279)\n\tat com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1072)\n\tat com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat com.cloud.utils.nio.Task.run(Task.java:83)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat java.lang.Thread.run(Thread.java:679)\n","wait":0}}] }
2013-06-14 09:38:34,434 DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-2:null) Seq 2-1571029023: No more commands found
2013-06-14 09:38:34,434 DEBUG [agent.transport.Request] (Job-Executor-1:job-20) Seq 2-1571029023: Received: { Ans: , MgmtId: 90520747364525, via: 2, Ver: v1, Flags: 110, { CreateAnswer } }
2013-06-14 09:38:34,435 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-1:job-20) Unable to create volume Vol[28|vm=26|ROOT]
2013-06-14 09:38:34,452 INFO [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-1:job-20) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200] is unreachable: Unable to create Vol[28|vm=26|ROOT]
at com.cloud.storage.StorageManagerImpl.prepare(StorageManagerImpl.java:3488)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:748)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:471)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:212)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3817)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3410)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3396)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:379)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
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:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-06-14 09:38:34,468 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-1:job-20) Cleaning up resources for the vm VM[User|wei001-002] in Starting state
This is because the templateUrl is not correct in database.
"templateUrl ":"/mnt/72301816-c94a-3ad4-a1fd-7a1749c56171/ea12c801-9fe6-491c-81d7-9d60d409d4c8"
should be
"templateUrl ":"ea12c801-9fe6-491c-81d7-9d60d409d4c8"
--
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