Updating ports is incompatible with the transaction
semantics that happen inside of ML2. See partial-bug for
more details.
This transaction served no purpose wrapped around the port
update because there should only be one port per agent per
network and if that port fails to update, the code to delete
the binding won't be hit anyway.
Reviewed: https:/ /review. openstack. org/305803 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=a2ceec28647 d835aaa52285785 37230ff571cee3
Committed: https:/
Submitter: Jenkins
Branch: master
commit a2ceec28647d835 aaa522857853723 0ff571cee3
Author: Kevin Benton <email address hidden>
Date: Wed Apr 13 05:20:00 2016 -0700
Don't update DHCP ports in a transaction
Updating ports is incompatible with the transaction
semantics that happen inside of ML2. See partial-bug for
more details.
This transaction served no purpose wrapped around the port
update because there should only be one port per agent per
network and if that port fails to update, the code to delete
the binding won't be hit anyway.
Change-Id: Ica2c5a19e10ae1 773e49537b5ff4a e0eacaeb388
Partial-Bug: #1540844