2018-10-01 Cloud-Atomic Testday

Cloud/Atomic Test Day


Date	2018-10-01
Time	all day

Website	QA/Test Days
IRC	#fedora-test-day (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 Bugzilla, 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 instalment of Fedora Test Day will focus on Fedora Atomic and Cloud images

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Development - Dustymabe (irc dustymabe), Sinny Kumari (irc ksinny), Sayan Chowdhury (irc sayan)
Quality Assurance - Kamil Paral (irc kparal), Geoff Marr (irc coremodule), Sumantro Mukherjee (irc sumantrom)

Prerequisite for Test Day[edit]

A fresh system, testcloud to test qcow images locally, or access to a cloud provider like OpenStack or AWS, and a desire to break software.

Fedora Atomic[edit]

Fedora Atomic Host (FAH) can be run as a traditional cloud image, or installed to bare metal. Feel free to try out the cloud images locally as a VM. If you have a spare machine you can install FAH to, please test the ISO image (link in table below). Download the image, write it to a USB stick, and install like any other Fedora deliverable. If you need help, please ping one of the test day organizers in IRC.

Image	Image URL	Checksum URLs
Fedora AtomicHost qcow2	x86_64 ppc64le aarch64	x86_64 ppc64le aarch64
Fedora AtomicHost raw	x86_64 ppc64le aarch64	x86_64 ppc64le aarch64
Fedora AtomicHost Vagrant libvirt	x86_64	x86_64
Fedora AtomicHost Vagrant VirtualBox	x86_64	x86_64
Fedora AtomicHost ISO Installer	x86_64 ppc64le aarch64	x86_64 ppc64le aarch64

If you have access to an AWS account then please try out an AMI from the following list:

Fedora-AtomicHost-29-20180929.n.0.x86_64      ap-northeast-1       ami-082fe651956205de0 hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      ap-northeast-2       ami-0f2ce9de90adef20a hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      ap-south-1           ami-061e972f6e3099823 hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      ap-southeast-1       ami-018da97419efd1819 hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      ap-southeast-2       ami-046146b16abce127b hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      ca-central-1         ami-01a5ca150e0216cba hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      eu-central-1         ami-04eda858fb0429f4d hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      eu-west-1            ami-0bf8145d3a459ad3c hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      eu-west-2            ami-0480a348ad5652ce7 hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      sa-east-1            ami-0990ef9f8e41edaf8 hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      us-east-1            ami-092cd6044e8e5e64f hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      us-west-1            ami-0319ffe4c99f751f5 hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      us-west-2            ami-016d9b70d01529326 hvm           standard       
Fedora-AtomicHost-29-20180929.n.0.x86_64      ap-northeast-1       ami-0af905f8e3e11a0c7 hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      ap-northeast-2       ami-0373aabc21b869c1f hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      ap-south-1           ami-02011ed25684658f5 hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      ap-southeast-1       ami-05c47592c530dc0d3 hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      ap-southeast-2       ami-04f0c8f5cce6a9cf2 hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      ca-central-1         ami-0c247a885cd469094 hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      eu-central-1         ami-05046ebe8db206dba hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      eu-west-1            ami-00b74096b2b675bde hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      eu-west-2            ami-079043c33252b3e57 hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      sa-east-1            ami-0bbd49ee494cced17 hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      us-east-1            ami-0a6a6d6f3f6b566df hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      us-west-1            ami-0ef421b6eee3b1cb0 hvm           gp2            
Fedora-AtomicHost-29-20180929.n.0.x86_64      us-west-2            ami-0eae057edad28eaa3 hvm           gp2

Fedora Cloud Base[edit]

This section is for the Fedora Cloud Base images, which can be used to run a yum/dnf based fedora in the cloud or as a VM. There are also Vagrant boxes available.

Image	Image URL	Checksum URLs
Fedora Cloud qcow2	x86_64 ppc64le aarch64	x86_64 ppc64le aarch64
Fedora Cloud raw	x86_64 ppc64le aarch64	x86_64 ppc64le aarch64
Fedora Cloud Vagrant libvirt	x86_64	x86_64
Fedora Cloud Vagrant VirtualBox	x86_64	x86_64

