yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

** Changed in: neutron
    Milestone: None => havana-2

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1192550

Title:
  dhcp_lease_time and dhcp_lease_duration should be a single config
  option

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  This is somewhat related to
  https://bugs.launchpad.net/quantum/+bug/1116500 where this issue was
  brought up but never fixed.

  The dnsmasq dhcp agent uses the setting  'dhcp_lease_time' (default
  120s)

  The db plugin uses the setting from dhcp_lease_duration (default 120s)

  It seems to me that there is a potential for bad things to happen if
  one (_duration) is set a lot shorter than the other (in that the db
  may expire a lease that dnsmasq still considers valid).

  To prevent the potential for such bad things, these settings should
  become one single setting used everywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1192550/+subscriptions