-
Notifications
You must be signed in to change notification settings - Fork 179
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
Fix manager tasks' status errors not being cleared on failed status updates for tasks present in manager state #2143
Fix manager tasks' status errors not being cleared on failed status updates for tasks present in manager state #2143
Conversation
@rzetelskik: GitHub didn't allow me to request PR reviews from the following users: rzetelskik. Note that only scylladb members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
…pdates for tasks present in manager state
0f4d6a8
to
66f8227
Compare
#2061 (comment) |
new flake #2145, unrelated |
/test images e2e-gke-parallel |
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.
lgtm
/assign tnozicka
#1028 (comment) /retest |
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rzetelskik, tnozicka, zimnx The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description of your changes: Manager task errors shouldn't be kept when building status for tasks existing in manager state and only cleared on status update, since if the status update fails, the error is retained even though the error no longer occurs. For tasks in manager state, if the error reappears, it will be propagated again. This bug is currently being covered by the logic comparing our spec with manager state (hot loop), but with #2143 this will no longer be the case, hence this is a prerequisite for #2143.
Which issue is resolved by this Pull Request:
Resolves #
/kind bug
/priority important-soon
/cc