-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 MHC should not remediate paused machines #3444
🌱 MHC should not remediate paused machines #3444
Conversation
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.
Thanks! Can we add a test as well?
4b9fd22
to
72f0d75
Compare
/test pull-cluster-api-verify |
changes lgtm pending @vincepri's request for a test |
Do we actually want to mark it with |
72f0d75
to
ec88094
Compare
I think that's the right thing, so I've updated the implementation to do so |
/milestone v0.3.9 |
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.
@benmoss thanks for this PR!
/test pull-cluster-api-test |
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
/assign @detiber @fabriziopandini
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri 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 |
/lgtm |
/retest |
/test pull-cluster-api-test |
What this PR does / why we need it:
Right now the MHC controller only checks if the MHC object itself or the Cluster is paused. It seems reasonable users would expect that pausing a machine would also pause remediation on it.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #3421
In #3108 I unintentionally changed the logic here to return when we encounter an error patching one of the machines, instead of the prior behavior of continuing to try to remediate all of the machines before returning an error collection. This also brings back that logic.