Fedora 34 CoreOS Test Day

More information about the event can be found here: http://fedoraproject.org/wiki/Test_Day:Fedora_34_CoreOS_2021-04-26
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.

Installation

Username Profile Virtual install Bare Metal install Comments
Enter result Enter result
Maddox Grey Lenovo yoga 730-ikb, gnome boxen [1] 1. Works just fine!
Vaclavk
akumar99 VM (AMD Ryzen 9 3900X)
baumkuchen42 KVM [1] 1. # Download as described in manual didn't work https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-qemu/ needs decompressed qcow2 image, downloaded image from https://getfedora.org/coreo s/download?tab=metal_virtualized&stream=next is a compressed image, don't know how to decrompress this kind of file, simple decompressing in nautilus doesn't work # Solution: `$ coreos-installer download -u https://builds.coreos.fedoraproject.org/prod/streams/next/builds/34.20210418.1.0/x86_64/fedora-coreos-34.20210418.1.0-qemu.x86_64.qcow2.xz -d` # Failed to generate ignition file ```sh $ butane --pretty --strict < example.bu > example.ign Error translating config: yaml: unmarshal errors: line 7: cannot unmarshal !!map into v0_3.SSHAuthorizedKey ``` I followed https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/ and copied my public rsa key after the `- ssh-rsa`.
bhavdeep009 fedora33. Processor: AMD Ryzen5. Lenovo IdeaPad 3 15ADA05, RAM: 8GB, Graphics card: AMD Radeon 2GB [1] 1. upgraded through software center from fedora 33
bittin HP 655 [1] 1. Failed Systemd service: systemd-backlight@backlight:acpi_video0.service
bittin Virtualbox
danniel KVM
donaldsebleung Launching with QEMU; Host: Ubuntu 20.04 LTS, x86_64, 4G RAM, Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz x 4
ersen virt-manager 3.2.0-2.fc33, qemu-kvm 2:5.1.0-9.fc33
figonzal VM: QEMU/KVM, CPU: 2 vCPU / 8 CPU, RAM: 2048 MiB / 7831 MiB, x86_64 -> Mode details: https://linux-hardware.org/?probe=bb7915aaba [1] 1. Everything working
garrmcnu 20210427.1.0 with QEMU
geraldosimiao KVM - Qemu-system [1] 1. Image tested: coreos-34.20210418.1.0-qemu.x86_64
jdoss Ignition file with 10 containerized services launched via systemd and Podman [1] 1. QEMU launched with qemu-kvm -m 2048 -cpu host -snapshot -daemonize \ -drive if=virtio,file={{ fcos_extraction_location }}/{{ fcos_download_basename | splitext | first }} \ -fw_cfg name=o pt/com.coreos/config,file={{ butane_ignition_file }} \ -nic user,model=virtio,hostfwd=tcp::2222-:22,hostfwd=tcp::9090-:9090
jlebon "virtualized" bare metal [1] 1. #1942205, #1932053, Hit known SELinux denials (RHBZs linked above). Apart from that, install went well.
lbazan x1 carbon
mythcat https://linux-hardware.org/?probe=7b4c090391
sayaksarkar 34.20210418.1.0 next VM in Boxes on Fedora 33 WS [1] 1. Works as expected!
shivkumar Fedora 33(Generic) | qemu-kvm-5.1.0-9.fc33.x86_64 | Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz | RAM: 16 Gb
sumantrom KVM [1] 1. Launched with ignition with multiple containerized services. All works good.
theonlyandy Lenovo T470s, QEMU
thunderbirdtr 34.20210418.1.0 next VM in Qemu / F34 KDE
tieredblocks [1] 1. Tested using Boxes
tieredblocks Lenovo T450; coreos-installer; 2048 MB; qemu; 20210418.1.0;
uwueviee [1] 1. Site downloaded a compressed version of the image, had to use coreos-installer to get a proper qcow2 file.
vipul0 Lenovo T460, QEMU [1] 1. works fine :)
zlopez Virtual Machine: GNOME Boxes 40.0-28981f2a

Cloud launch

