-
Notifications
You must be signed in to change notification settings - Fork 221
[smartswitch][chassisd] Fix missing DPU reboot cause when config-reload interrupts DPU reboot #771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
vvolam
wants to merge
14
commits into
sonic-net:master
Choose a base branch
from
vvolam:fix-reboot-cause-config-reload
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 12 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
891ea92
[chassisd] Persist DPU reboot cause on EMPTY-to-Offline transition
vvolam e9d2092
[chassisd] Defer DPU reboot-cause query to online transition
vvolam 1371c10
[chassisd] Skip duplicate reboot cause on back-to-back DPU reboot
vvolam ea91b57
Merge remote-tracking branch 'origin/master' into fix-reboot-cause-co…
vvolam 346bda2
Merge remote-tracking branch 'origin/master' into fix-reboot-cause-co…
vvolam 2cff182
[chassisd] Fix spurious reboot-cause persist on EMPTY→ONLINE transition
vvolam a6fb958
[chassisd] Replace timeout-based is_reboot with reboot-time comparison
vvolam 5e7c0ab
Merge remote-tracking branch 'origin/master' into fix-reboot-cause-co…
vvolam 917266a
[chassisd] Add testbed script for DPU reboot cause persistence
vvolam 1627248
[chassisd] Fix same-cause reboot not persisted in deferred='restart' …
vvolam f23e6a4
[chassisd] Improve readability: transition predicates, named constants
vvolam 15d07b5
[chassisd] Remove prev_reboot_time.txt generation from chassisd
vvolam 5403e81
[chassisd] Add fallback prev_reboot_time.txt generation for spontaneo…
vvolam 5e726a2
[chassisd] Move testbed script to separate PR
vvolam File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vvolum IMO this can be handled with a minimal addition in the existing module_db_update() logic itself.
Today, module_db_update() already:
The new EMPTY→Offline case is simply another transition condition in that same flow.
The helper functions introduced in this PR ultimately still reduce to checking:
That does not require introducing a new transition framework, deferred reboot-cause processing, or restructuring the existing reboot-cause handling model.
A couple of targeted lines in the existing transition handling path should be sufficient while preserving the current Online→Offline reboot-cause persistence semantics and overall design behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rameshraghupathy after our discussion in the meeting offline, do you have any other suggestions?