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.
Description of problem:
From https://bugzilla.redhat.com/show_bug.cgi?id=1517656#c10:
> After upgrading to the following packages (from latest RHEL 7.4 packages - I
> haven't bisected what's the minimal set of packages needing to be upgraded)
> the error shown in comment 5 is gone when running the command on command
> line (semodule -X 400 -i /var/lib/pcp/selinux/pcpupstream.pp) and all AVCs
> are also gone. Thanks.
I've now traced the minimal list of packages needing update to:
libsemanage-2.5-10.el7
libsemanage-python-2.5-10.el7
With
libsemanage-2.5-8.el7
libsemanage-python-2.5-8.el7
I get
# semodule -X 400 -i /var/lib/pcp/selinux/pcpupstream.pp
libsemanage.semanage_pipe_data: Child process /usr/libexec/selinux/hll/pp failed with code: 255. (No such file or directory).
pcpupstream: libsepol.policydb_read: policydb module version 19 does not match my version range 4-17
pcpupstream: libsepol.sepol_module_package_read: invalid module in module package (at section 0)
pcpupstream: Failed to read policy package
libsemanage.semanage_direct_commit: Failed to compile hll files into cil files.
(No such file or directory).
semodule: Failed!
After upgrading to
libsemanage-2.5-10.el7
libsemanage-python-2.5-10.el7
I see (but see also https://bugzilla.redhat.com/show_bug.cgi?id=1548020):
# semodule -X 400 -i /var/lib/pcp/selinux/pcpupstream.pp
#
So pcp-selinux should depend on new-enough libsemanage (or, depending on the case, not introduce such dependency on build time, if possible). Thanks.
Discussed at length in pcp engr team. We're going to recommend using the matching versions of pcp (7.x) with the platform selinux that was released for - and not doing piecemeal upgrades - its too complex for us to try to manage the deps and policydb versions within a minor release.
We're also not keen on adding runtime dependencies on selinux-policy-devel (and friends) to base pcp, which was our other angle of attack here.