Sanjeev N created CLOUDSTACK-2736:
-------------------------------------
Summary: [Multiple_IP_Ranges] Failed to deploy vm with IP address
from new CIDR
Key: CLOUDSTACK-2736
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2736
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: Latest build from master branch:
Zone: SG enabled advanced zone
Hypervisor:KVM
Reporter: Sanjeev N
Priority: Blocker
Fix For: 4.2.0
Failed to deploy vm with IP address from new CIDR
Steps to Reproduce:
=================
1.Bring up CS with SG enabled advnaced zone with KVM cluster
2.Add guest ip range in new CIDR in the existing default shared network
3.Deploy guest vm with IP address from the new CIDR
Expected Result:
==============
IP alias should be created on the VR and VM deployment should be successful
with IP address from the new CIDR
Actual Result:
============
VM deployment failed
Observations:
===========
Configuring dhcp service failed with following exceptions:
2013-05-29 13:04:38,782 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-24:null) submit async job-18, details: AsyncJobVO {id:18,
userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
instanceId: 7, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd,
cmdOriginator: null, cmdInfo:
{"sessionkey":"ySm8CvuVNkVVRASycbmxD0Lfby4\u003d","ctxUserId":"2","serviceOfferingId":"b69fbcae-6cbb-4ac4-9669-a8cc8effe2f3","httpmethod":"GET","securitygroupids":"a181bf2c-c853-11e2-96ab-06045a000066","zoneId":"4f13e6b8-aa69-425e-954f-b1852f202266","response":"json","templateId":"6fb1b1b4-c853-11e2-96ab-06045a000066","id":"7","networkIds":"a26a1c93-83c8-4f41-b6ba-7525e8aa0056","hypervisor":"KVM","name":"vm1-s2","_":"1369827334315","ctxAccountId":"2","ctxStartEventId":"79","displayname":"vm1-s2"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6615759585382,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-29 13:04:38,786 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null)
===END=== 10.146.0.15 -- GET
command=deployVirtualMachine&zoneId=4f13e6b8-aa69-425e-954f-b1852f202266&templateId=6fb1b1b4-c853-11e2-96ab-06045a000066&hypervisor=KVM&serviceOfferingId=b69fbcae-6cbb-4ac4-9669-a8cc8effe2f3&securitygroupids=a181bf2c-c853-11e2-96ab-06045a000066&networkIds=a26a1c93-83c8-4f41-b6ba-7525e8aa0056&displayname=vm1-s2&name=vm1-s2&response=json&sessionkey=ySm8CvuVNkVVRASycbmxD0Lfby4%3D&_=1369827334315
2013-05-29 13:04:38,789 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-2:job-18) Executing
org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-18
2013-05-29 13:04:40,365 DEBUG [db.Transaction.Transaction]
(Job-Executor-2:job-18) Rolling back the transaction: Time = 131 Name =
-AsyncJobManagerImpl$1.run:401-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679;
called by
-Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-NetworkManagerImpl.assignPublicIpAddressFromVlans:370-VirtualNetworkApplianceManagerImpl.configDhcpForSubnet:2798-VirtualRouterElement.configDhcpSupportForSubnet:870-NetworkManagerImpl.prepareElement:1962-NetworkManagerImpl.prepareNic:2077-NetworkManagerImpl.prepare:2018-VirtualMachineManagerImpl.advanceStart:842
2013-05-29 13:04:40,366 INFO
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-2:job-18)
Insufficient address capacity
2013-05-29 13:04:40,367 INFO
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-2:job-18)
unable to configure dhcp for this VM.
2013-05-29 13:04:40,367 INFO [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-2:job-18) Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: unable to configure
the dhcp service, due to insufficiant address capacityScope=interface
com.cloud.network.Network; id=203
at
com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2078)
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:3243)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2781)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2767)
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-05-29 13:04:40,369 WARN [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-2:job-18) unexpected InsufficientCapacityException :
com.cloud.network.Network
com.cloud.exception.InsufficientAddressCapacityException: unable to configure
the dhcp service, due to insufficiant address capacityScope=interface
com.cloud.network.Network; id=203
at
com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2078)
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:3243)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2781)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2767)
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-05-29 13:04:40,431 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-2:job-18) Cleaning up resources for the vm VM[User|vm1-s2] in
Starting state
2013-05-29 13:04:40,435 DEBUG [agent.transport.Request] (Job-Executor-2:job-18)
Seq 1-860553276: Sending { Cmd , MgmtId: 6615759585382, via: 1, Ver: v1,
Flags: 100111, [{"StopCommand":{"isProxy":false,"vmName":"i-2-7-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
