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:

After upgrading to 34.1.32-1 many tools reported output in the title.

This can be fixed by rebuilding selinux policy.

It seems something is not fully done when updating.

This was already an issue on F35: https://ask.fedoraproject.org/t/regex-version-mismatch-expected-10-39-fedora-35/19711/7


# restorecon /tmp
restorecon: Regex version mismatch, expected: 10.40 2022-04-14 actual: 10.37 2021-05-26
restorecon: Regex version mismatch, expected: 10.40 2022-04-14 actual: 10.37 2021-05-26
# semodule -B
# restorecon /tmp
# rpm -qi selinux-policy
Name        : selinux-policy
Version     : 34.1.32
Release     : 1.el9
Architecture: noarch
Install Date: Tue 24 May 2022 06:44:18 AM UTC
Group       : Unspecified
Size        : 25206
License     : GPLv2+
Signature   : RSA/SHA256, Thu 12 May 2022 09:53:00 AM UTC, Key ID 05b555b38483c65d
Source RPM  : selinux-policy-34.1.32-1.el9.src.rpm
Build Date  : Wed 11 May 2022 07:37:29 PM UTC
Build Host  : x86-02.stream.rdu2.redhat.com
Packager    : builder
Vendor      : CentOS
URL         : https://github.com/fedora-selinux/selinux-policy
Summary     : SELinux policy configuration
Description :
SELinux core policy package.
Originally based off of reference policy,
the policy has been adjusted to provide support for Fedora.

Dist-git commit to backport:
commit b15718470a296a7f10448e931e66ddc9a157098d (plautrba/pcre2)
Author: Petr Lautrbach <plautrba>
Date:   Mon Oct 18 14:44:42 2021 +0200

    Connect triggerin to pcre2 instead of pcre

The patch of b15718470a296a7f10448e931e66ddc9a157098d

---

diff --git a/selinux-policy.spec b/selinux-policy.spec
index 81e947e..16f42d3 100644
--- a/selinux-policy.spec
+++ b/selinux-policy.spec
@@ -599,7 +599,7 @@ fi
 exit 0
 
 
-%triggerin -- pcre
+%triggerin -- pcre2
 %{_sbindir}/selinuxenabled && %{_sbindir}/semodule -nB
 exit 0

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 (selinux-policy 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/RHBA-2022:8283