The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
For details on how to fill out this form, see the documentation.
To report an issue with this template, file an issue in the pgm_docs repo.
F42: Do not boot on a cgroup v1 machine
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
CGroups v2 has been the default for Fedora since F31. Systemd is aiming to not boot on cgroup v1 to help finally switch users to cgroup v2. See https://github.com/systemd/systemd/issues/30852.
The goal of this change request is to notify users that starting from systemd 256 fedora will not boot by default on a cgroup v1 node.
Owner
- Name: Kevin Hannon
- Email: kehannon@redhat.com
Current status
- Targeted release: <VERSION>/ Fedora Linux <VERSION>
- Last updated: 2024-09-13
- [Announced]
- [<will be assigned by the Wrangler> Discussion thread]
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Fedora has been defaulting with cgroup v2 since F31. The goal of this change request is to phase out cgroup v1 by avoiding users booting their nodes with cgroup v1. Systemd (v256) is aiming to not boot on a cgroup v1 by default. Fedora should follow a similar approach.
This change request serves as a notification/announcement for Fedora to inherit the same functionality as systemd. Fedora will not boot on a cgroup v1 node by default.
Feedback
Benefit to Fedora
CGroupv2 is the future and cgroup v1 is in support at best. Most kernel developers would encourage users to switch to cgroup v2 so Fedora should also make sure that the support for cgroup v1 goes down over time.
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with the Fedora Strategy:
Upgrade/compatibility impact
Early Testing (Optional)
Do you require 'QA Blueprint' support? Y/N
How To Test
1) One can set a kernel to boot with cgroup v1 and make sure that fedora will not boot on cgroup v1.
User Experience
An user who uses cgroup v1 node will no longer be able to use cgroup v1. They could modify the systemd settings to revert this change.
Dependencies
Systemd v256.
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)