If you have access to an AWS account then please try out an AMI from the following list:

Fedora-Cloud-Base-29-20180929.n.0.x86_64      ap-northeast-1       ami-039571052d94f83bc hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ap-northeast-2       ami-0c3ce6ad1659393ca hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ap-south-1           ami-04e97781b365eca14 hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ap-southeast-1       ami-0df84065cbcf0c499 hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ap-southeast-2       ami-03727d60f71b9c620 hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ca-central-1         ami-0046519c130e7cab4 hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      eu-central-1         ami-06fc5f933f49cc71c hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      eu-west-1            ami-03e765be5ddd782a7 hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      eu-west-2            ami-0ac9185e81cd5da18 hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      sa-east-1            ami-06ed6ce75db482fc1 hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      us-east-1            ami-072811dd4a61fe308 hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      us-west-1            ami-0594bc15c57fbcfc6 hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      us-west-2            ami-0cc4e3f1ada9ea007 hvm           standard       
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ap-northeast-1       ami-0bb9ba285fa7bd5bc hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ap-northeast-2       ami-051afab15436a0acd hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ap-south-1           ami-0b9a97ab47c43d710 hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ap-southeast-1       ami-03c571ecbaac800c4 hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ap-southeast-2       ami-0f675861f79feb668 hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      ca-central-1         ami-0d1b8fede9940f888 hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      eu-central-1         ami-0e5767c7da1bda391 hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      eu-west-1            ami-0548c593ffe563903 hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      eu-west-2            ami-036aba1225259c3f1 hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      sa-east-1            ami-0ac4e7af3253ccf99 hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      us-east-1            ami-03196b322cb288de9 hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      us-west-1            ami-093c0c7aee2a07556 hvm           gp2            
Fedora-Cloud-Base-29-20180929.n.0.x86_64      us-west-2            ami-0016f822fb1334788 hvm           gp2

Qcow2 images[edit]

The Fedora Cloud Base image and Atomic images are also delivered as qcow2 images. You can use testcloud to locally boot and test either of these images. You can run testcloud from a git checkout, or use dnf to install it:

sudo dnf install -y testcloud

Once it's installed, you can run testcloud like so:

testcloud instance create <name of instance> -u imag.qcow2

You can also boot qcow2 images using virtualization clients like virt-manager or VirtualBox with instruction provided here

How to test?[edit]

This testday is more general, so attempt to do anything and everything with these images :) Specifically though, we'd like to take a look at the following scenarios:

Atomic:

Deploy applications on top of Atomic
Upgrades and downgrades of existing Atomic Hosts (preferably with applications running)
Package layering with on top of the base Atomic OSTree
Install Kubernetes, via ansible or kubeadm

Cloud:

Test different cloud-init configs
Deploy and run some applications in the cloud

EC2 If you have access to Amazon EC2, you can use one of the AMIs listed above for testing.

Run the tests[edit]

Visit the result 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.

This testday is also meant to be exploratory, so the list on the testday app is not at all comprehensive!

Reporting bugs[edit]

If you find anything that seems wrong or off, please report a bug on Bugzilla. The affected component should be clear from whatever error message you happen to find, but if you aren't sure, ask in IRC. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.

Test Results[edit]

Basic tests[edit]

