This patch ensures that the ovsdb monitor propagates the events
received for modified ports.
We'll use a new list for the modified ports, which the neutron ovs
agent can handle.
In particular, this will cover the situation in which the ofport
changes. When using recent OVS Windows versions, VM ofports change
to -1 (invalid) when the VMs are shut down, receiving a valid
ofport when the VMs are powered back on (different than the initial
one). With this patch applied, "modify" events will be propagated
to the ovs agent, which will then update the OpenFlow rules.
The old rules are cleaned up by "update_stale_ofport_rules"
once the invalid ofport is detected.
Reviewed: https:/ /review. opendev. org/681984 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=451c21571f4 0ca83eb3189e5c9 24b03c0561f853
Committed: https:/
Submitter: Zuul
Branch: master
commit 451c21571f40ca8 3eb3189e5c924b0 3c0561f853
Author: Lucian Petrut <email address hidden>
Date: Thu Sep 12 17:34:04 2019 +0300
ovsdb monitor: handle modified ports
This patch ensures that the ovsdb monitor propagates the events
received for modified ports.
We'll use a new list for the modified ports, which the neutron ovs
agent can handle.
In particular, this will cover the situation in which the ofport stale_ofport_ rules"
changes. When using recent OVS Windows versions, VM ofports change
to -1 (invalid) when the VMs are shut down, receiving a valid
ofport when the VMs are powered back on (different than the initial
one). With this patch applied, "modify" events will be propagated
to the ovs agent, which will then update the OpenFlow rules.
The old rules are cleaned up by "update_
once the invalid ofport is detected.
Closes-Bug: #1843870
Co-authored-by: Alin Serdean <email address hidden>
Change-Id: I0c3a570cbb3fbb 03b4224744b32e0 34e9e255f8e