From Fedora Project Wiki

Fedora CoreOS Test Week
Fedora CoreOS
Date 2024-10-07 to 2024-10-11
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]

Today's installment of Fedora 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:

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

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

Prerequisites for Test Day[edit]

  • Virtual machine (x86_64, aarch64, s390x)
  • Test day Image

Grab images/artifacts/information for the most current next stream release (41) from our download page: https://fedoraproject.org/coreos/download/?stream=next#arches

How to test?[edit]

Run the tests[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 Enter result 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.

Test Results[edit]

aarch64[edit]

User Profile AWS GCP Virtual install Bare Metal install Raspberry Pi 4 References
alciregi EDK2: Combined Disk Mode Alternate Machine Disk Preparation
Pass pass
hricky Raspberry Pi 4 Model B
Pass pass
[1]
  1. ↑ Both U-Boot and EDK2 (Separate Firmware Disk Mode and Combined Disk Mode Alternate Machine Disk Preparation) boot methods work.
marmijo libvirt, 41.20241006.1.1, qemu.aarch64.qcow2
Pass pass
[1]
  1. ↑ Successfully booted 41.20241006.1.1 using qemu-system-aarch64 and connected via SSH

ppc64le[edit]

User Profile Virtual install Bare Metal install IBM Cloud References
marmijo libvirt, 41.20241006.1.1, qemu.ppc64le.qcow2
Pass pass
[1]
  1. ↑ Successfully booted 41.20241006.1.1 using qemu-system-ppc64 and connected via SSH

s390x[edit]

User Profile Virtual install Bare Metal install IBM Cloud References
marmijo libvirt, 41.20241006.1.1, qemu.s390x.qcow2
Pass pass
[1]
  1. ↑ Successfully booted 41.20241006.1.1 using qemu-system-s390x and connected via SSH
mnguyen
Pass pass
ndubrovs
Pass pass
ndubrovs LPAR, zVM
Pass pass
[1]
  1. ↑ Installation on eckd-dasd, scsi, multipath.
ndubrovs libvirt, 41.20241006.1.1, qemu.s390x.qcow2
Pass pass

x86_64[edit]

User Profile Virtual install Bare Metal install References
alciregi Supermicro server PXE
Pass pass
ersen v 41.20241006.1.1
Pass pass
geraldosimiao fedora-coreos-41.20241006.1.1-live.x86_64.iso
Pass pass
guiltydoggy
Pass pass
[1]
  1. ↑ Installed and worked as expected on F40 Kinoite host running libvirt.
hricky KVM/QEMU/libvirt, Version: 41.20241006.1.1
Pass pass
pnemade 41.20241006.1.1 in kvm
Pass pass

Platforms launch[edit]

User Profile Alibaba AWS Azure DigitalOcean Exoscale GCP Hyper-v IBM Cloud Kubevirt Nutanix OpenStack VirtualBox VMWare Vultr References
dustymabe s-2vcpu-2gb in nyc3
Pass pass
gursewak
Pass pass
[1]
  1. ↑ System launches in KubeVirt according to the instructions and can connect through ssh
hhei fedora-coreos-41.20241006.1.1-aliyun.x86_64.qcow2, ecs.t6-c1m1.large
Pass pass
[1]
  1. ↑ Successfully booted 41.20241006.1.1 using BIOS and connected via SSH
hricky 41.20241006.1.1, VirtualBox 7.1.2 on Windows 10
Pass pass
hricky VMware Workstation 17 Player
Fail fail
[1]
  1. ↑ https://github.com/coreos/fedora-coreos-tracker/issues/1802
marmijo fedora-coreos-41.20241006.1.1-azure.x86_64.vhd, Standard DS1 v2
Pass pass
ravanelli
Pass pass
ravanelli 41.20241006.1.1 VirtualBox 7.0 on MAC x86
Pass pass
ravanelli VMware Fusion Professional Version 13.6.0 on MAC x86
Fail fail
[1]
  1. ↑ RHBZ #2317048 https://github.com/coreos/fedora-coreos-tracker/issues/1802

Advanced configuration[edit]

User Profile Static networking Complex partitioning Building containers Containerized service Kernel Tuning (sysctl) Modifying Kernel Arguments OS extensions References
Nemric FCOS 41.20240922.1.0 on Bare Metal PXE booted with /var persistent storage
Pass pass
[1]
Pass pass
Pass pass
  1. ↑ PXE booted node did upgrade well with /var persistent storage spec in ign files : since months/years
aaradhak
Pass pass
alciregi Supermicro server PXE
Pass pass
Pass pass
geraldosimiao fedora-coreos-41.20241006.1.1-live.x86_64.iso
Pass pass
Pass pass
hricky KVM/QEMU/libvirt, Version: 41.20241006.1.1
Pass pass
Pass pass
Pass pass
Pass pass
ravanelli 41.20241006.1.1
Pass pass
Pass pass

Really Advanced Config[edit]

User Profile Configuring SwapOnZRAM Configuring Time Zone Debugging with Toolbox Customizing NIC name Setting alternatives Node counting KDump via Ignition Nmstate References
Nemric FCOS 41.20240922.1.0 on Bare Metal PXE booted with /var persistent storage
Pass pass
Pass pass
Warning warn
[1]
  1. ↑ Did not try to mask the timer unit
aaradhak
Pass pass
[1]
Pass pass
  1. ↑ Worked as expected
alciregi EDK2: Combined Disk Mode Alternate Machine Disk Preparation
Pass pass
alciregi Supermicro server PXE
Pass pass
Pass pass
hricky KVM/QEMU/libvirt, Version: 41.20241006.1.1
Pass pass
Pass pass
jbtrystram
Pass pass

Upgrade[edit]

User Profile Switch stream Bootloader updates References
Nemric FCOS 41.20240922.1.0 on Bare Metal PXE booted with /var persistent storage
Fail fail
[1]
  1. ↑ Did the upgrade to 41.20240916.1.0 and had this issue https://github.com/coreos/fedora-coreos-tracker/issues/1798 then I did delete /var/log/sssd directory since 41.20240922.1.0 ... I can't say if it is always true now but I have no more errors
hhei Test with 41.20241006.1.1 on GCP aarch64
Pass pass
hricky KVM/QEMU/libvirt, Version: 41.20241006.1.1
Pass pass
Pass pass

Tutorials[edit]

User Profile All Tests - Add the ones you did References

Miscellaneous[edit]

User Profile Documentation Exploratory testing References
Nemric FCOS 41.20240922.1.0 on Bare Metal PXE booted with /var persistent storage
Pass pass
[1]
  1. ↑ Quite new for me ... Installing CRI-O at boot time via ignition on a PXE booted node ! works great ! As well as running anything in a disposable way unless /var datas, like a containerized kubelet thanks to the poseidon/typhoon work ... everything is volatile and the "next stream" node works well
Nemric FCOS 41.20241006.1.1 on Bare Metal PXE booted with /var persistent storage
Pass pass
[1]
  1. ↑ Use of K8S Longhorn distributed storage that use iscsid : sudo iscsiadm -m session -o show tcp: [1] 10.0.3.202:3260,1 iqn.2019-10.io.longhorn:pvc-fca295fa-23da-4ea9-a6cf-7c8e909f528f (non-flash)
ersen v 41.20241006.1.1
Pass pass
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:Fedora_41_CoreOS&oldid=726124"