Fedora 33 CoreOS 2020-11-06

Fedora CoreOS Test Week

Fedora CoreOS

Date	2020-11-06 to 2020-11-12
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 http://freenode.net

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)
Test day Image

Grab images/artifacts/information for the most current next stream release (33.20201104.1.0) 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[edit]

Installation[edit]

User	Profile	Virtual install	Bare Metal install	References
Blu3	qemu virt-install ignition provisioned	pass
akumar99	KVM	pass ^[1]		↑ Worked fine.
bakers46@gilanet.com			pass
copperi	KVM	pass
danniel	KVM	pass	pass pass
donaldsebleung	Provisioning Fedora CoreOS on QEMU	pass
drakkai	libvirt	pass ^[1]		↑ Booted without problems, works fine.
ed.schmidt26@gmail.com	Bare Metal		pass ^[1]	↑ Pass HP Probook 650 install Great job
galoget	QEMU/KVM	pass
jimtahu	virt-install with ssh-key in ignition	pass ^[1]		↑ also manually ran some podman instances on the newly launched system
jlebon	"virtualized" bare metal		pass ^[1]	↑ A few UX improvements to `coreos-installer download` filed in https://github.com/coreos/coreos-installer/issues/406.
joydeep	QEMU/KVM	pass
lbazan	KVM	pass
lbazan	supermicro		pass
lucasaf88	QEMU/KVM	pass
nasirhm	qemu-kvm	pass ^[1]		↑ SSH configuration works as expected.
nielsenb	QEMU/KVM	pass
olem	libvirt	pass ^[1]		↑ Used coreos-installer and virt-install. No issue to launch the VM and log in.
pruthvi30sk	Intel® Core™ i7-8700U CPU @ 2.10GHz × 4	pass ^[1]	pass	↑ Installed successfully without any issue.
russ			pass ^[1]	↑ test bed was Thinkpad T400, saw some bash returns where my favorite scripts weren't in the vocabulary.
russk	libvirt/QEMU	pass ^[1]		↑ Got instance running and able to SSH in successfully. In "Producing an Ignition File" doc, you might change "Using FCCT" section label to be called "Convert FCC File to IGN Ignition File". That would more accurately describe the step.
sayaksarkar	qemu-kvm	pass
siddharthvipul1	virt-manager	pass
sinnykumari	Virtual install	pass ^[1]		↑ Works as described in Test case
sumantrom		pass	pass
uwueviee	KVM	pass

Cloud launch[edit]

User	Profile	AWS	Azure	GCP	DigitalOcean	VMWare	IBM Cloud	References
akumar99	t2.micro - all default	pass ^[1]						↑ Worked fine.
cptmorgan-rh						pass ^[1]		↑ Worked as expected.
dghubble	33.20201104.1.0				pass ^[1]			↑ FRA1
dustymabe	fedora-coreos-33.20201104.1.0-ibmcloud.x86_64.qcow2						pass ^[1]	↑ Seemed to work when following the documentation.
knarra	AWS [core@ip-172-31-88-179 ~]$ cat /etc/redhat-release Fedora release 33 (Thirty Three)	pass ^[1]						↑ Works with out any issues
lucasaf88	GCP			pass ^[1]				↑ Tested with custom Ignition file and access with ssh. Everything worked fine.
mnguyen				pass ^[1]				↑ [core@fcos-mnguyen ~]$ sudo rpm-ostree status State: idle Deployments: ● ostree://fedora:fedora/x86_64/coreos/next Version: 33.20201104.1.0 (2020-11-05T14:20:13Z) Commit: f7bff56c9710b5fedb22d50651bcd875856bb83510f7115e10d21167bd9a3b75 GPGSignature: Valid signature by 963A2BEB02009608FE67EA4249FD77499570FF31
nb		pass ^[1]						↑ [core@ip-172-30-1-165 ~]$ sudo rpm-ostree status State: idle Deployments: ● ostree://fedora:fedora/x86_64/coreos/next Version: 33.20201104.1.0 (2020-11-05T14:20:13Z) Commit: f7bff56c9710b5fedb22d50651bcd875856bb83510f7115e10d21167bd9a3b75 GPGSignature: Valid signature by 963A2BEB02009608FE67EA4249FD77499570FF31 [core@ip-172-30-1-165 ~]$
nielsenb	ami-08ae7387308b22a6a, t2.micro	pass ^[1]						↑ Used named key
olem	aws	pass ^[1]						↑ Used AWS web UI to provision the VM; passed ignition as user data.
pruthvi30sk	Intel® Core™ i7-8700U CPU @ 2.10GHz × 4	pass ^[1]						↑ Installation was fine
pruthvi30sk	azure		pass
sinnykumari	AWS	pass ^[1]						↑ Tested in ap-southeast-1 region

Advanced configuration[edit]

