You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sanjeev N (JIRA)" <ji...@apache.org> on 2013/06/27 14:06:20 UTC
[jira] [Created] (CLOUDSTACK-3240) [Multiple_IP_Ranges] Failed to
create ip alias on VR while deploying guest vm with ip address from new
CIDR
Sanjeev N created CLOUDSTACK-3240:
-------------------------------------
Summary: [Multiple_IP_Ranges] Failed to create ip alias on VR while deploying guest vm with ip address from new CIDR
Key: CLOUDSTACK-3240
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3240
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-6-17-stable branch
Reporter: Sanjeev N
Priority: Blocker
Fix For: 4.2.0
Failed to create ip alias on VR while deploying guest vm with ip address from new CIDR:
Repro steps:
===========
1.Bring up CS in Advanced zone with VMWare Cluster
2.Create shared network and add CIDR in the network
3.Add another guest ip range in new cidr in the shared network
4.Exhaust all guest IP addresses from the primary IP range
5.Try to deploy guest vm using the shared network created at step2 (CS will try to assing ip address from new cidr added at step3)
Expected Result:
==============
Since vm gets IP address from new cidr ip alias should be created on router vm to server dhcp requests
Actual Result:
============
vm deployment failed since ip alias creation failed.
Observations:
============
createipAlias command looks for createipAlias.sh script on router vm but actually the script name is "createIpAlias.sh". So it should try to execute createIpAlias.sh instead of createipAlias.sh on router vm.
Following is the log snippet from management server log:
2013-06-27 13:16:39,776 INFO [vmware.resource.VmwareResource] (DirectAgent-304:10.147.40.9) Executing createipAlias command: {"routerip":"10.147.33.11","ipAliasTOs":[{"routerip":"10.147.33.130","netmask":"255.255.255.192","alias_count":"31"}],"accessDetails":{"router.guest.ip":"10.147.33.11","zone.network.type":"Advanced","router.name":"r-34-VM","router.ip":"10.147.40.249"},"wait":0}
2013-06-27 13:16:39,776 DEBUG [vmware.resource.VmwareResource] (DirectAgent-304:10.147.40.9) Run command on domR 10.147.40.249, /root/createipAlias 10.147.40.249 31:10.147.33.130:255.255.255.192-
2013-06-27 13:16:39,776 DEBUG [vmware.resource.VmwareResource] (DirectAgent-304:10.147.40.9) Use router's private IP for SSH control. IP : 10.147.40.249
2013-06-27 13:16:40,030 ERROR [utils.ssh.SshHelper] (DirectAgent-304:10.147.40.9) SSH execution of command /root/createipAlias.sh 10.147.40.249 31:10.147.33.130:255.255.255.192- has an error status code in return. result output: bash: /root/createipAlias.sh: No such file or directory
2013-06-27 13:16:40,035 ERROR [vmware.resource.VmwareResource] (DirectAgent-304:10.147.40.9) ipAlias command on domr 10.147.40.249 failed, message: bash: /root/createipAlias.sh: No such file or directory
2013-06-27 13:16:40,035 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-304:null) Seq 9-1765409128: Cancelling because one of the answers is false and it is stop on error.
2013-06-27 13:16:40,035 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-304:null) Seq 9-1765409128: Response Received:
2013-06-27 13:16:40,035 DEBUG [agent.transport.Request] (DirectAgent-304:null) Seq 9-1765409128: Processing: { Ans: , MgmtId: 7332683579487, via: 9, Ver: v1, Flags: 10, [{"Answer":{"result":false,"details":"createipAlias failed due to bash: /root/createipAlias.sh: No such file or directory\n","wait":0}}] }
2013-06-27 13:16:40,036 DEBUG [agent.transport.Request] (Job-Executor-157:job-157) Seq 9-1765409128: Received: { Ans: , MgmtId: 7332683579487, via: 9, Ver: v1, Flags: 10, { Answer } }
2013-06-27 13:16:40,057 ERROR [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-157:job-157) Failed to start instance VM[User|z3-s2-passwd]
com.cloud.utils.exception.CloudRuntimeException: failed to configure ip alias on the router as a part of dhcp config
at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.configDhcpForSubnet(VirtualNetworkApplianceManagerImpl.java:2834)
at com.cloud.network.element.VirtualRouterElement.configDhcpSupportForSubnet(VirtualRouterElement.java:870)
at com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:1978)
at com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2093)
at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2034)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:848)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:556)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3313)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2851)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2837)
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:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
--
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