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.
+++ This bug was initially created as a clone of Bug #1835254 +++
Description of problem:
I have a code which runs a bunch of `semanage fcontext -a -t <type> <file>` commands on every initialising, and on one occurrence, a power outage happened while the command was still running.
After the power came back, I booted the server and this error message appeared, and the boot hanged.
I successfully booted the server by setting `selinux=0` to the kernel parameters, and then I noticed that selinux targeted policy files:
/etc/selinux/targeted/policy/policy.31
/etc/selinux/targeted/active/modules/100/*
were empty (0 size).
It successfully reproduced almost every time.
Reinstalling selinux-policy-targeted, running `touch /.autorelabel` and than reboot, resolved the issue.
Version-Release number of selected component (if applicable):
libsemanage-2.5-14.el7.x86_64
selinux-policy-3.13.1-252.el7_7.6.noarch
selinux-policy-targeted-3.13.1-252.el7_7.6.noarch
policycoreutils-2.5-33.el7.x86_64
policycoreutils-python-2.5-33.el7.x86_64
How reproducible:
Almost every time
Steps to Reproduce:
1. Create a file: `touch /tmp/abc`
2. Run `semanage fcontext -a -t var_t "/tmp/abc"`
3. DO NOT LET THE COMMAND FINISHED - it will take about 2-3 seconds, during that time, force shutdown the server.
Actual results:
Server is not bootable unless disabling SELinux using the kernel parameters
Expected results:
Server boot normally
Additional info:
I noticed that if I add to `semanage fcontext` the flag `-N` it does not reproduced, so the issue is probably related to the policy reload which this flag prevents. It probably does not sync the filesystem after the reload and does not do safe writes.
--- Additional comment from RHEL Program Management on 2020-05-13 15:50:45 CEST ---
Since this bug report was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
--- Additional comment from Zdenek Pytela on 2020-05-13 16:12:47 CEST ---
Also refer to:
https://bugzilla.redhat.com/show_bug.cgi?id=1490324https://bugzilla.redhat.com/show_bug.cgi?id=1688129
--- Additional comment from Stephen Smalley on 2020-05-14 14:38:59 CEST ---
Upstream fix proposed here:
https://lore.kernel.org/selinux/5ebc4bc6.1c69fb81.a8850.464e@mx.google.com/T/#u
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 (libsemanage 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-2020:4589