Skip to content

[action] [PR:20095] [dualotr] Fix disruptions after config reload#20137

Merged
mssonicbld merged 1 commit intosonic-net:202505from
mssonicbld:cherry/202505/20095
Aug 8, 2025
Merged

[action] [PR:20095] [dualotr] Fix disruptions after config reload#20137
mssonicbld merged 1 commit intosonic-net:202505from
mssonicbld:cherry/202505/20095

Conversation

@mssonicbld
Copy link
Copy Markdown
Collaborator

The device could be unstable after config reload, which results in possible packet drop and test failure.
Let's wait for more time after config reload.
And decrease the I/O verification time to 60s to reduce the test runtime.

Description of PR

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
  • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505

Approach

What is the motivation for this PR?

The device could be unstable after config reload, which results in
possible packet drop and test failure.
Let's wait for more time after config reload.
And decrease the I/O verification time to 60s to reduce the test runtime.

Signed-off-by: Longxiang Lyu <[email protected]

How did you do it?

Reload with safe_reload and wait_for_bgp to allow the DUT to recover.

How did you verify/test it?

dualtor_io/test_link_failure.py::test_active_link_admin_down_config_reload_downstream[active-active-1-10] PASSED [ 10%]
dualtor_io/test_link_failure.py::test_active_link_admin_down_config_reload_downstream[active-active-2-10] PASSED [ 20%]
dualtor_io/test_link_failure.py::test_active_link_admin_down_config_reload_downstream[active-active-3-10] PASSED [ 30%]
dualtor_io/test_link_failure.py::test_active_link_admin_down_config_reload_downstream[active-active-4-10] PASSED [ 40%]
dualtor_io/test_link_failure.py::test_active_link_admin_down_config_reload_downstream[active-active-5-10] PASSED [ 50%]
dualtor_io/test_link_failure.py::test_active_link_admin_down_config_reload_downstream[active-active-6-10] PASSED [ 60%]
dualtor_io/test_link_failure.py::test_active_link_admin_down_config_reload_downstream[active-active-7-10] PASSED [ 70%]
dualtor_io/test_link_failure.py::test_active_link_admin_down_config_reload_downstream[active-active-8-10] PASSED [ 80%]
dualtor_io/test_link_failure.py::test_active_link_admin_down_config_reload_downstream[active-active-9-10] PASSED [ 90%]
dualtor_io/test_link_failure.py::test_active_link_admin_down_config_reload_downstream[active-active-10-10] PASSED [100%]

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

The device could be unstable after config reload, which results in
possible packet drop and test failure.
Let's wait for more time after config reload.
And decrease the I/O verification time to 60s to reduce the test runtime.

Signed-off-by: Longxiang Lyu <[email protected]>
@mssonicbld
Copy link
Copy Markdown
Collaborator Author

Original PR: #20095

@mssonicbld
Copy link
Copy Markdown
Collaborator Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld mssonicbld merged commit 150b361 into sonic-net:202505 Aug 8, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants