Bug 1221934 - [rhel6] graphite-web needs type "httpd_sys_rw_content_t" for files in "/var/lib/graphite-web(/.*)?"
Summary: [rhel6] graphite-web needs type "httpd_sys_rw_content_t" for files in "/var/l...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.7
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Simon Sekidde
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-15 09:44 UTC by Milos Malik
Modified: 2016-05-10 19:57 UTC (History)
9 users (show)

Fixed In Version: selinux-policy-3.7.19-286.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1148766
Environment:
Last Closed: 2016-05-10 19:57:18 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0763 0 normal SHIPPED_LIVE selinux-policy bug fix update 2016-05-10 22:33:46 UTC

Description Milos Malik 2015-05-15 09:44:31 UTC 
Opened bug to track progress of below bug on rhel-6 branches:

 * https://bugzilla.redhat.com/show_bug.cgi?id=1148425
Comment 1 Milos Malik 2015-05-15 17:49:37 UTC 
# rpm -qa selinux-policy\*
selinux-policy-3.7.19-267.el6.noarch
selinux-policy-minimum-3.7.19-267.el6.noarch
selinux-policy-targeted-3.7.19-267.el6.noarch
selinux-policy-doc-3.7.19-267.el6.noarch
selinux-policy-mls-3.7.19-267.el6.noarch
# semanage fcontext -l | grep graphite
/var/lib/graphite-web(/.*)                         all files          system_u:object_r:httpd_sys_content_t:s0 
#

fcontext pattern for RHEL-7 is suffixed by '?'.
Comment 8 errata-xmlrpc 2016-05-10 19:57:18 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://rhn.redhat.com/errata/RHBA-2016-0763.html
Note You need to log in before you can comment on or make changes to this bug.