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.

Description of problem:
Puppet Master service fails to start after update to 7.3, worked in 7.2

Version-Release number of selected component (if applicable):
CentOS Linux release 7.3.1611 (Core)
selinux-policy-3.13.1-102.el7_3.7.noarch
selinux-policy-targeted-3.13.1-102.el7_3.7.noarch
puppet-server-3.6.2-3.el7.noarch (from EPEL)
puppet-3.6.2-3.el7.noarch (from EPEL) 

How reproducible:
100%

Steps to Reproduce:
1. systemctl start puppetmaster 
2. setenforce 0
3. systemctl start puppetmaster

Actual results:
start-puppet-master: /usr/bin/start-puppet-master: line 6: /usr/bin/puppet: Permission denied

Puppet master service starts after "setenforce 0"

Expected results:
Puppet master service should start with SELinux in enforcing mode.

Additional info:
# audit2allow <audit.log


#============= puppetmaster_t ==============
allow puppetmaster_t puppetagent_exec_t:file { execute execute_no_trans getattr ioctl open read };

I believe this bug is duplicate of BZ#1376893.

*** This bug has been marked as a duplicate of bug 1376893 ***