Fedora 39 CoreOS

Fedora CoreOS Test Week

Fedora CoreOS

Date	2023-09-25 to 2023-10-02
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:

Development: Renata Ravanelli (ravanelli), Dusty Mabe (dustymabe), Jonathan Lebon (jlebon)
Quality Assurance: Kamil Paral (kparal), Sumantro Mukherjee (sumantrom), Geoff Marr (coremodule)

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 (39) 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	Virtual install	Raspberry Pi 4	References
c4rt0	Raspberry Pi 4, 4GB			fail ^[1]	↑ I tried installing FCOS both on an SD card and on a USB drive in order to test it on Raspberry Pi4. I followed the [tutorial](https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_installing_fcos_and_booting_via_u_boot), considering next as a STREAM and 39 as a RELEASE. I also followed the [Raspberry Pi tutorial](https://www.raspberrypi.com/documentation//computers/raspberry-pi.html#updating-the-bootloader) on updating the bootloader. Until the very last step everything seems to work as expected, but after inserting the drive into the Raspberry Pi4, nothing but a dark screen was presented. Same goes for F38, stable.
hricky	Raspberry Pi 4, 8GB			fail ^[1]	↑ RHBZ #2241252 https://github.com/coreos/fedora-coreos-tracker/issues/1585
nielsenb	Raspberry Pi 4b, pieeprom-2023-05-11.bin			fail ^[1]	↑ Same issue as described in https://github.com/coreos/fedora-coreos-tracker/issues/1466
ravanelli	qemu on R152-P31-00 aarch64		pass
rravanel	a1.metal	pass

ppc64le[edit]

User	Profile	Virtual install	Bare Metal install	IBM Cloud	References
hhei	Install on FCOS 39.20230916.1.2 baremental in beaker		fail ^[1] pass ^[2]		↑ Get systemd-network-generator.service error - Failed to create temporary unit file in '/run/systemd/network': Permission denied. See https://github.com/coreos/fedora-coreos-tracker/issues/1587 ↑ Tested both passing password and enable SSH password authentication via the Ignition config, both can login successfully.

s390x[edit]

User	Profile	Virtual install	Bare Metal install	IBM Cloud	References
ravanelli	qemu on 8561 s390x	pass

x86_64[edit]

User	Profile	Virtual install	Bare Metal install	References
brianmcarey	fedora-coreos-39.20230916.1.2	pass
danniel	Lenovo ideapad S145		pass
danniel	Lenovo ideapad S145 KVM	pass
geraldosimiao	Fedora CoreOS 39.20230916.1.2 on KVM-QEMU-VirtManager (F39 KDE)	pass
nielsenb	libvirt on Fedora 38 AMD Ryzen 7 5800X3D x86_64	fail ^[1]		↑ Instructions in documentation don't work, see: https://github.com/coreos/fedora-coreos-docs/issues/544
pnemade	39.20230916.1.2 on KVM	pass
ravanelli	qemu on R152-P31-00 aarch64	pass
ydesouza	QEMU \| Fedora CoreOS 39.20230916.1.2	pass

Platforms launch[edit]

User	Profile	AWS	Azure	DigitalOcean	Exoscale	Hyper-v	Kubevirt	OpenStack	VirtualBox	Vultr	References
brianmcarey	KubeVirt v1.1.0-alpha.0 \| Fedora CoreOS 39.20230916.1.2						pass
c4rt0	sfo2, 1 GB / 1 CPU 25 GB SSD Disk 1000 GB transfer			warn ^[1] fail ^[2]							↑ https://github.com/coreos/fedora-coreos-tracker/issues/1586 ↑ While running : ` doctl compute image create my-next-fcos-image --region sfo2 --image-url https://builds.coreos.fedoraproject.org/prod/streams/next/builds/39.20230916.1.2/x86_64/fedora-coreos-39.20230916.1.2-digitalocean.x86_64.qcow2.gz while ! doctl compute image list-user \| grep my-next-fcos-image; do sleep 5; done ` The process finishes within the first few seconds. Returned result: ` ID Name Type Distribution Slug Public Min Disk 141380554 my-next-fcos-image custom Unknown OS false 0 ` Creating droplet directly on digitalocean with the custom FCOS-next image results with: 'The image you selected is no longer available'.
dustymabe	39.20230916.1.2 vultr image									pass
hhei	Test with fedora-coreos-39.20230916.1.2-hyperv.x86_64.vhdx on Hyper-V 2022					pass ^[1]					↑ Start gen2 vm with enabled secure boot, vm starts successfully
jlebon	FCOS next							pass ^[1]			↑ Tested both passing the SSH key via keypairs and via the Ignition config.
jmarrero	jmarrero			pass ^[1]							↑ Worked for me, however the image takes a bit to be available after is uploaded.
mnguyen			pass
nielsenb	ami-055c024e1ed6245f0, t2.micro	pass
ravanelli					pass ^[1]						↑ PR to update the docs: https://github.com/coreos/fedora-coreos-docs/pull/587
ravanelli	VirtualBox 7.0.10 r158379(Qt5.15.2) on Mac								pass

Advanced configuration[edit]

User	Profile	Static networking	Complex partitioning	Building containers	Containerized service	Kernel Tuning (sysctl)	OS extensions	References
Nemric	Fedora CoreOS 39.20230916.1.1 on a diskless PXE booted X86_64			pass ^[1] pass	pass ^[2]			↑ Podman use only ↑ All my containerized services are running as expected (jenkins, jenkins-agent, docker registry, redis, promtail, ...) but didn't try quadlet
brianmcarey	fedora-coreos-39.20230916.1.2			pass
danniel	Lenovo ideapad S145	pass		pass	pass
geraldosimiao	Fedora CoreOS 39.20230916.1.2 on KVM-QEMU-VirtManager (F39 KDE)			pass
ravanelli	qemu on R152-P31-00 aarch64		pass ^[1]			pass	pass ^[2]	↑ Changing the root filesystem to ext4 ↑ The vim package got issues to be installed due its deps. Installed calc that has no deps instead. The default edit also got changed to use vim
ydesouza	QEMU \| Fedora CoreOS 39.20230916.1.2	pass		pass			pass

Really Advanced Config[edit]

User	Profile	Configuring SwapOnZRAM	Configuring Time Zone	Debugging with Toolbox	Customizing NIC name	Setting alternatives	KDump via Ignition	References
Nemric	Fedora CoreOS 39.20230916.1.1 on a diskless PXE booted X86_64	pass		pass ^[1]				↑ Only run tests from documentation
brianmcarey	fedora-coreos-39.20230916.1.2			pass
danniel	Lenovo ideapad S145		pass
dustymabe	39.20230916.1.2 qemu qcow in libvirt					pass
ravanelli	qemu on 8561 s390x						fail ^[1]	↑ We have a Snoozing kola test pattern "ext.config.kdump.crash" until Sep 30 2023 with https://github.com/coreos/fedora-coreos-tracker/issues/1560 However, this issue seems different. It is not a selinux denial thing.
ravanelli	qemu on R152-P31-00 aarch64						fail ^[1]	↑ Same as s390x
rravanel	qemu on R152-P31-00 aarch64				pass ^[1]			↑ Tested via udev rule
ydesouza	QEMU \| Fedora CoreOS 39.20230916.1.2		pass		pass

Upgrade[edit]

User	Profile	Switch stream	Bootloader updates	References
jdoss		pass ^[1]		↑ Zincati upgraded to 39.20230916.1.2 on a DigitalOcean VM without issues.
jmarrero	jmarrero	pass	pass ^[1]	↑ seen expected results

Tutorials[edit]

User	Profile	All Tests - Add the ones you did	References

Miscellaneous[edit]

User	Profile	Documentation	Exploratory testing	References
Nemric	Fedora CoreOS 39.20230916.1.1 on a diskless PXE booted X86_64		fail ^[1]	↑ This issue still happen : https://github.com/coreos/fedora-coreos-tracker/issues/1296

[1] I tried installing FCOS both on an SD card and on a USB drive in order to test it on Raspberry Pi4. I followed the [tutorial](https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_installing_fcos_and_booting_via_u_boot), considering next as a STREAM and 39 as a RELEASE. I also followed the [Raspberry Pi tutorial](https://www.raspberrypi.com/documentation//computers/raspberry-pi.html#updating-the-bootloader) on updating the bootloader. Until the very last step everything seems to work as expected, but after inserting the drive into the Raspberry Pi4, nothing but a dark screen was presented. Same goes for F38, stable.

[2] RHBZ #2241252 https://github.com/coreos/fedora-coreos-tracker/issues/1585

[3] Same issue as described in https://github.com/coreos/fedora-coreos-tracker/issues/1466

[4] Get systemd-network-generator.service error - Failed to create temporary unit file in '/run/systemd/network': Permission denied. See https://github.com/coreos/fedora-coreos-tracker/issues/1587

[5] Tested both passing password and enable SSH password authentication via the Ignition config, both can login successfully.

[6] Instructions in documentation don't work, see: https://github.com/coreos/fedora-coreos-docs/issues/544

[7] ttps://github.com/coreos/fedora-coreos-tracker/issues/1586

[8] While running : ` doctl compute image create my-next-fcos-image --region sfo2 --image-url https://builds.coreos.fedoraproject.org/prod/streams/next/builds/39.20230916.1.2/x86_64/fedora-coreos-39.20230916.1.2-digitalocean.x86_64.qcow2.gz while ! doctl compute image list-user | grep my-next-fcos-image; do sleep 5; done ` The process finishes within the first few seconds. Returned result: ` ID Name Type Distribution Slug Public Min Disk 141380554 my-next-fcos-image custom Unknown OS false 0 ` Creating droplet directly on digitalocean with the custom FCOS-next image results with: 'The image you selected is no longer available'.

[9] Start gen2 vm with enabled secure boot, vm starts successfully

[10] Tested both passing the SSH key via keypairs and via the Ignition config.

[11] Worked for me, however the image takes a bit to be available after is uploaded.

[12] PR to update the docs: https://github.com/coreos/fedora-coreos-docs/pull/587

[1]

[1]

[1]

[1]

[2]

[1]

[1]

[2]

[1]

[1]

[1]

[1]

[1]

[2]

[1]

[2]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

Search

Test Day:Fedora 39 CoreOS

Contents