-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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: don't set crbResult to nil if the error is already exists #122900
Conversation
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/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pacoxu 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 |
e9b969a
to
c35b12a
Compare
/cc @danwinship @SataQiu |
I prefer the fix in #122901. kubernetes/cmd/kubeadm/app/phases/kubeconfig/kubeconfig.go Lines 698 to 702 in a07b1aa
With #122893, the code above is not correct anymore. |
Yeah, I think it now doesn't work as expected; I filed #122906 to fix that |
/close |
@pacoxu: Closed this PR. In 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 type of PR is this?
/kind bug
/kind failing-test
What this PR does / why we need it:
error handling crb existing
Which issue(s) this PR fixes:
Fixes kubernetes/kubeadm#3000 #122901
Special notes for your reviewer:
#122893 was merged yesterday to fix the test with #122892.
If EnsureAdminClusterRoleBindingImpl now works as expected, we should handle the existing error in post upgrade progress to make it pass.
Does this PR introduce a user-facing change?