Bug 1292865

Summary: [RFE] Allow 'foreman' user to read logs under '/var/log/foreman-proxy'
Product: Red Hat Satellite Reporter: John Matthews <jmatthew>
Component: UncategorizedAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.5CC: ddolguik, dgao, dmitri, jmontleo, ohadlevy, tsanders
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-18 09:20:57 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:
Bug Depends On:    
Bug Blocks: 1212602    

Description John Matthews 2015-12-18 15:05:24 UTC 
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.
Comment 1 Ohad Levy 2015-12-20 09:13:07 UTC 
Dmitri - does your work on exposing proxy status via the API can be an alternative to parsing log files?
Comment 2 Dmitri Dolguikh 2016-05-31 09:39:00 UTC 
Smart-proxy's log module provides access to smart-proxy logs. Those can be accessed via /log api end point.
Comment 3 Bryan Kearney 2016-07-26 19:07:51 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 4 Ohad Levy 2016-12-18 09:20:57 UTC 
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!