🌱 Improve Machine remediation logs

[fabriziopandini]

What this PR does / why we need it:
This PR improve logs added when a machine is remediated by adding key value pair for Machine ns/name and another for the node name, while dropping the key "target" which contained a confusing "MHC.Namespace/MHC.Name/Machine.Name/Node.Name".

Also, message now uses a more intuitive "Machine has failed health check..." instead of "Target has failed health check"

/area machinehalthcheck

[k8s-ci-robot]

@fabriziopandini: The label(s) area/machinehalthcheck cannot be applied, because the repository doesn't have them.

In response to this:

What this PR does / why we need it:
This PR improve logs added when a machine is remediated by adding key value pair for Machine ns/name and for the node, while dropping the key "target" which contained a confusing "MHC.Namespace/MHC.Name/Machine.Name/Node.Name".

Also, message now uses a more intuitive "Machine has failed health check..." instead of "Target has failed health check"

/area machinehalthcheck

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.

[sbueringer]

Thx!

/lgtm

/assign @chrischdi

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 23f3bf9897456a7455a60ef1260957d1a8c48ff8

[chrischdi]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi

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 [chrischdi]

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

[fabriziopandini]

/cherry-pick release-1.9

[fabriziopandini]

/cherry-pick release-1.8

[k8s-infra-cherrypick-robot]

@fabriziopandini: new pull request created: #11706

In response to this:

/cherry-pick release-1.9

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.

[k8s-infra-cherrypick-robot]

@fabriziopandini: #11692 failed to apply on top of branch "release-1.8":

Applying: Improve Machine remediation logs
Using index info to reconstruct a base tree...
M	internal/controllers/machinehealthcheck/machinehealthcheck_controller.go
Falling back to patching base and 3-way merge...
Auto-merging internal/controllers/machinehealthcheck/machinehealthcheck_controller.go
CONFLICT (content): Merge conflict in internal/controllers/machinehealthcheck/machinehealthcheck_controller.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Improve Machine remediation logs

In response to this:

/cherry-pick release-1.8

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.