Reviewed: https://review.openstack.org/475650 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0f536d5a25d410362e5a7b1390bc627cc3dc5071 Submitter: Jenkins Branch: master
commit 0f536d5a25d410362e5a7b1390bc627cc3dc5071 Author: Kevin Benton <[email protected]> Date: Tue Jun 20 00:00:12 2017 -0700 Use objects instead of SQLA deep copies in PortContext The workaround of using deepcopy calls on the PortBinding and PortBindingLevel objects prevents the port relationship from being loaded to bump its revision because it then fails to merge. So in order to allow port bindings to bump the revision we need to stop using sqlalchemy objects in the PortContext. This patch adds a new snapshot object that just copies the column values and provides a method to reconcile them back into the session. This workaround can go away after we switch to using OVOs, but this needs to be backportable so we can't just wait for OVO adoption. Partial-Bug: #1699034 Change-Id: Ib85ec8182117fa3c4844dabfffe881e38e68b556 ** 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/1699034 Title: port binding not bumping revision Status in neutron: Fix Released Bug description: Port binding is not bumping the revision level of the port so a port update of the host_id will generate two update events with the same revision number. The first sets the host_id and the second sets the binding info but does not change the revision which makes ordering difficult to distinguish on the agents. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1699034/+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
