Hide Forgot
Description of problem: The foreman-proxy-journald package is not installed when you run installer with this option: --foreman-proxy-log JOURNAL but it is required to make use of logging to journald. Version-Release number of selected component (if applicable): ~]# rpm -q satellite-installer satellite-installer-6.6.0.19-1.beta.el7sat.noarch How reproducible: Steps to Reproduce: 1. satellite-installer --foreman-proxy-log JOURNAL 2. rpm -q foreman-proxy-journald Actual results: ~]# rpm -q foreman-proxy-journald package foreman-proxy-journald is not installed Expected results: ~]# rpm -q foreman-proxy-journald foreman-proxy-journald-1.22.0.1-1.el7sat.noarch Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=1163020#c18
Hello Docs for 6.6 beta will say to install it. DocsBug Bug 1738850 - Logging to journald and rsyslog
Created redmine issue https://projects.theforeman.org/issues/27552 from this bug
Upstream bug assigned to ekohlvan
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27552 has been resolved.
This bug has successfully verified in 6.6.0 Snap18. foreman installer version: foreman-installer-1.22.0.10-1.el7sat.noarc Satellite installer version: satellite-installer-6.6.0.19-2.el7sat.noarch Verified Point: * Perform installation of foreman-proxy-log with JOURNAL and it was done successfully. # satellite-installer --foreman-proxy-log JOURNAL Package versions are locked. Continuing with unlock. Installing Done [100%] [......................................................................................................] Package versions are being locked. Success! * foreman-proxy-journald package installer successfully. # rpm -q foreman-proxy-journald foreman-proxy-journald-1.22.0.2-1.el7sat.noarch
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, 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-2019:3172