Bug 1851379

Summary:	Smart proxy dynflow core logs are missing newlines
Product:	Red Hat Satellite	Reporter:	Adam Ruzicka <aruzicka>
Component:	Tasks Plugin	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	aruzicka
Target Milestone:	6.9.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-smart_proxy_dynflow_core-0.3.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-21 13:15:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Ruzicka 2020-06-26 11:48:11 UTC

Description of problem:
Logs in /var/log/foreman-proxy/smart_proxy_dynflow_core.log seem to be missing readlines, the log is hard to follow.


Version-Release number of selected component (if applicable):
rubygem-smart_proxy_dynflow-0.2.4-5


How reproducible:
Always


Steps to Reproduce:
1. Bump smart proxy dynflow core log level to debug in /etc/smart_proxy_dynflow_core/settings.yml
2. Restart smart_proxy_dynflow_core service
3. Run for example a REX job
4. Watch the log file

Actual results:
Especially output from dynflow itself (step plan changes and so on) are printed without newlines, leading to unreadable long lines.


Expected results:
Each log message ends if a newline


Additional info:

Comment 1 Adam Ruzicka 2020-07-01 13:17:06 UTC

Created redmine issue http://projects.theforeman.org/issues/30278 from this bug

Comment 2 Bryan Kearney 2020-07-04 20:03:39 UTC

Upstream bug assigned to aruzicka

Comment 3 Bryan Kearney 2020-07-04 20:03:41 UTC

Upstream bug assigned to aruzicka

Comment 4 Bryan Kearney 2020-09-09 12:04:05 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30278 has been resolved.

Comment 5 Peter Ondrejka 2020-11-26 15:14:17 UTC

Verified on Sat 6.9 sn 3

Comment 8 errata-xmlrpc 2021-04-21 13:15:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1313