From Fedora Project Wiki
Fedora CoreOS Test Week
Fedora CoreOS

Date 2021-10-11 to 2021-10-15
Time all week

Website QA/Test Days
IRC #fedora-coreos (webirc)
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 the IRC: #fedora-coreos[?] on https://libera.chat/.

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)
  • Test day Image

Grab images/artifacts/information for the most current next stream release (35.XZAEXVC.00) from our download page: https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=next

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, just ask on IRC #fedora-coreos[?], #fedora-test-day[?] or #fedora-qa[?] and we will help you.

Test Results[edit]

Installation[edit]

User Profile Virtual install Bare Metal install References
bittin
Pass pass
bittin HP 655
Fail fail
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
bittin Virtualbox
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
danniel x86_64, virt-manager
Pass pass
Pass pass
donaldsebleung FCOS 35.20211003.1.0 with QEMU/KVM on Ubuntu 20.04 host
Pass pass
ersen x86_64, virt-manager
Pass pass
geraldosimiao x86_64, virt-manager
Pass pass
hricky x86_64, virt-manager
Pass pass
Pass pass
[1]
  1. Pentium(R) Dual-Core CPU E5200 @ 2.50GHz, 3.81G RAM
jaimelm
Pass pass
[1]
  1. Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz (read: Mac Pro 'trash can')
ravanelli x86_64, macOs Big Sur, VirtualBox
Pass pass
saqali VirtualBox (FCOS 35.20211010.1.0, 8.6 GiB disk size)
Pass pass
[1]
  1. Initially tried with 8.0 GiB disk size after reading that the root filesystem needs to be 8GiB. The additional partitions created brought the root filesystem to 7.5GiB so I received a warning on SSH. After retrying with a disk size of 8.6 GiB, I didn't have these problems.

Cloud launch[edit]

User Profile AWS Azure GCP DigitalOcean VMWare Exoscale IBM Cloud VirtualBox OpenStack Alibaba References
akumar99 ami-08a2a4f6f7a90e59f, t2.micro, us-east-1
Fail fail
[1]
  1. Applied security group with all ports and IPv4s open. Unable to ping the instance. System reachability check passed but Instance status checks is stuck at initialization. ssh cannot proceed as well. Tried with the image in ap-south-1 but same results.
alciregi Digitalocean droplet
Pass pass
[1]
donaldsebleung FCOS 35.20211003.1.0 with SSH key pair only on AWS web interface
Fail fail
[1]
Warning warn
[2]
Fail fail
[3]
  1. Confirmed the issue after a good night's sleep. Tested both FCOS 35.20211003.1.0 (next) and FCOS 34.20210919.3.0 (stable) with identical SSH key pair and security group. Next is unreachable via SSH (ssh timed out) and fails instance reachability check while stable is reachable via SSH and passes both checks as expected.
  2. Previous comment is incorrect as I confused Ubuntu instance IP with FCOS instance IP. However, FCOS instance is unreachable via SSH (ssh hangs indefinitely) and AWS web interface reports "1/2 checks passed" for FCOS instance; in particular, "instance reachability check failed".
  3. Attempting to run ssh core@$PUBLIC_IP gives "Permission denied (publickey)" error, even after allowing the instance a few minutes to stabilize. For reference, I created an Ubuntu 20.04 server instance with identical SSH key pair and security group, and was able to successfully SSH into that instance, ruling out configuration error on my part.
dustymabe 35.20211017.1.0 on ibmcloud bx2-2x8 instance
Pass pass
[1]
  1. Everything looked good. Will PR slight tweaks to the docs.
