No edit summary |
(→Ignition Config File: improve formatting) |
||
| Line 34: | Line 34: | ||
=== Ignition Config File === | === Ignition Config File === | ||
The inital-setup is deprecated. | The inital-setup is deprecated (the documentation doesn't reflect it yet). You you want to deploy a disk image, you need to have an ignition config prepared. Here's how: | ||
* [https://zezere.puiterwijk.org/netboot/ignition/00:01:C0:21:43:43 | * Download a [https://zezere.puiterwijk.org/netboot/ignition/00:01:C0:21:43:43 sample ignition json] and save it locally as <code>config.ign</code> | ||
* Replace | * Replace the included ssh public key with your own ssh public key | ||
* Boot the system with these < | * Host the ignition file somewhere (fedorapeople, your server, or https://paste.centos.org and get a link using ''View raw'') | ||
* Boot the system with these kernel arguments: <pre>ignition.firstboot=1 ignition.platform.id=cmdline ignition.config.url=http://<url>/config.ign</pre> and replace <code>http://<url>/config.ign</code> with the URL to your ignition file | |||
* For UEFI devices, use https://fedora-iot.roving-it.com/portal/ | * For UEFI devices, use https://fedora-iot.roving-it.com/portal/ | ||
This is '''not needed''' when you use the <code>.iso</code> installer to install the IoT Edition (then, the standard documented procedure applies). | |||
== How to test? == | == How to test? == | ||
Revision as of 11:25, 4 March 2020
| Fedora Test Day | |
|---|---|
| |
| Fedora IoT Edition | |
| Date | 2020-03-04 |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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?
Today's instalment of Fedora Test Day will focus on Fedora IoT Edition
Who's available?
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
- 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
Ignition Config File
The inital-setup is deprecated (the documentation doesn't reflect it yet). You you want to deploy a disk image, you need to have an ignition config prepared. Here's how:
- Download a sample ignition json and save it locally as
config.ign - Replace the included ssh public key with your own ssh public key
- Host the ignition file somewhere (fedorapeople, your server, or https://paste.centos.org and get a link using View raw)
- Boot the system with these kernel arguments:
ignition.firstboot=1 ignition.platform.id=cmdline ignition.config.url=http://<url>/config.ign
and replacehttp://<url>/config.ignwith the URL to your ignition file - For UEFI devices, use https://fedora-iot.roving-it.com/portal/
This is not needed when you use the .iso installer to install the IoT Edition (then, the standard documented procedure applies).
How to test?
Run the tests
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
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.