yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1180766] Re: Disassociate failed dhcp fixed ip in deallocate_for_instance() method

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 17 Jul 2013 12:20:10 -0000
Reply-to: Bug 1180766 <1180766@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

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

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1180766

Title:
  Disassociate failed dhcp fixed ip in deallocate_for_instance() method

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) grizzly series:
  In Progress

Bug description:
  Currently, fix_ip disassociation only happens in release_fixed_ip(),
  which is called by dhcp-bridge when ip is released. But there are
  circumstances when instancs fail to get lease from dnsmasq(instances
  fail to boot or instances fail to spawn). In such case, DHCPRELEASE
  packet sent to dnsmasq would not trigger dhcp-bridge to run. Thus the
  fixed ip would not be disassociated from instance until
  _disassociate_stale_fixed_ips() begins to run.  We need a fix for this
  problem.

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