[
https://issues.apache.org/jira/browse/CLOUDSTACK-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733310#comment-13733310
]
Naoki Sakamoto commented on CLOUDSTACK-3533:
--------------------------------------------
IPv4 has same issue.
1. Create VPC (Super CIDR = 10.0.0.0/16)
2. Create Tier (CIDR = 10.0.0.0/30, GW = 10.0.0.1, Netmask = 255.255.255.252)
3. Deploy VM01 (IP = 10.0.0.2)
4. Destroy VM01
5. Deploy VM02 (IP = 10.0.0.2)
VM02 Guest OS is not getting IP Address.
I confirmed in bigger range Tier (CIDR = 10.0.0.0/27, Netmask =
255.255.255.224) about 30 VMs and same issue occurred.
New VM can't get IP that is exhousted and released.
On Virtual Router
/var/log/dnsmasq.log
Aug 8 08:53:16 dnsmasq[13590]: read /etc/hosts - 6 addresses
Aug 8 08:53:16 dnsmasq-dhcp[13590]: read /etc/dhcphosts.txt
Aug 8 08:53:16 dnsmasq-dhcp[13590]: read /etc/dhcpopts.txt
Aug 8 08:54:27 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2
because it is leased to 02:00:68:25:00:07
Aug 8 08:54:27 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15
02:00:5d:19:00:09 no address available
Aug 8 08:54:31 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2
because it is leased to 02:00:68:25:00:07
Aug 8 08:54:31 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15
02:00:5d:19:00:09 no address available
Aug 8 08:54:41 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2
because it is leased to 02:00:68:25:00:07
Aug 8 08:54:41 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15
02:00:5d:19:00:09 no address available
Aug 8 08:55:02 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2
because it is leased to 02:00:68:25:00:07
Aug 8 08:55:02 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15
02:00:5d:19:00:09 no address available
Aug 8 08:55:21 dnsmasq-dhcp[13590]: not using configured address 10.0.0.2
because it is leased to 02:00:68:25:00:07
Aug 8 08:55:21 dnsmasq-dhcp[13590]: DHCPDISCOVER(eth2) 10.0.2.15
02:00:5d:19:00:09 no address available
02:00:68:25:00:07 is VM01's Mac Address.
I used latest edithosts.sh.
I could recover as following.
1. On Virtual Router
# service dnsmasq restart
2. Restart VM02 by GUI.
VM02 got IP Address 10.0.0.2.
Might I open a new issue for IPv4 ?
> [IPv6][dnsmasq] VM not able get ip from dhcp which is previously assigned to
> vm
> -------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3533
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3533
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Devices
> Affects Versions: 4.2.0
> Reporter: Jayapal Reddy
> Assignee: Sheng Yang
> Fix For: 4.2.0
>
>
> 1. Create a guest network with small ip range (ex: max ips 3)
> 2. Deploy VMs utill ip address exhaust.
> 3. Now delete the one vm ex: V3 . Here one IP got freed.
> 4. deploy new vm Ex: name V4. Now the V4 supposed to get ip address which is
> release by V3.
> Issue 1:
> V4 is not getting ip address.
> Issue 2:
> 1.destroy vm ex: v1 with ipv1.
> 2. create a vm ex:v2. v2 got ip address of v1.
> 3. Now observe the dhcphosts.txt. It contains the two entries for with same
> IP.
> edithosts.sh failed to delete entry with ip already in dhcphosts.txt
--
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
