You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Murali Reddy (JIRA)" <ji...@apache.org> on 2014/09/08 14:09:28 UTC

[jira] [Commented] (CLOUDSTACK-7423) [Automation] Unable to start Virtual Machine due to - Unable to apply dhcp entry on router

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-7423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125438#comment-14125438 ] 

Murali Reddy commented on CLOUDSTACK-7423:
------------------------------------------

There was a communication problem connecting through SSH to VR (169.254.3.229) from the XenServer, as noticed in the logs. 
2014-08-24 09:23:03,502 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-381:ctx-cf49055b) Executing command in VR: /opt/cloud/bin/router_proxy.sh edithosts.sh 169.254.3.229  -m 02:00:37:9a:00:01 -4 192.168.200.227 -h VM-f565ab8       2-6d89-416e-9d93-9b04cf2667d0 -d 192.168.200.1 -n 192.168.200.1

2014-08-24 09:23:03,513 DEBUG [c.c.a.t.Request] (DirectAgent-381:ctx-cf49055b) Seq 2-3323656524999428602: Processing:  { Ans: , MgmtId: 33385016016501, via: 2, Ver: v1, Flags: 10, [{"com.cloud.agent.api.Answer":{"result":false,"d       etails":"There was a problem while connecting to 10.220.163.7:22","wait":0}}] }

This is interment issue. Root cause why it happened could only be figured if we look in the xenserver host where the VM is running.

On subsequent test runs and when i manually launch the vm or run the tests I am not seeing any issue.  Please re-open the bug if the test case is failing consistently. 

> [Automation] Unable to start Virtual Machine due to - Unable to apply dhcp entry on router
> ------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7423
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7423
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation, Test
>    Affects Versions: 4.5.0
>            Reporter: Chandan Purushothama
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.5.0
>
>
> Unable to start after stopping a User VM as part of *integration.component.test_cpu_project_limits.TestProjectsCPULimits.test_01_project_counts_start_stop_instance*
> ============
> *Error Message*
> ============
> Failed to start instance: Job failed: {jobprocstatus : 0, created : u'2014-08-24T09:23:02+0000', jobresult : {errorcode : 530, errortext : u'Job failed due to exception Unable to create a deployment for VM[User|i-218-404-VM]'}, cmd : u'org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin', userid : u'77df13d2-2b4d-11e4-89bd-1e5d0e053e75', jobstatus : 2, jobid : u'76b12bb1-52fc-45f4-933f-31399cefd624', jobresultcode : 530, jobinstanceid : u'f565ab82-6d89-416e-9d93-9b04cf2667d0', jobresulttype : u'object', jobinstancetype : u'VirtualMachine', accountid : u'77df055e-2b4d-11e4-89bd-1e5d0e053e75'}   Logs available at http://xenrt.hq.xensource.com/control/queue.cgi?action=testlogs&id=804076&phase=Parallel&test=cpu_project_limits
> Stacktrace
>   File "/usr/lib/python2.7/unittest/case.py", line 332, in run
>     testMethod()
>   File "/root/cloudstack/test/integration/component/test_cpu_project_limits.py", line 263, in test_01_project_counts_start_stop_instance
>     self.fail("Failed to start instance: %s" % e)
>   File "/usr/lib/python2.7/unittest/case.py", line 413, in fail
>     raise self.failureException(msg)
> 'Failed to start instance: Job failed: {jobprocstatus : 0, created : u\'2014-08-24T09:23:02+0000\', jobresult : {errorcode : 530, errortext : u\'Job failed due to exception Unable to create a deployment for VM[User|i-218-404-VM]\'}, cmd : u\'org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin\', userid : u\'77df13d2-2b4d-11e4-89bd-1e5d0e053e75\', jobstatus : 2, jobid : u\'76b12bb1-52fc-45f4-933f-31399cefd624\', jobresultcode : 530, jobinstanceid : u\'f565ab82-6d89-416e-9d93-9b04cf2667d0\', jobresulttype : u\'object\', jobinstancetype : u\'VirtualMachine\', accountid : u\'77df055e-2b4d-11e4-89bd-1e5d0e053e75\'}\n
> ===========================
> Error of Management Server Log:
> ===========================
> {code}
> 2014-08-24 09:23:03,513 INFO  [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-21:ctx-e6e44390 job-2922/job-2923 ctx-2994f1d0) Unable to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable: Unable to apply dhcp entry on router 
> 	at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:4031)
> 	at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:3150)
> 	at sun.reflect.GeneratedMethodAccessor447.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:601)
> 	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> 	at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> 	at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> 	at $Proxy190.applyDhcpEntry(Unknown Source)
> 	at com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:924)
> 	at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareElement(NetworkOrchestrator.java:1251)
> 	at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(NetworkOrchestrator.java:1373)
> 	at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1309)
> 	at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:972)
> 	at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4582)
> 	at sun.reflect.GeneratedMethodAccessor383.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:601)
> 	at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> 	at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4738)
> 	at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> 	at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
> 	at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> 	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> 	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> 	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> 	at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> 	at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
> 	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:722)
> 2014-08-24 09:23:03,515 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-19:ctx-542348cb job-2924 ctx-7f90f0e1) Found a potential host id: 1 name: cl09-B-02 and associated storage pools for this VM
> 2014-08-24 09:23:03,517 DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-21:ctx-e6e44390 job-2922/job-2923 ctx-2994f1d0) Cleaning up resources for the vm VM[User|i-218-404-VM] in Starting state
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)