Bug 1305981

Summary: [RHCeph 1.3.2] rgw logs in '/var/log/radosgw/
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasu Kulkarni <vakulkar>
Component: Ceph-InstallerAssignee: Boris Ranto <branto>
Status: CLOSED ERRATA QA Contact: Vasu Kulkarni <vakulkar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.3.2CC: adeza, aschoen, ceph-eng-bugs, flucifre, hnallurv, nthomas, sankarshan
Target Milestone: rc   
Target Release: 1.3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-0.94.5-9.el7cp Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-29 14:46:09 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:

Description Vasu Kulkarni 2016-02-09 17:38:32 UTC 
Description of problem:

rgw logs in /var/log/radosgw instead of /var/log/ceph/radosgw

From bz1303799

issues noticed by borris

2.) You do store rgw logs in '/var/log/radosgw/ceph-client.rgw.clara005.log'. We should not do that as we have designated /var/log/ceph/ directory for ceph-related logs (we do not even package /var/log/radosgw directory). Again, let me know if this is a default (not configured) behaviour somewhere in the source code so that I could update the policy accordingly.

Version-Release number of selected component (if applicable):
1.3.2 - 0.94.5-8

How reproducible:
always


Steps to Reproduce:
run test with selinux and notice the denials

Actual results:
rgw logs should be in /var/log/ceph
Comment 2 Boris Ranto 2016-02-11 11:17:00 UTC 
The upstream PR:

https://github.com/ceph/ceph/pull/7604

We should do the same downstream.
Comment 3 Boris Ranto 2016-02-11 14:03:50 UTC 
dist-git commits related to build ceph-0.94.5-9.el7cp:
http://pkgs.devel.redhat.com/cgit/rpms/ceph/commit/?h=ceph-1.3-rhel-7&id=2ceb68f2a953acc1a12b7cc7ebcc14f35cf4bc6c
Comment 6 errata-xmlrpc 2016-02-29 14:46:09 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.

https://access.redhat.com/errata/RHBA-2016:0313