-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Prevent removing etcd member when running in check mode #8570
Prevent removing etcd member when running in check mode #8570
Conversation
Hi @fungusakafungus. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
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.
@fungusakafungus rofl.. that's a weird bug indeed :/
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, fungusakafungus 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 |
There's a similar issue in the etcd cert generation:
My guess is that that's just a copy and paste error from the task immediately above, where ignoring check mode makes sense. I checked the rest of the codebase (searched via |
I'll submit that fix separately |
Weird bug indeed. /ok-to-test |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Fixes removing etcd node when running with
--check
. Before, running remove-node playbook on an etcd node with--check
will happily remove the node. That's the opposite of how--check
is supposed to work. This seems to be a copy-paste issue(introduced in https://github.com/kubernetes-sigs/kubespray/pull/5009/files#diff-84b588aaf686ff2f99d525c4269b48f766a3bc074f4cb34bd381918a43fb2ab1R23-R54), so I'm also removing other irrelevant lines.Which issue(s) this PR fixes:
Special notes for your reviewer:
check_mode docs: https://docs.ansible.com/ansible/latest/user_guide/playbooks_checkmode.html#enforcing-or-preventing-check-mode-on-tasks
Does this PR introduce a user-facing change?: