[CrashRecover] Disable failing step based on failed boot count#1740
Merged
TD-er merged 1 commit intoletscontrolit:megafrom Sep 13, 2018
Merged
[CrashRecover] Disable failing step based on failed boot count#1740TD-er merged 1 commit intoletscontrolit:megafrom
TD-er merged 1 commit intoletscontrolit:megafrom
Conversation
When the node gets locked in a boot loop, the only recovery is to erase it and start all over. This fix will count the number of failed boots and above a certain threshold it will start disabling plugin, then controller and then notification. Only one will be disabled at once, so the user can see which one is giving issues. The disabled state will not be saved, so make sure to save the failing part when it is accessible again.
TD-er
added
Category: UX
Member
Author
|
This is also addressing #1616 |
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
1 participant
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.
When the node gets locked in a boot loop, the only recovery is to erase it and start all over.
This fix will count the number of failed boots and above a certain threshold it will start disabling plugin, then controller and then notification.
Only one will be disabled at once, so the user can see which one is giving issues.
The disabled state will not be saved, so make sure to save the failing part when it is accessible again.