On Thu, Jan 26, 2023 at 09:29:22AM +0100, Vít Ondruch wrote: > > Dne 25. 01. 23 v 19:53 Adam Williamson napsal(a): > > On Wed, 2023-01-25 at 10:30 -0800, Adam Williamson wrote: > > > The second issue is that systems that update to systemd-253~rc1-1.fc38 > > > seem to get stuck on boot. With Plymouth enabled you just see the > > > splash screen. With it disabled (or by pressing esc) it seems to be > > > stuck at "Stopped initrd-switch-root.service - Switch Root.". I'm still > > > looking into this one, but it's happened to a lot of openQA tests and I > > > was able to confirm it first try in a local VM, by installing from the > > > 20230123.n.0 compose then updating systemd and rebooting. Fresh > > > installs with the newer systemd seem to be OK, at least most openQA > > > tests for the new compose passed - it seems to be only updating an > > > existing install that has the problem, at least so far. > > I've now filed this as > > https://bugzilla.redhat.com/show_bug.cgi?id=2164594 . Quoting the commit in dist-git: The socket exists and is enabled in the initrd. After switch-root, the system goes into an infinite loop trying to stop the socket while incoming audit messages trigger start jobs for the socket. This is a bug in the transaction logic, that'll need to be fixed separately. We need to preset the socket after the upgrade so that it remains enabled by default. This should fix the boot issue, though it's not a complete fix, because we actually want to allow people to disable the socket. On initial install, the socket is covered by preset-all and gets enabled. This explains why the issue was observed on upgraded systems, but not on fresh installations. The issue should now be resolved in rawhide because the socket will be enabled again. But the issue with pid1 not handling this is a real problem that we should solve regardless, see https://github.com/systemd/systemd/issues/26216. > Just FTR, this is very likely duplicate of: > > https://bugzilla.redhat.com/show_bug.cgi?id=2164404 I *think* that those are separate issues. I'm having trouble with a combination of systemd-253~rc1 and the 6.2.0.rc4 kernel. udev is unhappy. Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
