Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1522765 - sysadm users cannot execute 'puppet agent' command [rhel-6.9.z]
Summary: sysadm users cannot execute 'puppet agent' command [rhel-6.9.z]
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.9
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
Mirek Jahoda
Depends On: 1515499
TreeView+ depends on / blocked
Reported: 2017-12-06 12:03 UTC by Oneata Mircea Teodor
Modified: 2018-01-25 12:51 UTC (History)
12 users (show)

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.
Clone Of: 1515499
Last Closed: 2018-01-25 12:51:38 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0176 normal SHIPPED_LIVE selinux-policy bug fix update 2018-01-25 16:52:20 UTC

Description Oneata Mircea Teodor 2017-12-06 12:03:28 UTC
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 12:51:38 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.

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