[platform_tests/test_reload_config]: Respect overridden timeout#16031
Merged
arlakshm merged 3 commits intosonic-net:masterfrom Jan 2, 2025
Merged
[platform_tests/test_reload_config]: Respect overridden timeout#16031arlakshm merged 3 commits intosonic-net:masterfrom
arlakshm merged 3 commits intosonic-net:masterfrom
Conversation
* Respect overridden timeout for reboot in reload_configuration_checks_test * Replace plt_override option with wait_for_processes - will bail early after SSH is up if not set * Don't check all containers for t2 / modular chassis * Increase timeouts Signed-off-by: Liam Kearney <[email protected]>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
liamkearney-msft
requested review from
arlakshm,
auspham and
wenyiz2021
and removed request for
prgeor
Signed-off-by: Liam Kearney <[email protected]>
auspham
approved these changes
Dec 13, 2024
arlakshm
previously approved these changes
Dec 13, 2024
Contributor
|
/Azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
8 tasks
Collaborator
|
Please share the test result for non-chassis platforms. The other PR #15951 caused regression on non-chassis platform |
Contributor
Author
|
Hi @bingwang-ms, please see attached pass run on t1: |
liamkearney-msft
dismissed stale reviews from arlakshm and yejianquan
via
10fda92
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
arlakshm
approved these changes
Jan 2, 2025
nnelluri-cisco
pushed a commit
to nnelluri-cisco/sonic-mgmt
that referenced
this pull request
Mar 15, 2025
…c-net#16031) Approach What is the motivation for this PR? There are various failures seen on nokia 7250 / arista 7800 / modular chassis DUTs for test_reload_config tests. Generally, they can be attributed to two things: too short of a timeout for t2 chassis, and the new docker status check. How did you do it? This PR refactors some logic in the reboot command, such that it will now respect overwritten values for the reboot timeout in the inventory file (so that SKU specific tweaks can be properly specified), and also repurposes the plt_reboot_ctrl_overwrite parameter to return_after_reconnect, which if set will cause the reboot function to return early after SSH comes back up, which is more in the spirit of how the test functions. Additionally, some timeouts have been increased for this testcase, as t2 requires more time for services to come up. Finally, the docker status check has been skipped for modular_chassis DUTs. How did you verify/test it? Ran on Nokia 7250 and Arista 7800 chassis --------- Signed-off-by: Liam Kearney <[email protected]>
rajkumar1-arista
added a commit
to rajkumar1-arista/sonic-mgmt
that referenced
this pull request
Jun 11, 2025
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031
rajkumar1-arista
added a commit
to rajkumar1-arista/sonic-mgmt
that referenced
this pull request
Jun 11, 2025
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031
11 tasks
wangxin
pushed a commit
that referenced
this pull request
Jun 12, 2025
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in #16031
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jul 3, 2025
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031
11 tasks
mssonicbld
pushed a commit
that referenced
this pull request
Jul 3, 2025
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in #16031
nissampa
pushed a commit
to nissampa/sonic-mgmt_dpu_test
that referenced
this pull request
Aug 7, 2025
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031 Signed-off-by: opcoder0 <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031 Signed-off-by: Guy Shemesh <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031 Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031 Signed-off-by: Guy Shemesh <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031 Signed-off-by: Guy Shemesh <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031 Signed-off-by: Yael Tzur <[email protected]>
Pterosaur
pushed a commit
to Pterosaur/sonic-mgmt
that referenced
this pull request
Mar 26, 2026
…c-net#16031) Approach What is the motivation for this PR? There are various failures seen on nokia 7250 / arista 7800 / modular chassis DUTs for test_reload_config tests. Generally, they can be attributed to two things: too short of a timeout for t2 chassis, and the new docker status check. How did you do it? This PR refactors some logic in the reboot command, such that it will now respect overwritten values for the reboot timeout in the inventory file (so that SKU specific tweaks can be properly specified), and also repurposes the plt_reboot_ctrl_overwrite parameter to return_after_reconnect, which if set will cause the reboot function to return early after SSH comes back up, which is more in the spirit of how the test functions. Additionally, some timeouts have been increased for this testcase, as t2 requires more time for services to come up. Finally, the docker status check has been skipped for modular_chassis DUTs. How did you verify/test it? Ran on Nokia 7250 and Arista 7800 chassis --------- Signed-off-by: Liam Kearney <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
reboot call is still using the outdated argument `plt_reboot_ctrl_overwrite` instead of `return_after_reconnect` that was introduced in sonic-net#16031
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
There are various failures seen on nokia 7250 / arista 7800 / modular chassis DUTs for test_reload_config tests. Generally, they can be attributed to two things: too short of a timeout for t2 chassis, and the new docker status check.
How did you do it?
This PR refactors some logic in the reboot command, such that it will now respect overwritten values for the reboot timeout in the inventory file (so that SKU specific tweaks can be properly specified), and also repurposes the
plt_reboot_ctrl_overwriteparameter toreturn_after_reconnect, which if set will cause the reboot function to return early after SSH comes back up, which is more in the spirit of how the test functions.Additionally, some timeouts have been increased for this testcase, as t2 requires more time for services to come up.
Finally, the docker status check has been skipped for modular_chassis DUTs.
How did you verify/test it?
Ran on Nokia 7250 and Arista 7800 chassis
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation