Reviewed: https://review.openstack.org/558724 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=35365ead42eec24027140d3cfd9dfeb40316e8d6 Submitter: Zuul Branch: master
commit 35365ead42eec24027140d3cfd9dfeb40316e8d6 Author: LIU Yulong <[email protected]> Date: Wed Apr 4 15:33:00 2018 +0800 [L3][QoS] Cover mixed dvr_snat and compute node dvr router The dvr_snat node can also run the nova-compute which will make the fip_qos l3 agent extension failed to install the qos tc rules for the dvr router floating IPs. To cover such mixed deployment, the tc rules for floating IP qos will be processed again in qrouter-namespace of the dvr_snat node, and the device is rfp-device. Change-Id: I9eca25201e0647d4da77b325fba03cca1db5bb4d Closes-Bug: #1758316 ** 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/1758316 Title: Floating IP QoS don't work in DVR router Status in neutron: Fix Released Bug description: It looks that QoS for FIP in DVR router doesn't work. Scenario test is failing all the time with error like: http://logs.openstack.org/63/555263/3/check/neutron-tempest-plugin-dvr-multinode-scenario/e7c012f/logs/testr_results.html.gz From what I found in job logs it looks that qos is applied in "snat-XXX" namespace on subnode-2: http://logs.openstack.org/63/555263/3/check/neutron-tempest-plugin-dvr-multinode-scenario/e7c012f/logs/subnode-2/screen-q-l3.txt.gz#_Mar_23_09_20_07_420244 but transfer to VM is not limited as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1758316/+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
