You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/05/03 22:12:16 UTC

[jira] [Commented] (CLOUDSTACK-2299) Stale DHCP leases block IP reallocation

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648751#comment-13648751 ] 

ASF subversion and git services commented on CLOUDSTACK-2299:
-------------------------------------------------------------

Commit 870d21c436f8ca34f3d865409444e2f4c84a4319 in branch refs/heads/master from Marcus Sorensen <ma...@betterservers.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=870d21c ]

Summary: Release old DHCP entries

Detail: Refresh dnsmasq with updated entries live, no outage

BUG-ID: CLOUDSTACK-2299
Submitted-by: Dennis Lawler <dl...@gmail.com>
Signed-off-by: Marcus Sorensen <ma...@betterservers.com> 1367611792 -0600

                
> Stale DHCP leases block IP reallocation
> ---------------------------------------
>
>                 Key: CLOUDSTACK-2299
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2299
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller, Network Devices
>    Affects Versions: pre-4.0.0, 4.0.0, 4.0.1
>         Environment: Virtual Router used for DHCP, DNS services
>            Reporter: Dennis Lawler
>
> Commit c9c68e1 fixed a 2 second DNS outage triggered with new VM instantiations, but introduced a different problem: old DHCP leases are maintained in memory by dnsmasq.  
> This causes IP re-allocations to fail as such:
> dnsmasq-dhcp[pid]: not using configured address 192.168.1.100 because it is leased to aa:bb:cc:11:22:33
> dnsmasq-dhcp[pid]: DHCPDISCOVER(eth0) aa:bb:cc:22:33:44 no address available

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