92f1281b69
Sometimes, when the OVSDB is too loaded (that could happen during the
functional tests), there is a delay between the OVSDB post transaction
end and when the register (new or updated) can be read. Although this is
something that should not happen (considering the OVSDB is transactional),
tests should deal with this inconvenience and provide a robust method to
retrieve a value and at the same time check the value. This new method
should provide a retrieving mechanism to read again the value in case of
discordance.
In order to solve the gate problem ASAP, another bug is fixed in this
patch: to skip the QoS removal when OVS agent is initialized during
funtional tests
When executing functional tests, several OVS QoS policies specific for
minimum bandwidth rules [1]. Because during the functional tests
execution several threads can create more than one minimum bandwidth
QoS policy (something in a production environment cannot happen), the
OVS QoS driver must skip the execution of [2] to avoid removing other
QoS created in parellel in other tests.
This patch is marking as unstable "test_min_bw_qos_policy_rule_lifecycle"
and "test_bw_limit_qos_port_removed". Those tests will be investigated
once the CI gates are stable.
[1] Those QoS policies are created only to hold minimum bandwidth rules.
Those policies are marked with:
external_ids: {'_type'='minimum_bandwidth'}
[2]
|
||
|---|---|---|
| .. | ||
| agents | ||
| resources | ||
| README | ||
| __init__.py | ||
| base.py | ||
| test_agent_bandwidth_report.py | ||
| test_connectivity.py | ||
| test_dhcp_agent.py | ||
| test_firewall.py | ||
| test_l3_agent.py | ||
| test_logging.py | ||
| test_mtu.py | ||
| test_port_shut_down.py | ||
| test_ports_rebind.py | ||
| test_qos.py | ||
| test_securitygroup.py | ||
| test_trunk.py | ||
| utils.py | ||
README
Please see neutron/TESTING.rst.