Was the system VM rebooted to get new software?
On May 3, 2013 4:57 AM, "Shashi Dahal" <s.da...@leaseweb.com> wrote:

> Hi All,
> Sending to both lists, as not sure if this is a dev or infra issue.
>
> I am not able to add a new VM after upgrade from 2.2.14 to 4.1.0  [CentOS
> 6.4 - Advance Networking with Security Groups]
>
> Log snippet:
> 2013-05-03 12:41:55,212 DEBUG [agent.transport.Request]
> (Job-Executor-24:job-33) Seq 2-1920335888: Received: { Ans: , MgmtId:
> 90520747364525, via: 2, Ver: v1, Flags: 110, { Answer } }
> 2013-05-03 12:41:55,212 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-24:job-33) 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:3431)
>         at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:2664)
>         at
> com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:831)
>         at
> com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:1547)
>         at
> com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:1658)
>         at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:1599)
>         at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:746)
>         at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:471)
>         at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:212)
>         at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
>         at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3865)
>         at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3458)
>         at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3444)
>         at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:379)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
>         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:1146)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-05-03 12:41:55,228 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-24:job-33) Cleaning up resources for the vm VM[User|MY-VM] in
> Starting state
>
> Full logs found in: https://issues.apache.org/jira/browse/CLOUDSTACK-2322
>
> Cheers,
> Shashi
>
>

Reply via email to