Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1522765 - sysadm users cannot execute 'puppet agent' command [rhel-6.9.z]
sysadm users cannot execute 'puppet agent' command [rhel-6.9.z]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy (Show other bugs)
6.9
All Linux
urgent Severity medium
: rc
: ---
Assigned To: Lukas Vrabec
Milos Malik
Mirek Jahoda
: Regression, Reopened, Reproducer, ZStream
Depends On: 1515499
Blocks:
  Show dependency treegraph
 
Reported: 2017-12-06 07:03 EST by Oneata Mircea Teodor
Modified: 2018-01-25 07:51 EST (History)
12 users (show)

See Also:
Fixed In Version: selinux-policy-3.7.19-307.el6_9.3
Doc Type: Bug Fix
Doc Text:
In Red Hat Enterprise Linux 6.9, the puppet module in the SELinux policy package had been restructured to follow Red Hat Enterprise Linux 7 puppet4 model, and the domain for the /usr/bin/puppet binary file had been set to 'puppet_exec_t`. As a consequence, SELinux denied executing the 'puppet agent' command for the 'sysadm_t' confined user. With this update, the missing domain transitions have been added, and `puppet agent` can be now successfully executed by 'sysadm_t' with SELinux in Enforcing mode.
Story Points: ---
Clone Of: 1515499
Environment:
Last Closed: 2018-01-25 07:51:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0176 normal SHIPPED_LIVE selinux-policy bug fix update 2018-01-25 11:52:20 EST

  None (edit)
Description Oneata Mircea Teodor 2017-12-06 07:03:28 EST
This bug has been copied from bug #1515499 and has been proposed to be backported to 6.9 z-stream (EUS).
Comment 7 errata-xmlrpc 2018-01-25 07:51:38 EST
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-2018:0176

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