From Fedora Project Wiki

No edit summary
No edit summary
 
Line 45: Line 45:


== Test Results ==
== Test Results ==
=== aarch64 ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_AWS#aarch64 AWS]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_GCP#aarch64 GCP]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_virtual_install#aarch64 Virtual install]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_baremetal_install#aarch64 Bare Metal install]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Raspberry_Pi#aarch64 Raspberry Pi 4]
! References
|-
| [[User:apiaseck|apiaseck]]
|  t2.micro, 1vCPU, 20GB, eu-central-1a
| {{result|warn}}<ref>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`.</ref>
|
|
|
|
| <references/>
|-
| [[User:apiaseck|apiaseck]]
| Raspberry Pi 4, 4GB
| {{result|warn}}
|
|
|
|
| <references/>
|-
| [[User:apiaseck|apiaseck]]
| t2.micro, 1vCPU, 20GB, eu-central-1a
| {{result|pass}}<ref>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.</ref>
|
|
|
|
| <references/>
|-
| [[User:hricky|hricky]]
| Raspberry Pi 4 Model B Rev 1.4, 8 GB
|
|
|
|
| {{result|pass}}<ref>Both U-Boot and EDK2 boot methods work.</ref>
| <references/>
|-
|}
=== ppc64le ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_virtual_install#ppc64le Virtual install]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_baremetal_install#ppc64le Bare Metal install]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_IBM_Cloud#ppc64le IBM Cloud]
! References
|-
| [[User:marmijo|marmijo]]
| libvirt, 40.20240331.1.0-qemu.ppc64le.qcow2
| {{result|pass}}
|
|
| <references/>
|-
|}
=== s390x ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_virtual_install#s390x Virtual install]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_baremetal_install#s390x Bare Metal install]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_IBM_Cloud#s390x IBM Cloud]
! References
|-
| [[User:dustymabe|dustymabe]]
| bx2-2x8
|
|
| {{result|pass}}
| <references/>
|-
|}
=== x86_64 ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_virtual_install Virtual install]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_baremetal_install Bare Metal install]
! References
|-
| [[User:aaradhak|aaradhak]]
| libvirt,qemu - Fedora CoreOS 40.20240331.1.0
| {{result|pass}}<ref>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.</ref>
|
| <references/>
|-
| [[User:danniel|danniel]]
| FCOS Live DVD 40.20240322.1.0
| {{result|pass}}
|
| <references/>
|-
| [[User:danniel|danniel]]
| FCOS Live DVD 40.20240322.1.0  - Gigabyte H81M-H , 8GB DDR3 ,
|
| {{result|pass}}
| <references/>
|-
| [[User:danniel|danniel]]
| FCOS Live DVD 40.20240322.1.0  - Gigabyte H81M-H , 8GB DDR3 , i5-4440
|
| {{result|pass}}
| <references/>
|-
| [[User:ersen|ersen]]
| FCOS 40.20240322.1.0
| {{result|pass}}
|
| <references/>
|-
| [[User:garrmcnu|garrmcnu]]
| 40.20240331.1.0 QEMU
| {{result|pass}}
|
| <references/>
|-
| [[User:hricky|hricky]]
| CPU: Pentium Dual-Core E6300, MB: Gigabyte G41M-ES2L, RAM: 4GB, 40.20240331.1.0-live.x86_64.iso
|
| {{result|pass}}
| <references/>
|-
| [[User:hricky|hricky]]
| libvirt, 40.20240331.1.0-qemu.x86_64.qcow2
| {{result|pass}}
|
| <references/>
|-
| [[User:mythcat|mythcat]]
| https://linux-hardware.org/?probe=a0cd8c1b40
| {{result|pass}}{{result|pass}}
| {{result|pass}}
| <references/>
|-
| [[User:plugs|plugs]]
| qemu,fedora-coreos-39.20240309.3.0-qemu.x86_64.qcow2
| {{result|pass}}
|
| <references/>
|-
| [[User:ydesouza|ydesouza]]
| ThinkPad T400 | QEMU | Fedora CoreOS FCOS 40.20240322.1.0
| {{result|pass}}
|
| <references/>
|-
|}
=== Platforms launch ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Alibaba Alibaba]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_AWS AWS]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Azure Azure]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_DigitalOcean DigitalOcean]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Exoscale Exoscale]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_GCP GCP]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_HyperV Hyper-v]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_IBM_Cloud IBM Cloud]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Kubevirt Kubevirt]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Nutanix Nutanix]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_OpenStack OpenStack]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Provisioning_on_VirtualBox VirtualBox]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_VMware VMWare]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Provisioning_on_Vultr Vultr]
! References
|-
| [[User:apiaseck|apiaseck]]
|  t2.micro, 1vCPU, 20GB, eu-central-1a
|
| {{result|warn}}<ref>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`.</ref>
|
|
|
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:apiaseck|apiaseck]]
| 40.20240331.1.0, 2 GB RAM / 60 GB / SFO2
|
|
|
| {{result|pass}}<ref>Everything worked as expected, documentation was clear and concise. </ref>
|
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:apiaseck|apiaseck]]
| AWS, m5zn.metal
|
|
|
|
|
|
| {{result|warn}}<ref>Using bgilbert's script AWS Instance was created successfully, but I failed to establish connection through the xfreerdp in the generated connect.sh script.</ref>
|
|
|
|
|
|
|
| <references/>
|-
| [[User:apiaseck|apiaseck]]
| t2.micro, 40.20240331.1.0
|
| {{result|pass}}<ref>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. </ref>
|
|
|
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:brianmcarey|brianmcarey]]
| Fedora CoreOS 40.20240331.1.0
|
|
|
|
|
|
|
|
| {{result|pass}}<ref>Tested on KubeVirt v1.2</ref>
|
|
|
|
|
| <references/>
|-
| [[User:fifofonix|fifofonix]]
|
|
|
|
|
|
|
|
|
|
|
|
|
| {{result|pass}}<ref>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).</ref>
|
| <references/>
|-
| [[User:hhei|hhei]]
| Borrow account and test fedora-coreos-40.20240331.1.0-aliyun.x86_64.qcow2 with ecs.t6-c1m1.large
| {{result|pass}}<ref>Launch success.</ref>
|
|
|
|
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:hhei|hhei]]
| Test fedora-coreos-40.20240331.1.0-azure.x86_64.vhd on Azure
|
|
| {{result|pass}}<ref>Launch gen1/gen2, both can start.</ref>
|
|
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:marmijo|marmijo]]
| t5.large, 1vCPU,  20GB, us-east-2
|
| {{result|pass}}
|
|
|
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:mnguyen|mnguyen]]
|
|
|
|
|
|
|
|
| {{result|pass}}<ref>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.</ref>
|
|
|
|
|
|
| <references/>
|-
| [[User:mythcat|mythcat]]
| https://linux-hardware.org/?probe=a0cd8c1b40
|
|
|
|
|
|
|
|
|
|
|
| {{result|pass}}
|
|
| <references/>
|-
| [[User:ravanelli|ravanelli]]
|  40.20240331.1.0
|
|
|
|
| {{result|pass}}
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:ravanelli|ravanelli]]
| VirtualBox 7.0.10 r158379
|
|
|
|
|
|
|
|
|
|
|
| {{result|pass}}
|
|
| <references/>
|-
|}
=== Advanced configuration ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_static_networking Static networking]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_complex_partitioning Complex partitioning]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_build_container Building containers]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_containerized_service Containerized service]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_kernel_tuning_sysctl Kernel Tuning (sysctl)]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_modifying_kernel_arguments Modifying Kernel Arguments]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_OS_extensions OS extensions]
! References
|-
| [[User:Nemric|Nemric]]
| PXE booted FCOS 40.20240322.1.0 on Baremetal
|
| {{result|pass}}<ref>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</ref>
| {{result|warn}}<ref>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</ref>
| {{result|pass}}
| {{result|pass}}<ref>Set kernel.domainname in /etc/sysctl.d/90-domainname.conf</ref>
|
|
| <references/>
|-
| [[User:Nemric|Nemric]]
| PXE booted FCOS 40.20240331.1.0 on Baremetal
|
| {{result|pass}}
| {{result|warn}}<ref>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</ref>
| {{result|pass}}
| {{result|pass}}
|
|
| <references/>
|-
| [[User:brianmcarey|brianmcarey]]
| Fedora CoreOS 40.20240331.1.0
|
|
| {{result|pass}}
| {{result|pass}}
|
|
| {{result|pass}}
| <references/>
|-
| [[User:danniel|danniel]]
| FCOS Live DVD 40.20240322.1.0  - Gigabyte H81M-H , 8GB DDR3 , i5-4440
| {{result|pass}}
|
| {{result|pass}}
| {{result|pass}}
|
|
| {{result|pass}}
| <references/>
|-
| [[User:hricky|hricky]]
| CPU: Pentium Dual-Core E6300, MB: Gigabyte G41M-ES2L, RAM: 4GB, 40.20240331.1.0-live.x86_64.iso
| {{result|pass}}
| {{result|pass}}<ref>Tested various partition configurations on a Bare Metal machine with 4 HHDs attached.</ref>
|
|
|
|
|
| <references/>
|-
| [[User:hricky|hricky]]
| libvirt, 40.20240331.1.0-qemu.x86_64.qcow2
| {{result|pass}}
| {{result|pass}}<ref>Change the root filesystem to btrfs and Add a separate /var partition to the primary disk</ref>
|
| {{result|pass}}
|
|
| {{result|pass}}<ref>Layer vim and python3. Vim is the default text editor and the Python HTTP server is accessible from the host.</ref>
| <references/>
|-
| [[User:jbtrystram|jbtrystram]]
| fedora-coreos-40.20240331.1.0-qemu.x86_64.qcow2 on QEMU
|
|
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
|
| <references/>
|-
|}
=== Really Advanced Config ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_swap_on_zram Configuring SwapOnZRAM]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_time_zone Configuring Time Zone]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_debugging_toolbox Debugging with Toolbox]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_NIC_Name Customizing NIC name]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Alternatives Setting alternatives]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Counting Node counting]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_Kdump KDump via Ignition]
! [http://fedoraproject.org/wiki/QA:Testcase_nmstate Nmstate]
! References
|-
| [[User:Nemric|Nemric]]
| PXE booted FCOS 40.20240322.1.0 on Baremetal
| {{result|pass}}<ref>Issue https://github.com/coreos/fedora-coreos-tracker/issues/1296 seems to be resolved</ref>
|
| {{result|pass}}
|
|
|
|
|
| <references/>
|-
| [[User:Nemric|Nemric]]
| PXE booted FCOS 40.20240331.1.0 on Baremetal
| {{result|pass}}
|
| {{result|pass}}
|
|
|
|
|
| <references/>
|-
| [[User:aaradhak|aaradhak]]
| libvirt,qemu - Fedora CoreOS 40.20240331.1.0
|
|
| {{result|pass}}
|
|
|
|
|
| <references/>
|-
| [[User:apiaseck|apiaseck]]
| 40.20240331.1.0, 2 GB RAM / 60 GB
|
| {{result|pass}}<ref>Tested via DigitalOcean droplet - everything worked as expected.</ref>
|
|
|
|
|
|
| <references/>
|-
| [[User:hhei|hhei]]
| Test fedora-coreos-40.20240331.1.0 with qemu
|
|
|
|
|
|
|
| {{result|pass}}<ref>Result looks good</ref>
| <references/>
|-
| [[User:hricky|hricky]]
| libvirt, 40.20240331.1.0-qemu.x86_64.qcow2
| {{result|pass}}<ref>It works as expected.</ref>
|
|
| {{result|pass}}<ref>systemd Link File and Udev Rules work on two NICs simultaneously, with static IPs assigned.</ref>
| {{result|pass}}
| {{result|pass}}
|
|
| <references/>
|-
| [[User:jbtrystram|jbtrystram]]
|
|
| {{result|pass}}<ref>tested on QEMU with fedora-coreos-40.20240331.1.0-qemu.x86_64.qcow2</ref>
| {{result|pass}}
|
|
|
| {{result|pass}}<ref>work as expected on fedora-coreos-40.20240331.1.0-qemu.x86_64.qcow2</ref>
|
| <references/>
|-
| [[User:sumantrom|sumantrom]]
| KVM
|
|
| {{result|pass}}
|
|
|
|
|
| <references/>
|-
|}
=== Upgrade ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_switch_stream Switch stream]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_bootupd Bootloader updates]
! References
|-
| [[User:aaradhak|aaradhak]]
| fedora:fedora/x86_64/coreos/next- 40.20240331.1.0
| {{result|pass}}<ref>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.</ref>
| {{result|pass}}<ref>The system successfully reboots and runs on the next stream with the latest bootloader.</ref>
| <references/>
|-
| [[User:hricky|hricky]]
| libvirt, 40.20240331.1.0-qemu.x86_64.qcow2
| {{result|pass}}<ref>Trying to rebase from stable to next with vim layered results in conflicting requests. Otherwise all rebases, manual and temporary rollbacks work as expected.</ref>
|
| <references/>
|-
|}
=== Tutorials ===
{| class="wikitable" width=100%
! User
! Profile
! [http://docs.fedoraproject.org/en-US/fedora-coreos/tutorial-setup/ All Tests - Add the ones you did]
! References
|-
|}
=== Miscellaneous ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_documentation Documentation]
! [http://fedoraproject.org/wiki/QA:Testcase_CoreOS_exploratory_testing Exploratory testing]
! References
|-
|}


