Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2143487

Summary: QOS bandwidth limiting tests are failing
Product: Red Hat OpenStack Reporter: Miro Tomaska <mtomaska>
Component: openstack-neutronAssignee: OSP Team <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Eran Kuris <ekuris>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16.2 (Train)CC: chrisw, scohen, skaplons
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-17 14:12:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Miro Tomaska 2022-11-17 02:33:00 UTC 
Description of problem:
neutron_plugin.tests.scenario.test_qos_16.QosTestCommon.test_bw_limit_east_west
neutron_plugin.tests.scenario.test_qos_16.QosTestCommon.test_bw_limit_south_north
neutron_plugin.tests.scenario.test_qos_16.QosTestCommon.test_bw_limit_tenant_network

All the tests above are not meeting the minimum set bandwidth limit and failing. Affects Jenkins jobs: 
DFG-network-neutron-16.2_director-rhel-virthost-3cont_2comp-ml2ovs-ipv4-vxlan-tobiko-tempest-dvr
DFG-network-neutron-16.2_director-rhel-virthost-3cont_2comp-ml2ovs-ipv4-vxlan-tobiko-tempest-nossl-ovsfirewall
DFG-network-neutron-16.1_director-rhel-virthost-3cont_2comp-ml2ovs-ipv4-vxlan-tobiko-tempest-dvr

[1] https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/DFG/view/network/view/neutron/job/DFG-network-neutron-16.2_director-rhel-virthost-3cont_2comp-ml2ovs-ipv4-vxlan-tobiko-tempest-nossl-ovsfirewall/24/testReport/

[2] https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/DFG/view/network/view/neutron/
Comment 1 Slawek Kaplonski 2022-11-17 14:12:31 UTC 

*** This bug has been marked as a duplicate of bug 2041859 ***