Public bug reported: The whitebox-neutron-temptest-plugin test test_dscp_bwlimit_external_network has been failing consistently since Jan 8th: https://zuul.opendev.org/t/openstack/builds?job_name=whitebox-neutron-tempest-plugin-ovn-single-thread&project=x%2Fwhitebox-neutron-tempest-plugin&pipeline=periodic&skip=0
The BW limit that the test applies to the external/provider network is not actually applied. test passes: https://03bdeb201ad5b10b1d29-c8e8f0465e65b3e97bf6a5ab87ec6f98.ssl.cf5.rackcdn.com/periodic/opendev.org/x/whitebox-neutron-tempest-plugin/master/whitebox-neutron-tempest-plugin-ovn-single-thread/dbf67fe/controller/logs/screen-q-svc.txt relevant request: req-739334e4-46ac-4806-b8b1-8b362587ebb1 when the BW limit is added to the policy (which was added to the external network before), it generates a transaction with 16 commands to the OVN NB DB, including two UpdateLSwitchPortQosOptionsCommand's test fails: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_6b9/939519/1/check/whitebox-neutron-tempest-plugin-ovn-single-thread/6b9ce99/controller/logs/screen-q-svc.txt relevant request: req-75cfa10b-f983-4756-982b-239b7c4caab6 when the BW limit is added to the policy (which was added to the external network before), it generates a transaction with 13 commands to the OVN NB DB. No UpdateLSwitchPortQosOptionsCommand's at all It seems to me the following patch, which was merged on Jan 7th, could have caused this regression: https://review.opendev.org/c/openstack/neutron/+/934418 ** Affects: neutron Importance: Undecided Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2095167 Title: BW limit not applied to external/provider network Status in neutron: New Bug description: The whitebox-neutron-temptest-plugin test test_dscp_bwlimit_external_network has been failing consistently since Jan 8th: https://zuul.opendev.org/t/openstack/builds?job_name=whitebox-neutron-tempest-plugin-ovn-single-thread&project=x%2Fwhitebox-neutron-tempest-plugin&pipeline=periodic&skip=0 The BW limit that the test applies to the external/provider network is not actually applied. test passes: https://03bdeb201ad5b10b1d29-c8e8f0465e65b3e97bf6a5ab87ec6f98.ssl.cf5.rackcdn.com/periodic/opendev.org/x/whitebox-neutron-tempest-plugin/master/whitebox-neutron-tempest-plugin-ovn-single-thread/dbf67fe/controller/logs/screen-q-svc.txt relevant request: req-739334e4-46ac-4806-b8b1-8b362587ebb1 when the BW limit is added to the policy (which was added to the external network before), it generates a transaction with 16 commands to the OVN NB DB, including two UpdateLSwitchPortQosOptionsCommand's test fails: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_6b9/939519/1/check/whitebox-neutron-tempest-plugin-ovn-single-thread/6b9ce99/controller/logs/screen-q-svc.txt relevant request: req-75cfa10b-f983-4756-982b-239b7c4caab6 when the BW limit is added to the policy (which was added to the external network before), it generates a transaction with 13 commands to the OVN NB DB. No UpdateLSwitchPortQosOptionsCommand's at all It seems to me the following patch, which was merged on Jan 7th, could have caused this regression: https://review.opendev.org/c/openstack/neutron/+/934418 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2095167/+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
