Fedora 31 IoT Edition Test Day

More information about the event can be found here: http://fedoraproject.org/wiki/Test_Day:2019-10-02_Fedora_31_IoT_Edition
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.
Note: results are cached and realoaded from the database each 10 seconds.

Basic Test

Username Profile Initial setup RpmOstree Package Layering ARM image deployment Boot Methods Pxeboot Install to SATA Base service manipulation Podman Validation Rpi Hardware Test Rebase Comments
Enter result Enter result Enter result Enter result Enter result Enter result Enter result Enter result Enter result
alciregi KVM, x86_64, bios, video qxl [1] 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 [1] [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
lbrabec rpi3 aarch64
mmerlin KVM, x86_64, bios, raw, serial, video qxl [1] [2] [3] [4] 1. #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 "s udo rpm-ostree status", where "rpm-ostree status" is all that is needed.
pwhalen KVM, AArch64 Host
pwhalen Pine 64 Plus (aarch64) [1] 1. Serial console
pwhalen Raspberry Pi 3B [1] 1. Bluetooth not working.
pwhalen Seattle Overdrive (aarch64)
syukorx Raspberry Pi 3 B+ [1] 1. Bluetooth not working
tdawson Raspberry Pi 3a, 512M, aarch64 [1] [2] [3] [4] 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 [1] 1. Bluetooth not working.
tdawson Raspberry Pi 3b, 1G, aarch64 [1] 1. Bluetooth not working.
tdawson Rock960 2Gig, aarch64 [1] [2] 1. Serial Console only, no HDMI
2. serial and bluetooth work. wifi no device found
Wiki Metadata