Test results will be transferred after the test event is over.


[[Category:Fedora 40 Test Days]]
[[Category:Fedora 40 Test Days]]

Latest revision as of 02:23, 24 April 2024

Fedora CoreOS Test Week
Fedora CoreOS
Date 2024-04-01 to 2024-04-07
Time all week
Website QA/Test Days
Matrix #coreos:fedoraproject.org
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 Fedora CoreOS issue tracker, 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 installment of Fedora Test Day will focus on Fedora CoreOS

Who's available?[edit]

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion:

For real time help, please join us on Matrix: #coreos:fedoraproject.org.

Documentation is also available here. Documentation feedback is welcome through chat, mailing list, github tracker and in the form of a pull request to the documentation sources.

Prerequisites for Test Day[edit]

  • Virtual machine (x86_64, aarch64, s390x)
  • Test day Image

Grab images/artifacts/information for the most current next stream release (40) from our download page: https://fedoraproject.org/coreos/download/?stream=next#arches

How to test?[edit]

Run the tests[edit]

Visit the results 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]

Please report all bugs, issues or enhancement proposals to the Fedora CoreOS issue tracker.

If you are unsure about exactly how to file the report or what other information to include, ask on Matrix #coreos:fedoraproject.org, #test-day:fedoraproject.org or #quality:fedoraproject.org and we will help you.

