+++ This bug was initially created as a clone of Bug #1152220 +++ Description of problem: The Initial Setup systemd service file[0] contains the TimeoutSec=0 options, but systemd still shuts-down the system after initial setup has been running for about 10-15 minutes. Version-Release number of selected component (if applicable): systemd Version : 216 Release : 10.fc22 initial-setup Version : 0.3.23 Release : 2.fc22 How reproducible: always Steps to Reproduce: 0a.: install rawhide with kickstart that contains "firstboot --enable" and don't configure user - this should make Initial Setup start after installation 0b.: some other service that has TimeoutSec=0 and is run during startup might also do 1. leave the given service running for about 10-15 minutes Actual results: The system is shutdown by systemd after about 10-15 minutes, regardless of what's going on (it even once shut down during dnf update, trashing my testing VM...). Expected results: The given service will run indefinitely without systemd shutting down the system. Additional info: This is in Journal directly before shutdown: Oct 13 15:38:28 rawinit systemd[1]: Startup timed out. Oct 13 15:38:28 rawinit systemd[1]: Forcibly powering off as result of failure. Oct 13 15:38:28 rawinit systemd[1]: Shutting down. [0] https://git.fedorahosted.org/cgit/initial-setup.git/tree/systemd/initial-setup-graphical.service --- Additional comment from Zbigniew Jędrzejewski-Szmek on 2014-10-13 18:04:29 CEST --- I don't know if this is a consolation, but a fix for this is on the todo list [1]: * apply start timeout during the "initializing" manager state only, instead of both "initializing" and "starting". maybe rename the timeout to "initialization-timeout" then or so? [1] http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n78 --- Additional comment from Martin Kolman on 2014-10-20 18:23:25 CEST --- Does not happen in the latest F21 nightly with systemd 215-19. --- Additional comment from Martin Kolman on 2014-10-20 19:09:05 CEST --- Looks like it got backported to F21 with 216-4.
Proposed as a Blocker for 21-alpha by Fedora user m4rtink using the blocker tracking app because: If Initial Setup is running, the computer will unconditionally shutdown after 15 minutes after startup. This can be problematic as user input can be lost, important operations as user and group creation being interrupted mid-way or computer shutting down unexpectedly when user expects it to be running after the installation & reboot.
Possibly a duplicate of my https://bugzilla.redhat.com/show_bug.cgi?id=1154416 ? Also, I think you might need to make this a Beta Blocker, since Alpha is already out (but not 100% sure).
(In reply to Andre Robatino from comment #2) > Possibly a duplicate of my > https://bugzilla.redhat.com/show_bug.cgi?id=1154416 ? Also, I think you > might need to make this a Beta Blocker, since Alpha is already out (but not > 100% sure). Looking at the tool, the 21-alpha is preselected as the default milestone for some reason. :)
Proposed as a Blocker for 21-beta by Fedora user m4rtink using the blocker tracking app because: If Initial Setup is running, the computer will unconditionally shutdown after 15 minutes after startup. This can be problematic as user input can be lost, important operations as user and group creation being interrupted mid-way or computer shutting down unexpectedly when user expects it to be running after the installation & reboot. (submitted again with correct milestone)
(In reply to Andre Robatino from comment #2) > Possibly a duplicate of my > https://bugzilla.redhat.com/show_bug.cgi?id=1154416 ? Actually, this bug is more detailed, so if it's the same bug, then mark bug 1154416 as a duplicate of this one. (This bug was also cloned from bug 1152220 which preceded mine.)
Discussed in 2014-10-20 Blocker Review meeting [1]. Rejected as a blocker, accepted as a freeze exception. It isn't clear how easy this bug is to hit. Getting a fix in for Beta would be good. Please repropose with reproduction steps if it's more widespread than currently indicated. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-20/
Patches sent for review: http://lists.freedesktop.org/archives/systemd-devel/2014-October/024502.html.
Beta got approved without a fix for this, so no point having it as a Beta FE any more. Re-proposing as Final FE as it seems significant and we'll want to make sure we don't lose it.
We suspect this is causing https://bugzilla.redhat.com/show_bug.cgi?id=1159292 , which may be a major problem for Beta. The upgrade.img for Beta is baked-in at this point. Our only hope is if fedup can, somehow, work around the problem: is there some way it can disable the shutdown-after-timeout behaviour for the fedup boot, perhaps?
kmod-18-4.fc21,systemd-216-7.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/kmod-18-4.fc21,systemd-216-7.fc21
systemd-216-8.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/systemd-216-8.fc21
systemd-216-8.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
kmod-18-4.fc21,systemd-216-9.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/kmod-18-4.fc21,systemd-216-9.fc21
kmod-18-4.fc21,systemd-216-10.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/kmod-18-4.fc21,systemd-216-10.fc21
kmod-18-4.fc21, systemd-216-11.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.