Fedora IoT Edition Test Day

More information about the event can be found here: http://fedoraproject.org/wiki/Test_Day:Fedora_IoT_Edition_2019-03-13
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 Comments
Enter result Enter result Enter result Enter result Enter result Enter result Enter result Enter result
alciregi MacBookPro5,5 [1] 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 [1] 1. with 2GB dracut crashed (https://alciregi.fedorapeople.org/screenshot/iotpxe.png), I had to assign 3GB of RAM
calinoiualex Fedora-IoT-ostree-x86_64-30-20190312.1.iso running on libvirt/kvm with 4 CPUs and 2 GB RAM [1] [2] [3] [4] 1. 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.
2. All tests passed successfully.
3. All tests ran successfully.
4. Followed steps in wiki. Every step completed successfully.
fab [1] [2] [3] 1. Tested with Fedora-IoT-ostree-x86_64-30-20190215.0.iso
2. Used 30.20190311.0
3. 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 [1] [2] 1. 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.
2. 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 [1] [2] [3] [4] 1. 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
2. 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.
3. arm-image-installer-2.10 (from F29) with minimal options --image=Fedora-IoT-30-20190312.1.aarch64.raw.xz --target=rpi3 --media=/dev/mmcblk0
4. 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".
lbrabec RPi3, Fedora-IoT-30-20190312.1.aarch64.raw.xz, HDMI, USB keyboard [1] 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
pwhalen Fitlet2 (x86_64) [1] 1. #1688283, pxe boot with kickstart. Clevis fails to unlock encrypted partition.
pwhalen Raspberry Pi 3B+ [1] [2] [3] [4] 1. #1688453,
2. When booting two identical grub menu entries appear, this appears to be because we have a bls snippet and grub.cfg
3. consoles listed should be 'console=ttyS0,115200 console=tty0'
4. 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 [1] 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 [1] [2] 1. 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.
2. #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 [1] 1. #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 [1] [2] 1. HDMI Output / USB mouse and keyboard input
2. #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. [1] 1. All went accordingly.
tjakobsen Fedora 29 (i7-7500U) running VirtualBox 6.0 with 4GB RAM and 2 vCPU. [1] [2] 1. 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.
2. All went accordingly.
Wiki Metadata