-
Notifications
You must be signed in to change notification settings - Fork 38.9k
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 dump backtrace on reset #73951
Conversation
The current code logs an error and full blown backtrace if we fail to remove the containers upon reset. This creates unneeded, huge and rather scary log message. Fix that by leaving just the error message. Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>
@fabriziopandini @timothysc I wonder if this is worthy of cherry-picking in 1.12 and 1.13? |
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
/approve
/retest |
@rosti thanks |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, neolit123, rosti 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The current code logs an error and full blown backtrace if we fail to remove
the containers upon reset. This creates unneeded, huge and rather scary log
message. Fix that by leaving just the error message.
Which issue(s) this PR fixes:
Fixes kubernetes/kubeadm#1404
Special notes for your reviewer:
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews
/area kubeadm
/assign @neolit123
/cc @chuckha
Does this PR introduce a user-facing change?: