-
Notifications
You must be signed in to change notification settings - Fork 463
Bug 2035005: Move removeUpdateInProgressTaint functionality to mcc #3064
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
Bug 2035005: Move removeUpdateInProgressTaint functionality to mcc #3064
Conversation
|
@ravisantoshgudimetla: This pull request references Bugzilla bug 2035005, which is invalid:
Comment DetailsIn 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/test-infra repository. |
yuqi-zhang
left a comment
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.
First pass looks good. Did you get a chance to test in-cluster?
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.
This is fine, but for consistency purposes, maybe we can add a check above for
if !checkIfNodeHasInProgressTaint(oldNode) {
return nil
}
instead?
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.
Removed this block considering we have a check here.
c1121a4 to
9c5839f
Compare
soltysh
left a comment
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
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.
Should we also move this check out? i.e. in the sync code, have:
if node.Annotations[daemonconsts.DesiredMachineConfigAnnotationKey] != targetConfig && !checkIfNodeHasInProgressTaint(node)
just to keep the two functions consistent
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.
Yup we can do that.
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.
Done.
9c5839f to
221229b
Compare
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.
Not sure changing this is actually clearer, but when I read this I had to think it out more like:
| if node.Annotations[daemonconsts.DesiredMachineConfigAnnotationKey] != targetConfig && !checkIfNodeHasInProgressTaint(node) { | |
| if err := ctrl.setUpdateInProgressTaint(ctx, node.Name); err != nil { | |
| return goerrs.Wrapf(err, "failed applying %s taint for node %s", constants.NodeUpdateInProgressTaint.Key, node.Name) | |
| } | |
| } else if node.Annotations[daemonconsts.DesiredMachineConfigAnnotationKey] == targetConfig && checkIfNodeHasInProgressTaint(node) { | |
| if err := ctrl.removeUpdateInProgressTaint(ctx, node.Name); err != nil { | |
| return goerrs.Wrapf(err, "failed removing %s taint for node %s", constants.NodeUpdateInProgressTaint.Key, node.Name) | |
| } | |
| hasInProgressTaint := checkIfNodeHasInProgressTaint(node) | |
| if node.Annotations[daemonconsts.DesiredMachineConfigAnnotationKey] == pool.Spec.Configuration.Name { | |
| if hasInProgressTaint { | |
| if err := ctrl.removeUpdateInProgressTaint(ctx, node.Name); err != nil { | |
| return goerrs.Wrapf(err, "failed removing %s taint for node %s", constants.NodeUpdateInProgressTaint.Key, node.Name) | |
| } | |
| } | |
| } else { | |
| if !hasInProgressTaint { | |
| if err := ctrl.setUpdateInProgressTaint(ctx, node.Name); err != nil { | |
| return goerrs.Wrapf(err, "failed applying %s taint for node %s", constants.NodeUpdateInProgressTaint.Key, node.Name) | |
| } | |
| } | |
| } |
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.
Done.
|
lgtm, but will let @yuqi-zhang take a final look |
|
@mkenigs - Thanks for the reviews. I'll try to address them shortly. @yuqi-zhang any other functional comments, if not I'd like to get this merged? |
|
Looks good otherwise |
221229b to
1719277
Compare
|
@yuqi-zhang - Please tag when you find time. |
1719277 to
ddb702b
Compare
yuqi-zhang
left a comment
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
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/bugzilla refresh Recalculating validity in case the underlying Bugzilla bug has changed. |
|
@openshift-bot: This pull request references Bugzilla bug 2035005, which is invalid:
Comment DetailsIn 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/test-infra repository. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/bugzilla refresh Recalculating validity in case the underlying Bugzilla bug has changed. |
|
@openshift-bot: This pull request references Bugzilla bug 2035005, which is invalid:
Comment DetailsIn 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/test-infra repository. |
ddb702b to
b490360
Compare
|
/bugzilla refresh |
|
@yuqi-zhang: This pull request references Bugzilla bug 2035005, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla ([email protected]), skipping review request. DetailsIn 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/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ravisantoshgudimetla, soltysh, yuqi-zhang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@ravisantoshgudimetla: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
@ravisantoshgudimetla: All pull requests linked via external trackers have merged: Bugzilla bug 2035005 has been moved to the MODIFIED state. DetailsIn 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/test-infra repository. |
|
/cherrypick release-4.10 |
|
@ravisantoshgudimetla: #3064 failed to apply on top of branch "release-4.10": DetailsIn 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/test-infra repository. |
- What I did
Move removeUpdateInProgressTaint functionality to mcc so that MCD is relieved of this job. The unit tests are updated as well. This was introduced in #2686
- How to verify it
- Description for the changelog