-
Notifications
You must be signed in to change notification settings - Fork 40k
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
kubeadm: fix a bug where the RemoveMember function did not return the correct member list when the member to be removed did not exist #127650
Conversation
… correct member list when the member to be removed did not exist
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SataQiu 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 |
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
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
the unit tests might need to be improved in the future to catch problems like this. i believe etcd have a mock server/client that can be used. cc @my-git9 you might be interested.
LGTM label has been added. Git tree hash: 06df3b57c832596025db59dfe772c8b71f840b22
|
/release-note-edit
|
…650-upstream-release-1.31 Automated cherry pick of #127650: kubeadm: fix a bug where the RemoveMember function did not return the correct member list when the member to be removed did not exist
…650-upstream-release-1.29 Automated cherry pick of #127650: kubeadm: fix a bug where the RemoveMember function did not return the correct member list when the member to be removed did not exist
…650-upstream-release-1.30 Automated cherry pick of #127650: kubeadm: fix a bug where the RemoveMember function did not return the correct member list when the member to be removed did not exist
…650-upstream-release-1.28 Automated cherry pick of #127650: kubeadm: fix a bug where the RemoveMember function did not
What type of PR is this?
/kind bug
What this PR does / why we need it:
kubeadm: fix a bug where the
RemoveMember
function did not return the correct member list when the member to be removed did not existWhich issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
We don't actually use the member list returned by
RemoveMember
, just to print debug messages:kubernetes/cmd/kubeadm/app/phases/etcd/local.go
Lines 129 to 133 in 9770283
So the cherry-pick doesn't seem to make much sense.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: