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:
When pcp is installed using kickstart, the %post stage of pcp-selinux package fails if selinux-policy-targeted package is not already installed. It fails during "semodule -i" command in "selinux-setup.sh" script with the following error message:
Failed to resolve typeattributeset statement at /etc/selinux/targeted/tmp/modules/400/pcpupstream/cil:1
Version-Release number of selected component (if applicable):
* pcp-4.3.2-6.el7.x86_64
* pcp-selinux-4.3.2-6.el7.x86_64
* selinux-policy-3.13.1-258.el7.noarch
* selinux-policy-targeted-3.13.1-258.el7.noarch
Steps to Reproduce:
1. Prepare a basic kickstart file to install RHEL-7.7
2. In the kickstart file put "pcp" line into "%packages" section
3. Install a RHEL-7.7 system using the kickstart file
Actual results:
Just after the installation the following command does not show "pcpupstream" module:
semodule -l | grep pcpupstream
Expected results:
The following command
semodule -l | grep pcpupstream
shows "pcpupstream" module.
Additional info:
This issue is caused by missing dependency of pcp-selinux package on selinux-policy-targeted package.
However the selinux-policy-targeted package is typically installed during later stages of system installations and "semodule -i /var/lib/pcp/selinux/pcpupstream.pp" or simply "yum reinstall pcp-selinux" fixes the problem after the installation.
Jan, I've committed the spec file change upstream as:
commit ad45af6efabfa2211a66e53bdcf798be643418ec (HEAD -> master)
Author: Jan Kurik <jkurik>
Date: Wed Oct 2 13:59:42 2019 +1000
build: add runtime rpm dep on selinux-policy-targeted
When pcp is installed using kickstart, the %post stage of pcp-selinux
package fails if selinux-policy-targeted package is not already
installed. It fails during "semodule -i" command in "selinux-setup.sh"
script with the following error message:
Failed to resolve typeattributeset statement at /etc/selinux/targeted/tmp/modules/400/pcpupstream/cil:1
This issue is caused by missing dependency of pcp-selinux package on
selinux-policy-targeted package.
Running either "semodule -i /var/lib/pcp/selinux/pcpupstream.pp" or
"yum reinstall pcp-selinux" fixes the problem after an installation.
This resolves Red Hat bugzilla #1756252.
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