Fedora 40 CoreOS

Fedora CoreOS Test Week

Fedora CoreOS

Date	2024-04-01 to 2024-04-07
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 (40) 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	Raspberry Pi 4	References
apiaseck	t2.micro, 1vCPU, 20GB, eu-central-1a	warn ^[1]		↑ I successfully ran an instance, but failed ssh'ing into it. Ihad to configure multiple AWS-related mechanisms to run an instance through `aws ec2 run-instances`.
apiaseck	Raspberry Pi 4, 4GB	warn
apiaseck	t2.micro, 1vCPU, 20GB, eu-central-1a	pass ^[1]		↑ An update of the documentation is required, related to creating VPC, security groups and key pairs. Also, the manual assignment of elastic IP addresses and modification of inbound rules for the security group should be mentioned. I will look into that in the coming week.
hricky	Raspberry Pi 4 Model B Rev 1.4, 8 GB		pass ^[1]	↑ Both U-Boot and EDK2 boot methods work.

ppc64le[edit]

User	Profile	Virtual install	Bare Metal install	IBM Cloud	References
marmijo	libvirt, 40.20240331.1.0-qemu.ppc64le.qcow2	pass

s390x[edit]

User	Profile	Virtual install	Bare Metal install	IBM Cloud	References
dustymabe	bx2-2x8			pass

x86_64[edit]

User	Profile	Virtual install	Bare Metal install	References
aaradhak	libvirt,qemu - Fedora CoreOS 40.20240331.1.0	pass ^[1]		↑ Expected results : PASSED The system runs in a virtual machine according to the instructions. I can read the IP address of the machine from the serial console. I can connect to the machine via SSH. The linked documentation is clear, all steps are understandable, and nothing important is missing from it.
danniel	FCOS Live DVD 40.20240322.1.0	pass
danniel	FCOS Live DVD 40.20240322.1.0 - Gigabyte H81M-H , 8GB DDR3 ,		pass
danniel	FCOS Live DVD 40.20240322.1.0 - Gigabyte H81M-H , 8GB DDR3 , i5-4440		pass
ersen	FCOS 40.20240322.1.0	pass
garrmcnu	40.20240331.1.0 QEMU	pass
hricky	CPU: Pentium Dual-Core E6300, MB: Gigabyte G41M-ES2L, RAM: 4GB, 40.20240331.1.0-live.x86_64.iso		pass
hricky	libvirt, 40.20240331.1.0-qemu.x86_64.qcow2	pass
mythcat	https://linux-hardware.org/?probe=a0cd8c1b40	pass pass	pass
plugs	qemu,fedora-coreos-39.20240309.3.0-qemu.x86_64.qcow2	pass
ydesouza	QEMU \| Fedora CoreOS FCOS 40.20240322.1.0	pass

Platforms launch[edit]

User	Profile	Alibaba	AWS	Azure	DigitalOcean	Exoscale	Hyper-v	IBM Cloud	Kubevirt	VirtualBox	VMWare	References
apiaseck	t2.micro, 1vCPU, 20GB, eu-central-1a		warn ^[1]									↑ I successfully ran the instance using a simple ignition file but failed to ssh into it. had to configure multiple AWS-related mechanisms to run an instance through `aws ec2 run-instances`.
apiaseck	40.20240331.1.0, 2 GB RAM / 60 GB / SFO2				pass ^[1]							↑ Everything worked as expected, documentation was clear and concise.
apiaseck	AWS, m5zn.metal						warn ^[1]					↑ Using bgilbert's script AWS Instance was created successfully, but I failed to establish connection through the xfreerdp in the generated connect.sh script.
apiaseck	t2.micro, 40.20240331.1.0		pass ^[1]									↑ An update of the documentation is required, related to creating VPC, security groups and key pairs. Also, the manual assignment of elastic IP addresses and modification of inbound rules for the security group should be mentioned. I will look into that in the coming week.
brianmcarey	Fedora CoreOS 40.20240331.1.0								pass ^[1]			↑ Tested on KubeVirt v1.2
fifofonix											pass ^[1]	↑ Created and successfully SSH'd to a Fedora40 `next` VMWare vSphere node following the govc-based test case steps for creation from a template (as opposed to a library template).
hhei	Borrow account and test fedora-coreos-40.20240331.1.0-aliyun.x86_64.qcow2 with ecs.t6-c1m1.large	pass ^[1]										↑ Launch success.
hhei	Test fedora-coreos-40.20240331.1.0-azure.x86_64.vhd on Azure			pass ^[1]								↑ Launch gen1/gen2, both can start.
marmijo	t5.large, 1vCPU, 20GB, us-east-2		pass
mnguyen								pass ^[1]				↑ ibmcloud version 2.24 and higher require `Allow source IP spoofing` set to `true` in order to launch an instance. Older versions can launch without issue. https://cloud.ibm.com/docs/vpc?topic=vpc-vni-api-introduction was introduced in March 2024.
mythcat	https://linux-hardware.org/?probe=a0cd8c1b40									pass
ravanelli	40.20240331.1.0					pass
ravanelli	VirtualBox 7.0.10 r158379									pass

Advanced configuration[edit]

