2019-10-02 Fedora 31 IoT Edition

Fedora Test Day

Fedora IoT Edition

Date	2019-10-02
Time	all day

Website	QA/Test Days
IRC	#fedora-test-day (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 Bugzilla, 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 instalment of Fedora Test Day will focus on Fedora IoT Edition

Who's available?[edit]

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...

Development - Pwhalen (Pwhalen)
Quality Assurance - Sumantro Mukherjee (sumantrom), Geoff Marr (coremodule)

For real time help, please join us on the IRC: #fedora-iot^[?] on http://freenode.net

Documentation is also available here. Documentation feedback is welcome through chat, mailing list, or as an issue. NOTE: there is a known issue about the links on the obtaining images page. For the test day, please use the images specified below!

Prerequisites for Test Day[edit]

for x86_64 download the ostree iso
for AArch64 download the ostree iso
for AArch64 SBC's (like the Raspberry Pi 3) download the disk image here
Enough free space on HDD

How to test?[edit]

Run the tests[edit]

Visit the result 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]

This is mostly useful for issues with packaging and for issues that need tracking (blocker bugs for F31): Red Hat Bugzilla.

If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.

Test Results[edit]

Basic Test[edit]

User	Profile	Initial setup	RpmOstree Package Layering	ARM image deployment	Boot Methods Pxeboot	Install to SATA	Base service manipulation	Podman Validation	Rpi Hardware Test	Rebase	References
alciregi	KVM, x86_64, bios, video qxl	pass	pass				pass	pass ^[1]		pass	↑ I always get this message WARN[0000] Error initializing configured OCI runtime runc: no valid executable found for OCI runtime runc: invalid argument, but I get it also on regular F31 installations
alciregi	Raspberry Pi 3 aarch64	pass	pass	pass					fail ^[1] warn ^[2]		↑ systemctl status bluetooth Active: inactive (dead) Oct 02 15:16:55 host systemd[1]: Condition check resulted in Bluetooth service being skipped. ↑ I'm unable to use the serial console. uart=1 is in place, but the console messages stop at EFI stub: Exiting boot services and installing virtual address map...
garrmcnu	Fedora IoT 31.20191001.0 on KVM	pass	pass				pass	pass		pass
lbrabec	rpi3 aarch64	pass	pass	pass			pass	pass		pass
mmerlin	KVM, x86_64, bios, raw, serial, video qxl	warn ^[1]	pass ^[2]				pass ^[3]	pass		pass ^[4]	↑ RHBZ #1757960 Failed to set the requested host name No way to set the root password during initialization No way to cleanly back out or, or clear, setting IPv6 default gateway Help information not available ↑ error: Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-31&arch=x86_64 on initial install for httpd, but retry worked ↑ Using `sudo` instead of `su -c` ↑ Documentation error: https://fedoraproject.org/wiki/User:Pwhalen/QA/IoT_Tests/Rebase says to use "sudo rpm-ostree reboot" which should be "systemctl reboot". Also the last status check is shown as "sudo rpm-ostree status", where "rpm-ostree status" is all that is needed.
pwhalen	KVM, AArch64 Host	pass	pass					pass		pass
pwhalen	Pine 64 Plus (aarch64)	pass ^[1]	pass pass	pass				pass		pass	↑ Serial console
pwhalen	Raspberry Pi 3B	pass		pass				pass	fail ^[1]	pass	↑ Bluetooth not working.
pwhalen	Seattle Overdrive (aarch64)				pass	pass
syukorx	Raspberry Pi 3 B+	pass	pass	pass			pass	pass	fail ^[1]	pass	↑ Bluetooth not working
tdawson	Raspberry Pi 3a, 512M, aarch64	pass	pass ^[1] fail ^[2]	pass			pass	fail ^[3]	fail ^[4]	pass	↑ Had to grow root partition and reboot to work ↑ Last two lines of failed install are "Importing rpm-md... done" and "error: Bus owner changed, aborting." ↑ Able to run images, Unable to build images, runs out of memory ↑ Bluetooth not working.
tdawson	Raspberry Pi 3b+, 1G, aarch64	pass	pass	pass			pass	pass	fail ^[1]	pass	↑ Bluetooth not working.
tdawson	Raspberry Pi 3b, 1G, aarch64	pass	pass	pass			pass	pass	fail ^[1]	pass	↑ Bluetooth not working.
tdawson	Rock960 2Gig, aarch64	pass ^[1]	pass	pass			pass	pass	warn ^[2]	pass	↑ Serial Console only, no HDMI ↑ serial and bluetooth work. wifi no device found

[1] I always get this message WARN[0000] Error initializing configured OCI runtime runc: no valid executable found for OCI runtime runc: invalid argument, but I get it also on regular F31 installations

[2] systemctl status bluetooth Active: inactive (dead) Oct 02 15:16:55 host systemd[1]: Condition check resulted in Bluetooth service being skipped.

[3] I'm unable to use the serial console. uart=1 is in place, but the console messages stop at EFI stub: Exiting boot services and installing virtual address map...

[4] RHBZ #1757960 Failed to set the requested host name No way to set the root password during initialization No way to cleanly back out or, or clear, setting IPv6 default gateway Help information not available

[5] rror: Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-31&arch=x86_64 on initial install for httpd, but retry worked

[6] Using sudo instead of su -c

[7] Documentation error: https://fedoraproject.org/wiki/User:Pwhalen/QA/IoT_Tests/Rebase says to use "sudo rpm-ostree reboot" which should be "systemctl reboot". Also the last status check is shown as "sudo rpm-ostree status", where "rpm-ostree status" is all that is needed.

[8] Serial console

[9] Bluetooth not working.

[10] Bluetooth not working

[11] Had to grow root partition and reboot to work

[12] Last two lines of failed install are "Importing rpm-md... done" and "error: Bus owner changed, aborting."

[13] Able to run images, Unable to build images, runs out of memory

[14] Bluetooth not working.

[15] Bluetooth not working.

[16] Bluetooth not working.

[17] Serial Console only, no HDMI

[18] serial and bluetooth work. wifi no device found

[1]

[1]

[2]

[1]

[2]

[3]

[4]

[1]

[1]

[1]

[1]

[2]

[3]

[4]

[1]

[1]

[1]

[2]

Search

Test Day:2019-10-02 Fedora 31 IoT Edition

Contents