← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1414232] [NEW] l3-agent restart fails to remove qrouter namespace

 

Public bug reported:

When a router is removed while a l3-agent is stopped, then started again
the qrouter namespace will fail to be destroyed because the driver
returns a 'Device or resource busy' error.   The reason for the error is
the metadata proxy is still running on the namespace.

The metadata proxy code has recently been refactored and no longer is
called in the _destroy_router_namespace() method.  In the use case of
this bug, there is no ri/router object since it has been removed, only
the namespace remains.  The new before_router_removed() method requires
a router object.

Changes will be required in both the l3-agent code and metadata proxy
service code to resolve this bug.

** Affects: neutron
     Importance: Undecided
     Assignee: Mike Smith (michael-smith6)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Mike Smith (michael-smith6)

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

Title:
  l3-agent restart fails to remove qrouter namespace

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When a router is removed while a l3-agent is stopped, then started
  again the qrouter namespace will fail to be destroyed because the
  driver returns a 'Device or resource busy' error.   The reason for the
  error is the metadata proxy is still running on the namespace.

  The metadata proxy code has recently been refactored and no longer is
  called in the _destroy_router_namespace() method.  In the use case of
  this bug, there is no ri/router object since it has been removed, only
  the namespace remains.  The new before_router_removed() method
  requires a router object.

  Changes will be required in both the l3-agent code and metadata proxy
  service code to resolve this bug.

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


Follow ups

References