yahoo-eng-team team mailing list archive

[Kevin Benton <1590316@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Subscribers to callback events can perform DB operations that may
encounter deadlocks or other DB errors that should be retried after
restarting the entire transaction. However, in the cases where we catch
exceptions.CallbackFailure and then raise a different exception, the DB
retry wrapper cannot recognize that it is retriable failure and will
make it fatal for the request. This can lead to a user getting a
SubnetInUse or something similar because of something completely
unrelated to the actual validation.

** Affects: neutron
     Importance: Medium
     Assignee: Kevin Benton (kevinbenton)
         Status: New

** Changed in: neutron
   Importance: Undecided => Medium

** Changed in: neutron
     Assignee: (unassigned) => Kevin Benton (kevinbenton)

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

Title:
  exception handling of callback failures doesn't take into account
  retriable errors

Status in neutron:
  New

Bug description:
  Subscribers to callback events can perform DB operations that may
  encounter deadlocks or other DB errors that should be retried after
  restarting the entire transaction. However, in the cases where we
  catch exceptions.CallbackFailure and then raise a different exception,
  the DB retry wrapper cannot recognize that it is retriable failure and
  will make it fatal for the request. This can lead to a user getting a
  SubnetInUse or something similar because of something completely
  unrelated to the actual validation.

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