Fedora 45 CoreOS

Fedora CoreOS 45 Test Week

Fedora CoreOS

Date	2025-09-21 to 2025-09-25
Time	All Week

Website	QA/Test Days
Matrix	#coreos:fedoraproject.org
Mailing list	test

Can't make the date?
If you come to this page before or 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 at Fedora CoreOS issue tracker, 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:

Development - Yasmin de Souza (ydesouza), Hristo Marinov (hricky)
Quality - Lukáš Růžička (lruzicka), Kamil Paral (kparal), Adam Williamson (adamw)

For real time help, please join us on Matrix: #coreos:fedoraproject.org.

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 (45) 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 + button for the test.

Reporting bugs[edit]

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

If you are unsure about exactly how to file the report or what other information to include, ask on Matrix #coreos:fedoraproject.org, #test-day:fedoraproject.org or #quality:fedoraproject.org and we will help you.

Exported test results[edit]

aarch64[edit]

User	Profile	AppleHV	AWS	GCP	Virtual install	Bare Metal install	Raspberry Pi 4	References
Michael Erwin	GIGABYTE B550i Aorus Pro AX latest HFc bios, AMD 5900xt, 64GB, Radeon R9700 GPU					warn

ppc64le[edit]

User	Profile	Virtual install	Bare Metal install	IBM Cloud	References
Aman Shrivastava	IBM POWER10 (9105-22A), QEMU/KVM guest via coreos-assembler, Fedora 44 host	pass ^[1]			↑ Build 45.20260917.1.2 (next, ppc64le). VM boots, Ignition applied the SSH key, networking up, systemctl is-system-running = running, kernel 7.2.5-300.fc45.
Aman Shrivastava	IBM PowerVS (mon01), s1022 POWER10, 8 GiB, tier1			pass ^[1]	↑ Build 45.20260917.1.2 (next, ppc64le) on IBM PowerVS. Imported the powervs OVA from COS, created an instance with Ignition passed as user data. Boots fine, Ignition applied the config and wrote the SSH keys for core. Kernel 7.2.5-300.fc45. Two PowerVS notes: instance health stays WARNING (rmc_state inactive, since RMC needs the RSCT agents cloud-init ships), and that WARNING blocks attaching a NIC after creation — all networks must be attached at create time.

s390x[edit]

User	Profile	Virtual install	Bare Metal install	IBM Cloud	References

x86_64[edit]

User	Profile	Virtual install	Bare Metal install	References
bolo yeung	Fedora CoreOS 45 , VBox VM, 2 GB RAM, 2 vCPU, 10 GB disk	fail ^[1]		↑ Imported the .ova Appliance downloaded "fedora-coreos-45.20260913.1.1-virtualbox.x86_64.ova" in vbox, created and insert the ignition file, started the OS and load services and get stuck right after a service named zincati.service...
glocks17		pass
Leandro Abdallah	Fedora CoreOS 45, KVM/QEMU VM, 8 GB RAM, 4 vCPU, 60 GB disk	fail ^[1]		↑ "Tested virtual install using the live ISO in a KVM/QEMU VM. Installation via coreos-installer completed successfully, but after reboot the system fails to display a login prompt on VT1. Services start normally but the console appears stuck. This matches the known issue reported in coreos/fedora-coreos-tracker#2160. The login prompt is also not accessible via the serial console. Result: Fail (known bug)."
lruzicka	Libvirt KVM based VM (45.20260913.1.1 iso file)	fail ^[1]^[2]		↑ I cannot boot the CoreOS live image (iso) in the virtual machine. The system gets stuck at Reached target: multi-user.target and Finished nmstate.service. The qemu.xz variant gets stuck, too. ↑ https://github.com/coreos/fedora-coreos-tracker/issues/2229
lruzicka	Libvirt KVM based VM (45.20260913.1.1 QCOW2 file)	pass ^[1]		↑ The getty service does not run in the system and it only can be accessed via ssh. It never displays a login prompt. However, if the service is enabled and started, login prompt appears normally.
Michael Erwin	GIGABYTE B550i Aorus Pro AX latest HFc bios, AMD 5900xt, 64GB, Radeon R9700 AI GPU		pass ^[1]	↑ BARE METAL: Everything tested worked well, except Dropbox RPM. AI usage: ROCm with ollama, llama.cpp, LMStudio Bionic, nvtop, etc. worked great.
Oğuz Ersen	45.20260913.1.1	pass
Parag Nemade	Fedora CoreOS 45, KVM VM	fail ^[1]		↑ Stuck at "Started systemd-journald.service - Journal Service." No login prompt displayed.

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
Rolv Apneseth	Hetzner aarch64 and x86_64							pass ^[1]											↑ Following the guide for each architecture worked as expected
Yasmin Valim de Souza	fedora-coreos-45.20260913.1.1-qemu.x86_64.qcow2.xz												pass

Advanced configuration[edit]

User	Profile	Static networking	Complex partitioning	Building containers	Containerized service	Kernel tuning (sysctl)	Modifying kernel arguments	References
lruzicka	Libvirt KVM based VM (45.20260913.1.1 QCOW2 file)	pass	pass	pass	pass	pass	pass
Nemric	Fedora CoreOS 45.20260913.1.1 live/PXE mode (1 k8s node and 1 standalone node)				pass ^[1]			↑ Ok, with systemd services and quadlets
Nemric	Fedora CoreOS 45.20260913.1.1 live/PXE mode 1 standalone node		pass ^[1]					↑ Ok for full drive raid 1 / mirroring
Yasmin Valim de Souza	fedora-coreos-45.20260913.1.1-qemu.x86_64.qcow2.xz	pass

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
lruzicka	Libvirt KVM based VM (45.20260913.1.1 QCOW2 file)	pass	pass	pass	pass			pass
Nemric	Fedora CoreOS 45.20260913.1.1 live/PXE mode (1 k8s node and 1 standalone node)	pass ^[1]							pass ^[2]	↑ Swap on ZRAM & OOMD ↑ Only tested nmstatectl show

Upgrade[edit]

User	Profile	Switch stream	Bootloader updates	References
Alex Hedges	libvirt VM booted from 44.20260829.3.1 QCOW2 file, then rebased against 45.20260913.1.1	pass ^[1]	pass ^[2]	↑ Used custom derived OCI images instead of exact upstream ones ↑ Used custom derived OCI images instead of exact upstream ones
lruzicka	Libvirt KVM based VM (45.20260913.1.1 QCOW2 file)	pass	pass

Tutorials[edit]

User	Profile	All Tests - Note the ones you did	References
glocks17	Tutorial Autologin	pass ^[1]	↑ Tutorial Autologin: https://docs.fedoraproject.org/en-US/fedora-coreos/tutorial-autologin/
Rolv Apneseth	All	pass ^[1]	↑ All passed
Yasmin Valim de Souza	fedora-coreos-45.20260913.1.1-qemu.x86_64.qcow2.xz	pass ^[1]	↑ All passed

Miscellaneous[edit]

User	Profile	Documentation	Exploratory testing	References

[1] Build 45.20260917.1.2 (next, ppc64le). VM boots, Ignition applied the SSH key, networking up, systemctl is-system-running = running, kernel 7.2.5-300.fc45.

[2] Build 45.20260917.1.2 (next, ppc64le) on IBM PowerVS. Imported the powervs OVA from COS, created an instance with Ignition passed as user data. Boots fine, Ignition applied the config and wrote the SSH keys for core. Kernel 7.2.5-300.fc45. Two PowerVS notes: instance health stays WARNING (rmc_state inactive, since RMC needs the RSCT agents cloud-init ships), and that WARNING blocks attaching a NIC after creation — all networks must be attached at create time.

[3] Imported the .ova Appliance downloaded "fedora-coreos-45.20260913.1.1-virtualbox.x86_64.ova" in vbox, created and insert the ignition file, started the OS and load services and get stuck right after a service named zincati.service...

[4] "Tested virtual install using the live ISO in a KVM/QEMU VM. Installation via coreos-installer completed successfully, but after reboot the system fails to display a login prompt on VT1. Services start normally but the console appears stuck. This matches the known issue reported in coreos/fedora-coreos-tracker#2160. The login prompt is also not accessible via the serial console. Result: Fail (known bug)."

[5] I cannot boot the CoreOS live image (iso) in the virtual machine. The system gets stuck at Reached target: multi-user.target and Finished nmstate.service. The qemu.xz variant gets stuck, too.

[6] ttps://github.com/coreos/fedora-coreos-tracker/issues/2229

[7] The getty service does not run in the system and it only can be accessed via ssh. It never displays a login prompt. However, if the service is enabled and started, login prompt appears normally.

[8] BARE METAL: Everything tested worked well, except Dropbox RPM. AI usage: ROCm with ollama, llama.cpp, LMStudio Bionic, nvtop, etc. worked great.

[9] Stuck at "Started systemd-journald.service - Journal Service." No login prompt displayed.

[10] Following the guide for each architecture worked as expected

[11] Ok, with systemd services and quadlets

[1]

[1]

[1]

[1]

[1]

[2]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[2]

[1]

[2]

[1]

[1]

[1]

Search

Test Day:Fedora 45 CoreOS

Contents