User	Profile	Boot	Logging	Services Start	SELinux	Service Manipulation	References
garrmcnu	Atomic Host 29 20180929.n.0 Vagrant libvirt	pass	pass	pass	pass	pass
jaydeepgo	Fedora Cloud qcow2 x86_64	fail ^[1]					↑ RHBZ #1634378 Failed to create user at boot time
jlanda	Fedora-AtomicHost-ostree-x86_64-29-20180929.n.0.iso fresh install on libvirt	pass ^[1]	pass	pass	pass	pass	↑ 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	pass	pass	pass	pass	fail ^[1]	↑ sshd still enabled and running on reboot
pwhalen	Fedora-AtomicHost-ostree-aarch64-29-20180929.n.0.iso	pass	pass	pass	pass	pass
reavessm	Fedora Atomic 29	pass ^[1]	pass	pass	pass	pass	↑ 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		pass
sayanchowdhury	Fedora-Cloud-Base-29-20180929.n.0.x86_64.qcow2	pass	pass	pass pass	pass	pass
sinnykumari	Fedora-AtomicHost-29-20180929.n.0.{x86_64,ppc64le,aarch64}.{qcow2,raw} , KVM	pass	pass	pass	pass	pass
sinnykumari	Fedora-AtomicHost-ostree-{x86_64,aarch64, ppc64le}-29-20180929.n.0.iso, KVM	pass ^[1]	pass	pass	pass	pass	↑ 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[edit]

User	Profile	Atomic Boot Test	Container Storage Setup	Docker Lifecycle	Atomic Upgrade	Atomic Downgrade	rpm-ostree package layering	References
garrmcnu	Atomic Host 29 20180929.n.0 Vagrant libvirt	pass	pass	pass	pass ^[1]	pass	pass	↑ Changed URL in /etc/ostree/remotes.d/fedora-atomic.conf (as documented by others).
pwhalen	Fedora-AtomicHost-29-20180929.n.0.aarch64.raw	pass	pass	pass	pass	pass	pass
pwhalen	Fedora-AtomicHost-ostree-aarch64-29-20180929.n.0.iso	pass	pass	pass	pass	pass	pass
reavessm	Fedora Atomic 29	pass ^[1]	pass	pass	pass	fail ^[2]	pass	↑ virt-manager worked perfectly once I followed the directions correctly... ↑ file2 still existed after reboot
sinnykumari	Fedora-AtomicHost-29-20180929.n.0.{x86_64,ppc64le,aarch64}.{qcow2,raw} , KVM	pass	pass	pass	pass ^[1]	pass ^[2]	pass ^[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 ↑ 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 ↑ 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	pass	pass	pass	pass ^[1] pass	pass	pass	↑ 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[edit]

User	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)	References
sinnykumari	Fedora-AtomicHost-29-20180929.n.0		pass ^[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[edit]

User	Profile	Launch on AWS	Launch on OpenStack (requires openstack instance)	References
qba	Fedora-Cloud-Base-29-20180929.n.0.x86_64.qcow2		pass ^[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	pass
sayanchowdhury	Fedora-AtomicHost-29-20180929.n.0.x86_64, region us-east-1, standard	pass
sayanchowdhury	Fedora-Cloud-Base-29-20180929.n.0.x86_64, region us-east-1, gp2	pass
sayanchowdhury	Fedora-Cloud-Base-29-20180929.n.0.x86_64, region us-east-1, standard	pass
sinnykumari	Fedora-AtomicHost-29-20180929.n.0.x86_64, region ap-southeast-1	pass
sinnykumari	Fedora-Cloud-Base-29-20180929.n.0.x86_64, region ap-southeast-1	pass

[1] RHBZ #1634378 Failed to create user at boot time

[2] 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?

[3] sshd still enabled and running on reboot

[4] 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.

[5] 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.

[6] Changed URL in /etc/ostree/remotes.d/fedora-atomic.conf (as documented by others).

[7] virt-manager worked perfectly once I followed the directions correctly...

[8] 2 still existed after reboot

[9] 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

[10] 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

[11] 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

[12] 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

[13] * 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

[14] Using origin clients from F30 (origin-clients-3.11.0-0.alpha1.0.fc30) doesn't need workaround

[15] This issue is being tracked at https://pagure.io/atomic-wg/issue/510

[1]

[1]

[1]

[1]

[1]

[1]

[1]

[2]

[1]

[2]

[3]

[1]

[1]

[1]

Search

Test Day:2018-10-01 Cloud-Atomic Testday

Contents