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:

In RHCI we require the ability of the 'foreman' user to be able to read the logs generated by 'foreman-proxy'.

Currently the logs for /var/log/foreman-proxy are owned by:  foreman-proxy:foreman-proxy and they are 750.

We need 'foreman' to be able to read these logs.

In general, RHCI requests that the 'foreman' user has access to read all logs generated by Satellite-6.

Dmitri - does your work on exposing proxy status via the API can be an alternative to parsing log files?

Smart-proxy's log module provides access to smart-proxy logs. Those can be accessed via /log api end point.

Moving 6.2 bugs out to sat-backlog.

Since satellite 6.2 the smart proxy component has an API to return its logs, it can be visible under the infra -> capsules -> select the one you wish, assuming it has the proxy log feature enabled.

You may also parse this information via a plugin, or a rest api call to the proxy if you are developing a plugin on top of satellite.

I'm closing this due to the above, please re-open if you disagree. thanks!