Fedora 37 CoreOS Test Day

More information about the event can be found here: http://fedoraproject.org/wiki/Test_Day:Fedora_37_CoreOS_2022-09-29
Go back to List of Events.

Results

Clicking on the testcase name will show you the appropriate "how to test" page.
Click on the Enter result button, to enter result.

Installation

Username	Profile	Virtual install	Bare Metal install	Comments
		Enter result	Enter result
ersen	Virtualbox
ersen	v 36.20220906.3.2
geraldosimiao	fedora-coreos-37.20220918.1.1
nielsenb	KVM, x86_64, fedora-coreos-37.20220918.1.1
ravanelli	fedora-coreos-37.20220918.1.1

Cloud launch

Username	Profile	AWS	Azure	GCP	DigitalOcean	VMWare	Exoscale	IBM Cloud	VirtualBox	Vultr	OpenStack	Alibaba	Comments
		Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result
fifofonix	vSphere 7.0.3.00500 on NUCs					[1]							1. Had to deploy with `govc import.ova -name ${VM_NAME} ${FCOS_OVA}` as I am not permissioned to load FCOS_OVA to library.
jasonbrooks
jlebon	37.20220918.1.1/x86_64										[1]		1. No issues. Ignition config fetched, SSH works fine, no failed units, networking seems fine.
mnguyen								[1]					1. Installed with no issues
ravanelli	ravanelli								[1]				1. Tested via Mac using VirtualBox version 6.1.34 r150636
sohank2602										[1]			1. An FCOS VM boots up using an ignition config without any issues.

aarch64

Username	Profile	AWS	Virtual install	Bare Metal install	Comments
		Enter result	Enter result	Enter result
jskladan	Disregard	[1]			1. Just testing Testdays-Web changes

Advanced configuration

Username	Profile	Static networking	Complex partitioning	Building containers	Containerized service	Kernel Tuning (sysctl)	Modifying Kernel Arguments	OS extensions	Configuring SwapOnZRAM	Configuring Time Zone	Debugging with Toolbox	Customizing NIC name	Setting alternatives	Node counting	KDump via Ignition	Comments
		Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result	Enter result
Nemric	Fedora CoreOS 37.20220918.1.1 automatically updated			[1] [2]					[3]		[4]					1. Build my own container with success in rootless mode 2. Built via a containerized jenkins agent, launched at startup (as root), that drive podman from inside the container via a socket. https://github.com/Relativ-IT/Jenkins-Agent 3. variant: fcos version: 1.4.0 storage: files: - path: /etc/systemd/zram-generator.conf mode: 0644 contents: inline: | # This config file enables a /dev/zram0 device with the default settings [zram0] 4. Only followed https://docs.fedoraproject.org/en-US/fedora-coreos/debugging-with-toolbox/
Nemric	Fedora CoreOS 37.20220918.1.1 automaticly updated
dustymabe	37.20221003.10.0 on libvirt VM	[1]														1. passed manual static networking test script at https://github.com/coreos/fedora-coreos-config/blob/testing-devel/tests/manual/c...
fifofonix														[1]		1. - Additionally, confirmed configuring countme for corporate proxy via systemd drop-in. - Re-deployed some servers opting into countme (long deferred!), others will opt in as re-deployed.
fifofonix	Newly provisioned 37.20220918.1.1							[1]								1. Chose to install open-vm-tools instead of vim: /usr/bin/rpm-ostree install --idempotent --allow-inactive open-vm-tools
geraldosimiao	fedora-coreos-37.20220918.1.1		[1]													1. Tested with luks
jlebon	37.20220918.1.1/x86_64/QEMU		[1]										[2]			1. No issues. Tried partitioning and LUKS reprovisioning. 2. Works fine, yielded a docs update: https://github.com/coreos/fedora-coreos-docs/pull/468
nielsenb	KVM, x86_64, fedora-coreos-37.20220918.1.1

Upgrade

Username	Profile	Switch stream	Bootloader updates	Comments
		Enter result	Enter result
dustymabe	37.20220929.10.0 on libvirt VM
fifofonix	Existing 36.20220918.2.2 MacOS VMWare Fusion Node	[1]		1. Upgrade to 'next' 37.20220918.1.1 completed successfully including triggering of a custom systemd unit that re-applies custom crypto settings (systemd unit invoking privileged podman call to update-crypto-policies).

Tutorials

Username	Profile	Comments

Miscellaneous

Username	Profile	Documentation	Exploratory testing	Comments
		Enter result	Enter result
fifofonix	Newly provisoned 'next' nodes on AWS		[1]	1. Investigated setting FIPS mode via systemd/podman unit and kernel parameter addition. Seems to work potentially closing long standing issue (https://github.com/coreos/fedora-coreos-tracker/issues/302). Needs independent confirmation.