You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "manasaveloori (JIRA)" <ji...@apache.org> on 2013/07/12 09:39:48 UTC

[jira] [Updated] (CLOUDSTACK-3490) [VMware]Router VM failed to start with VMware hypervisor .

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

manasaveloori updated CLOUDSTACK-3490:
--------------------------------------

    Attachment: management-server.zip
    
> [VMware]Router VM failed to start  with VMware hypervisor .
> -----------------------------------------------------------
>
>                 Key: CLOUDSTACK-3490
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3490
>             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
>         Environment: 4.2 stable build
>            Reporter: manasaveloori
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: management-server.zip
>
>
> Steps:
> 1.	Have CS with VMware hypervisor.
> 2.	Create primary storage –local   .Secondary storage-NFS.
> 3.	Deploy a user VM.
> Observations:
> Observed that the Router VM fails to start with following exception
> 2013-07-12 18:25:49,696 DEBUG [vmware.mo.HostMO] (DirectAgent-16:10.147.40.29) VM r-18-VM found in host cache
> 2013-07-12 18:25:49,766 INFO  [vmware.resource.VmwareResource] (DirectAgent-16:10.147.40.29) Configure VNC port for VM r-18-VM, port: 5926, host: 10.147.40.29
> 2013-07-12 18:25:50,224 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
> 2013-07-12 18:25:50,265 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 2 is ready to launch secondary storage VM
> 2013-07-12 18:25:50,626 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1 is ready to launch console proxy
> 2013-07-12 18:25:50,643 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 2 is ready to launch console proxy
> 2013-07-12 18:25:51,048 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) ===START===  10.252.192.69 -- GET  command=queryAsyncJobResult&jobId=c5e0d5a6-f41f-4014-86f7-41f0d6d6c43a&response=json&sessionkey=B2dkl66uTrHsb5xkAC2urfO%2F7xo%3D&_=1373614297789 
> 2013-07-12 18:25:51,087 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) ===END===  10.252.192.69 -- GET  command=queryAsyncJobResult&jobId=c5e0d5a6-f41f-4014-86f7-41f0d6d6c43a&response=json&sessionkey=B2dkl66uTrHsb5xkAC2urfO%2F7xo%3D&_=1373614297789
> 2013-07-12 18:25:51,693 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 3 routers to update status.
> 2013-07-12 18:25:51,696 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-07-12 18:25:51,808 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 3 routers to update status.
> 2013-07-12 18:25:51,811 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-07-12 18:25:53,411 WARN  [vmware.resource.VmwareResource] (DirectAgent-16:10.147.40.29) StartCommand failed due to Exception: java.lang.RuntimeException
> Message: A specified parameter was not correct.
> java.lang.RuntimeException: A specified parameter was not correct.
>         at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:835)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2834)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:507)
>         at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>         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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>         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-07-12 18:25:53,419 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-16:null) Seq 4-676266156: Cancelling because one of the answers is false and it is stop on error.
> 2013-07-12 18:25:53,419 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-16:null) Seq
> Attaching the Ms logs

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