Description of problem: [chris@f27m ~]$ sudo systemctl status systemd-tmpfiles-setup.service ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2018-01-27 19:49:46 MST; 2min 35s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 722 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 722 (code=exited, status=1/FAILURE) Jan 27 19:49:46 f27m.localdomain systemd[1]: Starting Create Volatile Files and Directories... Jan 27 19:49:46 f27m.localdomain systemd-tmpfiles[722]: Failed to write file "/sys/class/scsi_host/host0/link_power_management_policy": Invalid argument Jan 27 19:49:46 f27m.localdomain systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Jan 27 19:49:46 f27m.localdomain systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Jan 27 19:49:46 f27m.localdomain systemd[1]: Failed to start Create Volatile Files and Directories. Version-Release number of selected component (if applicable): systemd-236-4.git3e14c4c.fc28.x86_64 How reproducible: Always Steps to Reproduce: 1. Each boot 2. 3. Actual results: failed Expected results: success Additional info:
Created attachment 1387077 [details] journal
I don't see an AVC related to this in the journal, but also booting with enforcing=0
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
https://github.com/systemd/systemd/pull/8617
Oh, this was included in the last version bump.