Author: Jakub Libosvar <libos...@redhat.com>
Date: Tue Aug 1 17:04:30 2017 +0000
ovs-fw: Handle only known trusted ports
Similarly to filtered ports this patch caches so called trusted ports to
avoid processing in case of unknown port is passed down to firewall
driver. The cached ofport is used for removal as the cache reflects
currently installed flows.
The patch also catches exception caused by inconsistency coming from
** 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.
test_trunk_subport_lifecycle fails on subport down timeout
Status in neutron:
subport doesn't transition to DOWN state after trunk deletion
A failed run:
The agent log is filled with trace:
Error while processing VIF ports: OVSFWPortNotFound: Port
526e3ca9-9af3-4b94-8550-90a5bdc9b4e7 is not managed by this agent.
Incidentally, this port is a parent of a trunk port.
Now the trunk's OVSDB handler on the agent side relies on the OVS
agent main loop to detect the port removal and let it notify the
server to mark the logical port down. I wonder if these exceptions
prevent that from happening.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp