From Fedora Project Wiki

Fedora Test Day
Fedora IoT Edition

Date 2020-03-04
Time all day

Website QA/Test Days
IRC #fedora-iot (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 ...

For real time help, please join us on the IRC: #fedora-iot[?] on

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 F32): Red Hat Bugzilla under "IoT".

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]

Network Boot[edit]

User Profile PXE Boot References


User Profile Install to SATA Install to VirtIO References
lnie Fedora-IoT-IoT-dvd-x86_64-32-20200408.0.iso,KVM
Fail fail
  1. stucked at "Reached target basic system",then Dracut Emergency Shell was started due to "/dev/root dose not exits"


User Profile Previous KVM Current KVM References

Disk Image Deployment[edit]

User Profile ARM image deployment References
frantisekz rpi4
Fail fail
  1. Booting got stuck on NetworkManager loop. Both with (Connecting > Timeout > Connecting ... ) and without ethernet connected.
lbrabec rpi3
Warning warn
  1. Copied ssh public key to the root account using the fedora-arm-installer
Warning warn rpi4
Fail fail


User Profile Zezere Ignition Base service manipulation RpmOstree Package Layering Podman Validation Rpi Hardware Test Rebase Clevis References
lbrabec rpi3
Pass pass