Test Results[edit]

aarch64[edit]

User Profile AWS GCP Virtual install Bare Metal install Raspberry Pi 4 References
apiaseck t2.micro, 1vCPU, 20GB, eu-central-1a
Warning warn
[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
Warning warn
apiaseck t2.micro, 1vCPU, 20GB, eu-central-1a
Pass pass
[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
Pass pass
[1]
  1. ↑ Both U-Boot and EDK2 boot methods work.

ppc64le[edit]

User Profile Virtual install Bare Metal install IBM Cloud References
marmijo libvirt, 40.20240331.1.0-qemu.ppc64le.qcow2
Pass pass

s390x[edit]

User Profile Virtual install Bare Metal install IBM Cloud References
dustymabe bx2-2x8
Pass pass

x86_64[edit]

User Profile Virtual install Bare Metal install References
aaradhak libvirt,qemu - Fedora CoreOS 40.20240331.1.0
Pass pass
[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
Pass pass
danniel FCOS Live DVD 40.20240322.1.0 - Gigabyte H81M-H , 8GB DDR3 ,
Pass pass
danniel FCOS Live DVD 40.20240322.1.0 - Gigabyte H81M-H , 8GB DDR3 , i5-4440
Pass pass
ersen FCOS 40.20240322.1.0
Pass pass
garrmcnu 40.20240331.1.0 QEMU
Pass pass
hricky CPU: Pentium Dual-Core E6300, MB: Gigabyte G41M-ES2L, RAM: 4GB, 40.20240331.1.0-live.x86_64.iso
Pass pass
hricky libvirt, 40.20240331.1.0-qemu.x86_64.qcow2
Pass pass
mythcat https://linux-hardware.org/?probe=a0cd8c1b40
Pass pass
Pass pass
Pass pass
plugs qemu,fedora-coreos-39.20240309.3.0-qemu.x86_64.qcow2
Pass pass
ydesouza QEMU | Fedora CoreOS FCOS 40.20240322.1.0
Pass pass

Platforms launch[edit]

User Profile Alibaba AWS Azure DigitalOcean Exoscale GCP Hyper-v IBM Cloud Kubevirt Nutanix OpenStack VirtualBox VMWare Vultr References
apiaseck t2.micro, 1vCPU, 20GB, eu-central-1a
Warning warn
[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
Pass pass
[1]
  1. ↑ Everything worked as expected, documentation was clear and concise.
apiaseck AWS, m5zn.metal
Warning warn
[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
Pass pass
[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
Pass pass
[1]
  1. ↑ Tested on KubeVirt v1.2
fifofonix
Pass pass
[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
Pass pass
[1]
  1. ↑ Launch success.
hhei Test fedora-coreos-40.20240331.1.0-azure.x86_64.vhd on Azure
Pass pass
[1]
  1. ↑ Launch gen1/gen2, both can start.
marmijo t5.large, 1vCPU, 20GB, us-east-2
Pass pass
mnguyen
Pass pass
[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
Pass pass
ravanelli 40.20240331.1.0
Pass pass
ravanelli VirtualBox 7.0.10 r158379
Pass pass

Advanced configuration[edit]

User Profile Static networking Complex partitioning Building containers Containerized service Kernel Tuning (sysctl) Modifying Kernel Arguments OS extensions References
Nemric PXE booted FCOS 40.20240322.1.0 on Baremetal
Pass pass
[1]
Warning warn
[2]
Pass pass
Pass pass
[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
Pass pass
Warning warn
[1]
Pass pass
Pass pass
  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
Pass pass
Pass pass
Pass pass
danniel FCOS Live DVD 40.20240322.1.0 - Gigabyte H81M-H , 8GB DDR3 , i5-4440
Pass pass
Pass pass
Pass pass
Pass pass
hricky CPU: Pentium Dual-Core E6300, MB: Gigabyte G41M-ES2L, RAM: 4GB, 40.20240331.1.0-live.x86_64.iso
Pass pass
Pass pass
[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
Pass pass
Pass pass
[1]
Pass pass
Pass pass
[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
Pass pass
Pass pass
Pass pass
Pass pass

Really Advanced Config[edit]

User Profile Configuring SwapOnZRAM Configuring Time Zone Debugging with Toolbox Customizing NIC name Setting alternatives Node counting KDump via Ignition Nmstate References
Nemric PXE booted FCOS 40.20240322.1.0 on Baremetal
Pass pass
[1]
Pass pass
  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
Pass pass
Pass pass
aaradhak libvirt,qemu - Fedora CoreOS 40.20240331.1.0
Pass pass
apiaseck 40.20240331.1.0, 2 GB RAM / 60 GB
Pass pass
[1]
  1. ↑ Tested via DigitalOcean droplet - everything worked as expected.
hhei Test fedora-coreos-40.20240331.1.0 with qemu
Pass pass
[1]
  1. ↑ Result looks good
hricky libvirt, 40.20240331.1.0-qemu.x86_64.qcow2
Pass pass
[1]
Pass pass
[2]
Pass pass
Pass pass
  1. ↑ It works as expected.
  2. ↑ systemd Link File and Udev Rules work on two NICs simultaneously, with static IPs assigned.
jbtrystram
Pass pass
[1]
Pass pass
Pass pass
[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
Pass pass

Upgrade[edit]

User Profile Switch stream Bootloader updates References
aaradhak fedora:fedora/x86_64/coreos/next- 40.20240331.1.0
Pass pass
[1]
Pass pass
[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
Pass pass
[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.

Tutorials[edit]

User Profile All Tests - Add the ones you did References

Miscellaneous[edit]

User Profile Documentation Exploratory testing References
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:Fedora_40_CoreOS&oldid=707617"