Red Hat Bugzilla – Bug 692436
Incorrect SELinux labelling of new /run directory prevents system boot
Last modified: 2011-04-04 16:35:05 EDT
Description of problem:
After latest yum update in Fedora 15 the system won't boot at all. It's stuck with the last message being "Starting monitoring LVM2 mirrors, snapshots, etc." (or similar). When enforce=0 is put into kernel boot line, system works fine.
Version-Release number of selected component (if applicable):
Created attachment 489037 [details]
Created attachment 489038 [details]
Created attachment 489039 [details]
*** Bug 692137 has been marked as a duplicate of this bug. ***
*** Bug 692440 has been marked as a duplicate of this bug. ***
*** Bug 692475 has been marked as a duplicate of this bug. ***
*** Bug 692600 has been marked as a duplicate of this bug. ***
systemd-22-1.fc15, selinux-policy-3.9.16-9.fc15 has been submitted as an update for Fedora 15.
I have updated to systemd-22-1.fc15 and selinux-policy-3.9.16-10.fc15, and the system still fails to boot. If these updates are working for others, then it may be important to mention that my system has selinux disabled.
Discussed during the 2011-04-01 blocker review meeting. One of the release criteria this hits is:
after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention.
Proposed fix has been pushed to updates, not clear if it fixes the problem. More testing of the proposed update is needed to verify that it does/does not work.
Updated to selinux-policy-3.9.16-10.fc15.noarch, systemd-22-1.fc15.x86_64; after relabeling boot went fine. So it works for me.
systemd-22-1.fc15, selinux-policy-3.9.16-10.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
Why was this bug closed? I clearly stated that my system still fails to boot.
Andrew is it failing to boot in enforcing=0?
It still fails to boot if I set enforcing=0 (with the "Failed to load SELinux policy" from bug #692537), but it does boot if I specify selinux=0.
(In reply to comment #10)
> it may be important to mention that my system has selinux disabled.
Very important. This bug affected SELinux-enabled systemds. Broken systems with SELinux disabled using /etc/config/selinux is bug 692573.
So I am closing this again. Anyone is still seeing problems booting *with SELinux enabled*, please reopen or file a new bug.
That is a different bug then this one, related to systemd, which you found the
We are working to fix the labeling of /run which is mostly fixed by this
systemd-23-1 is supposed to be released tonight to fix the rest of the
In the other bug, it was stated that this one was for the failure to boot, and the other was for the selinux-related error message. I will try to clarify the situation for all who are following the other bug.
Both bugs could cause a failure to boot.
(In reply to comment #21)
> Both bugs could cause a failure to boot.
Both indeed do. :)