Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( 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 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 "", 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.
Bug 1738784 - foreman-proxy-log JOURNAL option should install foreman-proxy-journald
Summary: foreman-proxy-log JOURNAL option should install foreman-proxy-journald
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: 6.6.0
Assignee: Ewoud Kohl van Wijngaarden
QA Contact: Devendra Singh
Depends On:
TreeView+ depends on / blocked
Reported: 2019-08-08 07:35 UTC by Stephen Wadeley
Modified: 2019-10-22 19:48 UTC (History)
2 users (show)

Fixed In Version: foreman-installer-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-10-22 19:48:03 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27552 0 Normal Closed foreman-proxy-log JOURNAL option should install foreman-proxy-journald 2020-04-07 12:49:41 UTC

Description Stephen Wadeley 2019-08-08 07:35:13 UTC
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

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

Additional info:

Comment 2 Stephen Wadeley 2019-08-08 11:10:00 UTC

Docs for 6.6 beta will say to install it.

DocsBug Bug 1738850 - Logging to journald and rsyslog

Comment 3 Ewoud Kohl van Wijngaarden 2019-08-08 14:47:15 UTC
Created redmine issue from this bug

Comment 4 Bryan Kearney 2019-08-08 16:06:23 UTC
Upstream bug assigned to ekohlvan

Comment 5 Bryan Kearney 2019-08-08 16:06:24 UTC
Upstream bug assigned to ekohlvan

Comment 6 Bryan Kearney 2019-08-09 14:06:31 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue has been resolved.

Comment 7 Devendra Singh 2019-09-04 15:07:16 UTC
This bug has successfully verified in 6.6.0 Snap18.

foreman installer version: foreman-installer-
Satellite installer version: satellite-installer-

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.

* foreman-proxy-journald package installer successfully.

# rpm -q foreman-proxy-journald

Comment 9 Bryan Kearney 2019-10-22 19:48:03 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, and where to find the updated
files, follow the link below.

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

Note You need to log in before you can comment on or make changes to this bug.