[warm-reboot][multi-asic] Added error-handling for faulty ASIC/s after orchagent freeze#4297
Open
YairRaviv wants to merge 1 commit intosonic-net:masterfrom
Open
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…r orchagent freeze Signed-off-by: Yair Raviv <yraviv@nvidia.com>
YairRaviv
force-pushed
the
yraviv-warm-reboot-masic-error-handling
branch
from
f1f05f9 to
fd34414
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
oleksandrivantsiv
approved these changes
Feb 23, 2026
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
3 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.
What I did
Aligned the error-handling logic for warm/fast reboot on multi-ASIC devices
How I did it
FORCE var is set to "yes" on multi-ASIC devices before pausing orchagents.
I added a condition to "execute_in_namespace" function that in case of failures:
How to verify it
Tested on a multi-ASIC simulation, added manual failures, and verified the behavior
Previous command output (if the output of a command-line utility has changed)
New command output (if the output of a command-line utility has changed)