You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "prashant kumar mishra (JIRA)" <ji...@apache.org> on 2013/06/04 08:54:19 UTC

[jira] [Created] (CLOUDSTACK-2835) VR Deployement from admin registered tamplate is failing because registered template type is user.

prashant kumar mishra created CLOUDSTACK-2835:
-------------------------------------------------

             Summary: VR  Deployement from admin registered tamplate is failing because registered template type is user.
                 Key: CLOUDSTACK-2835
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2835
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.2.0
            Reporter: prashant kumar mishra
             Fix For: 4.2.0


Step to reproduce
--------------------------
--------------------------
1-Set Global parameter "router.template.xen" to   some string say "newtmpl" .
2-Register a system vm template with name "newtmpl"
3-Deploy a vm with new network

Expected
---------------
New router vm should come with newly registered template

Actual
------------
Router vm is not coming up with error "2013-06-04 07:39:20,431 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) XenServer won't support system vm, skip it"

Logs
--------
--------
2013-06-04 07:39:20,328 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) lock account 2 is acquired
2013-06-04 07:39:20,362 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing lock account 2
2013-06-04 07:39:20,368 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Asking VirtualRouter to implemenet Ntwk[204|Guest|8]
2013-06-04 07:39:20,373 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Lock is acquired for network id 204 as a part of router startup in Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(3|ROOT-->Pool(1))]
2013-06-04 07:39:20,396 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Adding nic for Virtual Router in Guest network Ntwk[204|Guest|8]
2013-06-04 07:39:20,397 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Adding nic for Virtual Router in Control network
2013-06-04 07:39:20,401 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Found existing network configuration for offering [Network Offering [3-Control-System-Control-Network]: Ntwk[202|Control|3]
2013-06-04 07:39:20,401 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing lock for Acct[1-system]
2013-06-04 07:39:20,402 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Adding nic for Virtual Router in Public network
2013-06-04 07:39:20,407 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Found existing network configuration for offering [Network Offering [1-Public-System-Public-Network]: Ntwk[200|Public|1]
2013-06-04 07:39:20,407 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing lock for Acct[1-system]
2013-06-04 07:39:20,418 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Creating the router 4 in datacenter com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$9e67d269@1
2013-06-04 07:39:20,418 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Allocating the domR with the hypervisor type XenServer
2013-06-04 07:39:20,431 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) XenServer won't support system vm, skip it
2013-06-04 07:39:20,433 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) Lock is released for network id 204 as a part of router startup in Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(3|ROOT-->Pool(1))]
2013-06-04 07:39:20,437 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Cleaning up because we're unable to implement the network Ntwk[204|Guest|8]
2013-06-04 07:39:20,465 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing 0 port forwarding rules for network id=204 as a part of shutdownNetworkRules
2013-06-04 07:39:20,465 DEBUG [network.firewall.FirewallManagerImpl] (Job-Executor-1:job-13) There are no rules to forward to the network elements
2013-06-04 07:39:20,467 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing 0 static nat rules for network id=204 as a part of shutdownNetworkRules
2013-06-04 07:39:20,467 DEBUG [network.firewall.FirewallManagerImpl] (Job-Executor-1:job-13) There are no rules to forward to the network elements
2013-06-04 07:39:20,473 DEBUG [network.lb.LoadBalancingRulesManagerImpl] (Job-Executor-1:job-13) Revoking 0 Public load balancing rules for network id=204
2013-06-04 07:39:20,473 DEBUG [network.lb.LoadBalancingRulesManagerImpl] (Job-Executor-1:job-13) There are no Load Balancing Rules to forward to the network elements
2013-06-04 07:39:20,475 DEBUG [network.lb.LoadBalancingRulesManagerImpl] (Job-Executor-1:job-13) Revoking 0 Internal load balancing rules for network id=204
2013-06-04 07:39:20,475 DEBUG [network.lb.LoadBalancingRulesManagerImpl] (Job-Executor-1:job-13) There are no Load Balancing Rules to forward to the network elements
2013-06-04 07:39:20,477 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing 0 firewall ingress rules for network id=204 as a part of shutdownNetworkRules
2013-06-04 07:39:20,477 DEBUG [network.firewall.FirewallManagerImpl] (Job-Executor-1:job-13) There are no rules to forward to the network elements
2013-06-04 07:39:20,479 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Releasing 0 firewall egress rules for network id=204 as a part of shutdownNetworkRules
2013-06-04 07:39:20,479 DEBUG [network.firewall.FirewallManagerImpl] (Job-Executor-1:job-13) There are no rules to forward to the network elements
2013-06-04 07:39:20,481 DEBUG [network.rules.RulesManagerImpl] (Job-Executor-1:job-13) Found 0 static nat rules to apply for network id 204
2013-06-04 07:39:20,497 DEBUG [network.element.VirtualRouterElement] (Job-Executor-1:job-13) Virtual router elemnt doesn't need to associate ip addresses on the backend; virtual router doesn't exist in the network 204
2013-06-04 07:39:20,502 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Sending network shutdown to VirtualRouter
2013-06-04 07:39:20,503 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Network id=204 is shutdown successfully, cleaning up corresponding resources now.
2013-06-04 07:39:20,506 DEBUG [network.guru.GuestNetworkGuru] (Job-Executor-1:job-13) Releasing vnet for the network id=204
2013-06-04 07:39:20,536 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-1:job-13) Lock is released for network id 204 as a part of network implement
2013-06-04 07:39:20,537 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-1:job-13) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable: Can't find at least one running router!
        at com.cloud.network.element.VirtualRouterElement.implement(VirtualRouterElement.java:207)
        at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:1936)
        at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1841)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2018)
        at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:842)
        at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550)
        at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:239)
        at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
        at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3340)
        at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2867)
        at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2853)
        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: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-06-04 07:39:20,549 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-1:job-13) Cleaning up resources for the vm VM[User|new] in Starting state
2013-06-04 07:39:20,556 DEBUG [agent.transport.Request] (Job-Executor-1:job-13) Seq 1-886177815: Sending  { Cmd , MgmtId: 7635042566263, via: 1, Ver: v1, Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-3-VM","wait":0}}] }
2013-06-04 07:39:20,557 DEBUG [agent.transport.Request] (Job-Executor-1:job-13) Seq 1-886177815: Executing:  { Cmd , MgmtId: 7635042566263, via: 1, Ver: v1, Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-3-VM","wait":0}}] }


--
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