Reviewed: https://review.openstack.org/457423 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=47fdee443680c04a85d741a2f7efd31df4bfcff5 Submitter: Jenkins Branch: master
commit 47fdee443680c04a85d741a2f7efd31df4bfcff5 Author: Kevin Benton <[email protected]> Date: Mon Apr 17 18:46:49 2017 -0700 Fixup event transaction semantics for ML2 bulk ops This splits out code in ML2 for ports, subnets, and networks into clear before, during, and after functions corresponding to the state of the transaction they are called within. This allows the bulk creation to correctly call chunks of code outside of DB transactions even when doing many creations at once. Change-Id: Id6fe0f5066358be954a6ca14dd49c36755897e31 Closes-Bug: #1683550 ** Changed in: neutron Status: In Progress => 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/1683550 Title: BEFORE and AFTER events called in bulk transactions Status in neutron: Fix Released Bug description: Bulk network creation ends up calling BEFORE and AFTER events while in an enclosing transaction. This violates the callback event semantics and leads to traces like http://logs.openstack.org/78/385178/20/gate /gate-tempest-dsvm-neutron-full-ubuntu- xenial/ba7dfb9/logs/screen-q-svc.txt.gz?level=TRACE#_2017-04-17_07_48_36_708 that indicate that a result couldn't be retrieved from the DB in a separate transaction because it's not committed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1683550/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
