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:
Run of pmlogger triggers a SELinux issue

Version-Release number of selected component (if applicable):
* 

How reproducible:
* This issue is always reproducible on PPC64LE architecture
* It is not reproducible on other supported RHEL-7.x architectures

Steps to Reproduce:
1. Install RHEL-7.7 (or the latest build of RHEL-7.8) on PPC64LE architecture
2. Install pcp
# yum install -y pcp
3. Start pmlogger service
# systemctl start pmlogger

Actual results:
* An AVC issue is reported

type=AVC msg=audit(1579509798.199:106): avc:  denied  { execute } for  pid=9634 comm="pmlogger_daily" name="setfiles" dev="dm-0" ino=34500334 scontext=system_u:system_r:pcp_pmlogger_t:s0 tcontext=system_u:object_r:setfiles_exec_t:s0 tclass=file permissive=0
type=AVC msg=audit(1579271450.951:117): avc:  denied  { fowner } for  pid=20309 comm="xz" capability=3  scontext=system_u:system_r:pcp_pmlogger_t:s0 tcontext=system_u:system_r:pcp_pmlogger_t:s0 tclass=capability permissive=0

#============= pcp_pmlogger_t ==============
allow pcp_pmlogger_t setfiles_exec_t:file execute;

Expected results:
* No AVC issues observed

Additional info:
IMO this is a follow-up (or a re-occurrence) of bz1394199 and bz1697808

commit 0b70cb89fcc51a9d0b582f04ee1c21134bd4c624
Author: Nathan Scott <nathans>
Date:   Thu Feb 20 17:14:07 2020 +1100

    selinux: allow pcp_pmlogger_t access to execute setfiles on el7 ppc64le
    
    Resolves Red Hat BZ #1792859

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 (Low: pcp security, bug fix, and enhancement update), 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/RHSA-2020:3869