Skip to content
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 1804738: Ensure DeleteNodes doesn't delete a node twice #125

Merged
merged 1 commit into from
Feb 20, 2020

Conversation

JoelSpeed
Copy link

I have seen the autoscaler call DeleteNodes several times while a node it is trying to delete has not been fully deleted (finalizer still present). Currently, it does not check if the node's Machine has already been deleted and blindly reduces the size of the node group by 1 on every call to DeleteNodes

This PR adds a check, so that if a node's Machine already has a deletion timestamp, we do not decrease the size of the node group any further

I've added a test that calls the DeleteNodes twice and expects the node group size to not decrease on the second call, which passes with the fix, and fails without

@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 19, 2020
@enxebre
Copy link
Member

enxebre commented Feb 19, 2020

cc @bison @frobware

@enxebre
Copy link
Member

enxebre commented Feb 19, 2020

/hold
until we get a bz
/cherry-pick release-4.4
/cherry-pick release-4.3

@openshift-cherrypick-robot

@enxebre: once the present PR merges, I will cherry-pick it on top of release-4.4 in a new PR and assign it to you.

In response to this:

/hold
until we get a bz
/cherry-pick release-4.4
/cherry-pick release-4.3

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.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 19, 2020
@JoelSpeed JoelSpeed changed the title Ensure DeleteNodes doesn't delete a node twice BUG 1804738: Ensure DeleteNodes doesn't delete a node twice Feb 19, 2020
@openshift-ci-robot
Copy link

@JoelSpeed: This pull request references Bugzilla bug 1804738, which is invalid:

  • expected the bug to target the "4.5.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

BUG 1804738: Ensure DeleteNodes doesn't delete a node twice

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.

@openshift-ci-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Feb 19, 2020
@alexander-demicev
Copy link

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Feb 19, 2020
@openshift-ci-robot
Copy link

@alexander-demichev: This pull request references Bugzilla bug 1804738, 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.

In response to this:

/bugzilla refresh

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.

@openshift-ci-robot openshift-ci-robot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Feb 19, 2020
@enxebre
Copy link
Member

enxebre commented Feb 19, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 19, 2020
@enxebre
Copy link
Member

enxebre commented Feb 19, 2020

lgtm PTAL @frobware, would like your blessing here

@enxebre
Copy link
Member

enxebre commented Feb 20, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2020
@enxebre
Copy link
Member

enxebre commented Feb 20, 2020

thanks! @JoelSpeed please make sure to follow up with the cherry-picks

@JoelSpeed
Copy link
Author

/retest

@openshift-merge-robot openshift-merge-robot merged commit 5ae305a into openshift:master Feb 20, 2020
@openshift-ci-robot
Copy link

@JoelSpeed: All pull requests linked via external trackers have merged. Bugzilla bug 1804738 has been moved to the MODIFIED state.

In response to this:

BUG 1804738: Ensure DeleteNodes doesn't delete a node twice

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.

@openshift-cherrypick-robot

@enxebre: new pull request created: #128

In response to this:

/hold
until we get a bz
/cherry-pick release-4.4
/cherry-pick release-4.3

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.

@JoelSpeed JoelSpeed deleted the idempotent-delete branch February 20, 2020 11:27
@JoelSpeed
Copy link
Author

/cherry-pick release-4.3

@openshift-cherrypick-robot

@JoelSpeed: new pull request created: #129

In response to this:

/cherry-pick release-4.3

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.

@frobware
Copy link

lgtm PTAL @frobware, would like your blessing here

Yep, sorry (github outage yesterday). I did have one minor nit, but not important now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants