🐛 Log errors on specific log levels correctly

[sbueringer]

Signed-off-by: Stefan Büringer [email protected]

What this PR does / why we need it:
Was working on something new and realized that Errors are always logged independent of the configured log level.
So using log.V(4).Error(err, ), doesn't make sense as the errors are always logged...

godoc of the Error func:

// Error logs an error, with the given message and key/value pairs as context.
// It functions similarly to Info, but may have unique behavior, and should be
// preferred for logging errors (see the package documentations for more
// information). The log message will always be emitted, regardless of
// verbosity level.

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 #

[sbueringer]

/assign @chrischdi @fabriziopandini

[sbueringer]

/test pull-cluster-api-e2e-main

[fabriziopandini]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: a59018cbf5eb279f768ffe8ae1358c3ef1ab1aa7

[k8s-ci-robot]

[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:

• OWNERS [fabriziopandini]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[chrischdi]

/lgtm