-
Notifications
You must be signed in to change notification settings - Fork 214
status: Report the operators that have not yet deployed #158
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
Merged
openshift-merge-robot
merged 2 commits into
openshift:master
from
smarterclayton:display_partial_status
Apr 12, 2019
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
Next
Next commit
status: Report the operators that have not yet deployed
The current single error return strategy from the CVO sync loop predates parallel payload execution and limited retries. Instead, collect all errors from the task execution graph and attempt to synthesize better messages that describe what is actually happening. 1. Filter out cancellation error messages - they aren't useful and are a normal part of execution 2. When multiple errors are reported, display a reasonable multi-line error that summarizes any blockers 3. Treat ClusterOperatorNotAvailable as a special case - if all errors reported are of that type convert it to ClusterOperatorsNotAvailable and synthesize a better message 4. In the sync loop, if we are still making progress towards the update goal and we haven't waited too long for an update, and if the error is the specific cluster operator not available types, display the condition Progressing=True instead of Failing=true with a synthetic message. This also passes along the task with the UpdateError so that we can do more selective error messages for specific error cases.
- Loading branch information
commit c2ac20fa172da73a873d3e3728053a30af9cf4dc
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
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
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.
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.
ques: why create new
nestederror list?