We have planned some changes to the OVF metadata inside the Fedora
CoreOS VMware OVA.
Scheduled for the next cycle of `testing` and `next` releases:
- OVF metadata will select UEFI firmware by default
- OVF metadata will enable Secure Boot by default
- OVF metadata will identify the OS as Fedora instead of RHEL 7
These changes will flow into `stable` the week of April 11. You can
track the status of this change at
Scheduled for after October 15, when vSphere 6.5 and 6.7 will reach end of life:
- OVF metadata will update from hardware version 13 to version 17
You can track the status of this change at
If these changes break your deployment workflow, please follow up in
the issues listed above or open a new issue.
Micah Abbott, for the Fedora CoreOS team
The most recent kernel update to 5.16.13-200.fc35 has been reported
to cause failures for NFS clients connecting to some QNAP NAS systems.
Details of the issue as well as links to upstream forum posts and
downstream bug reports can be found in our issue tracker:
Fortunately this bug was caught in our `testing` stream. Unfortunately,
we do need to proceed promoting this kernel into our `stable` stream
because the update will fix CVE-2022-0847 (known as "dirty pipe").
If you will be affected by this bug, the easiest workaround is to switch
the mount options for the mount to add `vers=4.0` for NFS 4.0. You can
then follow progress in the tracker issue to know when to revert
Dusty Mabe for the Fedora CoreOS Team
In the coming months, the Podman container runtime will be upgraded
from v3 to v4. This is a major release  that introduces backward
incompatible changes to configuration files and APIs.
The full release notes for Podman v4 are available at . Here is a
brief summary of how this will impact Fedora CoreOS nodes:
- Existing containers will be preserved without any change required.
- Compatibility for the Docker API is fully preserved.
- Users of the Podman remote API will need matching server/client versions.
- Rollbacks to a version with Podman v3.x will require manual action.
- Only new installations will use the new network stack by default.
For more details, see the Major Changes page in the Fedora CoreOS
This change will be rolled out together with the rebase to Fedora 36:
- the `next` rebase is targeted for 2022-03-15
- the `testing` rebase is targeted for 2022-04-19
- the `stable` stream will follow `testing` as usual
Jonathan Lebon, for the Fedora CoreOS team