yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1135948] Re: Wrong behavior when a DHCP agent goes down

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 13 Mar 2013 08:52:13 -0000
Reply-to: Bug 1135948 <1135948@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

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

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

Title:
  Wrong behavior when a DHCP agent goes down

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

Bug description:
  Steps to reproduce:
  1. Set up a DHCP agent
  2. Create a network with a subnet and ensure the subnet is hosted by the DHCP agent mentioned above
  3. Optional: create an instance, attached to the created network.
  4. Stop the DHCP agent.
  5. If an instance has been launched at the step 3, terminate it.
  6. Delete a network.

  What happens at this point:
  1. Since the agent went down the instance of dnsmaqs that was serving the network is still up and running. Configuraion files for the deleted network still exist.
  2. No error was reported neither to the web ui, nor to the quantum log.

  After restarting the DHCP agent the garbage won't get wiped because its message queue was destroyed.
  There's no way of being informed about the error from the user side other than setting up an external monitoring environment.

  There's also no way of cleaning up the garbasge  other than doing some
  manual labor on the server side.

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