From Fedora Project Wiki

Fedora 44 CoreOS Test Week

Date 2026-03-23 to 2026-03-27
Time All Week

Website QA/Test Days
Matrix #coreos:fedoraproject.org(other clients|?)
Mailing list test


Can't make the date?
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

This Test Day will focus on Fedora CoreOS.

Who's available?[edit]

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion:

You can chat with us on Matrix. See the infobox on top of the page to learn where to join.

Prerequisites for Test Day[edit]

  • A virtual machine or a bare metal machine (x86_64, aarch64, ppc64le, s390x)
  • Test Day Image

Grab images/artifacts/information for the most current next stream release (44) from our Download Page.

The Documentation is available here.
Documentation feedback is welcome through chat, mailing list, GitHub issue tracker and in the form of a pull request to the documentation sources.

How to test?[edit]

Visit the results page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ➕ (plus) button for that test case.

Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.

Reporting bugs[edit]

Please report all bugs, issues or enhancement proposals to the Fedora CoreOS issue tracker.

We really need bug reports!
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!

When filing the bug, it's very helpful to include:

  • exact steps you've performed (and whether you can reproduce it again)
  • screenshots or videos, if applicable
  • system journal (log), which you can retrieve by journalctl -b > journal.txt
  • all output in a terminal, if started from a terminal
  • your system description

If you are unsure about exactly how to file the report or what other information to include, just ask us.

Please make sure to link to the bug when submitting your test result, thanks!

Exported Test Results[edit]

aarch64[edit]

User Profile AppleHV AWS GCP Virtual install Bare Metal install Running from RAM Raspberry Pi 4 References
Cory Farmer Fedora CoreOS 44.20260316.1.1 (aarch64)
Pass pass
[1]
Pass pass
[2]
Pass pass
[3]
  1. Successfully booted Raspberry Pi 4 (1GB) using EDK2 UEFI firmware.
  2. Successfully layered neovim.raw via systemd-sysext.
  3. Used .build quadlet unit to build a custom rootless Forgejo image with asciidoctor layered in via apk.
Joel Capitao RPi 4 Model B/8GB with fedora-coreos-44.20260316.1.1-metal.aarch64.raw.xz
Pass pass
[1]
  1. Successfully booted using U-Boot bootloader
Osama Albahrani M2 Pro MacBook Pro
Pass pass
[1]
Pass pass
[2]
Pass pass
[3]
Pass pass
[4]
  1. Able to ssh and rpm-ostree install fastfetch
  2. Able to password login and rpm-ostree install fastfetch
  3. Able to ssh and brew install fastfetch
  4. Able to password login and brew install fastfetch
Steven Presti M4 Max MacBook Pro
Pass pass
[1]

ppc64le[edit]

User Profile Virtual install Bare Metal install Running from RAM IBM Cloud References

s390x[edit]

User Profile Virtual install Bare Metal install Runnning from RAM IBM Cloud References

x86_64[edit]

User Profile AppleHV Virtual install Bare Metal install Running from RAM References
Cory Farmer Fedora CoreOS 44.20260316.1.1 (x86_64)
Pass pass
[1]
  1. Bare Metal (Thinkpad P43s) via coreos-installer
Jaroslav Groman Fedora CoreOS 44.20260316.1.1 Live ISO
Pass pass
Pass pass
Pass pass
lruzicka Libvirt based VM, CoreOS Live ISO
Pass pass
Nemric Fedora CoreOS 44.20260316.1.1 iPXE
Pass pass
Oğuz Ersen fedora-coreos-44.20260316.1.1-live-iso.x86_64
Pass pass
Parag Nemade Fedora CoreOS 44.20260316.1.1 ISO
Pass pass
Venkata Subramani vvspune
Pass pass
[1]
  1. virtual install using virt-manager in Fedora43 iso file

Platforms launch[edit]

User Profile Alibaba AWS Azure DigitalOcean Exoscale GCP Hetzner Hyper-v IBM Cloud Kubevirt Nutanix OpenStack Oracle Cloud Proxmox VE VirtualBox VMWare Vultr References
Dusty Mabe aarch64 VM.Standard.A1.Flex shape with fedora-coreos-44.20260316.1.1-oraclecloud.aarch64.qcow2
Pass pass
[1]
  1. Opened a PR to make the docs better: https://github.com/coreos/fedora-coreos-docs/pull/799
Dusty Mabe s-2vcpu-2gb DigitalOcean fedora-coreos-44.20260316.1.1-digitalocean.x86_64.qcow
Pass pass
Huijing Hei ecs.e-c1m1.large with fedora-coreos-44.20260316.1.1-aliyun.x86_64.qcow2
Pass pass
[1]
  1. Launch VM successfully
Jean-Baptiste Trystram jbtrystram
Pass pass
[1]
  1. Launched a kubevirt VM on openshift without issues
Michael Armijo fedora-coreos-44.20260316.1.1-hyperv.x86_64.vhdx
Pass pass
[1]
  1. Launched Hyper-V Gen2 VM with no issues
Michael Armijo fedora-coreos-44.20260316.1.1-proxmoxve.x86_64.qcow2
Pass pass
[1]
Rolv Apneseth fedora-coreos-44.20260316.1.1-hetzner.x86_64.raw.xz
Pass pass

Advanced configuration[edit]

User Profile Static networking Complex partitioning Building containers Containerized service Kernel tuning (sysctl) Modifying kernel arguments OS extensions References
Cory Farmer Fedora CoreOS 44.20260316.1.1 (aarch64)
Pass pass
[1]
Pass pass
[2]
Pass pass
[3]
Pass pass
[4]
  1. Set static IP via /etc/NetworkManager/system-connections/*.nmconnection
  2. Used .build quadlet unit to build a custom rootless Forgejo image with asciidoctor layered in via apk.
  3. Ran rootful Pi-hole container via quadlet in /etc/containers/systemd/.
  4. Layered tang (rpm-ostree install) using provided systemd unit from documentation as example.
Cory Farmer Fedora CoreOS 44.20260316.1.1 (x86_64)
Pass pass
[1]
Pass pass
[2]
Pass pass
[3]
Pass pass
[4]
Pass pass
[5]
  1. Used .build quadlet unit to build a custom rootless Forgejo image with asciidoctor layered in via apk.
  2. Successfully deployed Ollama and Forgejo via user-level Quadlet
  3. Applied vm.swappiness = 10 via /etc/sysctl.d/ and verified with sysctl.
  4. Successfully modified boot arguments via Ignition to include mitigations=off and crashkernel=300M.
  5. Successfully layered neovim.raw via systemd-sysext.
Jaroslav Groman bare metal / Fedora CoreOS 44.20260316.1.1 Live ISO
Pass pass
lruzicka Libvirt based VM, CoreOS Live ISO
Pass pass
[1]
  1. Only tested with podman
Nemric Fedora CoreOS 44.20260316.1.1 iPXE
Pass pass
[1]
  1. Ok with quadlet and systemd units

Really advanced configuration[edit]

User Profile Configuring swap on ZRAM Configuring time zone Debugging with Toolbox Customizing NIC name Setting alternatives Node counting KDump via Ignition Nmstate References
Cory Farmer Fedora CoreOS 44.20260316.1.1 (aarch64)
Pass pass
[1]
Pass pass
[2]
Fail fail
[3]
Pass pass
[4]
  1. Initialized /dev/zram0 via zram-generator.conf; Verified via zramctl
  2. Verified /etc/localtime symlink persistence.
  3. EDK2 UEFI on RPi4 fails to pass the hardware MAC via ACPI, forcing the bcmgenet driver to generate a random MAC on every boot. Documented MAC Address matching fails; must use Driver= matching or switch UEFI to Devicetree mode.
  4. Unit rpm-ostree-countme.timer is masked.
Cory Farmer Fedora CoreOS 44.20260316.1.1 (x86_64)
Pass pass
[1]
Pass pass
[2]
Pass pass
[3]
Pass pass
[4]
Pass pass
[5]
  1. Initialized /dev/zram0 via zram-generator.conf; Verified via zramctl
  2. Verified /etc/localtime symlink persistence.
  3. Created and entered a Fedora 44 toolbox; verified package installation (dnf install strace) and host-mount access.
  4. Successfully set interface name using documentation's systemd link file & udev rule methods.
  5. Enabled and verified kdump.service status. Verified that kexec-dmesg.log file was created in /var/crash.
Dusty Mabe s-2vcpu-2gb DigitalOcean fedora-coreos-44.20260316.1.1-digitalocean.x86_64.qcow
Fail fail
[1][2]
  1. setting alternatives example in the docs doesn't work because iptables-legacy is no longer installed. Opened an issue
  2. https://github.com/coreos/fedora-coreos-docs/issues/798
Nemric Fedora CoreOS 44.20260316.1.1 iPXE
Pass pass

Upgrade[edit]

User Profile Switch stream Bootloader updates References
Angel Cervera Roldan Fedora CoreOS 44.20260316.1.1
Pass pass
Joel Capitao RPi 4 Model B/8GB with Fedora CoreOS 44.20260316.1.1
Pass pass

Tutorials[edit]

User Profile All Tests - Note the ones you did References
Yasmin Valim de Souza fedora-coreos-44.20260316.1.1-qemu.x86_64.qcow2.xz
Pass pass
[1]
Pass pass
[2]
Pass pass
[3]
Pass pass
[4]
Pass pass
[5]
  1. Starting a service on first boot.
  2. Launching a user-level systemd unit on boot.
  3. Enabling autologin and custom hostname.
  4. SSH access and starting containers.
  5. Testing Fedora CoreOS updates.

Miscellaneous[edit]

User Profile Documentation Exploratory testing References
Cory Farmer Fedora CoreOS 44.20260316.1.1 (aarch64)
Pass pass
[1]
  1. Successfully layered neovim.raw via systemd-sysext.
Nemric Fedora CoreOS 44.20260316.1.1 iPXE
Pass pass
[1]
Pass pass
[2]
  1. Using sysexts https://fedora-sysexts.github.io/fedora/
  2. Running k8s node with containerized kubelet and Cri-O