RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 1369938 - Puppet 4 AIO Packages aren't supported by the targeted selinux policy
Summary: Puppet 4 AIO Packages aren't supported by the targeted selinux policy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.2
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks: 1386181
TreeView+ depends on / blocked
 
Reported: 2016-08-24 19:51 UTC by Stephen Benjamin
Modified: 2016-11-04 02:37 UTC (History)
8 users (show)

Fixed In Version: selinux-policy-3.13.1-97.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1386181 (view as bug list)
Environment:
Last Closed: 2016-11-04 02:37:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2283 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2016-11-03 13:36:25 UTC

Description Stephen Benjamin 2016-08-24 19:51:48 UTC
Description of problem:
Puppet has significantly restructured their packaging to be an all-in-one RPM shipping puppet, puppet server, and facter.  We will likely include these with Satellite 6.3.

/etc/puppetlabs does not get the puppet_etc_t context (which comes from selinux-policy-targeted), so applications which previously granted access to this context no longer work.

For example, in Satellite 6 pulp's selinux policy grants access to puppet_etc_t to publish, which previously was /etc/puppet/modules/environments, however this has been move to /etc/puppetlabs/code/environments, resulting in this denial:

type=AVC msg=audit(1472066646.325:1365): avc:  denied  { write } for  pid=28236 comm="celery" name="environments" dev="vda3" ino=268419 scontext=system_u:system_r:celery_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=dir



Additional info:

https://docs.puppet.com/puppet/4.0/reference/whered_it_go.html

Comment 2 Lukas Vrabec 2016-08-25 08:20:50 UTC
We need to add proper label for /etc/puppetlabs/code/environments.

Comment 3 Milos Malik 2016-08-25 17:04:13 UTC
Is this a RHEL-7.3 material?  Version is set to 7.4. Based on BZ tooltip, the version field defines the version of the software the bug was found in.

Comment 4 Stephen Benjamin 2016-08-25 18:27:24 UTC
It was found in 7.2.  It would be great if it can make 7.3, in time for Satellite 6.3 release which will need this.

Comment 11 errata-xmlrpc 2016-11-04 02:37:50 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-2283.html


Note You need to log in before you can comment on or make changes to this bug.