Bug 1163418

Summary:	Adjust log permissions to 0750 for openstack-ceilometer
Product:	Red Hat OpenStack	Reporter:	Lon Hohberger <lhh>
Component:	openstack-ceilometer	Assignee:	Pradeep Kilambi <pkilambi>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.0 (RHEL 7)	CC:	jjoyce, jruzicka, jschluet, mburns, srevivo, yprokule
Target Milestone:	---	Keywords:	EasyFix, Triaged, ZStream
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ceilometer-2014.1.5-4.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-14 15:32:45 UTC	Type:	---
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:	1163424

Description Lon Hohberger 2014-11-12 16:42:00 UTC

The spec file for openstack-ceilometer sets the permissions for /var/log/ceilometer directory to 0755, which is world-readable.  To maintain consistency, please set this to 0750.  See bug 1149688 for more details.  In the RPM spec file in the %files section, you can use the following:

%dir %attr(0750, ceilometer, ceilometer) %{_localstatedir}/log/ceilometer

(Owner/Group are examples and may be different for this component)

Comment 1 Lon Hohberger 2014-11-12 16:51:06 UTC

The intent here is to tighten up access on /var/log directories and files.  Note that, apart from the RPM spec files, it's possible some OpenStack components may be setting permissions incorrectly as well.

It also may be the case that this component has a valid need to have its /var/log directory world-readable.  If that is the case, please close this bugzilla.

Comment 2 Jon Schlueter 2015-08-18 16:35:03 UTC

can we get pm and qa acks for this cleanup?

Comment 10 errata-xmlrpc 2017-06-14 15:32:45 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-2017:1444