Bug 2323323 - After Fedora 41 upgrade : Refusing to run under cgroup v1 / freezing execution
Summary: After Fedora 41 upgrade : Refusing to run under cgroup v1 / freezing execution
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 41
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2323345 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-02 01:39 UTC by Fabrice Salvaire
Modified: 2024-11-16 02:15 UTC (History)
10 users (show)

Fixed In Version: systemd-256.8-1.fc41
Clone Of:
Environment:
Last Closed: 2024-11-16 02:15:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fabrice Salvaire 2024-11-02 01:39:03 UTC
I updated to Fedora 41 from 40.
At boot, systemd freeze with:

Refusing to run under cgroup v1, SY<filled square char> specified on kernel command line.
systemd[1]: freezing execution.


Reproducible: Always

Comment 2 Fabrice Salvaire 2024-11-02 01:56:42 UTC
Fix

switch in Grub2 boot command line

systemd.unified_cgroup_hierarchy=0

to

systemd.unified_cgroup_hierarchy=1

Comment 3 Zbigniew Jędrzejewski-Szmek 2024-11-02 10:50:33 UTC
Yes, the support cgroup v1 is being removed. This is intentional.

Comment 4 Fabrice Salvaire 2024-11-02 13:32:01 UTC
That means a broken system after an upgrade is not a bug ?
Interesting QA approach...

Comment 5 Fabrice Salvaire 2024-11-02 13:53:01 UTC
I suspect this is not a default Fedora setting, but due to a package like Docker ???
Anyway, Fedora 41 should clean the kernel boot settings automatically in order to boot !
I am the second person to report this issue.

Comment 6 Zbigniew Jędrzejewski-Szmek 2024-11-02 15:59:20 UTC
We have been warning that support for v1 is going away for a while now (systemd
v248 in 2021 started setting a taint and issuing a warning during boot).
We switched the Fedora default to v2 in F31 and some people opted
to undo the switch. We could switch systems silently to v2, but it's likely that
that'd make people unhappy. The primary reason to undo the switch was having some
other software installed that was not compatible with v2. Some people also didn't
switch because of emotional reasons. In any case, it's usually a bad idea to
ignore explicit local configuration. The users have two choices: either remove
the local config and move to v2, making other adjustments as necessary, or add
the additional override and continue with v1 while it remains supported.
Please note that the local admin had to create the configuration to remain on
v1 in the first place, and only they know what the appropriate choice now is.

But looking at this again, we probably shouldn't refuse to boot. I'll post a
patch to remove that error path.

Comment 7 Zbigniew Jędrzejewski-Szmek 2024-11-02 16:49:16 UTC
*** Bug 2323345 has been marked as a duplicate of this bug. ***

Comment 8 Zbigniew Jędrzejewski-Szmek 2024-11-02 16:59:04 UTC
https://github.com/systemd/systemd/pull/34999

Comment 9 Fedora Update System 2024-11-14 19:29:49 UTC
FEDORA-2024-48a0ce13b3 (systemd-256.8-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-48a0ce13b3

Comment 10 Fedora Update System 2024-11-15 03:31:38 UTC
FEDORA-2024-48a0ce13b3 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-48a0ce13b3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-48a0ce13b3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2024-11-16 02:15:02 UTC
FEDORA-2024-48a0ce13b3 (systemd-256.8-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


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