| Username | Profile | Virtual install | Bare Metal install | Comments |
|---|---|---|---|---|
| Enter result | Enter result | |||
| Jimmy | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | [1] |
1.
SSH cannot sign in
[jimmy@m4700 Downloads]$ ssh core@10.0.2.15 -v -v -v
OpenSSH_8.3p1, OpenSSL 1.1.1g FIPS 21 Apr 2020
...
debug2: ssh_connect_direct
debug1: Connecting to 10.0.2.15
[10.0.2.15] port 22.
|
|
| andydude | fedora-coreos-32.20200601.2.1-live.x86_64.iso | [1] |
1.
VirtualBox on macOS
|
|
| andydude | fedora-coreos-32.20200601.2.1-vmware.x86_64.ova | [1] |
1.
There are essentially 3 bugs: 1. On BIOS boot, the boot process hangs after starting NetworkManager, 2. On UEFI boot, the boot process is unable to find a suitable boot loader, and 3. There is no way
to specify ignition on VirtualBox
|
|
| axat | edora-coreos-32.20200601.1.1-live.x86_64.iso | [1] |
1.
VMware on ubuntu
|
|
| blueduckdock42 | fedora-coreos-32.20200601.1.1-live.x86_64.iso | |||
| condor | fedora-coreos-32.20200601.1.1-live.x86_64.iso | |||
| coremodule | fedora-coreos-32.20200601.2.1 | [1] |
1.
I only tested this once, but it passed. I accidentally put "Failed".
|
|
| gabibbo97 | ||||
| garrmcnu | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | |||
| grantral | fedora-coreos-32.20200601.1.1-live.x86_64.iso | [1] |
1.
Optional steps:
1. try to log into the machine on the serial console using password - OK
2. try to log into the machine over SSH using a username and password - OK
|
|
| grantral | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | |||
| information@josephpesco.info | ||||
| jlebon | fedora-coreos-32.20200601.2.1-live.x86_64.iso | |||
| jskladan | fedora-coreos-32.20200601.1.1-live.x86_64.iso | |||
| kparal | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | [1] |
1.
Networking works fine with libvirt, I can ssh into the machine. But with the QEMU instructions, I can't ssh in, the tutorial is misleading. That is already reported here:
https://github.com/coreos/fedora-coreos-docs/issues/6
|
|
| lnie | [1] |
1.
works,but the document need to be updated:https://github.com/coreos/fedora-coreos-docs/issues/6
|
||
| lruzicka | fedora-coreos-32.20200601.1.1-live.x86_64.iso | |||
| mhoungbo | fedora-coreos-32.20200601.2.1-live.x86_64 | |||
| nielsenb | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | |||
| profit | [1] |
1.
Install guide on https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_provisionin... shows no mention of network adaptor for virt-install so you cannot ssh into the machine.
|
||
| robmusial | fedora-coreos-31.20200517.3.0-live.x86_64.iso | |||
| rudrapratap | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | |||
| sassam | fedora-coreos-32.20200601.1.2-qemu.x86_64.qcow2 | [1] |
1.
Works as documented.
|
|
| shiwanibiradar | fedora-coreos-32.20200601.2.1-live.x86_64.iso | |||
| sumantrom | fedora-coreos-32.20200601.1.1-live.x86_64.iso | |||
| tartina | fedora-coreos-32.20200601.2.1-qemu.x86_64.qcow2 | [1] |
1.
I had to add network options (-net nic,model=virtio,netdev=manage -netdev bridge,br=virbr0,id=manage) to qemu to ssh into the machine
|
|
| yozaam | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2.xz | [1] |
1.
Not able to boot in qemu-system-x86_64 -> macOS
-> after qemu-system-x86_64 -> exited with preempt_count 1
-> ignition file created successfully
-> started the coreOS in qemu, but after ostree
selection screen -> few seconds into booting I get a migration error,
-> qemu command and output
https://pastebin.com/a5kAzZBZ
|
| Username | Profile | AWS | Azure | GCP | DigitalOcean | VMWare | Comments |
|---|---|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | Enter result | Enter result | |||
| anantj12 | ami-0ddfdca8ca28b02a1 | ||||||
| axat | fedora-coreos-32.20200601.2.1-vmware.x86_64.ova | ||||||
| blueduckdock42 | fedora-coreos-32.20200601.1.1-live.x86_64.iso | ||||||
| coremodule | fedora-coreos-32.20200601.2.1 | ||||||
| dustymabe | fedora-coreos-32.20200601.2.1-azure.x86_64.vhd | [1] |
1.
Everything worked but I did find a cosmetic issue which I'll submit a PR for.
|
||||
| dustymabe | fedora-coreos-32.20200601.2.2-digitalocean.x86_64 | [1] |
1.
Found one bug where DO images aren't getting their hostname set (info comes from the metadata service). https://github.com/coreos/fedora-coreos-tracker/issues/538
|
||||
| dustymabe | latest image from fedora-coreos-next image family |
| Username | Profile | Static networking | Complex partitioning | Building containers | Containerized service | Comments |
|---|---|---|---|---|---|---|
| Enter result | Enter result | Enter result | Enter result | |||
| blueduckdock42 | fedora-coreos-32.20200601.1.1-live.x86_64.iso | [1] |
1.
Container service- started and enabled fine. Has insufficient permissions to write to journal files but otherwise fine and works fine after reboots as well.
|
|||
| gabibbo97 | [1] |
1.
Could not set root on btrfs
|
||||
| grantral | fedora-coreos-32.20200601.1.1-live.x86_64.iso | [1] |
1.
https://github.com/coreos/fedora-coreos-tracker/issues/527
https://github.com/coreos/fedora-coreos-tracker/issues/528
|
|||
| jligon | Fedora CoreOS 32.20200601.1.1 | [1] |
1.
created via vagrant box builder pointing at the next stream
|
|||
| jskladan | fedora-coreos-32.20200601.1.1-live.x86_64.iso | |||||
| kparal | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | [1] |
1.
everything worked, but it was a bit confusing that I couldn't mount a partition under / or /mnt and I had to use /var (which I didn't see mentioned in the guide). Also, I didn't notice at first that
a systemd mount unit needs to be created, I had to ask on IRC. During debugging, many default values weren't specified, filed as https://github.com/coreos/fedora-coreos-docs/issues/83
|
|||
| lnie | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | [1] | [2] |
1.
https://github.com/coreos/fedora-coreos-tracker/issues/539
2. Everything works. but "podman run -ti --rm rootless-test-fcct --help" and "sudo docker run -ti --rm docker-fcct --help",complaints" SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue)" |
||
| lruzicka | fedora-coreos-32.20200601.1.1-live.x86_64.iso | [1] | [2] |
1.
I could not manipulate the whole layout, but I could add the /var partition as described in the Docs.
2. The Podman test is OK, but the Docker test could not be run due to permission error (see message). When using 'sudo' the Docker test could be completed. [core@localhost fcct]$ docker build -t fcct . Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.40/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&session=vj72ol73yshsll1c85i9tm2qo&shmsize=0&t=fcct&target=&ulimits=null&version=1": dial unix /var/run/docker.sock: connect: permission denied |
||
| nielsenb | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | |||||
| rudrapratap | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | [1] |
1.
podman ----> passed
docker ----> failed
rpratap@rudy fcct]$ sudo docker build -t fcct .
Sending build context to Docker daemon 2.332MB
Step 1/8 : FROM golang:latest AS builder
latest: Pulling
from library/golang
376057ac6fa1: Pull complete
5a63a0a859d8: Pull complete
496548a8c952: Pull complete
2adae3950d4d: Pull complete
039b991354af: Pull complete
6b823afb12d9: Pull complete
30b9d62bd869: Pull complete
Digest: sha256:4d58164df51901679307e547ffed19837e63a1d1b9ed80453b8d88749b6033f4
Status: Downloaded newer image for golang:latest
---> 05feda542433
Step 2/8 : RUN mkdir /fcct
---> Running in c4b0df78e3fb
cgroups: cgroup mountpoint does not exist: unknown
|
|||
| sassam | fedora-coreos-32.20200601.1.2-qemu.x86_64.qcow2 | [1] |
1.
Works as expected.
|
|||
| sassam | https://docs.fedoraproject.org/en-US/fedora-coreos/ | |||||
| shiwanibiradar | fedora-coreos-32.20200601.2.1-live.x86_64.iso | [1] |
1.
failed both test case of podman as well as docker . Error: error creating build container: The following failures happened while trying to pull image specified by "golang:latest" based on search
registries in /etc/containers/registries.conf:
|
|||
| tartina | fedora-coreos-32.20200601.2.1-qemu.x86_64.qcow2 | [1] |
1.
I had to add network options (-net nic,model=virtio,netdev=manage -netdev bridge,br=virbr0,id=manage) to qemu to ssh into the machine
|
| Username | Profile | Switch stream | Comments |
|---|---|---|---|
| Enter result | |||
| bdlink | fedora-coreos-31.20200517.3.0-live.x86_64.iso switch to 32.20200601.1.1 next | [1] |
1.
#529,
Upgraded from fedora-coreos-31.20200517.3.0-live.x86_64. SSH in, no errors.
Verified temporary and permanent rollback did roll back. (but afterward, when boot up have issue sssd.service failing)
|
| blueduckdock42 | fedora-coreos-32.20200601.1.1-live.x86_64.iso | [1] |
1.
Decided to be bold and went from stable directly to next- no issues noticed, no systemd units failed, etc.
|
| coremodule | fedora-coreos-32.20200601.2.1 | ||
| grantral | fedora-coreos-32.20200601.1.1-live.x86_64.iso | [1] |
1.
https://github.com/coreos/fedora-coreos-tracker/issues/525
|
| kparal | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | [1] |
1.
everything worked including optional steps, except sssd.service fails with "Lower version of database is expected" after rollback, but that is expected according to the documentation
|
| lnie | fedora-coreos-32.20200601.1.1-qemu.x86_64.qcow2 | ||
| sumantrom | fedora-coreos-32.20200601.1.1-live.x86_64.iso |
| Username | Profile | Documentation | Exploratory testing | Comments |
|---|---|---|---|---|
| Enter result | Enter result | |||
| anamika | ||||
| axat | https://docs.fedoraproject.org/en-US/fedora-coreos/ | [1] |
1.
Can be more comprehensive
|
|
| sassam | https://docs.fedoraproject.org/en-US/fedora-coreos/ | [1] |
1.
Producing an Ignition File [https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/] could include an example using password_hash, described in
https://coreos.com/os/docs/latest/adding-users.html.
|