Nitin Mehta created CLOUDSTACK-3945:
---------------------------------------
Summary: CLONE - [single Zone with multiple clusters] SystemVM
Templates are not downloaded for the second cluster.
Key: CLOUDSTACK-3945
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3945
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
Environment: commit # ca474d0e09f772cb22abf2802a308a2da5351592
Reporter: Nitin Mehta
Assignee: Nitin Mehta
Priority: Critical
Fix For: 4.2.0
Steps to reproduce :
1. Have at least one advanced zone.
2. Create a XenServer Cluster with 1 host and add secondary, primary storages
Observations:
(i) system vm template from secondary to primary got copied successfully and
System VMs came up fine without any issues.
(ii) One additional observation made during this was : It deleted all the
system vm templates entries except the xenserver routing-1.
Snippet from mgmt server log is here:
2013-07-29 15:38:18,089 INFO [storage.image.TemplateServiceImpl]
(AgentConnectTaskPool-9:null) Template Sync found routing-1 already in the
image store
2013-07-29 15:38:18,169 INFO [storage.image.TemplateServiceImpl]
(AgentConnectTaskPool-9:null) Template Sync did not find routing-3 on image
store 8, may request download based on available hypervisor types
2013-07-29 15:38:18,170 INFO [storage.image.TemplateServiceImpl]
(AgentConnectTaskPool-9:null) Removing leftover template routing-3 entry from
template store table
2013-07-29 15:38:18,181 INFO [storage.image.TemplateServiceImpl]
(AgentConnectTaskPool-9:null) Template Sync did not find routing-8 on image
store 8, may request download based on available hypervisor types
2013-07-29 15:38:18,181 INFO [storage.image.TemplateServiceImpl]
(AgentConnectTaskPool-9:null) Removing leftover template routing-8 entry from
template store table
2013-07-29 15:38:18,188 INFO [storage.image.TemplateServiceImpl]
(AgentConnectTaskPool-9:null) Template Sync did not find routing-9 on image
store 8, may request download based on available hypervisor types
2013-07-29 15:38:18,188 INFO [storage.image.TemplateServiceImpl]
(AgentConnectTaskPool-9:null) Removing leftover template routing-9 entry from
template store table
2013-07-29 15:38:18,194 INFO [storage.image.TemplateServiceImpl]
(AgentConnectTaskPool-9:null) Template Sync did not find routing-10 on image
store 8, may request download based on available hypervisor types
(3) Add another cluster with KVM hypervisor with at least 1 host
Observation:
(iii) Didn't see any systemVM template download happening for kvm hypervisor.
(4) disable the XenServer cluster
(iv) When tried to deploy a VM using a manually uploaded centOS template then
it failed with the following error.
2013-07-29 16:55:20,556 ERROR [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-13:job-89 = [ 4ce02580-1239-400c-9638-3225599b949c ]) Failed to
start instance VM[User|testVM]
com.cloud.utils.exception.CloudRuntimeException: Template 3 has not been
completely downloaded to zone 2
at
com.cloud.template.TemplateManagerImpl.getTemplateSize(TemplateManagerImpl.java:1648)
at
com.cloud.storage.VolumeManagerImpl.allocateTemplatedVolume(VolumeManagerImpl.java:1451)
at
com.cloud.vm.VirtualMachineManagerImpl.allocate(VirtualMachineManagerImpl.java:389)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.vm.VirtualMachineManagerImpl.allocate(VirtualMachineManagerImpl.java:417)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.deployRouter(VirtualNetworkApplianceManagerImpl.java:1648)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInGuestNetwork(VirtualNetworkApplianceManagerImpl.java:1548)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.deployVirtualRouterInGuestNetwork(VirtualNetworkApplianceManagerImpl.java:1946)
at
com.cloud.network.element.VirtualRouterElement.implement(VirtualRouterElement.java:203)
at
com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:1984)
at
com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1889)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2070)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:911)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:618)
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3334)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2894)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2880)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
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)
Attaching all the required logs along with db dump to the bug.
--
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