User	Profile	Static networking	Complex partitioning	Building containers	Containerized service	Kernel Tuning (sysctl)	Modifying Kernel Arguments	OS extensions	References
Nemric	PXE booted FCOS 40.20240322.1.0 on Baremetal		pass ^[1]	warn ^[2]	pass	pass ^[3]			↑ Mount /var for persistent datas for PXE storage: filesystems: - path: /var device: /dev/sda format: xfs label: Var wipe_filesystem: false with_mount_unit: true ↑ Facing issue https://github.com/containers/podman/issues/22109 in a Jenkins "podman build" caused by default pasta network use, using rootless podman remote with rootfull server, should be fixed in Podman 5.0.1 Didn't run tests with docker ↑ Set kernel.domainname in /etc/sysctl.d/90-domainname.conf
Nemric	PXE booted FCOS 40.20240331.1.0 on Baremetal		pass	warn ^[1]	pass	pass			↑ Facing issue https://github.com/containers/podman/issues/22109 in a Jenkins "podman build" caused by default pasta network use, using rootless podman remote with rootfull server, should be fixed in Podman 5.0.1 Didn't run tests with docker
brianmcarey	Fedora CoreOS 40.20240331.1.0			pass	pass			pass
danniel	FCOS Live DVD 40.20240322.1.0 - Gigabyte H81M-H , 8GB DDR3 , i5-4440	pass		pass	pass			pass
hricky	CPU: Pentium Dual-Core E6300, MB: Gigabyte G41M-ES2L, RAM: 4GB, 40.20240331.1.0-live.x86_64.iso	pass	pass ^[1]						↑ Tested various partition configurations on a Bare Metal machine with 4 HHDs attached.
hricky	libvirt, 40.20240331.1.0-qemu.x86_64.qcow2	pass	pass ^[1]		pass			pass ^[2]	↑ Change the root filesystem to btrfs and Add a separate /var partition to the primary disk ↑ Layer vim and python3. Vim is the default text editor and the Python HTTP server is accessible from the host.
jbtrystram	fedora-coreos-40.20240331.1.0-qemu.x86_64.qcow2 on QEMU			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	PXE booted FCOS 40.20240322.1.0 on Baremetal	pass ^[1]		pass						↑ Issue https://github.com/coreos/fedora-coreos-tracker/issues/1296 seems to be resolved
Nemric	PXE booted FCOS 40.20240331.1.0 on Baremetal	pass		pass
aaradhak	libvirt,qemu - Fedora CoreOS 40.20240331.1.0			pass
apiaseck	40.20240331.1.0, 2 GB RAM / 60 GB		pass ^[1]							↑ Tested via DigitalOcean droplet - everything worked as expected.
hhei	Test fedora-coreos-40.20240331.1.0 with qemu								pass ^[1]	↑ Result looks good
hricky	libvirt, 40.20240331.1.0-qemu.x86_64.qcow2	pass ^[1]			pass ^[2]	pass	pass			↑ It works as expected. ↑ systemd Link File and Udev Rules work on two NICs simultaneously, with static IPs assigned.
jbtrystram			pass ^[1]	pass				pass ^[2]		↑ tested on QEMU with fedora-coreos-40.20240331.1.0-qemu.x86_64.qcow2 ↑ work as expected on fedora-coreos-40.20240331.1.0-qemu.x86_64.qcow2
sumantrom	KVM			pass

Upgrade[edit]

User	Profile	Switch stream	Bootloader updates	References
aaradhak	fedora:fedora/x86_64/coreos/next- 40.20240331.1.0	pass ^[1]	pass ^[2]	↑ The system successfully reboots and runs on the next stream. The system is functional The linked documentation is clear, all steps are understandable, and nothing important is missing from it. ↑ The system successfully reboots and runs on the next stream with the latest bootloader.
hricky	libvirt, 40.20240331.1.0-qemu.x86_64.qcow2	pass ^[1]		↑ Trying to rebase from stable to next with vim layered results in conflicting requests. Otherwise all rebases, manual and temporary rollbacks work as expected.

Tutorials[edit]

User	Profile	All Tests - Add the ones you did	References

Miscellaneous[edit]

User	Profile	Documentation	Exploratory testing	References

[1] I successfully ran an instance, but failed ssh'ing into it. Ihad to configure multiple AWS-related mechanisms to run an instance through aws ec2 run-instances.

[2] An update of the documentation is required, related to creating VPC, security groups and key pairs. Also, the manual assignment of elastic IP addresses and modification of inbound rules for the security group should be mentioned. I will look into that in the coming week.

[3] Both U-Boot and EDK2 boot methods work.

[4] Expected results : PASSED The system runs in a virtual machine according to the instructions. I can read the IP address of the machine from the serial console. I can connect to the machine via SSH. The linked documentation is clear, all steps are understandable, and nothing important is missing from it.

[5] I successfully ran the instance using a simple ignition file but failed to ssh into it. had to configure multiple AWS-related mechanisms to run an instance through aws ec2 run-instances.

[6] Everything worked as expected, documentation was clear and concise.

[7] Using bgilbert's script AWS Instance was created successfully, but I failed to establish connection through the xfreerdp in the generated connect.sh script.

[8] An update of the documentation is required, related to creating VPC, security groups and key pairs. Also, the manual assignment of elastic IP addresses and modification of inbound rules for the security group should be mentioned. I will look into that in the coming week.

[9] Tested on KubeVirt v1.2

[10] Created and successfully SSH'd to a Fedora40 next VMWare vSphere node following the govc-based test case steps for creation from a template (as opposed to a library template).

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[2]

[3]

[1]

[1]

[1]

[2]

[1]

[1]

[1]

[1]

[2]

[1]

[2]

[1]

[2]

[1]

Search

Test Day:Fedora 40 CoreOS

Contents