The notification about port create/update should be done no matter
if host (or any other field) was changed or not - it should be up to
handler to decide how to handle it.
This also fixes the bug when there was actually no notification to l3
dvr agent on compute node on new port creation:
_get_host_port_if_changed() always returned None - this is a regression
from commit 2ee08c3464c53abaf9bc5493132ad7958611e3b8
Reviewed: https:/ /review. openstack. org/273274 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=4581c485993 53ccaa4dc6b5ffc d0b9158872cbba
Committed: https:/
Submitter: Jenkins
Branch: stable/kilo
commit 4581c48599353cc aa4dc6b5ffcd0b9 158872cbba
Author: Oleg Bondarev <email address hidden>
Date: Tue Dec 1 11:47:05 2015 +0300
Notify about port create/update unconditionally
The notification about port create/update should be done no matter
if host (or any other field) was changed or not - it should be up to
handler to decide how to handle it.
This also fixes the bug when there was actually no notification to l3 host_port_ if_changed( ) always returned None - this is a regression af9bc5493132ad7 958611e3b8
dvr agent on compute node on new port creation:
_get_
from commit 2ee08c3464c53ab
Conflicts: plugins/ ml2/plugin. py tests/unit/ plugins/ ml2/test_ plugin. py
neutron/
neutron/
Closes-Bug: #1521524 2526f06a5620c0a 4ea96340d21 0ffc523f253fdf8 7aef11d1c7)
Change-Id: I5bb416d2aaab63
(cherry picked from commit 87ce73141dddb84