You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sangeetha Hariharan (JIRA)" <ji...@apache.org> on 2013/07/09 01:51:49 UTC

[jira] [Created] (CLOUDSTACK-3404) KVM - IPV6 - Not able deploy a VM in ipv6 network because of attempting to release non existent ipv4 address.

Sangeetha Hariharan created CLOUDSTACK-3404:
-----------------------------------------------

             Summary: KVM - IPV6 - Not able deploy a VM in ipv6 network because of attempting to release non existent ipv4 address.
                 Key: CLOUDSTACK-3404
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3404
             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: Build from master-6-17-stable
            Reporter: Sangeetha Hariharan
            Priority: Blocker
             Fix For: 4.2.0


KVM - IPV6 - Not able deploy a VM in ipv6 network because of attempting to release non existent ipv4 address.

Steps to reproduce the problem:

Create a ipv6 network ( only ipv6 - donot provide anty ipv4 parameters).
Deploy a VM in this network.
Vm deployment fails.


Following exception seen in management server logs:

2013-07-08 16:22:02,484 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-14:job-14) Applying dhcp entry in network Ntwk[204|Guest|7]
2013-07-08 16:22:02,498 DEBUG [agent.transport.Request] (Job-Executor-14:job-14) Seq 1-1212088427: Sending  { Cmd , MgmtId: 7261447522054, via: 1, Ver: v1, Flags: 100111, [{"routing.DhcpEnt
ryCommand":{"vmMac":"06:94:7e:00:00:24","vmName":"test-2","vmIp6Address":"fc00:3:1370::9731","ip6Gateway":"fc00:3:1370::1","duid":"00:03:00:01:06:94:7e:00:00:24","isDefault":true,"accessDet
ails":{"zone.network.type":"Advanced","router.name":"r-4-VM","router.ip":"169.254.3.205"},"wait":0}}] }


2013-07-08 16:24:02,546 DEBUG [agent.transport.Request] (Job-Executor-14:job-14) Seq 1-1212088427: Received:  { Ans: , MgmtId: 7261447522054, via: 1, Ver: v1, Flags: 110, { Answer } }
2013-07-08 16:24:02,546 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-14:job-14) 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:3781)
        at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:2900)
        at com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:916)
        at com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2003)
        at com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2115)
        at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2056)
        at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:847)
        at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:554)
        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:3335)
        at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2873)
        at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2859)
        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-07-08 16:24:02,570 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-14:job-14) Cleaning up resources for the vm VM[User|test-2] in Starting state

Following error seen in KVM host -  /var/log/cloudstack/agent/cloudstack-agent.out
2013-07-08 14:46:39,697{GMT} INFO  [cloud.agent.Agent] (agentRequest-Handler-1:) Set agent id 1
2013-07-08 14:46:39,698{GMT} INFO  [cloud.agent.Agent] (agentRequest-Handler-1:) Ready command is processed: agent id = 1
2013-07-08 15:00:17,217{GMT} WARN  [resource.virtualnetwork.VirtualRoutingResource] (Script-4:) Interrupting script.
2013-07-08 15:00:17,218{GMT} WARN  [resource.virtualnetwork.VirtualRoutingResource] (agentRequest-Handler-2:) Timed out: /usr/share/cloudstack-common/scripts/network/domr/dhcp_entry.sh -r 169.254.3.205 -m 06:9b:0e:00:00:22 -n test1 -6 fc00:3:1370::6379 -u 00:03:00:01:06:9b:0e:00:00:22 .  Output is:
2013-07-08 15:02:17,844{GMT} WARN  [resource.virtualnetwork.VirtualRoutingResource] (Script-8:) Interrupting script.
2013-07-08 15:02:17,844{GMT} WARN  [resource.virtualnetwork.VirtualRoutingResource] (agentRequest-Handler-4:) Timed out: /usr/share/cloudstack-common/scripts/network/domr/dhcp_entry.sh -r 169.254.3.205 -m 06:9b:0e:00:00:22 -n test1 -6 fc00:3:1370::6379 -u 00:03:00:01:06:9b:0e:00:00:22 .  Output is:
2013-07-08 15:31:52,710{GMT} WARN  [resource.virtualnetwork.VirtualRoutingResource] (Script-1:) Interrupting script.



--
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