Issue Type
Bug Report
Description
In container_checker.py fixture config_reload_after_tests, on teardown performs config reload (with bgp check enabled) on DUTs in selected_rand_one_per_hwsku_hostname successively, this causes test failures (see below).
Issue Details
When more than 1 DUT is being reloaded, because this test brings down swss/syncd containers, the iBGP neighbors of the earlier DUTs being reloaded will not be able to come up, as the other DUTs swss containers are still down. This causes the test to fail.
Impact or Proposed Behavior
When more than 1 DUTs are successively called to config reload with BGP check, test fails because earlier DUTs are unable to establish iBGP sessions with DUTs that haven't been config reloaded.
DUTs should reload in parallel, allowing all iBGP neighbors to come up.
Importance or Severity
Low
Is it platform specific
generic
Relevant log output
Output of show version
Attach files (if any)
N/A
Issue Type
Bug Report
Description
In
container_checker.pyfixtureconfig_reload_after_tests, on teardown performs config reload (with bgp check enabled) on DUTs inselected_rand_one_per_hwsku_hostnamesuccessively, this causes test failures (see below).Issue Details
When more than 1 DUT is being reloaded, because this test brings down swss/syncd containers, the iBGP neighbors of the earlier DUTs being reloaded will not be able to come up, as the other DUTs swss containers are still down. This causes the test to fail.
Impact or Proposed Behavior
When more than 1 DUTs are successively called to config reload with BGP check, test fails because earlier DUTs are unable to establish iBGP sessions with DUTs that haven't been config reloaded.
DUTs should reload in parallel, allowing all iBGP neighbors to come up.
Importance or Severity
Low
Is it platform specific
generic
Relevant log output
Output of
show versionAttach files (if any)
N/A