prashant kumar mishra created CLOUDSTACK-3228:
-------------------------------------------------
Summary: system vms are not comming up in zone with two cluster
xen and kvm;Zone host is ready, but secondary storage vm template: 3 is not
ready on secondary storage: 2
Key: CLOUDSTACK-3228
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3228
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: branch -master stable ;hypervisor - XS-6.1,KVM-rhel6.3
Reporter: prashant kumar mishra
Fix For: 4.2.0
Even xen sysetm vm templates are available MS is not able to deploy system vms
because it is checking for kvm system vm templates which is not downloaded.
Steps to reproduce
-----------------------------
1-Have a xenserver zone with one host and running system vms
2-create one guest vm
3-add one more KVM cluster with one host + primary storage
4-ssvm will try to download kvm system vm template (in my setup it failed with
message no route to host)
5-deploy one guest vm in kvm cluster
6-destroy system vms
Expected
--------------
since default kvm system vm template download failed. ssvms should come up in
xen cluster
Actual
---------
MS is always checking for kvm system vm template which is not downloaded .
Log
------
2013-06-27 08:10:34,381 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone host is ready, but secondary storage vm template: 3 is
not ready on secondary storage: 2
2013-06-27 08:10:34,381 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone 1 is not ready to launch secondary storage VM yet
2013-06-27 08:10:35,055 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone host is ready, but console proxy template: 3 is not
ready on secondary storage: 2
2013-06-27 08:10:35,055 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is not ready to launch console proxy yet
--
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