hhei 35.20211010.1.0 next
Fail fail
[1]
Pass pass
[2]
  1. Login fcos VM, and test "modifying kernel arguments", except the sudo rpm-ostree kargs --editor get "No changes." issue(https ://github.com/coreos/rpm-ostree/issues/3182), other results are OK
  2. Launch fcos VM on azure and ssh core@ipaddress successfully, doc is good
hhei 35.20211010.1.0 next, testing CoreOS Azure and "CoreOS modifying kernel arguments"
Fail fail
[1]
Fail fail
[2]
  1. Test with "CoreOS Azure", launch coreos VM on azure and can ssh successfully Test with "CoreOS modifying kernel arguments", except the sudo rpm-ostree kargs --editor get "No changes." issue(https://github.com/coreos/rpm-ostree/issues/3182), other results are OK
  2. 1. Test "Testcase CoreOS Azure", result is PASSED, and doc is good 2. Test "CoreOS modifying kernel arguments", except https://github.com/coreos/rpm-ostree/issues/3182, other results and doc are OK
jlebon 35.20211010.1.0
Pass pass
[1]
  1. Tested with and without Ignition config
jlebon 35.20211010.1.0; no Ignition config
Pass pass
jmarrero
Pass pass
[1]
miabbott
Pass pass
[1]
  1. Ran through the steps to use the cloud provided SSH key and Ignition workflow. Need to make some slight tweaks to the docs, but the steps work great.

aarch64[edit]

User Profile AWS Virtual install Bare Metal install References
akumar99 ami-08a2a4f6f7a90e59f, t2.micro, us-east-1
Fail fail
[1]
  1. Applied security group with all ports and IPv4s open. Unable to ping the instance. System reachability check passed but Instance status checks is stuck at initialization. ssh cannot proceed as well. Tried with the image in ap-south-1 but same results.
bittin
Pass pass
bittin HP 655
Fail fail
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
bittin Virtualbox
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
danniel x86_64, virt-manager
Pass pass
Pass pass
donaldsebleung FCOS 35.20211003.1.0 with QEMU/KVM on Ubuntu 20.04 host
Pass pass
donaldsebleung FCOS 35.20211003.1.0 with SSH key pair only on AWS web interface
Fail fail
[1]
Warning warn
[2]
Fail fail
[3]
  1. Confirmed the issue after a good night's sleep. Tested both FCOS 35.20211003.1.0 (next) and FCOS 34.20210919.3.0 (stable) with identical SSH key pair and security group. Next is unreachable via SSH (ssh timed out) and fails instance reachability check while stable is reachable via SSH and passes both checks as expected.
  2. Previous comment is incorrect as I confused Ubuntu instance IP with FCOS instance IP. However, FCOS instance is unreachable via SSH (ssh hangs indefinitely) and AWS web interface reports "1/2 checks passed" for FCOS instance; in particular, "instance reachability check failed".
  3. Attempting to run ssh core@$PUBLIC_IP gives "Permission denied (publickey)" error, even after allowing the instance a few minutes to stabilize. For reference, I created an Ubuntu 20.04 server instance with identical SSH key pair and security group, and was able to successfully SSH into that instance, ruling out configuration error on my part.
ersen x86_64, virt-manager
Pass pass
geraldosimiao x86_64, virt-manager
Pass pass
hricky x86_64, virt-manager
Pass pass
Pass pass
[1]
  1. Pentium(R) Dual-Core CPU E5200 @ 2.50GHz, 3.81G RAM
jaimelm
Pass pass
[1]
  1. Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz (read: Mac Pro 'trash can')
ravanelli x86_64, macOs Big Sur, VirtualBox
Pass pass
saqali VirtualBox (FCOS 35.20211010.1.0, 8.6 GiB disk size)
Pass pass
[1]
  1. Initially tried with 8.0 GiB disk size after reading that the root filesystem needs to be 8GiB. The additional partitions created brought the root filesystem to 7.5GiB so I received a warning on SSH. After retrying with a disk size of 8.6 GiB, I didn't have these problems.

Advanced configuration[edit]

User Profile Static networking Complex partitioning Building containers Containerized service Kernel Tuning (sysctl) Modifying Kernel Arguments OS extensions References
danniel x86_64, virt-manager
Pass pass
Pass pass
donaldsebleung FCOS 35.20211003.1.0 with QEMU/KVM on Ubuntu 20.04 host
Pass pass
[1]
Pass pass
[2]
Pass pass
[3]
Pass pass
[4]
Pass pass
[5]
Pass pass
[6]
Pass pass
[7]
  1. Configured static IP,gateway 10.0.2.100/24,10.0.2.2 with user networking and DNS server 8.8.8.8. Can successfully SSH into FCOS instance and interface details as reported by nmcli conn show ens3 match the configuration
  2. Configured LUKS device at /var/lib/data as per linked example with 16G capacity. Confirmed FCOS system partitioning matches configuration on boot
  3. Configured /var on separate partition with ext4 filesystem as per linked example. Confirmed FCOS system partitioning matches configuration
  4. All test cases (rootless podman, privileged podman, privileged docker) passed
  5. etcd etcd-member.service
  6. busybox hello.service
  7. kernel.sysrq = 0
geraldosimiao x86_64, virt-manager
Pass pass
hricky x86_64, virt-manager
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
mnguyen
Warning warn
[1]
  1. Needs update to docs. The systemd units needs a Wants=network-online.target also otherwise rpm-ostree can't fetch the repoxml because it can't resolve the host for the mirrors.
ravanelli x86_64, macOs Big Sur, VirtualBox
Pass pass

Upgrade[edit]

User Profile Switch stream Bootloader updates References
donaldsebleung FCOS 34.20210919.3.0 with QEMU/KVM on Ubuntu 20.04 host
Pass pass
[1]
Pass pass
[2]
Pass pass
[3]
Pass pass
[4]
Pass pass
[5]
Pass pass
  1. Automatic bootloader update with systemd service
  2. Testcase CoreOS bootupd
  3. Manually configured busybox hello.service survived switch stream
  4. Permanent manual rollback
  5. Temporary rollback
hricky x86_64, virt-manager
Pass pass

Miscellaneous[edit]

User Profile Documentation Exploratory testing References