Fedora CoreOS streams rebasing to Fedora Linux 35

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Over the next few weeks we're rolling out Fedora Linux 35 to the
`testing` and `stable` streams of Fedora CoreOS. During the Fedora 35
development cycle we followed the Fedora Change process more closely [1]
in order to provide a smoother transition of incoming Fedora Changes.

Current known issues with recent kernels (F34 & F35):

- AWS `m6i` instances fail to boot [2]
- Some OKD [3] and Kubernetes [4] workloads cause kernel deadlock

Some highlights of recently added features:

- cgroups v2 is now the default [5]
- Ignition now supports setting/updating kernel arguments [6]
- DNF Count Me support was added and is now enabled by default [7].
- 64-bit ARM (aarch64) artifacts are now available [8]
- Raspberry Pi 4 install documentation is now available [9]
- systemd-resolved is now fully enabled [10]

Some new features landing in the coming months:

- Support for Virtualbox [11]
- Support for a minimal ISO image [12]
- Support for Nutanix [13]
- Switching to iptables-nft by default [14]

Thanks to everyone who participated in the test day [15] and to everyone that
follows the `testing` and `next` streams to help us identify and fix issues
before they get to `stable`.

Dusty Mabe, for the Fedora CoreOS team

[1] https://github.com/coreos/fedora-coreos-tracker/issues/856
[2] https://github.com/coreos/fedora-coreos-tracker/issues/1004
[3] https://github.com/coreos/fedora-coreos-tracker/issues/957
[4] https://github.com/coreos/fedora-coreos-tracker/issues/940
[5] https://github.com/coreos/fedora-coreos-tracker/issues/292
[6] https://github.com/coreos/ignition/issues/1168
[7] https://github.com/coreos/fedora-coreos-tracker/issues/717
[8] https://github.com/coreos/fedora-coreos-tracker/issues/13
[9] https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/
[10] https://github.com/coreos/fedora-coreos-tracker/issues/834
[11] https://github.com/coreos/fedora-coreos-tracker/issues/1008
[12] https://github.com/coreos/fedora-coreos-tracker/issues/868
[13] https://github.com/coreos/fedora-coreos-tracker/issues/1007
[14] https://github.com/coreos/fedora-coreos-tracker/issues/676
[15] https://github.com/coreos/fedora-coreos-tracker/issues/973#issuecomment-947834145
















Over the next two days we're rolling out the first Fedora 34 based
Fedora CoreOS into the `stable` stream. 
 
Some notable issues/configurations:

- Very old systems (Fedora 32 and earlier) may not be able to update [0]
- systemd-resolved is still enabled but not used yet [1]

Here are some highlights of recently added features in Fedora CoreOS:

- The `/boot` partition is now mounted read-only.
    - This continues the work to protect more of the OS from accidental damage.
- It is now possible to configure boot disk RAID 1 mirroring via Ignition [2].
- Better introspection into the state of Zincati (the update agent) from `rpm-ostree status`.
- Better support for disk encryption.
- Initial (non-automatic) support for updating the bootloader. [3]

Here are some new features landing in the coming months:

- Support for specifying kernel arguments via Ignition [4].
- Move to cgroup v2 by default [5].
- DNF Count Me support for Fedora CoreOS [6].
    
Thanks to everyone who participated in the test day [7] and to everyone that
run the `testing` and `next` streams to help us identify and fix issues
before they get to `stable`.

Dusty Mabe, for the Fedora CoreOS team

[0] https://github.com/coreos/fedora-coreos-tracker/issues/749#issuecomment-843446996
[1] https://github.com/coreos/fedora-coreos-tracker/issues/834
[2] https://docs.fedoraproject.org/en-US/fedora-coreos/storage/#_reconfiguring_the_root_filesystem
[3] https://docs.fedoraproject.org/en-US/fedora-coreos/bootloader-updates/
[4] https://github.com/coreos/ignition/issues/1168
[5] https://github.com/coreos/fedora-coreos-tracker/issues/292
[6] https://github.com/coreos/fedora-coreos-tracker/issues/717
[7] https://testdays.fedoraproject.org/events/113
_______________________________________________
CoreOS mailing list -- coreos@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to coreos-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/coreos@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux