Fedora 37 CoreOS 2022-09-29

Fedora CoreOS Test Week

Fedora CoreOS

Date	2022-09-29 to 2022-10-03
Time	all week

Website	QA/Test Days
IRC	#fedora-coreos (webirc)
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 - 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 the IRC: #fedora-coreos^[?] on https://libera.chat/.

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 (37) from our download page: https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=next

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, just ask on IRC #fedora-coreos^[?], #fedora-test-day^[?] or #fedora-qa^[?] and we will help you.

Test Results ===== Installation =[edit]

User	Profile	Virtual install	Bare Metal install
ersen	Virtualbox	pass
ersen	v 36.20220906.3.2	pass
geraldosimiao	fedora-coreos-37.20220918.1.1	pass	pass
nielsenb	KVM, x86_64, fedora-coreos-37.20220918.1.1	pass	pass
ravanelli	fedora-coreos-37.20220918.1.1		pass

Cloud launch[edit]

User	Profile	VMWare	IBM Cloud	VirtualBox	Vultr	OpenStack	Alibaba	References
fifofonix	vSphere 7.0.3.00500 on NUCs	pass ^[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							pass
jlebon	37.20220918.1.1/x86_64					pass ^[1]		↑ No issues. Ignition config fetched, SSH works fine, no failed units, networking seems fine.
mnguyen			pass ^[1]					↑ Installed with no issues
ravanelli	ravanelli			pass ^[1]				↑ Tested via Mac using VirtualBox version 6.1.34 r150636
sohank2602					pass ^[1]			↑ An FCOS VM boots up using an ignition config without any issues.

aarch64[edit]

User	Profile	AWS	Virtual install	Bare Metal install	References
jskladan	Disregard	warn ^[1]			↑ Just testing Testdays-Web changes

Advanced configuration[edit]

User	Profile	Static networking	Complex partitioning	Building containers	Containerized service	OS extensions	Configuring SwapOnZRAM	Configuring Time Zone	Debugging with Toolbox	Setting alternatives	Node counting	References
Nemric	Fedora CoreOS 37.20220918.1.1 automatically updated			pass ^[1] warn ^[2]			pass ^[3]		pass ^[4]			↑ Build my own container with success in rootless mode ↑ 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 ↑ 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] ↑ Only followed https://docs.fedoraproject.org/en-US/fedora-coreos/debugging-with-toolbox/
Nemric	Fedora CoreOS 37.20220918.1.1 automaticly updated				pass
dustymabe	37.20221003.10.0 on libvirt VM	pass ^[1]										↑ passed manual static networking test script at https://github.com/coreos/fedora-coreos-config/blob/testing-devel/tests/manual/coreos-network-testing.sh
fifofonix											pass ^[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					pass ^[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	pass	pass ^[1]				pass					↑ Tested with luks
jlebon	37.20220918.1.1/x86_64/QEMU		pass ^[1]							pass ^[2]		↑ No issues. Tried partitioning and LUKS reprovisioning. ↑ 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			pass	pass	pass	pass	pass

Upgrade[edit]

User	Profile	Switch stream	Bootloader updates	References
dustymabe	37.20220929.10.0 on libvirt VM		pass
fifofonix	Existing 36.20220918.2.2 MacOS VMWare Fusion Node	pass ^[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[edit]

User	Profile	References

Miscellaneous[edit]

User	Profile	Documentation	Exploratory testing	References
fifofonix	Newly provisoned 'next' nodes on AWS		pass ^[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.

[1] Had to deploy with govc import.ova -name ${VM_NAME} ${FCOS_OVA} as I am not permissioned to load FCOS_OVA to library.

[2] No issues. Ignition config fetched, SSH works fine, no failed units, networking seems fine.

[3] Installed with no issues

[4] Tested via Mac using VirtualBox version 6.1.34 r150636

[5] An FCOS VM boots up using an ignition config without any issues.

[6] Just testing Testdays-Web changes

[7] Build my own container with success in rootless mode

[8] 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

[9] 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]

[10] Only followed https://docs.fedoraproject.org/en-US/fedora-coreos/debugging-with-toolbox/

[11] ssed manual static networking test script at https://github.com/coreos/fedora-coreos-config/blob/testing-devel/tests/manual/coreos-network-testing.sh

[12] - 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.

[13] Chose to install open-vm-tools instead of vim: /usr/bin/rpm-ostree install --idempotent --allow-inactive open-vm-tools

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[2]

[3]

[4]

[1]

[1]

[1]

[1]

[1]

[2]

[1]

[1]

Search

Test Day:Fedora 37 CoreOS 2022-09-29

Contents