Latest revision |
Your text |
Line 22: |
Line 22: |
| * Quality Assurance - [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:coremodule|Geoff Marr]] (coremodule) | | * Quality Assurance - [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:coremodule|Geoff Marr]] (coremodule) |
|
| |
|
| For real time help, please join us on the IRC: {{fpchat|#fedora-iot}} on http://freenode.net
| | == Prerequisites for Test Day == |
| | |
| Documentation is also available [https://docs.fedoraproject.org/en-US/iot/ here]. Documentation feedback is welcome through chat, mailing list, or as an [https://pagure.io/fedora-iot/iot-docs/issues 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 ==
| | * As of today, the Fedora IoT Edition can be tested be tested by downloading from here [https://kojipkgs.fedoraproject.org/compose/iot/latest-Fedora-IoT-30/compose/] |
| Due to ongoing compose issues in Fedora 30, the testday will focus on available deliverables using yesterdays compose (Fedora-IoT-30-20190312.1).
| |
| * for x86_64 download the [https://kojipkgs.fedoraproject.org/compose//iot/Fedora-IoT-30-20190312.1/compose/IoT/x86_64/iso/Fedora-IoT-ostree-x86_64-30-20190312.1.iso ostree iso]
| |
| * for AArch64 download the [https://kojipkgs.fedoraproject.org/compose//iot/Fedora-IoT-30-20190312.1/compose/IoT/aarch64/iso/Fedora-IoT-ostree-aarch64-30-20190312.1.iso ostree iso]
| |
| * for AArch64 SBC's (like the Raspberry Pi 3) download the [https://kojipkgs.fedoraproject.org//work/tasks/6422/33436422/Fedora-IoT-30-20190312.1.aarch64.raw.xz disk image here]
| |
| * Enough free space on HDD | | * Enough free space on HDD |
|
| |
|
Line 37: |
Line 31: |
| === Run the tests === | | === Run the tests === |
|
| |
|
| Visit the [http://testdays.fedorainfracloud.org/events/62 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. | | Visit the [http://testdays.fedorainfracloud.org/events/xx 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 == | | == Reporting bugs == |
Line 46: |
Line 40: |
|
| |
|
| == Test Results == | | == Test Results == |
| === Basic Test ===
| |
| {|
| |
| ! User
| |
| ! Profile
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_base_initial_setup Initial setup]
| |
| ! [http://fedoraproject.org/wiki/User:Miabbott/QA/AtomicTests/RpmOstree_Package_Layering RpmOstree Package Layering]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_arm_image_deployment ARM image deployment]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_Pxeboot Boot Methods Pxeboot]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_install_to_SATA Install to SATA]
| |
| ! [http://fedoraproject.org/wiki/QA:Testcase_base_service_manipulation Base service manipulation]
| |
| ! [http://fedoraproject.org/wiki/User:Pwhalen/QA/IoT_Tests/Podman_Basic Podman Validation]
| |
| ! [http://fedoraproject.org/wiki/User:Pwhalen/QA/IoT_Tests/RaspberryPi_3 Rpi Hardware Test]
| |
| ! References
| |
| |-
| |
| | [[User:alciregi|alciregi]]
| |
| | MacBookPro5,5
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|pass}}<ref>Testcase as is: OK,
| |
| podman as unprivileged user returns: ERRO[0004] could not find slirp4netns, the network namespace won't be configured: exec: "slirp4netns": executable file not found in $PATH
| |
| </ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:alciregi|alciregi]]
| |
| | x86_64 KVM 2GB RAM 1cpu
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| | {{result|warn}}<ref>with 2GB dracut crashed (https://alciregi.fedorapeople.org/screenshot/iotpxe.png), I had to assign 3GB of RAM</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:bikramUTD|bikramUTD]]
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:calinoiualex|calinoiualex]]
| |
| | Fedora-IoT-ostree-x86_64-30-20190312.1.iso running on libvirt/kvm with 4 CPUs and 2 GB RAM
| |
| | {{result|pass}}<ref>1. Installed with default settings, including the default disk layout. Only set the root password during the install phase, did not create a standard user account. After reboot, the initial setup utility runs automatically, as it should, user creation was successful. Also, login with the newly created account works as expected. </ref>
| |
| | {{result|pass}}<ref>All tests passed successfully.</ref>
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>All tests ran successfully.</ref>
| |
| | {{result|pass}}<ref>Followed steps in wiki. Every step completed successfully.</ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:fab|fab]]
| |
| |
| |
| | {{result|pass}}<ref>Tested with Fedora-IoT-ostree-x86_64-30-20190215.0.iso</ref>
| |
| | {{result|pass}}<ref>Used 30.20190311.0</ref>
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>Used 30.20190311.0 </ref>
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:laubersm|laubersm]]
| |
| | F29 libvirt/KVM - (2G RAM, 1 CPU, 8G disk file, default nat network) from Fedora-IoT-ostree-x86_64-30-20190312.1.iso
| |
| | {{result|pass}}<ref>during install, changed timezone (defaulted to Central?), auto partition. Set root password but did not create a user.
| |
| Created user with password and as admin during inital setup dialog. All worked as expected.</ref>
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|pass}}<ref>Also worked as user (rootless) with two changes:
| |
| (1) install network namespace support: rpm-ostree install --reboot slirp4netns
| |
| (2) port forward to a non privilaged port: podman run -p 8080:80 </ref>
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:laubersm|laubersm]]
| |
| | rpi3 B+ with 16GB SanDisk Ultra. USB keyboard (no mouse), HDMI display
| |
| | {{result|pass}}<ref>Booted right up and showed the setup. Note no console added to grub:
| |
| $ cat /proc/cmdline
| |
| BOOT_IMAGE=(hd0,msdos2)/ostree/fedora-iot-6542e513f9f4574dc666f82314a6ab0357707892d3229d03fb147fe912378ac4/vmlinuz-5.0.0-300.fc30.aarch64 net.ifnames=0 modprobe.blacklist=vc4 root=UUID=040d735a-2828-4e4a-9ec8-c4304ead7712 ostree=/ostree/boot.0/fedora-iot/6542e513f9f4574dc666f82314a6ab0357707892d3229d03fb147fe912378ac4/0</ref>
| |
| |
| |
| | {{result|warn}}<ref>I reset SD card with more options: --image=Fedora-IoT-30-20190312.1.aarch64.raw.xz --target=rpi3 --media=/dev/mmcblk0 --resizefs --addconsole --addkey=/home/susan/.ssh/id_rsa.pub --args "console=tty0"
| |
| The resizefs worked as did the addkey. addconsole does make sure that the config.txt has enable_uart=1 but nothing gets added to the grub console line for the console. There is a "sed: can't read /tmp/boot/extlinux/extlinux.conf: No such file or directory" message which is expected since this file does not exist. no console=tty0 in any of the /boot config files or after booting in cat /proc/cmdline. </ref>{{result|pass}}<ref>arm-image-installer-2.10 (from F29) with minimal options --image=Fedora-IoT-30-20190312.1.aarch64.raw.xz --target=rpi3 --media=/dev/mmcblk0</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|warn}}<ref>Used HDMI for display. No serial console configured.
| |
| initial boot with wired lan but wifi tests work great!
| |
| bluetooth service "inactive (dead)" I was able to systemctl start bluetooth but bluetoothctl still shows "No default controller available". </ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:lavanajain|lavanajain]]
| |
| |
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:lbrabec|lbrabec]]
| |
| | RPi3, Fedora-IoT-30-20190312.1.aarch64.raw.xz, HDMI, USB keyboard
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|warn}}<ref>Wifi works, bluetooth doesn't (service "inactive (dead)", condition check resulted in bluetooth service being skipped)</ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:maxentropy|maxentropy]]
| |
| | I3-4360 Gigabyte GA-Z97X-SLI 8GB Inland 120GB SATA SSD
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:pwhalen|pwhalen]]
| |
| | Fitlet2 (x86_64)
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>{{bz|1688283}} pxe boot with kickstart. Clevis fails to unlock encrypted partition. </ref>
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:pwhalen|pwhalen]]
| |
| | Raspberry Pi 3B+
| |
| | {{result|pass}}
| |
| |
| |
| | {{result|warn}}<ref>{{bz|1688453}} </ref>{{result|pass}}<ref>When booting two identical grub menu entries appear, this appears to be because we have a bls snippet and grub.cfg</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|warn}}<ref>consoles listed should be 'console=ttyS0,115200 console=tty0'</ref>{{result|warn}}<ref>To use the serial console I added 'console=ttyS1,115200 console=tty0' to the bls snippet (/boot/loader/entries/ostree-1-fedora-iot.conf) . This gave working output on display and serial console. Wifi working. Bluetooth failed to start at boot. </ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:szydell|szydell]]
| |
| | Fedora IoT 30.20190215.0 -> Virtualbox 5.2.24 -> Fedora KDE 29 -> System76 Oryx Pro (oryp4), i7-8750H, 32GB ram
| |
| | {{result|pass}}
| |
| | {{result|fail}}<ref>screenshot with an error message: https://postimg.cc/sBzz1LD1</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:tdawson|tdawson]]
| |
| | Raspberry Pi 3a+ / 32 G Samsung EVO sd card / Fedora-IoT-30-20190312.1.aarch64.raw.xz
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|fail}}<ref>It passed installing and running images. It fails building an image with "fatal error: runtime: out of memory". The 3a+ only has 512M of memory.</ref>
| |
| | {{result|warn}}<ref>{{bz|1688453}} Serial Console: Passed - Had to put "console=tty0 console=ttyS0,115200" on proper lines in /boot/efi/EFI/fedora/grub.cfg | Display: Passed | Wifi: Passed | Bluetooth: Failed - no device found.</ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:tdawson|tdawson]]
| |
| | Raspberry Pi 3b / 32 G Samsung EVO sd card / Fedora-IoT-30-20190312.1.aarch64.raw.xz
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|warn}}<ref>{{bz|1688453}} Serial Console: Passed - Had to put "console=tty0 console=ttyS0,115200" on proper lines in /boot/efi/EFI/fedora/grub.cfg and /boot/loader/entries/ostree-1-fedora-iot.conf | Display: Passed | Wifi: Passed | Bluetooth: Failed - no device found.</ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:tdawson|tdawson]]
| |
| | Raspberry Pi 3b+ / 32 G Samsung EVO sd card / Fedora-IoT-30-20190312.1.aarch64.raw.xz
| |
| | {{result|pass}}<ref>HDMI Output / USB mouse and keyboard input</ref>
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| |
| |
| |
| |
| | {{result|pass}}
| |
| | {{result|pass}}
| |
| | {{result|warn}}<ref>{{bz|1688453}} Serial Console: Passed - Had to put "console=tty0 console=ttyS0,115200" on proper lines in /boot/efi/EFI/fedora/grub.cfg and /boot/loader/entries/ostree-1-fedora-iot.conf | Display: Passed | Wifi: Passed | Bluetooth: Failed - no device found.</ref>
| |
| | <references/>
| |
| |-
| |
| | [[User:tjakobsen|tjakobsen]]
| |
| | Fedora 29 (i7-7500U) running VirtualBox 6.0 with 2GB RAM and 1 vCPU.
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | {{result|pass}}<ref>All went accordingly. </ref>
| |
| |
| |
| |
| |
| | <references/>
| |
| |-
| |
| | [[User:tjakobsen|tjakobsen]]
| |
| | Fedora 29 (i7-7500U) running VirtualBox 6.0 with 4GB RAM and 2 vCPU.
| |
| | {{result|pass}}<ref>I gave root a password at install, all values are default. After a reboot I got the initial-setup, in this I created my user. I was able to login, root password was set and the timezone was OK.</ref>
| |
| | {{result|pass}}<ref>All went accordingly.</ref>
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | <references/>
| |
|
| |
| |-
| |
| |}
| |
|
| |
|
| [[Category:Fedora 30 Test Days]]
| | Test results will be transferred once the test day is over |