| Username | Profile | Virtual install | Bare Metal install | Comments |
|---|---|---|---|---|
| Enter result | Enter result | |||
| bittin | ||||
| bittin | HP 655 | |||
| bittin | Virtualbox | |||
| danniel | x86_64, virt-manager | |||
| donaldsebleung | FCOS 35.20211003.1.0 with QEMU/KVM on Ubuntu 20.04 host | |||
| ersen | x86_64, virt-manager | |||
| geraldosimiao | x86_64, virt-manager | |||
| hricky | x86_64, virt-manager | [1] |
1.
Pentium(R) Dual-Core CPU E5200 @ 2.50GHz, 3.81G RAM
|
|
| jaimelm | [1] |
1.
Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz (read: Mac Pro 'trash can')
|
||
| ravanelli | x86_64, macOs Big Sur, VirtualBox | |||
| saqali | VirtualBox (FCOS 35.20211010.1.0, 8.6 GiB disk size) | [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.
|
| Username | Profile | AWS | Azure | GCP | DigitalOcean | VMWare | Exoscale | IBM Cloud | VirtualBox | OpenStack | Alibaba | Comments |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | |||
| akumar99 | ami-08a2a4f6f7a90e59f, t2.micro, us-east-1 | [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 | [1] |
1.
https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-digitalocean/#_l... - The "user data" link leads to a 404 digitalocean page
|
|||||||||
| donaldsebleung | FCOS 35.20211003.1.0 with SSH key pair only on AWS web interface | [1] [2] [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 | [1] |
1.
Everything looked good. Will PR slight tweaks to the docs.
|
|||||||||
| hhei | 35.20211010.1.0 next | [1] [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" | [1] [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 | [1] |
1.
Tested with and without Ignition config
|
|||||||||
| jlebon | 35.20211010.1.0; no Ignition config | |||||||||||
| jmarrero | [1] |
1.
doc update:
https://github.com/coreos/fedora-coreos-docs/pull/333
|
||||||||||
| miabbott | [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.
|
| Username | Profile | AWS | Virtual install | Bare Metal install | Comments |
|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | |||
| akumar99 | ami-08a2a4f6f7a90e59f, t2.micro, us-east-1 | [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 | |||||
| bittin | HP 655 | ||||
| bittin | Virtualbox | ||||
| danniel | x86_64, virt-manager | ||||
| donaldsebleung | FCOS 35.20211003.1.0 with QEMU/KVM on Ubuntu 20.04 host | ||||
| donaldsebleung | FCOS 35.20211003.1.0 with SSH key pair only on AWS web interface | [1] [2] [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 | ||||
| geraldosimiao | x86_64, virt-manager | ||||
| hricky | x86_64, virt-manager | [1] |
1.
Pentium(R) Dual-Core CPU E5200 @ 2.50GHz, 3.81G RAM
|
||
| jaimelm | [1] |
1.
Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz (read: Mac Pro 'trash can')
|
|||
| ravanelli | x86_64, macOs Big Sur, VirtualBox | ||||
| saqali | VirtualBox (FCOS 35.20211010.1.0, 8.6 GiB disk size) | [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.
|
| 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 | |||
| danniel | x86_64, virt-manager | ||||||||
| donaldsebleung | FCOS 35.20211003.1.0 with QEMU/KVM on Ubuntu 20.04 host | [1] | [2] [3] | [4] | [5] [6] | [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 | ||||||||
| hricky | x86_64, virt-manager | ||||||||
| mnguyen | [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 |
| Username | Profile | Switch stream | Bootloader updates | Comments |
|---|---|---|---|---|
| Enter result | Enter result | |||
| donaldsebleung | FCOS 34.20210919.3.0 with QEMU/KVM on Ubuntu 20.04 host | [1] [2] [3] [4] [5] |
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 |
| Username | Profile | Documentation | Exploratory testing | Comments |
|---|---|---|---|---|
| Enter result | Enter result |