Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
I assumed the same fix will be ok, based on fact that both rhel6 and 7 has the same output for this command:
# semanage fcontext -l |grep puppet_etc
/etc/puppet(/.*)? all files system_u:object_r:puppet_etc_t:s0
And if rhel7.3 is adding
/etc/puppetlabs(/.*)? all files system_u:object_r:puppet_etc_t:s0
Then adding the same on rhel6 would fix it.
Simply put we need to extend puppet_etc_t type to include /etc/puppetlabs(/.*)? (Puppet4), which happened already on rhel73.
The automated TC does not generate any USER_AVCs when executed on a machine where puppet 2.7 is installed. The same automated TC generates following USER_AVC when executed on a machine where puppet 3.8 is installed:
----
type=USER_AVC msg=audit(12/15/2016 11:43:13.837:374) : user pid=2232 uid=dbus auid=unset ses=unset subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_return dest=:1.33 spid=52620 tpid=65026 scontext=unconfined_u:system_r:NetworkManager_t:s0 tcontext=unconfined_u:system_r:puppet_t:s0 tclass=dbus exe=/bin/dbus-daemon sauid=dbus hostname=? addr=? terminal=?'
----
In both cases NetworkManager must be running.
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-2017-0627.html