Bug 692602
Summary: | systemd produces selinux error msg during boot, but selinux=disabled in my /etc/selinux/config | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joachim Backes <joachim.backes> |
Component: | systemd | Assignee: | Lennart Poettering <lpoetter> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | amcnabb, awilliam, ivenvd, johannbg, lpoetter, metherid, mschmidt, notting, plautrba |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-03-31 19:07:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joachim Backes
2011-03-31 16:48:40 UTC
When I upgraded my Fedora 15 Alpha system from systemd 20 to systemd 21, I encountered these same error messages. As in Joachim's case, I have selinux disabled. By the way, I tried booting with systemd.unit=rescue.target and sytsemd.unit=emergency.target, and the system hung at the selinux errors in both cases. Since it now appears to be impossible to boot the system by any means less drastic than init=/bin/sh, I think the severity of this issue is urgent. Is there any other information that would be helpful for this bug report? I had the same issue with you, and I found a workaround, just set SELINUX=permissive in /etc/sysconfig/selinux. There seems to be a bug when SELinux is disabled via the config file. Try using "selinux=0" on the kernel command line. *** This bug has been marked as a duplicate of bug 692573 *** |