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.
Created attachment 1574585[details]
avc.log
Description of problem:
selinux issue observed during pcp installation.
Version-Release number of selected component (if applicable):
pcp-selinux-4.3.2-2.el7
selinux-policy-3.13.1-249.el7
RHEL-ALT-7.6-updates-20190514.0
Actual results:
See attached avc.log.
These selinux policy rules suppress this issue:
===
module newsemodule00 1.0;
require {
type tracefs_t;
type pcp_pmcd_t;
class dir { open read search };
}
#============= pcp_pmcd_t ==============
allow pcp_pmcd_t tracefs_t:dir { open read search };
===
Additional info:
Described problem breaks the ci-gating.
Hmm, this one seems to be a build problem - we have tracefs_t knowledge in PCP selinux-policy already.
From src/selinux/GNUlocaldefs in pcp ...
ifeq "$(PCP_SELINUX_TRACEFS)" "true"
PCP_TRACEFS="type tracefs_t;"
PCP_TRACEFS_FS_RULE="allow pcp_pmcd_t tracefs_t:filesystem mount;"
PCP_TRACEFS_DIR_RULE="allow pcp_pmcd_t tracefs_t:dir { search read open };"
PCP_TRACEFS_FILE_RULE="allow pcp_pmcd_t tracefs_t:file { getattr read open append write };"
endif
... so, this seems to have been disabled by missing tracefs_t on the build system (not test system). :|
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-2020:0994
Created attachment 1574585 [details] avc.log Description of problem: selinux issue observed during pcp installation. Version-Release number of selected component (if applicable): pcp-selinux-4.3.2-2.el7 selinux-policy-3.13.1-249.el7 RHEL-ALT-7.6-updates-20190514.0 Actual results: See attached avc.log. These selinux policy rules suppress this issue: === module newsemodule00 1.0; require { type tracefs_t; type pcp_pmcd_t; class dir { open read search }; } #============= pcp_pmcd_t ============== allow pcp_pmcd_t tracefs_t:dir { open read search }; === Additional info: Described problem breaks the ci-gating.