[Smartswitch] Stabilize the DPU kernel panic and memory exhaustion tests#22252
Merged
roy-sror merged 1 commit intosonic-net:masterfrom Mar 1, 2026
Merged
[Smartswitch] Stabilize the DPU kernel panic and memory exhaustion tests#22252roy-sror merged 1 commit intosonic-net:masterfrom
roy-sror merged 1 commit intosonic-net:masterfrom
Conversation
We should check the DPUs are offline before checking they are online after the kernel panic or memory exhaustion. Otherwise the check for DPU online could pass even before the DPUs are rebooted and the later crirical services check will fail. Signed-off-by: Cong Hou <congh@nvidia.com>
cdc474f to
6ca31ca
Compare
Contributor
Author
|
/azpw run |
Collaborator
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
nhe-NV
approved these changes
Feb 7, 2026
roy-sror
approved these changes
Mar 1, 2026
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Mar 2, 2026
…#22252) We should check the DPUs are offline before checking they are online after the kernel panic or memory exhaustion. Otherwise the check for DPU online could pass even before the DPUs are rebooted and the later crirical services check will fail. Signed-off-by: mssonicbld <sonicbld@microsoft.com>
Collaborator
|
Cherry-pick PR to 202511: #22691 |
Open
12 tasks
aronovic
pushed a commit
to aronovic/sonic-mgmt
that referenced
this pull request
Mar 3, 2026
…#22252) We should check the DPUs are offline before checking they are online after the kernel panic or memory exhaustion. Otherwise the check for DPU online could pass even before the DPUs are rebooted and the later crirical services check will fail. Signed-off-by: Mihut Aronovici <aronovic@cisco.com>
rraghav-cisco
pushed a commit
to rraghav-cisco/sonic-mgmt
that referenced
this pull request
Mar 3, 2026
…#22252) We should check the DPUs are offline before checking they are online after the kernel panic or memory exhaustion. Otherwise the check for DPU online could pass even before the DPUs are rebooted and the later crirical services check will fail. Signed-off-by: Raghavendran Ramanathan <rraghav@cisco.com>
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
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:
We should check the DPUs are offline before checking they are online after the kernel panic or memory exhaustion.
Otherwise the check for DPU online could pass even before the DPUs are rebooted and the later critical services check will fail.
Type of change
Back port request
Approach
What is the motivation for this PR?
Stabilize the DPU kernel panic and memory exhaustion tests
How did you do it?
Add a check for DPUs offline before the post_test_dpus_check in 2 test cases of test test_reload_dpu.py:
test_dpu_status_post_dpu_kernel_panic
test_dpu_check_post_dpu_mem_exhaustion
How did you verify/test it?
Run the test on SN4280 testbed.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation