Public bug reported: 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. ** Affects: neutron Importance: High Status: Confirmed ** Tags: trunk ** Changed in: neutron Status: New => Confirmed ** Changed in: neutron Importance: Undecided => High ** Tags added: tru ** Tags removed: tru ** Tags added: trunk -- 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: Confirmed 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 : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
