| Username | Profile | Virtual install | Bare Metal install | Comments |
|---|---|---|---|---|
| Enter result | Enter result | |||
| Blu3 | qemu virt-install ignition provisioned | |||
| akumar99 | KVM | [1] |
1.
Worked fine.
|
|
| bakers46@gilanet.com | ||||
| copperi | KVM | |||
| danniel | KVM | |||
| donaldsebleung | Provisioning Fedora CoreOS on QEMU | |||
| drakkai | libvirt | [1] |
1.
Booted without problems, works fine.
|
|
| ed.schmidt26@gmail.com | Bare Metal | [1] |
1.
Pass HP Probook 650 install Great job
|
|
| galoget | QEMU/KVM | |||
| geraldosimiao | KVM - Qemu-system | |||
| jimtahu | virt-install with ssh-key in ignition | [1] |
1.
also manually ran some podman instances on the newly launched system
|
|
| jlebon | "virtualized" bare metal | [1] |
1.
A few UX improvements to `coreos-installer download` filed in https://github.com/coreos/coreos-installer/issues/406.
|
|
| joydeep | QEMU/KVM | |||
| lbazan | KVM | |||
| lbazan | supermicro | |||
| lucasaf88 | QEMU/KVM | |||
| nasirhm | qemu-kvm | [1] |
1.
SSH configuration works as expected.
|
|
| nielsenb | QEMU/KVM | |||
| olem | libvirt | [1] |
1.
Used coreos-installer and virt-install. No issue to launch the VM and log in.
|
|
| pruthvi30sk | Intel® Core™ i7-8700U CPU @ 2.10GHz × 4 | [1] |
1.
Installed successfully without any issue.
|
|
| russ | [1] |
1.
test bed was Thinkpad T400, saw some bash returns where my favorite scripts weren't in the vocabulary.
|
||
| russk | libvirt/QEMU | [1] |
1.
Got instance running and able to SSH in successfully. In "Producing an Ignition File" doc, you might change "Using FCCT" section label to be called "Convert FCC File to IGN Ignition File". That
would more accurately describe the step.
|
|
| sayaksarkar | qemu-kvm | |||
| siddharthvipul1 | virt-manager | |||
| sinnykumari | Virtual install | [1] |
1.
Works as described in Test case
|
|
| sumantrom | ||||
| uwueviee | KVM |
| Username | Profile | AWS | Azure | GCP | DigitalOcean | VMWare | Exoscale | IBM Cloud | Comments |
|---|---|---|---|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | |||
| akumar99 | t2.micro - all default | [1] |
1.
Worked fine.
|
||||||
| cptmorgan-rh | [1] |
1.
Worked as expected.
|
|||||||
| dghubble | 33.20201104.1.0 | [1] |
1.
FRA1
|
||||||
| dustymabe | fedora-coreos-33.20201104.1.0-ibmcloud.x86_64.qcow2 | [1] |
1.
Seemed to work when following the documentation.
|
||||||
| knarra | AWS [core@ip-172-31-88-179 ~]$ cat /etc/redhat-release Fedora release 33 (Thirty Three) | [1] |
1.
Works with out any issues
|
||||||
| lucasaf88 | GCP | [1] |
1.
Tested with custom Ignition file and access with ssh. Everything worked fine.
|
||||||
| mnguyen | [1] |
1.
[core@fcos-mnguyen ~]$ sudo rpm-ostree status
State: idle
Deployments:
● ostree://fedora:fedora/x86_64/coreos/next
Version: 33.20201104.1.0 (2020-11-05T14:20:13Z)
Commit: f7bff56c9710b5fedb22d50651bcd875856bb83510f7115e10d21167bd9a3b75
GPGSignature: Valid signature by 963A2BEB02009608FE67EA4249FD77499570FF31
|
|||||||
| nb | [1] |
1.
[core@ip-172-30-1-165 ~]$ sudo rpm-ostree status
State: idle
Deployments:
● ostree://fedora:fedora/x86_64/coreos/next
Version: 33.20201104.1.0 (2020-11-05T14:20:13Z)
Commit: f7bff56c9710b5fedb22d50651bcd875856bb83510f7115e10d21167bd9a3b75
GPGSignature: Valid signature by 963A2BEB02009608FE67EA4249FD77499570FF31
[core@ip-172-30-1-165 ~]$
|
|||||||
| nielsenb | ami-08ae7387308b22a6a, t2.micro | [1] |
1.
Used named key
|
||||||
| olem | aws | [1] |
1.
Used AWS web UI to provision the VM; passed ignition as user data.
|
||||||
| pruthvi30sk | Intel® Core™ i7-8700U CPU @ 2.10GHz × 4 | [1] |
1.
Installation was fine
|
||||||
| pruthvi30sk | azure | ||||||||
| sinnykumari | AWS | [1] |
1.
Tested in ap-southeast-1 region
|
| Username | Profile | Static networking | Complex partitioning | Building containers | Containerized service | Comments |
|---|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | Enter result | |||
| cptmorgan-rh | [1] |
1.
Used my fcos-gitlab repo to deploy on `next` release. Worked as expected. - https://github.com/cptmorgan-rh/fcos-gitlab
|
||||
| danniel | KVM | |||||
| donaldsebleung | Provisioning Fedora CoreOS on QEMU | [1] | [2] |
1.
All 6 basic tests passed. Also tried using the containers to convert example.fcc in https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/#_writing_the_f... to example.ign with
expected results. Additionally, tried NGINX with port forwarding (8080->80) with rootless podman, privileged podman and docker and all work as expected.
2. /bin/podman kill busybox1 and /bin/podman rm busybox1 exited with codes 125 and 1 respectively but I suppose that should be expected on the first run since the container does not exist yet. Other than that, systemctl status hello gives a status of "active (running)" and Hello World is printed every second as expected. |
||
| jlebon | "virtualized" bare metal | [1] | [2] | [3] |
1.
Tested with /var on LUKS on a separate disk
2. Built and ran fcct as rootless podman and privileged podman. 3. Successfully ran busybox example as a service |
|
| lucasaf88 | GCP | [1] |
1.
Tested all steps on an FCOS instance in GCP.
|
|||
| mnguyen | [1] |
1.
No issues found
|
||||
| nasirhm | qemu-kvm | [1] [2] | [3] |
1.
rootless podman works fine too.
2. Privileged Docker and Podman works fine. 3. Busybox as a containerized service works fine. |
||
| olem | aws | [1] [2] |
1.
Launched FCOS vm on eu-west-1 using rancher-machine (https://github.com/rancher/machine). Tested docker daemon shared over network.
2. All basic tests worked (rootless podman, privileged podman, docker). Also accessed network from the containers. |
| Username | Profile | Switch stream | Comments |
|---|---|---|---|
| Enter result | |||
| donaldsebleung | Provisioning Fedora CoreOS on QEMU | [1] |
1.
Performed basic testing plus point #2 in the "Optional" section (temporary and permanent rollbacks). Everything was as expected, though the only service I tested was that zincati was up and running
after every reboot.
|
| lucab | aliyun - ecs.c6e.large | ||
| nasirhm | qemu-kvm | [1] [2] |
1.
Rollback works fine too.
2. Rebased from stable to next |
| olem | libvirt | [1] |
1.
Updated from stable (32.20201018.3.0) to next (33.20201104.1.0), then permanent rollback to 32.20201018.3.0, then again permanent rollback to 33.20201104.1.0.
I launched a web application on Docker
before the upgrade; it still worked after the upgrade and then after the restorations. I observed that moby-engine was upgraded from 19.03.11 to 19.03.13 and back.
|
| sinnykumari | Switch stream | [1] |
1.
Rebase from stable to next works fine, rollback works fine, container related changes exist and works as expected with switching stream
|
| Username | Profile | Documentation | Exploratory testing | Comments |
|---|---|---|---|---|
| Enter result | Enter result | |||
| dustymabe | 33.20201104.1.0 qemu qcow2 | [1] |
1.
Ran the manual network testing script at https://github.com/coreos/fedora-coreos-config/blob/testing-devel/tests/manual/c... . Passed all tests.
|
|
| dustymabe | fedora-coreos-33.20201104.1.0-openstack.x86_64.qcow2 | [1] |
1.
Tested out running on openstack using the new documentation I just wrote: https://github.com/coreos/fedora-coreos-docs/pull/202
|
|
| jingzhan | [1] |
1.
1. Tested creating snapshot and running a fcos instance on vultr using the `next` release, all tests worked.
|
||
| lucab | aliyun - ecs.c6e.large | [1] |
1.
Verified cloud SSH pubkey too.
|