Test Day:2019-03-13 Fedora IoT Edition: Difference between revisions

Latest revision as of 13:47, 16 April 2019

Fedora Test Day

Fedora IoT Edition

Date	2019-03-13
Time	all day

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

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[edit]

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 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

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 F30): 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	References
alciregi	MacBookPro5,5	pass	pass				pass	pass ^[1]		↑ 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
alciregi	x86_64 KVM 2GB RAM 1cpu	pass			warn ^[1]					↑ with 2GB dracut crashed (https://alciregi.fedorapeople.org/screenshot/iotpxe.png), I had to assign 3GB of RAM
bikramUTD		pass
calinoiualex	Fedora-IoT-ostree-x86_64-30-20190312.1.iso running on libvirt/kvm with 4 CPUs and 2 GB RAM	pass ^[1]	pass ^[2]				pass ^[3]	pass ^[4]		↑ 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. ↑ All tests passed successfully. ↑ All tests ran successfully. ↑ Followed steps in wiki. Every step completed successfully.
fab		pass ^[1]	pass ^[2]				pass ^[3]			↑ Tested with Fedora-IoT-ostree-x86_64-30-20190215.0.iso ↑ Used 30.20190311.0 ↑ Used 30.20190311.0
laubersm	F29 libvirt/KVM - (2G RAM, 1 CPU, 8G disk file, default nat network) from Fedora-IoT-ostree-x86_64-30-20190312.1.iso	pass ^[1]	pass				pass	pass ^[2]		↑ 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. ↑ 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
laubersm	rpi3 B+ with 16GB SanDisk Ultra. USB keyboard (no mouse), HDMI display	pass ^[1]		warn ^[2] pass ^[3]					warn ^[4]	↑ 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 ↑ 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. ↑ arm-image-installer-2.10 (from F29) with minimal options --image=Fedora-IoT-30-20190312.1.aarch64.raw.xz --target=rpi3 --media=/dev/mmcblk0 ↑ 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".
lavanajain		pass
lbrabec	RPi3, Fedora-IoT-30-20190312.1.aarch64.raw.xz, HDMI, USB keyboard	pass	pass	pass			pass	pass	warn ^[1]	↑ Wifi works, bluetooth doesn't (service "inactive (dead)", condition check resulted in bluetooth service being skipped)
maxentropy	I3-4360 Gigabyte GA-Z97X-SLI 8GB Inland 120GB SATA SSD	pass	pass			pass	pass	pass
pwhalen	Fitlet2 (x86_64)				pass ^[1]	pass	pass	pass		↑ RHBZ #1688283 pxe boot with kickstart. Clevis fails to unlock encrypted partition.
pwhalen	Raspberry Pi 3B+	pass		warn ^[1] pass ^[2]					warn ^[3] warn ^[4]	↑ RHBZ #1688453 ↑ When booting two identical grub menu entries appear, this appears to be because we have a bls snippet and grub.cfg ↑ consoles listed should be 'console=ttyS0,115200 console=tty0' ↑ 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.
szydell	Fedora IoT 30.20190215.0 -> Virtualbox 5.2.24 -> Fedora KDE 29 -> System76 Oryx Pro (oryp4), i7-8750H, 32GB ram	pass	fail ^[1]							↑ screenshot with an error message: https://postimg.cc/sBzz1LD1
tdawson	Raspberry Pi 3a+ / 32 G Samsung EVO sd card / Fedora-IoT-30-20190312.1.aarch64.raw.xz	pass	pass	pass			pass	fail ^[1]	warn ^[2]	↑ 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. ↑ RHBZ #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.
tdawson	Raspberry Pi 3b / 32 G Samsung EVO sd card / Fedora-IoT-30-20190312.1.aarch64.raw.xz	pass	pass	pass			pass	pass	warn ^[1]	↑ RHBZ #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.
tdawson	Raspberry Pi 3b+ / 32 G Samsung EVO sd card / Fedora-IoT-30-20190312.1.aarch64.raw.xz	pass ^[1]	pass	pass			pass	pass	warn ^[2]	↑ HDMI Output / USB mouse and keyboard input ↑ RHBZ #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.
tjakobsen	Fedora 29 (i7-7500U) running VirtualBox 6.0 with 2GB RAM and 1 vCPU.						pass ^[1]			↑ All went accordingly.
tjakobsen	Fedora 29 (i7-7500U) running VirtualBox 6.0 with 4GB RAM and 2 vCPU.	pass ^[1]	pass ^[2]							↑ 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. ↑ All went accordingly.

[1] 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

[2] with 2GB dracut crashed (https://alciregi.fedorapeople.org/screenshot/iotpxe.png), I had to assign 3GB of RAM

[3] 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.

[4] All tests passed successfully.

[5] All tests ran successfully.

[6] Followed steps in wiki. Every step completed successfully.

[7] Tested with Fedora-IoT-ostree-x86_64-30-20190215.0.iso

[8] Used 30.20190311.0

[9] Used 30.20190311.0

[10] uring 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.

[11] 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

[12] 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

[13] 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.

[14] rm-image-installer-2.10 (from F29) with minimal options --image=Fedora-IoT-30-20190312.1.aarch64.raw.xz --target=rpi3 --media=/dev/mmcblk0

[15] 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".

[16] Wifi works, bluetooth doesn't (service "inactive (dead)", condition check resulted in bluetooth service being skipped)

[17] RHBZ #1688283 pxe boot with kickstart. Clevis fails to unlock encrypted partition.

[18] RHBZ #1688453

[19] When booting two identical grub menu entries appear, this appears to be because we have a bls snippet and grub.cfg

[20] soles listed should be 'console=ttyS0,115200 console=tty0'

[21] 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.

[22] screenshot with an error message: https://postimg.cc/sBzz1LD1

[1]

[1]

[1]

[2]

[3]

[4]

[1]

[2]

[3]

[1]

[2]

[1]

[2]

[3]

[4]

[1]

[1]

[1]

[2]

[3]

[4]

[1]

[1]

[2]

[1]

[1]

[2]

[1]

[1]

[2]

Search