yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

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

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

Title:
  port usage tracking not reliable anymore

Status in neutron:
  Fix Released

Bug description:
  Patch https://review.openstack.org/#/c/188883/23 modified neutron.db.ipam_backend in order to ensure a sqlalchemy event is triggered when deleting a port. This caused an issue when transaction isolation level is below repeatable read as the sqlalchemy ORM mapper throws an exception if the record is deleted by another transaction.
  Patch https://review.openstack.org/#/c/224289/ fixed this but reinstated query.delete which does not trigger the sqlalchemy event.

  It might be worth considering just handling the sqlalchemy orm
  exception in this case; alternatively usage tracking for ports might
  be disabled.

  A related question is why the logic for deleting a port resides in the
  ipam module, but probably it should not be answered here.

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