Description of problem: A F20 system fails to boot and the last boot message is: [ OK ] Reached target Initrd Default Target Then nothing happens. Booting with rhgb and quiet removed from the kernel command line and rd.debug added reveals an error message from systemd[1] that it freezes because the selinux policy fails to load. However it should be more obvious in the normal case when booting fails why this happens and that it happend, because there is no indication that nothing will happen in the default case. Version-Release number of selected component (if applicable): systemd-208-22.fc20 dracut-037-11.git20140402.fc20 How reproducible: unknown, it is still unclear why the selinux policy fails to load
To reproduce change in /etc/selinux/config SELINUXTYPE=targeted to SELINUXTYPE=disabled
Such SELinux configuration is invalid. If you want to disable SELinux, change the SELINUX variable, not SELINUXTYPE.
(In reply to Jan Synacek from comment #2) > Such SELinux configuration is invalid. If you want to disable SELinux, > change the SELINUX variable, not SELINUXTYPE. I agree, however this bug is about Fedora not properly telling that this configuration is invalid but only saying "[ OK ] Reached target Initrd Default Target" and failing to boot.
We are loading the policy and it is our job to inform the user in big bold letters if that fails.
OK, so this happens only when SELINUX=enforcing and SELINUXTYPE=<whatever invalid>. I'll dig into it. Also, please excuse my quick decision on in Comment 2, I didn't know systemd actually loaded the policy.
After all, freezing the system when systemd isn't able to load the policy in enforcing mode is expected. http://lists.freedesktop.org/archives/systemd-devel/2014-November/025059.html Closing as NOTABUG.
(In reply to Jan Synacek from comment #6) > After all, freezing the system when systemd isn't able to load the policy in > enforcing mode is expected. > > http://lists.freedesktop.org/archives/systemd-devel/2014-November/025059.html > > Closing as NOTABUG. Yes, it is good to freeze the system. However, the error reporting should be improved, since "Failed to load SELinux policy. Freezing." is not reliable displayed, but "[ OK ] Reached target Initrd Default Target" is the last message. See also comment:4 where Zbigniew agrees that a user should be properly notified.
Yeah, I have a patch ready, but I want to test it a bit before committing.
So, I pushed a patch upstream http://cgit.freedesktop.org/systemd/systemd/commit/?id=cb6531bee6, but it might not make it into F20... If it conflicts a lot, the fix will only go to F21.
*** Bug 1170665 has been marked as a duplicate of this bug. ***
F21: http://pkgs.fedoraproject.org/cgit/systemd.git/commit/?h=f21&id=ed5fc99b3c5977ab09d48442dc0be20845f3f81a F20: http://pkgs.fedoraproject.org/cgit/systemd.git/commit/?h=f20&id=4d68180abf28786f38b7ecbbee6d9f8714e13cb2
systemd-208-29.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-29.fc20
systemd-216-14.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/systemd-216-14.fc21
Package systemd-216-14.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-216-14.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-0251/systemd-216-14.fc21 then log in and leave karma (feedback).
systemd-216-14.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
systemd-208-29.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.