From Fedora Project Wiki
Fedora Test Days
Easily deploy and manage your Docker containers

Date 22 Sep 2015
Time all day

Website QA/Fedora_23_test_days
IRC #atomic (webirc)
Mailing list cloud


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?

Today's installment of Fedora Test Day will focus on Fedora Atomic

Who's available

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

Prerequisite for Test Day

You'll need to either have an AWS account or a system that's capable of running one of the Atomic images for KVM/OpenStack.

  • OpenStack installation [outside the scope of test day to set up!]
  • Virt-Manager or KVM setup to run the qcow2 image.
  • Run testcloud locally

We need to add links to images here.

Links for "how to setup" for the Test Day

How to test?

We need to test several things on the Fedora Atomic release before Fedora 23 Final.

  • Test with a variety of Docker images. We do want to test the Fedora images in particular, but also we need to test a wide variety of images to see if there are any hidden bugs or problems we might not have noticed yet.
  • Test Cockpit to make sure that managing Docker images and connecting multiple hosts works.
  • Try out Kubernetes and make sure those packages are working.
  • Test out the rpm-ostree/atomic update/rollback commands and other functions.
  • Try out docker-storage-config.
  • What is the image/package set missing? What is unnecessary?

Grab the Image

Update the image links here

To test Fedora Atomic, we're going to use a beta image located here: [1].

Test Cases

Fedora Cloud Working Group member Dusty Mabe has quite a few tests on this Gist. For other examples, see Category:Test_Cases.

For better worded test steps please refer to Mike's pages: User:Roshi/QA/AtomicTests

Additionally, many of the tests that are written for Cloud Base also apply to atomic. The tests are located here. If you don't know if the test applies to Atomic or not then feel free to ask in #fedora-cloud on freenode.

Test Results

If you are unsure about exactly how to file a bug report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the appropriate table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.


Atomic Basic Cloud Tests

User Hardware Startup System Logging Services Start SELinux Service Manipulation References
Example User Example Hardware
Pass pass username
Warning warn username
Fail fail username [1]
none
none
  1. RHBZ #12345
maxamillion ThinkPad T440s running testcloud from git checkout (master@9da7bf08c)
Pass pass username
Fail fail dustymabe [1]
  1. RHBZ #1265295

Atomic Host Tests DO NOT EXECUTE THESE TESTS - NO UPDATE TREES ARE AVAILABLE

For the Atomic Tests, download the latest image from and execute tests

User Hardware Image Boots Upgrade Works Rollback Works References
Example Example Hardware
Pass pass username
Warning warn username
Fail fail username [1]
  1. RHBZ #12345

Atomic Docker Tests

For the Atomic Tests, download the latest image from and execute tests

User Hardware docker-storage-setup Docker Lifecycle Docker Image Test References
Example Username Example hardware
Pass pass username
Warning warn username
Fail fail username [1]
  1. RHBZ #12345
maxamillion ThinkPad T440s running testcloud from git checkout (master@9da7bf08c)

Bugs filled during Test Day (22nd September 2015)

Other Common Bugs

Long comments