MGMT-17388: Log string literal format shown with "special" characters

[jgyselov]

https://issues.redhat.com/browse/MGMT-17388

Replacing \n with a space is probably the best we can do here.

[openshift-ci-robot]

@jgyselov: This pull request references MGMT-17388 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set.

In response to this:

https://issues.redhat.com/browse/MGMT-17388

Replacing \n with a space is probably the best we can do here.

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 openshift-eng/jira-lifecycle-plugin repository.

[celdrake]

Did you consider splitting the message in the new line and creating a div / li per item?

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ammont82, celdrake, jgyselov

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[jgyselov]

Did you consider splitting the message in the new line and creating a div / li per item?

I did consider it. But given how rare \n appearing seems to be (I've only seen this one instance in this screenshot), I don't think it's worth it.

[openshift-ci]

New changes are detected. LGTM label has been removed.