yahoo-eng-team team mailing list archive

[Gregoire Mahe <1846703@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hello,


We discovered that when designate is configured on neutron, and the service is down, neutron will fails to delete port.

The current behavior for port creation is not the same for port
deletion.

When we create a port, while designate is down, neutron will ignore it,
and create the port without the record on designate.

When we delete a port, while designate is down, neutron will return a
500 error because designate is down.

We need to normalize the behavior. For now, I propose to catch the
exception, and just logs the exception and continue to delete the port.

In a next step, later on, I maybe suggest to create a "dead queue" on
the neutron rabbitmq, and store record creation on error, which can be
retried later manually, to keep consistancy.

** Affects: neutron
     Importance: Undecided
         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/1846703

Title:
  Avoid neutron to return error 500 when deleting port if designate is
  down

Status in neutron:
  New

Bug description:
  Hello,

  
  We discovered that when designate is configured on neutron, and the service is down, neutron will fails to delete port.

  The current behavior for port creation is not the same for port
  deletion.

  When we create a port, while designate is down, neutron will ignore
  it, and create the port without the record on designate.

  When we delete a port, while designate is down, neutron will return a
  500 error because designate is down.

  We need to normalize the behavior. For now, I propose to catch the
  exception, and just logs the exception and continue to delete the
  port.

  In a next step, later on, I maybe suggest to create a "dead queue" on
  the neutron rabbitmq, and store record creation on error, which can be
  retried later manually, to keep consistancy.

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