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.
If the passt-selinux package is reinstalled (e.g. with 'dnf reinstall'), the package scriptlets temporarily unload the related SELinux policy with 'semodule -r'. See bz2172268#c45 for a complete example.
We need to modify the spec file with changes equivalent to upstream commit:
https://passt.top/passt/commit/?id=dd2349661933c4e9756e524ae9465f38b53b7557
fedora: Refresh SELinux labels in scriptlets, require -selinux package
which, in particular, replaces the existing %preun actions with:
%postun selinux
if [ $1 -eq 0 ]; then
%selinux_modules_uninstall -s %{selinuxtype} passt
%selinux_modules_uninstall -s %{selinuxtype} pasta
fi
so that the policy modules are unloaded only if the package is actually removed.
Hello Stefano
According to QE test result,the current problem is not fixed. The policy modules brought by the passt-selinux package still do not survive after reinstalling the passt* packages. Please help review the following steps:
1. Check the current status
# rpm -qa selinux\* passt\* | sort
passt-0^20230222.g4ddbcb9-3.el9.x86_64
passt-selinux-0^20230222.g4ddbcb9-3.el9.noarch
selinux-policy-38.1.13-1.el9.noarch
selinux-policy-devel-38.1.13-1.el9.noarch
selinux-policy-targeted-38.1.13-1.el9.noarch
2. Check the policy modules brought by the passt-selinux package
# semodule -lfull | grep -e pasta -e passt
400 passt pp
400 pasta pp
3. Reinstall passt* packages
yum -y reinstall passt-0^20230222.g4ddbcb9-3.el9.x86_64.rpm passt-selinux-0^20230222.g4ddbcb9-3.el9.noarch.rpm
4. Check the policy modules again, it can not be found on the host
# semodule -lfull | grep -e pasta -e passt
#
Thanks
Lei
1. Check the current status
# rpm -qa selinux\* passt\* | sort
passt-0^20230222.g4ddbcb9-4.el9.x86_64
passt-selinux-0^20230222.g4ddbcb9-4.el9.noarch
selinux-policy-38.1.14-1.el9.noarch
selinux-policy-devel-38.1.14-1.el9.noarch
selinux-policy-targeted-38.1.14-1.el9.noarch
2. Check the policy modules brought by the passt-selinux package
# semodule -lfull | grep -e pasta -e passt
200 passt pp
200 pasta pp
3. Reinstall passt* packages
# yum -y reinstall passt-0^20230222.g4ddbcb9-4.el9.x86_64.rpm passt-selinux-0^20230222.g4ddbcb9-4.el9.noarch.rpm
4. Check the policy modules again,the policy modules brought by the passt-selinux package survive after reinstalling the passt* packages.
# semodule -lfull | grep -e pasta -e passt
200 passt pp
200 pasta pp
Based on the above test result this problem has been fixed very well on the passt-0^20230222.g4ddbcb9-4.el9.x86_64, so move to "VERIFIED".
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 (passt 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-2023:6430