You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Dennis Lawler (JIRA)" <ji...@apache.org> on 2013/05/01 20:28:16 UTC

[jira] [Updated] (CLOUDSTACK-2299) Stale DHCP leases block

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lawler updated CLOUDSTACK-2299:
--------------------------------------

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


  was:
Every time a new VM is started up, there is a 2 second outage in DNS services that can cause problems in guest VMs that use the router VM for DNS.

For Cloudstack configurations using both DHCP and DNS services on the router VM (both implemented with dnsmasq), there is currently a 2 second DNS service outage every time a new VM is instantiated

The source of this outage is in edithosts.sh, which uses “service dnsmasq restart” to pick up the freshly added DNS and DHCP entries.  Restarting the dnsmasq service triggers a sleep for 2 seconds after killing dnsmasq before starting it back up again.

See thread on dev@cloudstack.apache.org for discussion.

        Summary: Stale DHCP leases block  (was: New VM instantiations trigger 2 second DNS outage)
    
> Stale DHCP leases block
> -----------------------
>
>                 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