Username Profile AWS Azure GCP DigitalOcean VMWare Exoscale IBM Cloud Comments
Enter result Enter result Enter result Enter result Enter result Enter result Enter result
donaldsebleung AWS CLI (no ignition file)
donaldsebleung AWS CLI (with ignition file) [1] 1. I could successfully create the instance with the simplest example Ignition file (the one with SSH key only) and could ping the instance after setting the security group to allow all traffic, but get a "Connection refused" when trying to SSH into the instance even after waiting for 5+ minutes for the instance to stabilize. That said, 1) I'm using AWS CLI 1.18.69 prepackaged in Ubuntu 20.04 LTS which is not officially supported by AWS itself and 2) I'm fairly new to AWS having only started Feb 2021 due to taking a cloud computing course at university so maybe I'm missing something. Anyway, the documentation could perhaps be more clear on any modifications to the example Ignition file for it to work on AWS.
donaldsebleung AWS Web Interface
dustymabe 34.20210427.1.0
jdoss DigitalOcean with Ignition file with 10 containerized services launched via systemd and Podman [1] 1. LGTM!
jdoss Ignition file with 10 containerized services launched via systemd and Podman [1] [2] 1. LGTM!
2. LGTM!
mnguyen vSphere with ignition [1] 1. FCOS VM boots successfully and log in with no issues.
nb
sinnykumari GCP [1] [2] 1. 4. Rollback from testing to next stream went fine
2. 1. Successfully launched an instance with ignition file provided. 2. ssh to the instance worked fine 3. stream switch from next to testing went fine 4. Rollback from testing to stream went fine
sohank2602 [1] 1. Everything looks good.
sohank2602 Azure [1] 1. Covered all the test cases mentioned here: https://fedoraproject.org/wiki/QA:Testcase_CoreOS_Azure FCOS VM boots successfully using the following options: 1. Azure CLI (no ignition file) 2. Azure C LI (ignition file)
vipul0 AWS [1] 1. completed the test case
vipul0 GCP

Advanced configuration

Username Profile Static networking Complex partitioning Building containers Containerized service Comments
Enter result Enter result Enter result Enter result
donaldsebleung Launching with QEMU; Host: Ubuntu 20.04 LTS, x86_64, 4G RAM, Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz x 4 [1] [2] 1. For building the podman image, I chose the base image from docker.io (3rd option of 4 total) since the first 2 options (fedoraproject, redhat) give a repo not found error. Did not test the 4th option (quay.io). Not sure if this is intended or not.
2. Successfully installed and started both hello.service and etcd-member.service in one go
jlebon "virtualized" bare metal [1] 1. Tested with 7 separate partitions at/under `/var` without issues.
lbazan Lenovo X1 Carbon, QEMU
sayaksarkar 34.20210418.1.0 next VM in Boxes on Fedora 33 WS
sohank2602 Lenovo X1 Carbon, QEMU [1] [2] [3] 1. Connection is properly configured
2. All test cases were passed with the base image from docker.io, however, other images don't seem to work (hitting an `Error: error creating build container: Error initializing source docker:` issue)
3. This looks good
theonlyandy Lenovo T470s, QEMU [1] 1. Connection is correctly configured, but not active, no device is attached

Upgrade

Username Profile Switch stream Comments
Enter result
donaldsebleung Launching with QEMU; Host: Ubuntu 20.04 LTS, x86_64, 4G RAM, Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz x 4 [1] 1. Tested switch stream to next; manual rollback (both temporary and permanent)
sayaksarkar 34.20210418.1.0 next VM in Boxes on Fedora 33 WS [1] 1. Switching streams worked as expected and manual rollback was also possible.
theonlyandy Lenovo T470s, QEMU [1] 1. Did not test the optional parts
thunderbirdtr 34.20210418.1.0 next VM in Qemu / F34 KDE

Miscellaneous

Username Profile Documentation Exploratory testing Comments
Enter result Enter result
mnguyen vSphere with ignition [1] 1. I used the documentation to launch the FCOS VM on vSphere. Directions were clear and easy to follow.
sayaksarkar 34.20210418.1.0 next VM in Boxes on Fedora 33 WS [1] 1. I went through documentation and followed through the instructions on the Getting Started and the Provisioning Fedora CoreOS on QEMU pages to correctly setup the FCOS VM. Also, the Producing an Igniti on Config was quite helpful. Also, for switching between multiple streams, the Update Streams document was particularly handy.
thunderbirdtr [1] 1. I tested on QEMU and Vmware and both of them was clean easy to install
thunderbirdtr v 34.20210418.1.0 next VM in Virt-manager on Fedora 34 KDE
Wiki Metadata