-
Notifications
You must be signed in to change notification settings - Fork 5
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
reboot operation #11
Merged
reboot operation #11
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
388d2db
reboot operation
prinikasn b047255
remove redundant type
prinikasn 4010425
update reboot func
prinikasn 4cb807b
update comment for Execute fun
prinikasn c601aa3
update reboot command
prinikasn 4afb071
remove cancelreboot, not used
prinikasn 28f104f
address comments
prinikasn 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 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
This file contains 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
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.
I think we just drop this and always ignore UnavailableErrors when waiting for active
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.
hmmm.. is UnavailableError always acceptable after reboot?
Having a function to ignore the error gives the flexibility to ignore errors based on the usecase.
I do see a test here which performs a reboot and expects error to be nil -> https://github.com/openconfig/featureprofiles/blob/main/feature/gnoi/system/tests/chassis_reboot_status_and_cancel_test/chassis_reboot_status_and_cancel_test.go#L168
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.
Yeah, I see the pros and cons. Three comments:
First, It just seems to me that the likelihood that we would see an unexpected Unavailable error it is very low, especially given that the prior RebootRequest must have succeeded by then. Other errors would obviously still be reported.
Second, almost all uses of
WaitForActive(true)
is going to want to be accompanied byIgnoreUnavailableErr(true)
, because nearly all will be rebooting the chassis, and if not that the management linecard. So I feel likeIgnoreUnavailableErr(true)
is going to be one of these lines people just copy and paste everywhere anyway, regardless of whether they need it, because that's what most calls look like.Third, I'm holding out some hope that we can extend the
RebootRequestResponse
to makeIgnoreUnavailableErr
eventually unnecessary. I'm going to be starting a thread on the OpenConfig chat about that.Due to those three, I was feeling like IgnoreUnavailableErr maybe isn't offering enough to pull its weight. All that said, I still see the reasons for including it, so I'm fine with you leaving it in if you prefer to keep it.