| Username | Profile | AWS | GCP | Virtual install | Bare Metal install | Raspberry Pi 4 | Comments |
|---|---|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | Enter result | Enter result | |||
| apiaseck | t2.micro, 1vCPU, 20GB, eu-central-1a | [1] |
1.
I successfully ran an instance, but failed ssh'ing into it. Ihad to configure multiple AWS-related mechanisms to run an instance through `aws ec2 run-instances`.
|
||||
| apiaseck | Raspberry Pi 4, 4GB | ||||||
| apiaseck | t2.micro, 1vCPU, 20GB, eu-central-1a | [1] |
1.
An update of the documentation is required, related to creating VPC, security groups and key pairs. Also, the manual assignment of elastic IP addresses and modification of inbound rules for the
security group should be mentioned. I will look into that in the coming week.
|
||||
| hricky | Raspberry Pi 4 Model B Rev 1.4, 8 GB | [1] |
1.
Both U-Boot and EDK2 boot methods work.
|
| Username | Profile | Virtual install | Bare Metal install | IBM Cloud | Comments |
|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | |||
| marmijo | libvirt, 40.20240331.1.0-qemu.ppc64le.qcow2 |
| Username | Profile | Virtual install | Bare Metal install | IBM Cloud | Comments |
|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | |||
| dustymabe | bx2-2x8 |
| Username | Profile | Virtual install | Bare Metal install | Comments |
|---|---|---|---|---|
| Enter result | Enter result | |||
| aaradhak | libvirt,qemu - Fedora CoreOS 40.20240331.1.0 | [1] |
1.
Expected results : PASSED
The system runs in a virtual machine according to the instructions.
I can read the IP address of the machine from the serial console.
I can connect to the machine via
SSH.
The linked documentation is clear, all steps are understandable, and nothing important is missing from it.
|
|
| danniel | FCOS Live DVD 40.20240322.1.0 | |||
| danniel | FCOS Live DVD 40.20240322.1.0 - Gigabyte H81M-H , 8GB DDR3 , | |||
| danniel | FCOS Live DVD 40.20240322.1.0 - Gigabyte H81M-H , 8GB DDR3 , i5-4440 | |||
| ersen | FCOS 40.20240322.1.0 | |||
| garrmcnu | 40.20240331.1.0 QEMU | |||
| hricky | CPU: Pentium Dual-Core E6300, MB: Gigabyte G41M-ES2L, RAM: 4GB, 40.20240331.1.0-live.x86_64.iso | |||
| hricky | libvirt, 40.20240331.1.0-qemu.x86_64.qcow2 | |||
| mythcat | https://linux-hardware.org/?probe=a0cd8c1b40 | |||
| plugs | qemu,fedora-coreos-39.20240309.3.0-qemu.x86_64.qcow2 | |||
| ydesouza | ThinkPad T400 | QEMU | Fedora CoreOS FCOS 40.20240322.1.0 |
| Username | Profile | Alibaba | AWS | Azure | DigitalOcean | Exoscale | GCP | Hyper-v | IBM Cloud | Kubevirt | Nutanix | OpenStack | VirtualBox | VMWare | Vultr | Comments |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | |||
| apiaseck | t2.micro, 1vCPU, 20GB, eu-central-1a | [1] |
1.
I successfully ran the instance using a simple ignition file but failed to ssh into it. had to configure multiple AWS-related mechanisms to run an instance through `aws ec2 run-instances`.
|
|||||||||||||
| apiaseck | 40.20240331.1.0, 2 GB RAM / 60 GB / SFO2 | [1] |
1.
Everything worked as expected, documentation was clear and concise.
|
|||||||||||||
| apiaseck | AWS, m5zn.metal | [1] |
1.
Using bgilbert's script AWS Instance was created successfully, but I failed to establish connection through the xfreerdp in the generated connect.sh script.
|
|||||||||||||
| apiaseck | t2.micro, 40.20240331.1.0 | [1] |
1.
An update of the documentation is required, related to creating VPC, security groups and key pairs. Also, the manual assignment of elastic IP addresses and modification of inbound rules for the
security group should be mentioned. I will look into that in the coming week.
|
|||||||||||||
| brianmcarey | Fedora CoreOS 40.20240331.1.0 | [1] |
1.
Tested on KubeVirt v1.2
|
|||||||||||||
| fifofonix | [1] |
1.
Created and successfully SSH'd to a Fedora40 `next` VMWare vSphere node following the govc-based test case steps for creation from a template (as opposed to a library template).
|
||||||||||||||
| hhei | Borrow account and test fedora-coreos-40.20240331.1.0-aliyun.x86_64.qcow2 with ecs.t6-c1m1.large | [1] |
1.
Launch success.
|
|||||||||||||
| hhei | Test fedora-coreos-40.20240331.1.0-azure.x86_64.vhd on Azure | [1] |
1.
Launch gen1/gen2, both can start.
|
|||||||||||||
| ketanbaitule | VirtualBox 7.0.18 r162988, fedora-coreos-40.20240519.1.0-virtualbox.x86_64.ova | [1] |
1.
Successfully Created A VM in VirtualBox using Ignition File and then ssh into it.
|
|||||||||||||
| marmijo | t5.large, 1vCPU, 20GB, us-east-2 | |||||||||||||||
| mnguyen | [1] |
1.
ibmcloud version 2.24 and higher require `Allow source IP spoofing` set to `true` in order to launch an instance. Older versions can launch without issue.
https://cloud.ibm.com/docs/vpc?topic=vpc-vni-api-introduction was introduced in March 2024.
|
||||||||||||||
| mythcat | https://linux-hardware.org/?probe=a0cd8c1b40 | |||||||||||||||
| ravanelli | 40.20240331.1.0 | |||||||||||||||
| ravanelli | VirtualBox 7.0.10 r158379 |
| Username | Profile | Static networking | Complex partitioning | Building containers | Containerized service | Kernel Tuning (sysctl) | Modifying Kernel Arguments | OS extensions | Comments |
|---|---|---|---|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | |||
| Nemric | PXE booted FCOS 40.20240322.1.0 on Baremetal | [1] | [2] | [3] |
1.
Mount /var for persistent datas for PXE
storage:
filesystems:
- path: /var
device: /dev/sda
format: xfs
label: Var
wipe_filesystem: false
with_mount_unit:
true
2. Facing issue https://github.com/containers/podman/issues/22109 in a Jenkins "podman build" caused by default pasta network use, using rootless podman remote with rootfull server, should be fixed in Podman 5.0.1 Didn't run tests with docker 3. Set kernel.domainname in /etc/sysctl.d/90-domainname.conf |
||||
| Nemric | PXE booted FCOS 40.20240331.1.0 on Baremetal | [1] |
1.
Facing issue https://github.com/containers/podman/issues/22109 in a Jenkins "podman build" caused by default pasta network use, using rootless podman remote with rootfull server, should be fixed in
Podman 5.0.1 Didn't run tests with docker
|
||||||
| brianmcarey | Fedora CoreOS 40.20240331.1.0 | ||||||||
| danniel | FCOS Live DVD 40.20240322.1.0 - Gigabyte H81M-H , 8GB DDR3 , i5-4440 | ||||||||
| hricky | CPU: Pentium Dual-Core E6300, MB: Gigabyte G41M-ES2L, RAM: 4GB, 40.20240331.1.0-live.x86_64.iso | [1] |
1.
Tested various partition configurations on a Bare Metal machine with 4 HHDs attached.
|
||||||
| hricky | libvirt, 40.20240331.1.0-qemu.x86_64.qcow2 | [1] | [2] |
1.
Change the root filesystem to btrfs and Add a separate /var partition to the primary disk
2. Layer vim and python3. Vim is the default text editor and the Python HTTP server is accessible from the host. |
|||||
| jbtrystram | fedora-coreos-40.20240331.1.0-qemu.x86_64.qcow2 on QEMU |
| Username | Profile | Configuring SwapOnZRAM | Configuring Time Zone | Debugging with Toolbox | Customizing NIC name | Setting alternatives | Node counting | KDump via Ignition | Nmstate | Comments |
|---|---|---|---|---|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | |||
| Nemric | PXE booted FCOS 40.20240322.1.0 on Baremetal | [1] |
1.
Issue https://github.com/coreos/fedora-coreos-tracker/issues/1296 seems to be resolved
|
|||||||
| Nemric | PXE booted FCOS 40.20240331.1.0 on Baremetal | |||||||||
| aaradhak | libvirt,qemu - Fedora CoreOS 40.20240331.1.0 | |||||||||
| apiaseck | 40.20240331.1.0, 2 GB RAM / 60 GB | [1] |
1.
Tested via DigitalOcean droplet - everything worked as expected.
|
|||||||
| hhei | Test fedora-coreos-40.20240331.1.0 with qemu | [1] |
1.
Result looks good
|
|||||||
| hricky | libvirt, 40.20240331.1.0-qemu.x86_64.qcow2 | [1] | [2] |
1.
It works as expected.
2. systemd Link File and Udev Rules work on two NICs simultaneously, with static IPs assigned. |
||||||
| jbtrystram | [1] | [2] |
1.
tested on QEMU with fedora-coreos-40.20240331.1.0-qemu.x86_64.qcow2
2. work as expected on fedora-coreos-40.20240331.1.0-qemu.x86_64.qcow2 |
|||||||
| sumantrom | KVM |
| Username | Profile | Switch stream | Bootloader updates | Comments |
|---|---|---|---|---|
| Enter result | Enter result | |||
| aaradhak | fedora:fedora/x86_64/coreos/next- 40.20240331.1.0 | [1] | [2] |
1.
The system successfully reboots and runs on the next stream.
The system is functional
The linked documentation is clear, all steps are understandable, and nothing important is missing from it.
2. The system successfully reboots and runs on the next stream with the latest bootloader. |
| hricky | libvirt, 40.20240331.1.0-qemu.x86_64.qcow2 | [1] |
1.
Trying to rebase from stable to next with vim layered results in conflicting requests. Otherwise all rebases, manual and temporary rollbacks work as expected.
|
| Username | Profile | All Tests - Add the ones you did | Comments |
|---|---|---|---|
| Enter result |
| Username | Profile | Documentation | Exploratory testing | Comments |
|---|---|---|---|---|
| Enter result | Enter result |