From Fedora Project Wiki

Fedora Test Day
Echo-testing-48px.png
Fedora IoT Edition

Date 2019-20-02
Time all day

Website QA/Test Days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
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 ...

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]

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
Pass pass
Pass pass
[1]
Pass pass
  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
alciregi Raspberry Pi 3 aarch64
Pass pass
Pass pass
Pass pass
Fail fail
[1]
Warning warn
[2]
  1. systemctl status bluetooth Active: inactive (dead) Oct 02 15:16:55 host systemd[1]: Condition check resulted in Bluetooth service being skipped.
  2. 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 pass
Pass pass
Pass pass
lbrabec rpi3 aarch64
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
mmerlin KVM, x86_64, bios, raw, serial, video qxl
Warning warn
[1]
Pass pass
[2]
Pass pass
[3]
Pass pass
Pass pass
[4]
  1. 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
  2. error: Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-31&arch=x86_64 on initial install for httpd, but retry worked
  3. Using sudo instead of su -c
  4. 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
Pass pass
Pass pass
pwhalen Pine 64 Plus (aarch64)
Pass pass
[1]
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
  1. Serial console
pwhalen Raspberry Pi 3B
Pass pass
Pass pass
Pass pass
Fail fail
[1]
Pass pass
  1. Bluetooth not working.
pwhalen Seattle Overdrive (aarch64)
Pass pass
Pass pass
syukorx Raspberry Pi 3 B+
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Fail fail
[1]
Pass pass
  1. Bluetooth not working
tdawson Raspberry Pi 3a, 512M, aarch64
Pass pass
Pass pass
[1]
Fail fail
[2]
Pass pass
Pass pass
Fail fail
[3]
Fail fail
[4]
Pass pass
  1. Had to grow root partition and reboot to work
  2. Last two lines of failed install are "Importing rpm-md... done" and "error: Bus owner changed, aborting."
  3. Able to run images, Unable to build images, runs out of memory
  4. Bluetooth not working.
tdawson Raspberry Pi 3b+, 1G, aarch64
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Fail fail
[1]
Pass pass
  1. Bluetooth not working.
tdawson Raspberry Pi 3b, 1G, aarch64
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Fail fail
[1]
Pass pass
  1. Bluetooth not working.
tdawson Rock960 2Gig, aarch64
Pass pass
[1]
Pass pass
Pass pass
Pass pass
Pass pass
Warning warn
[2]
Pass pass
  1. Serial Console only, no HDMI
  2. serial and bluetooth work. wifi no device found