Fedora 29 Cloud/Atomic Test Day

More information about the event can be found here: http://fedoraproject.org/wiki/Test_Day:2018-10-01_Cloud-Atomic_Testday
Go back to List of Events.

Results

Clicking on the testcase name will show you the appropriate "how to test" page.
Click on the Enter result button, to enter result.
Note: results are cached and realoaded from the database each 10 seconds.

Basic tests

Username Profile Boot Logging Services Start SELinux Service Manipulation Comments
Enter result Enter result Enter result Enter result Enter result
garrmcnu Atomic Host 29 20180929.n.0 Vagrant libvirt
jaydeepgo Fedora Cloud qcow2 x86_64 [1] 1. #1634378, Failed to create user at boot time
jlanda Fedora-AtomicHost-ostree-x86_64-29-20180929.n.0.iso fresh install on libvirt [1] 1. Althrought the test case is PASSED, the bootup process is delayed due to two stucked boot jobs (root.device and swap.device something). Due to lack of cloud-init source?
pwhalen Fedora-AtomicHost-29-20180929.n.0.aarch64.raw [1] 1. sshd still enabled and running on reboot
pwhalen Fedora-AtomicHost-ostree-aarch64-29-20180929.n.0.iso
reavessm Fedora Atomic 29 [1] 1. Couldn't boot vm from provided qcow2, error said no route to 169.254.169.254. Host machine couldn't ping that address either. Testcloud wouldn't work from URL, had to use wget then use testcloud on the qcow2 image.
sayanchowdhury
sayanchowdhury Fedora-Cloud-Base-29-20180929.n.0.x86_64.qcow2
sinnykumari Fedora-AtomicHost-29-20180929.n.0.{x86_64,ppc64le,aarch64}.{qcow2,raw} , KVM
sinnykumari Fedora-AtomicHost-ostree-{x86_64,aarch64, ppc64le}-29-20180929.n.0.iso, KVM [1] 1. Boot process took longer time on x86_64 at step "A start job is running fedora root.device / swap.device". Waited around 1 minute 30 seconds.

Atomic

Username Profile Atomic Boot Test Container Storage Setup Docker Lifecycle Atomic Upgrade Atomic Downgrade rpm-ostree package layering Comments
Enter result Enter result Enter result Enter result Enter result Enter result
garrmcnu Atomic Host 29 20180929.n.0 Vagrant libvirt [1] 1. Changed URL in /etc/ostree/remotes.d/fedora-atomic.conf (as documented by others).
pwhalen Fedora-AtomicHost-29-20180929.n.0.aarch64.raw
pwhalen Fedora-AtomicHost-ostree-aarch64-29-20180929.n.0.iso
reavessm Fedora Atomic 29 [1] [2] 1. virt-manager worked perfectly once I followed the directions correctly...
2. file2 still existed after reboot
sinnykumari Fedora-AtomicHost-29-20180929.n.0.{x86_64,ppc64le,aarch64}.{qcow2,raw} , KVM [1] [2] [3] 1. To perform rpm-ostree upgrade, updated url in /etc/ostree/remotes.d/fedora-atomic.conf from https://kojipkgs.fedoraproject.org/atomic/repo/ to https://kojipkgs.fedoraproject.org/compose/atomic/repo
2. To perform rpm-ostree upgrade, updated url in /etc/ostree/remotes.d/fedora-atomic.conf from https://kojipkgs.fedoraproject.org/atomic/repo/ to https://kojipkgs.fedoraproject.org/compose/atomic/repo
3. To perform rpm-ostree upgrade, updated url in /etc/ostree/remotes.d/fedora-atomic.conf from https://kojipkgs.fedoraproject.org/atomic/repo/ to https://kojipkgs.fedoraproject.org/compose/atomic/repo
sinnykumari Fedora-AtomicHost-ostree-{x86_64,aarch64, ppc64le}-29-20180929.n.0.iso, KVM [1] 1. To perform rpm-ostree upgrade, updated url in /etc/ostree/remotes.d/fedora-atomic.conf from https://kojipkgs.fedoraproject.org/atomic/repo/ to https://kojipkgs.fedoraproject.org/compose/atomic/repo

Exploratory

Username Profile Kubeadm Cluster on Atomic oc cluster up on Atomic Launch app on Cloud Base image Launch app on FAH Custom (write in comment what you did) Comments
Enter result Enter result Enter result Enter result Enter result
sinnykumari Fedora-AtomicHost-29-20180929.n.0 [1] 1. * If using origin-clients package available in F29(origin-clients-3.10.0-2.fc29), needs workaround specified in bug https://bugzilla.redhat.com/show_bug.cgi?id=1558425#c3 * Using origin clients from F30 (origin-clients-3.11.0-0.alpha1.0.fc30) doesn't need workaround * This issue is being tracked at https://pagure.io/atomic-wg/issue/510

Cloud Providers

Username Profile Launch on AWS Launch on OpenStack (requires openstack instance) Comments
Enter result Enter result
qba Fedora-Cloud-Base-29-20180929.n.0.x86_64.qcow2 [1] 1. https://www.cloudwatt.com/ n2.cw.standard-2 Install OK, Cloud-Init Not Tested (but it looks like it tried to run, should be OK), dnf update OK, cockpit OK (login, main dashboard, setting auto-updates ), k8s with kubeadm KO (timeout on installation, not investigated).
sayanchowdhury Fedora-AtomicHost-29-20180929.n.0.x86_64, region us-east-1, gp2
sayanchowdhury Fedora-AtomicHost-29-20180929.n.0.x86_64, region us-east-1, standard
sayanchowdhury Fedora-Cloud-Base-29-20180929.n.0.x86_64, region us-east-1, gp2
sayanchowdhury Fedora-Cloud-Base-29-20180929.n.0.x86_64, region us-east-1, standard
sinnykumari Fedora-AtomicHost-29-20180929.n.0.x86_64, region ap-southeast-1
sinnykumari Fedora-Cloud-Base-29-20180929.n.0.x86_64, region ap-southeast-1
Wiki Metadata