Reviewed: https://review.openstack.org/488914 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1d80c960f61248f11af427d6008faac7fcc2db0b Submitter: Jenkins Branch: master
commit 1d80c960f61248f11af427d6008faac7fcc2db0b Author: Jakub Libosvar <[email protected]> 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 ovsdb. Closes-bug: #1707339 Change-Id: I15cdb28072835fcb8c37ae4b56fc8754375a807c ** 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/1707339 Title: test_trunk_subport_lifecycle fails on subport down timeout Status in neutron: Fix Released Bug description: subport doesn't transition to DOWN state after trunk deletion logstash query: http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3Agate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv%20AND%20build_branch%3Amaster%20AND%20message%3A%5C%22Timed%20out%20waiting%20for%20subport%20%5C%22%20AND%20message%3A%5C%22to%20transition%20to%20DOWN%5C%22%20AND%20tags%3Aconsole A failed run: http://logs.openstack.org/76/467976/22/check/gate-tempest-dsvm- neutron-dvr-multinode-scenario-ubuntu-xenial- nv/e11aeaf/logs/testr_results.html.gz 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. http://logs.openstack.org/76/467976/22/check/gate-tempest-dsvm- neutron-dvr-multinode-scenario-ubuntu-xenial- nv/e11aeaf/logs/screen-q-agt.txt.gz?level=TRACE 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: https://bugs.launchpad.net/neutron/+bug/1707339/+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