User	Profile	Complex partitioning	Building containers	Containerized service	References
cptmorgan-rh				pass ^[1]	↑ Used my fcos-gitlab repo to deploy on `next` release. Worked as expected. - https://github.com/cptmorgan-rh/fcos-gitlab
danniel	KVM		pass	pass
donaldsebleung	Provisioning Fedora CoreOS on QEMU		pass ^[1]	pass ^[2]	↑ All 6 basic tests passed. Also tried using the containers to convert example.fcc in https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/#_writing_the_fcc_file to example.ign with expected results. Additionally, tried NGINX with port forwarding (8080->80) with rootless podman, privileged podman and docker and all work as expected. ↑ /bin/podman kill busybox1 and /bin/podman rm busybox1 exited with codes 125 and 1 respectively but I suppose that should be expected on the first run since the container does not exist yet. Other than that, systemctl status hello gives a status of "active (running)" and Hello World is printed every second as expected.
jlebon	"virtualized" bare metal	pass ^[1]	pass ^[2]	pass ^[3]	↑ Tested with /var on LUKS on a separate disk ↑ Built and ran fcct as rootless podman and privileged podman. ↑ Successfully ran busybox example as a service
lucasaf88	GCP		pass ^[1]		↑ Tested all steps on an FCOS instance in GCP.
mnguyen			pass	pass ^[1]	↑ No issues found
nasirhm	qemu-kvm		pass ^[1] pass ^[2]	pass ^[3]	↑ rootless podman works fine too. ↑ Privileged Docker and Podman works fine. ↑ Busybox as a containerized service works fine.
olem	aws		pass ^[1] pass ^[2]		↑ Launched FCOS vm on eu-west-1 using rancher-machine (https://github.com/rancher/machine). Tested docker daemon shared over network. ↑ All basic tests worked (rootless podman, privileged podman, docker). Also accessed network from the containers.

Upgrade[edit]

User	Profile	Switch stream	References
donaldsebleung	Provisioning Fedora CoreOS on QEMU	pass ^[1]	↑ Performed basic testing plus point #2 in the "Optional" section (temporary and permanent rollbacks). Everything was as expected, though the only service I tested was that zincati was up and running after every reboot.
lucab	aliyun - ecs.c6e.large	pass
nasirhm	qemu-kvm	pass ^[1] pass ^[2]	↑ Rollback works fine too. ↑ Rebased from stable to next
olem	libvirt	pass ^[1]	↑ Updated from stable (32.20201018.3.0) to next (33.20201104.1.0), then permanent rollback to 32.20201018.3.0, then again permanent rollback to 33.20201104.1.0. I launched a web application on Docker before the upgrade; it still worked after the upgrade and then after the restorations. I observed that moby-engine was upgraded from 19.03.11 to 19.03.13 and back.
sinnykumari	Switch stream	pass ^[1]	↑ Rebase from stable to next works fine, rollback works fine, container related changes exist and works as expected with switching stream

Miscellaneous[edit]

User	Profile	Documentation	Exploratory testing	References
dustymabe	33.20201104.1.0 qemu qcow2		pass ^[1]	↑ Ran the manual network testing script at https://github.com/coreos/fedora-coreos-config/blob/testing-devel/tests/manual/coreos-network-testing.sh . Passed all tests.
dustymabe	fedora-coreos-33.20201104.1.0-openstack.x86_64.qcow2		pass ^[1]	↑ Tested out running on openstack using the new documentation I just wrote: https://github.com/coreos/fedora-coreos-docs/pull/202
jingzhan			pass ^[1]	↑ 1. Tested creating snapshot and running a fcos instance on vultr using the `next` release, all tests worked.
lucab	aliyun - ecs.c6e.large	pass ^[1]		↑ Verified cloud SSH pubkey too.

[1] Worked fine.

[2] Booted without problems, works fine.

[3] Pass HP Probook 650 install Great job

[4] so manually ran some podman instances on the newly launched system

[5] A few UX improvements to coreos-installer download filed in https://github.com/coreos/coreos-installer/issues/406.

[6] SSH configuration works as expected.

[7] Used coreos-installer and virt-install. No issue to launch the VM and log in.

[8] Installed successfully without any issue.

[9] test bed was Thinkpad T400, saw some bash returns where my favorite scripts weren't in the vocabulary.

[10] Got instance running and able to SSH in successfully. In "Producing an Ignition File" doc, you might change "Using FCCT" section label to be called "Convert FCC File to IGN Ignition File". That would more accurately describe the step.

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[2]

[1]

[2]

[3]

[1]

[1]

[1]

[2]

[3]

[1]

[2]

[1]

[1]

[2]

[1]

[1]

[1]

[1]

[1]

[1]

Search

Test Day:Fedora 33 CoreOS 2020-11-06

Contents