Bug 1255980 - systemd-sysctl.service fails to start with selinux enabled
systemd-sysctl.service fails to start with selinux enabled
Status: CLOSED DUPLICATE of bug 1253926
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
x86_64 Linux
unspecified Severity low
: ---
: ---
Assigned To: Miroslav Grepl
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-22 16:36 EDT by Andrew
Modified: 2015-08-23 13:45 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-08-23 13:45:11 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew 2015-08-22 16:36:27 EDT
Description of problem:

Service "Apply Kernel Variables" (systemd-sysctl.service) fails to start during boot and thereafter while the current SELinux mode is set to "enforced". After setting the current mode to "permissive", this service starts flawlessly.

The workaround is:
- setenforce 0
- systemctl start systemd-sysctl.service
- setenforce 1

Note: this bug looks like a recurrence of the Bug 1057616 on Fedora 22 after the last kernel upgrade:

4.1.5-200.fc22.x86_64 #1 SMP Mon Aug 10 23:38:23 UTC 2015

LSB Version:	:core-4.1-amd64:core-4.1-noarch
Distributor ID:	Fedora
Description:	Fedora release 22 (Twenty Two)
Release:	22
Codename:	TwentyTwo

Version-Release number of selected component (if applicable):

How reproducible:

systemctl status systemd-sysctl.service

Steps to Reproduce:
1. (re)boot the system
2. check status of the systemd-sysctl.service

Actual results:

Expected results:

Additional info:
Comment 1 Lukas Vrabec 2015-08-23 13:45:11 EDT

*** This bug has been marked as a duplicate of bug 1253926 ***

Note You need to log in before you can comment on or make changes to this bug.