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 1471131 [details]
Patch

Description of problem:

In container builds, we sometimes install RPMs even though the contents are not used within the container. We found that we had to guard all macros from selinux-policy's rpm.macros with selinuxenabled.

The cause is that the RPM macros from selinux-policy all immediately source /etc/selinux/config, even if it does not exist and SELinux is disabled. This causes the RPM scriptlets to fail.

So, here's one way to fix that in rpm.macros so callers don't have to guard with 'selinuxenabled'.

Version-Release number of selected component (if applicable): (all current builds)


How reproducible: 100%


Steps to Reproduce:
1. Install any RPM calling an RPM macro from a a current selinux-policy build in an environment where 'selinuxenabled' is false.

Actual results: RPM scriptlets fail

Expected results: RPM scriptlets pass

Additional information:

I think these macros are copied from selinux-policy to the relevant RPMs during the build process, so any RPMs utilizing a fix like this will have to have the updated rpm.macros from selinux-policy in the RPM build root.

This issue was not selected to be included in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small number of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available.

We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.