From Fedora Project Wiki

m (Update IRC to Matrix :))
(import results from blockerbugs)
 
(One intermediate revision by one other user not shown)
Line 18: Line 18:
== Who's available? ==
== Who's available? ==


The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion:
* Development - Renata Ravanelli (ravanelli), [[User:dustymabe|Dusty Mabe]] (dustymabe), Jonathan Lebon (jlebon)
* Development: Renata Ravanelli (ravanelli), [[User:dustymabe|Dusty Mabe]] (dustymabe), Jonathan Lebon (jlebon)
* Quality Assurance - [[User:kparal|Kamil Paral]] (kparal), [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:coremodule|Geoff Marr]] (coremodule)  
* Quality Assurance: [[User:kparal|Kamil Paral]] (kparal), [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:coremodule|Geoff Marr]] (coremodule)  


For real time help, please join us on Matrix: [https://chat.fedoraproject.org/#/room/#coreos:fedoraproject.org #coreos:fedoraproject.org].
For real time help, please join us on Matrix: [https://chat.fedoraproject.org/#/room/#coreos:fedoraproject.org #coreos:fedoraproject.org].
Line 30: Line 30:
* Test day Image
* Test day Image


Grab images/artifacts/information for the most current `next` stream release (`39`) from our download page: https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=next
Grab images/artifacts/information for the most current `next` stream release (`39`) from our download page: https://fedoraproject.org/coreos/download/?stream=next#arches


== How to test? ==
== How to test? ==
Line 42: Line 42:
Please report all bugs, issues or enhancement proposals to the '''[https://github.com/coreos/fedora-coreos-tracker/issues Fedora CoreOS issue tracker]'''.
Please report all bugs, issues or enhancement proposals to the '''[https://github.com/coreos/fedora-coreos-tracker/issues Fedora CoreOS issue tracker]'''.


If you are unsure about exactly how to file the report or what other information to include, ask on Matrix [https://chat.fedoraproject.org/#/room/#coreos:fedoraproject.org #coreos:fedoraproject.org], {{fpchat|#fedora-test-day}} or {{fpchat|#fedora-qa}} and we will help you.
If you are unsure about exactly how to file the report or what other information to include, ask on Matrix [https://chat.fedoraproject.org/#/room/#coreos:fedoraproject.org #coreos:fedoraproject.org], [https://chat.fedoraproject.org/#/room/#test-day:fedoraproject.org #test-day:fedoraproject.org] or [https://chat.fedoraproject.org/#/room/#quality:fedoraproject.org #quality:fedoraproject.org] and we will help you.


== 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:c4rt0|c4rt0]]
| Raspberry Pi 4, 4GB
|
|
|
|
| {{result|fail}}<ref>I tried installing FCOS both on an SD card and on a USB drive in order to test it on Raspberry Pi4.
I followed the  [tutorial](https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_installing_fcos_and_booting_via_u_boot), considering next as a STREAM and 39 as a RELEASE.
I also followed the [Raspberry Pi tutorial](https://www.raspberrypi.com/documentation//computers/raspberry-pi.html#updating-the-bootloader) on updating the bootloader.
Until the very last step everything seems to work as expected, but after inserting the drive into the Raspberry Pi4, nothing but a dark screen was presented. Same goes for F38, stable.</ref>
| <references/>
|-
| [[User:hricky|hricky]]
| Raspberry Pi 4, 8GB
|
|
|
|
| {{result|fail}}<ref>{{bz|2241252}} https://github.com/coreos/fedora-coreos-tracker/issues/1585</ref>
| <references/>
|-
| [[User:nielsenb|nielsenb]]
| Raspberry Pi 4b, pieeprom-2023-05-11.bin
|
|
|
|
| {{result|fail}}<ref>Same issue as described in https://github.com/coreos/fedora-coreos-tracker/issues/1466</ref>
| <references/>
|-
| [[User:ravanelli|ravanelli]]
| qemu on R152-P31-00 aarch64
|
|
| {{result|pass}}
|
|
| <references/>
|-
| [[User:rravanel|rravanel]]
| a1.metal
| {{result|pass}}
|
|
|
|
| <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:hhei|hhei]]
| Install on FCOS 39.20230916.1.2 baremental in beaker
|
| {{result|fail}}<ref>Get systemd-network-generator.service error - Failed to create temporary unit file in '/run/systemd/network': Permission denied. See https://github.com/coreos/fedora-coreos-tracker/issues/1587</ref>{{result|pass}}<ref>Tested both passing password and enable SSH password authentication via the Ignition config, both can login successfully.</ref>
|
| <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:ravanelli|ravanelli]]
| qemu on 8561 s390x
| {{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:brianmcarey|brianmcarey]]
| Framework 13 i5-1240P QEMU | fedora-coreos-39.20230916.1.2
| {{result|pass}}
|
| <references/>
|-
| [[User:danniel|danniel]]
| Lenovo ideapad S145
|
| {{result|pass}}
| <references/>
|-
| [[User:danniel|danniel]]
| Lenovo ideapad S145 KVM
| {{result|pass}}
|
| <references/>
|-
| [[User:geraldosimiao|geraldosimiao]]
| Fedora CoreOS 39.20230916.1.2  on KVM-QEMU-VirtManager (F39 KDE)
| {{result|pass}}
|
| <references/>
|-
| [[User:nielsenb|nielsenb]]
| libvirt on Fedora 38 AMD Ryzen 7 5800X3D x86_64
| {{result|fail}}<ref>Instructions in documentation don't work, see: https://github.com/coreos/fedora-coreos-docs/issues/544</ref>
|
| <references/>
|-
| [[User:pnemade|pnemade]]
| 39.20230916.1.2 on KVM
| {{result|pass}}
|
| <references/>
|-
| [[User:ravanelli|ravanelli]]
| qemu on R152-P31-00 aarch64
| {{result|pass}}
|
| <references/>
|-
| [[User:ydesouza|ydesouza]]
| ThinkPad T400 | QEMU | Fedora CoreOS 39.20230916.1.2
| {{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:brianmcarey|brianmcarey]]
| Kubernetes v1.28 | KubeVirt v1.1.0-alpha.0 | Fedora CoreOS 39.20230916.1.2
|
|
|
|
|
|
|
|
| {{result|pass}}
|
|
|
|
|
| <references/>
|-
| [[User:c4rt0|c4rt0]]
| sfo2, 1 GB / 1 CPU 25 GB SSD Disk 1000 GB transfer
|
|
|
| {{result|warn}}<ref>https://github.com/coreos/fedora-coreos-tracker/issues/1586</ref>{{result|fail}}<ref>While running :
```
doctl compute image create my-next-fcos-image --region sfo2 --image-url https://builds.coreos.fedoraproject.org/prod/streams/next/builds/39.20230916.1.2/x86_64/fedora-coreos-39.20230916.1.2-digitalocean.x86_64.qcow2.gz
while ! doctl compute image list-user | grep my-next-fcos-image; do sleep 5; done
```
The process finishes within the first few seconds.
Returned result:
```
ID          Name                  Type      Distribution    Slug    Public    Min Disk
141380554    my-next-fcos-image    custom    Unknown OS              false    0
```
Creating droplet directly on digitalocean with the custom FCOS-next image results with:
'The image you selected is no longer available'.</ref>
|
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:dustymabe|dustymabe]]
| 39.20230916.1.2 vultr image
|
|
|
|
|
|
|
|
|
|
|
|
|
| {{result|pass}}
| <references/>
|-
| [[User:hhei|hhei]]
| Test with fedora-coreos-39.20230916.1.2-hyperv.x86_64.vhdx on Hyper-V 2022
|
|
|
|
|
|
| {{result|pass}}<ref>Start gen2 vm with enabled secure boot, vm starts successfully</ref>
|
|
|
|
|
|
|
| <references/>
|-
| [[User:jlebon|jlebon]]
| FCOS next
|
|
|
|
|
|
|
|
|
|
| {{result|pass}}<ref>Tested both passing the SSH key via keypairs and via the Ignition config.</ref>
|
|
|
| <references/>
|-
| [[User:jmarrero|jmarrero]]
| jmarrero
|
|
|
| {{result|pass}}<ref>Worked for me, however the image takes a bit to be available after is uploaded.</ref>
|
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:mnguyen|mnguyen]]
|
|
|
| {{result|pass}}
|
|
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:nielsenb|nielsenb]]
| ami-055c024e1ed6245f0, t2.micro
|
| {{result|pass}}
|
|
|
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:ravanelli|ravanelli]]
|
|
|
|
|
| {{result|pass}}<ref>PR to update the docs: https://github.com/coreos/fedora-coreos-docs/pull/587</ref>
|
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:ravanelli|ravanelli]]
| VirtualBox 7.0.10  r158379(Qt5.15.2) on Mac
|
|
|
|
|
|
|
|
|
|
|
| {{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]]
| Fedora CoreOS 39.20230916.1.1 on a diskless PXE booted X86_64
|
|
| {{result|pass}}<ref>Podman use only</ref>{{result|pass}}
| {{result|pass}}<ref>All my containerized services are running as expected (jenkins, jenkins-agent, docker registry, redis, promtail, ...) but didn't try quadlet </ref>
|
|
|
| <references/>
|-
| [[User:brianmcarey|brianmcarey]]
| Framework 13 i5-1240P QEMU | fedora-coreos-39.20230916.1.2
|
|
| {{result|pass}}
|
|
|
|
| <references/>
|-
| [[User:danniel|danniel]]
| Lenovo ideapad S145
| {{result|pass}}
|
| {{result|pass}}
| {{result|pass}}
|
|
|
| <references/>
|-
| [[User:geraldosimiao|geraldosimiao]]
| Fedora CoreOS 39.20230916.1.2  on KVM-QEMU-VirtManager (F39 KDE)
|
|
| {{result|pass}}
|
|
|
|
| <references/>
|-
| [[User:ravanelli|ravanelli]]
| qemu on R152-P31-00 aarch64
|
| {{result|pass}}<ref>Changing the root filesystem to ext4</ref>
|
|
| {{result|pass}}
|
| {{result|pass}}<ref>The vim package got issues to be installed due its deps. Installed calc that has no deps instead.
The default edit also got changed to use vim</ref>
| <references/>
|-
| [[User:ydesouza|ydesouza]]
| ThinkPad T400 | QEMU | Fedora CoreOS 39.20230916.1.2
| {{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]]
| Fedora CoreOS 39.20230916.1.1 on a diskless PXE booted X86_64
| {{result|pass}}
|
| {{result|pass}}<ref>Only run tests from documentation</ref>
|
|
|
|
|
| <references/>
|-
| [[User:brianmcarey|brianmcarey]]
| Framework 13 i5-1240P QEMU | fedora-coreos-39.20230916.1.2
|
|
| {{result|pass}}
|
|
|
|
|
| <references/>
|-
| [[User:danniel|danniel]]
| Lenovo ideapad S145
|
| {{result|pass}}
|
|
|
|
|
|
| <references/>
|-
| [[User:dustymabe|dustymabe]]
| 39.20230916.1.2 qemu qcow in libvirt
|
|
|
|
| {{result|pass}}
|
|
|
| <references/>
|-
| [[User:ravanelli|ravanelli]]
| qemu on 8561 s390x
|
|
|
|
|
|
| {{result|fail}}<ref>We have a Snoozing kola test pattern "ext.config.kdump.crash" until Sep 30 2023 with https://github.com/coreos/fedora-coreos-tracker/issues/1560
However, this issue seems different. It is not a selinux denial thing. </ref>
|
| <references/>
|-
| [[User:ravanelli|ravanelli]]
| qemu on R152-P31-00 aarch64
|
|
|
|
|
|
| {{result|fail}}<ref>Same as s390x</ref>
|
| <references/>
|-
| [[User:rravanel|rravanel]]
| qemu on R152-P31-00 aarch64
|
|
|
| {{result|pass}}<ref>Tested via udev rule</ref>
|
|
|
|
| <references/>
|-
| [[User:ydesouza|ydesouza]]
| ThinkPad T400 | QEMU | Fedora CoreOS 39.20230916.1.2
|
| {{result|pass}}
|
| {{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:jdoss|jdoss]]
|
| {{result|pass}}<ref>Zincati upgraded to 39.20230916.1.2 on a DigitalOcean VM without issues.</ref>
|
| <references/>
|-
| [[User:jmarrero|jmarrero]]
| jmarrero
| {{result|pass}}
| {{result|pass}}<ref>seen expected results</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
|-
| [[User:Nemric|Nemric]]
| Fedora CoreOS 39.20230916.1.1 on a diskless PXE booted X86_64
|
| {{result|fail}}<ref>This issue still happen : https://github.com/coreos/fedora-coreos-tracker/issues/1296</ref>
| <references/>
|-
|}


[[Category:Fedora 39 Test Days]]
[[Category:Fedora 39 Test Days]]

Latest revision as of 23:08, 21 February 2024

Fedora CoreOS Test Week
Fedora CoreOS

Date 2023-09-25 to 2023-10-02
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 (39) 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
c4rt0 Raspberry Pi 4, 4GB
Fail fail
[1]
  1. I tried installing FCOS both on an SD card and on a USB drive in order to test it on Raspberry Pi4. I followed the [tutorial](https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_installing_fcos_and_booting_via_u_boot), considering next as a STREAM and 39 as a RELEASE. I also followed the [Raspberry Pi tutorial](https://www.raspberrypi.com/documentation//computers/raspberry-pi.html#updating-the-bootloader) on updating the bootloader. Until the very last step everything seems to work as expected, but after inserting the drive into the Raspberry Pi4, nothing but a dark screen was presented. Same goes for F38, stable.
hricky Raspberry Pi 4, 8GB
Fail fail
[1]
nielsenb Raspberry Pi 4b, pieeprom-2023-05-11.bin
Fail fail
[1]
ravanelli qemu on R152-P31-00 aarch64
Pass pass
rravanel a1.metal
Pass pass

ppc64le[edit]

User Profile Virtual install Bare Metal install IBM Cloud References
hhei Install on FCOS 39.20230916.1.2 baremental in beaker
Fail fail
[1]
Pass pass
[2]
  1. Get systemd-network-generator.service error - Failed to create temporary unit file in '/run/systemd/network': Permission denied. See https://github.com/coreos/fedora-coreos-tracker/issues/1587
  2. Tested both passing password and enable SSH password authentication via the Ignition config, both can login successfully.

s390x[edit]

User Profile Virtual install Bare Metal install IBM Cloud References
ravanelli qemu on 8561 s390x
Pass pass

x86_64[edit]

User Profile Virtual install Bare Metal install References
brianmcarey fedora-coreos-39.20230916.1.2
Pass pass
danniel Lenovo ideapad S145
Pass pass
danniel Lenovo ideapad S145 KVM
Pass pass
geraldosimiao Fedora CoreOS 39.20230916.1.2 on KVM-QEMU-VirtManager (F39 KDE)
Pass pass
nielsenb libvirt on Fedora 38 AMD Ryzen 7 5800X3D x86_64
Fail fail
[1]
  1. Instructions in documentation don't work, see: https://github.com/coreos/fedora-coreos-docs/issues/544
pnemade 39.20230916.1.2 on KVM
Pass pass
ravanelli qemu on R152-P31-00 aarch64
Pass pass
ydesouza QEMU | Fedora CoreOS 39.20230916.1.2
Pass pass

Platforms launch[edit]

User Profile Alibaba AWS Azure DigitalOcean Exoscale GCP Hyper-v IBM Cloud Kubevirt Nutanix OpenStack VirtualBox VMWare Vultr References
brianmcarey KubeVirt v1.1.0-alpha.0 | Fedora CoreOS 39.20230916.1.2
Pass pass
c4rt0 sfo2, 1 GB / 1 CPU 25 GB SSD Disk 1000 GB transfer
Warning warn
[1]
Fail fail
[2]
  1. https://github.com/coreos/fedora-coreos-tracker/issues/1586
  2. While running : ` doctl compute image create my-next-fcos-image --region sfo2 --image-url https://builds.coreos.fedoraproject.org/prod/streams/next/builds/39.20230916.1.2/x86_64/fedora-coreos-39.20230916.1.2-digitalocean.x86_64.qcow2.gz while ! doctl compute image list-user | grep my-next-fcos-image; do sleep 5; done ` The process finishes within the first few seconds. Returned result: ` ID Name Type Distribution Slug Public Min Disk 141380554 my-next-fcos-image custom Unknown OS false 0 ` Creating droplet directly on digitalocean with the custom FCOS-next image results with: 'The image you selected is no longer available'.
dustymabe 39.20230916.1.2 vultr image
Pass pass
hhei Test with fedora-coreos-39.20230916.1.2-hyperv.x86_64.vhdx on Hyper-V 2022
Pass pass
[1]
  1. Start gen2 vm with enabled secure boot, vm starts successfully
jlebon FCOS next
Pass pass
[1]
  1. Tested both passing the SSH key via keypairs and via the Ignition config.
jmarrero jmarrero
Pass pass
[1]
  1. Worked for me, however the image takes a bit to be available after is uploaded.
mnguyen
Pass pass
nielsenb ami-055c024e1ed6245f0, t2.micro
Pass pass
ravanelli
Pass pass
[1]
ravanelli VirtualBox 7.0.10 r158379(Qt5.15.2) on Mac
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 Fedora CoreOS 39.20230916.1.1 on a diskless PXE booted X86_64
Pass pass
[1]
Pass pass
Pass pass
[2]
  1. Podman use only
  2. All my containerized services are running as expected (jenkins, jenkins-agent, docker registry, redis, promtail, ...) but didn't try quadlet
brianmcarey fedora-coreos-39.20230916.1.2
Pass pass
danniel Lenovo ideapad S145
Pass pass
Pass pass
Pass pass
geraldosimiao Fedora CoreOS 39.20230916.1.2 on KVM-QEMU-VirtManager (F39 KDE)
Pass pass
ravanelli qemu on R152-P31-00 aarch64
Pass pass
[1]
Pass pass
Pass pass
[2]
  1. Changing the root filesystem to ext4
  2. The vim package got issues to be installed due its deps. Installed calc that has no deps instead. The default edit also got changed to use vim
ydesouza QEMU | Fedora CoreOS 39.20230916.1.2
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 Fedora CoreOS 39.20230916.1.1 on a diskless PXE booted X86_64
Pass pass
Pass pass
[1]
  1. Only run tests from documentation
brianmcarey fedora-coreos-39.20230916.1.2
Pass pass
danniel Lenovo ideapad S145
Pass pass
dustymabe 39.20230916.1.2 qemu qcow in libvirt
Pass pass
ravanelli qemu on 8561 s390x
Fail fail
[1]
  1. We have a Snoozing kola test pattern "ext.config.kdump.crash" until Sep 30 2023 with https://github.com/coreos/fedora-coreos-tracker/issues/1560 However, this issue seems different. It is not a selinux denial thing.
ravanelli qemu on R152-P31-00 aarch64
Fail fail
[1]
  1. Same as s390x
rravanel qemu on R152-P31-00 aarch64
Pass pass
[1]
  1. Tested via udev rule
ydesouza QEMU | Fedora CoreOS 39.20230916.1.2
Pass pass
Pass pass

Upgrade[edit]

User Profile Switch stream Bootloader updates References
jdoss
Pass pass
[1]
  1. Zincati upgraded to 39.20230916.1.2 on a DigitalOcean VM without issues.
jmarrero jmarrero
Pass pass
Pass pass
[1]
  1. seen expected results

Tutorials[edit]

User Profile All Tests - Add the ones you did References

Miscellaneous[edit]

User Profile Documentation Exploratory testing References
Nemric Fedora CoreOS 39.20230916.1.1 on a diskless PXE booted X86_64
Fail fail
[1]