Description of problem: In https://bugzilla.redhat.com/show_bug.cgi?id=710840#c8 I noticed a bug unrelated to the report: Jun 5 06:38:53 recorder kernel: <28>systemd[1]: Found ordering cycle on local-fs.target/start Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Walked on cycle path to fedora-storage-init-late.service/start Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Walked on cycle path to cryptsetup.target/start Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Walked on cycle path to cryptsetup/start Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Walked on cycle path to systemd-random-seed-load.service/start Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Walked on cycle path to local-fs.target/start Jun 5 06:38:53 recorder kernel: <28>systemd[1]: Breaking ordering cycle by deleting job fedora-storage-init-late.service/start Version-Release number of selected component (if applicable): systemd-26
Frederic Crozat pointed out a similar cycle reported in OpenSUSE: https://bugzilla.novell.com/show_bug.cgi?id=721666 [ 10.043323] systemd[1]: Found ordering cycle on local-fs.target/start [ 10.043326] systemd[1]: Walked on cycle path to cryptsetup/start [ 10.043330] systemd[1]: Walked on cycle path to systemd-random-seed-load.service/start [ 10.043333] systemd[1]: Walked on cycle path to local-fs.target/start [ 10.043336] systemd[1]: Breaking ordering cycle by deleting job cryptsetup/start
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This is in Fedora 16, too, and this time systemd kills the cryptsetup job, leading to no swap (which uses ecryptfs). [ 4.153977] systemd[1]: Found ordering cycle on local-fs.target/start [ 4.153983] systemd[1]: Walked on cycle path to cryptsetup/start [ 4.153987] systemd[1]: Walked on cycle path to systemd-random-seed-load.service/start [ 4.153991] systemd[1]: Walked on cycle path to local-fs.target/start [ 4.153996] systemd[1]: Breaking ordering cycle by deleting job cryptsetup/start It seems that the patch in http://comments.gmane.org/gmane.comp.sysutils.systemd.devel/3597 could be the fix.
Fixed in git.
systemd-37-6.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/systemd-37-6.fc16
Package systemd-37-6.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-6.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-6.fc16 then log in and leave karma (feedback).
Package systemd-37-7.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-7.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-7.fc16 then log in and leave karma (feedback).
Package systemd-37-8.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-8.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-8.fc16 then log in and leave karma (feedback).
Package systemd-37-10.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-10.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-10.fc16 then log in and leave karma (feedback).
Package systemd-37-11.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-11.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-11.fc16 then log in and leave karma (feedback).
Even with systemd-37-11.fc16 this is still NOT FIXED COMPLETELY. I'm getting the same message as in comment #1, but my swap is activated properly (it wasn't before the fix - I was getting both this cycle and the one in comment #3, that one is now gone): systemd[1]: Found ordering cycle on local-fs.target/start systemd[1]: Walked on cycle path to fedora-storage-init-late.service/start systemd[1]: Walked on cycle path to cryptsetup.target/start systemd[1]: Walked on cycle path to cryptsetup/start systemd[1]: Walked on cycle path to systemd-random-seed-load.service/start systemd[1]: Walked on cycle path to local-fs.target/start systemd[1]: Breaking ordering cycle by deleting job fedora-storage-init-late.service/start As seen from this, the After=local-fs.target is not generated directly into cryptsetup (which was the problem fixed by git commit 87e75fddbb3701fd5f4e0d62dc1d661e8d94b071), but pulled in indirectly. I am wondering whether this is not in some way related to there being a second encrypted volume present on the system (though not mentioned in fstab or mounted on boot).
(In reply to comment #11) > Even with systemd-37-11.fc16 this is still NOT FIXED COMPLETELY. It's possible. But since the update helps several people with this problem at least a bit, I'm not going to revert. When the build reaches stable updates, Bodhi will auto-close this bug, but we can reopen it then to resolve the remaining part of the problem.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
THis should be fixed in F18 with the new RequiresMountsFor= logic that adds the dependency on the random seed only to the swap partition, not everything else.