Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

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

Upstream bug assigned to aruzicka

Upstream bug assigned to aruzicka

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

Verified on Sat 6.9 sn 3

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