4d983d2fea
It seems that in test test_configurations_are_synced_towards_placement
when the fake placement process is stopped it can take longer and
the test restarts the agent before it is really dead.
In this case neutron-server can report the status and the agent's
'resources_synced' field is True when the tests checks it.
A simple workaround for this can be to check if the AsyncProcess
class' _is_running property is False.
Closes-Bug: #1856319
Change-Id: Ia4c25110ee5a7b7539407d3531f559555fec50cc
(cherry picked from commit
|
||
---|---|---|
.. | ||
agents | ||
resources | ||
schedulers | ||
servers | ||
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_local_ip.py | ||
test_logging.py | ||
test_mtu.py | ||
test_ovs_dhcp_extension.py | ||
test_port_shut_down.py | ||
test_ports_api.py | ||
test_ports_binding.py | ||
test_ports_rebind.py | ||
test_qos.py | ||
test_quota.py | ||
test_securitygroup.py | ||
test_segmentation_id.py | ||
test_subnet.py | ||
test_trunk.py |
README
Please see neutron/TESTING.rst.