Hi all,
Last week's Fedora CoreOS `next` release, 38.20230310.1.0, introduced
an issue [1] causing boot failures on aarch64 after updating from an
older Fedora CoreOS release. We detected the problem and withdrew the
release [2] before any user systems were affected. The release was
available from our website and stream metadata for three days, and was
never rolled out to existing nodes.
To fix the boot failure, upcoming releases will automatically perform
a one-time bootloader update on aarch64 systems. As a consequence
[3], any systems installed on (or manually updated to)
38.20230310.1.0, on any CPU architecture, cannot be updated to future
Fedora CoreOS releases and must be reinstalled. Affected systems will
display a warning message upon SSH login:
> This release is a dead-end and will not further auto-update:
> https://github.com/coreos/fedora-coreos-tracker/issues/1441
Other than systems running 38.20230310.1.0, no manual intervention is required.
We apologize for any inconvenience this causes. If you have any
questions or concerns, please contact us in the Fedora CoreOS issue
[1] or in #fedora-coreos on Libera.Chat.
Benjamin Gilbert, for the Fedora CoreOS team
[1]: https://github.com/coreos/fedora-coreos-tracker/issues/1441
[2]: https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedorapro…
[3]: https://github.com/coreos/fedora-coreos-tracker/issues/1441#issuecomment-14…
Fedora Linux 38 Beta will be released next week [1]. Starting March
14, newly provisioned Fedora CoreOS nodes on the `next` stream will be
based on Fedora Linux 38. On March 16, existing Fedora CoreOS nodes on
the `next` stream will begin to update.
For more information about Fedora 38, see the Fedora Project's list of
official Changes [2] and the Fedora CoreOS analysis of each Change
[3].
One Change related to OpenSSH [4] deserves special mention. In Fedora
38, SSH host keys are migrating to a new set of permissions to better
match upstream defaults. This migration is performed automatically and
we do not expect any issues. However, a failed migration may prevent
SSH access to the machine. If you have console access to your machines
and wish to be especially cautious, consider setting a password for
the `core` user.
Please test out the `next` stream over the coming month and report any
issues in our issue tracker [5].
Thank you to everyone helping find issues by running the `next` stream!
Jonathan Lebon, for the Fedora CoreOS team
[1] https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…
[2] https://fedoraproject.org/wiki/Releases/38/ChangeSet
[3] https://github.com/coreos/fedora-coreos-tracker/issues/1357
[4] https://fedoraproject.org/wiki/Changes/SSHKeySignSuidBit
[5] https://github.com/coreos/fedora-coreos-tracker/issues