cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-8092) Unable to start instance due to failed to configure ip alias on the router as a part of dhcp config
Date Thu, 18 Dec 2014 16:57:13 GMT
Tom created CLOUDSTACK-8092:
-------------------------------

             Summary: Unable to start instance due to failed to configure ip alias on the
router as a part of dhcp config
                 Key: CLOUDSTACK-8092
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8092
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: KVM, Management Server
    Affects Versions: 4.4.1
            Reporter: Tom


I have a guest network that I recently added an additional IP range on a different subnet
to.  When I try to deploy a VM while specifying an IP in that new IP range it fails to deploy
with the following error:

2014-12-17 15:42:23,598 ERROR [c.c.a.ApiAsyncJobDispatcher] (API-Job-Executor-103:ctx-b660e3e5
job-3004) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd
java.lang.RuntimeException: Job failed due to exception Resource [Host:19] is unreachable:
Host 19: Unable to start instance due to failed to configure ip alias on the router as a part
of dhcp config
        at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:114)
        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.run(FutureTask.java:262)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
2014-12-17 15:42:23,599 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-103:ctx-b660e3e5
job-3004) Complete async job-3004, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/
null/{"uuidList":[],"errorcode":530,"errortext":"Job failed due to exception Resource [Host:19]
is unreachable: Host 19: Unable to start instance due to failed to configure ip alias on the
router as a part of dhcp config"}

This looks very similar to CLOUDSTACK-3871, but if I'm reading the fix correctly it only applied
to XenServer.



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

Mime
View raw message