yahoo-eng-team team mailing list archive

[Vincent Untz <1539640@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

We just happened to have broken dhcp because the dhcp ports were in
binding_failed state.

We tried to disable/enable dhcp again, but apparently (not 100% sure,
unfortunately), disabling didn't remove the ports (assuming that it was
because they were in binding_failed state) and re-enabling just ended up
with ports in binding_failed states again (likely the same ports because
dhcp agent tries to recycle ports whenever possible). Unfortunately, I
don't have the logs / traces of this.

So disabling / re-enabling didn't fix anything while, I believe, users
would try that first to fix the situation. If we could make that just
work, then that would make it easier for people to get out of this "no
dhcp" problem when ports are failing to bind.

In the end, we had to remove the ports to have new ports created when
dhcp was disable / re-enabled.

** Affects: neutron
     Importance: Undecided
     Assignee: Rossella Sblendido (rossella-o)
         Status: New

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

Title:
  Make dhcp agent not recycle ports in binding_failed state

Status in neutron:
  New

Bug description:
  We just happened to have broken dhcp because the dhcp ports were in
  binding_failed state.

  We tried to disable/enable dhcp again, but apparently (not 100% sure,
  unfortunately), disabling didn't remove the ports (assuming that it
  was because they were in binding_failed state) and re-enabling just
  ended up with ports in binding_failed states again (likely the same
  ports because dhcp agent tries to recycle ports whenever possible).
  Unfortunately, I don't have the logs / traces of this.

  So disabling / re-enabling didn't fix anything while, I believe, users
  would try that first to fix the situation. If we could make that just
  work, then that would make it easier for people to get out of this "no
  dhcp" problem when ports are failing to bind.

  In the end, we had to remove the ports to have new ports created when
  dhcp was disable / re-enabled.

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