-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🐛 fix panic in clusterctl backup #5050
🐛 fix panic in clusterctl backup #5050
Conversation
/assign @fabriziopandini |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
@@ -366,7 +366,7 @@ func (o *objectMover) backup(graph *objectGraph, directory string) error { | |||
moveSequence := getMoveSequence(graph) | |||
|
|||
// Save all objects group by group | |||
log.Info("Saving files to %s", directory) | |||
log.Info(fmt.Sprintf("Saving files to %s", directory)) |
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.
Does this logger not have Infof
?
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.
For future reference, let's make sure that PR titles have more explicit information, like Fix panic in logger not using string interpolation ....
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.
Yup will do. The logger has no Infof func (it's the go-logr/logr.Logger interface)
What this PR does / why we need it:
Without this change clusterctl backup panics because of an uneven amount of key-value arguments. The unit test didn't catch this as it's using the
NullLogger
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #