From Fedora Project Wiki

Revision as of 19:36, 26 June 2015 by Adamwill (talk | contribs) (Drop direct Test Days category membership)

Fedora Test Days
Easily deploy and manage your Docker containers

Date 20 November 2014
Time all day

Website QA/Fedora_21_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 instalment of Fedora Test Day will focus on Fedora Atomic Host

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
  • An updated test image, or later nightly live image if one is released before 20 November.

Links for "how to setup" for the Test Day

AMIs for Test Day

Region AMI name
us-east-1 ami-a8c95dc0
us-west-1 ami-879187c2
us-west-2 ami-f7256fc7
eu-west-1 ami-7ec97e09
eu-central-1 ami-6072437d
ap-southeast-1 ami-9c6547ce
ap-northeast-1 ami-4d655e4c
ap-southeast-2 ami-4f3c5275
sa-east-1 ami-676ddb7a

How to test?

We need to test several things on the Fedora Atomic release before Fedora 21 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

To test Fedora Atomic, we're going to use a Koji build located here: [1]. You can also use one of the AMIs if you would prefer to do your testing on Amazon Web Services.

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

Test Results

Atomic Tests

User Hardware Image Boots Upgrade Works Rollback Works References
larsks openstack
Pass pass
Pass pass
Pass pass
ssamanta testvm1
Pass pass
Anil Virt-Manager
Pass pass
Pass pass
Pass pass
Pass pass
amrithajij KVM
Warning warn
[long 1]
Pass pass
Pass pass
lnie KVM
Pass pass
Pass pass
roshi KVM
Pass pass
Pass pass
Pass pass
sinnykumari KVM
Warning warn
[long 2]
sten openstack RHOSP5 x64
Pass pass
Pass pass
Pass pass
jzb KVM
Pass pass
[1]
Pass pass
[2]
Pass pass
  1. Yup. Happy result there.
  2. atomic upgrade worked a treat. All happy.
jkalliyat KVM
Warning warn
[1]
  1. Executed the 'runcmd' manually to make it work.
dustymabe Openstack Juno on F21
Pass pass
Pass pass
Pass pass
Prasanth VM on KVM
Warning warn
[1]
Pass pass
  1. Executed the 'runcmd' manually to make it work.
lalatendu VM on virt-manager
Pass pass
[1]
Pass pass
Pass pass
  1. runcmd issue

Docker Tests

User Hardware docker-storage-setup Docker Lifecycle References
larsks openstack
Pass pass
[1]
Pass pass
[2]
  1. Appears to have run automatically (and successfully).
  2. Started/interacted with/stopped fedora and ubuntu containers.
amrithajij KVM
Warning warn
[1]
Pass pass
  1. Manually expanded the qcow2 image fron host and then ran journalctl -o cat --unit docker-storage-setup.service.
roshi KVM
Pass pass
Pass pass
sinnykumari KVM
Warning warn
[1]
sten openstack RHOSP5 x64
Pass pass
Pass pass [1]

That confused me, but just using "sudo docker foo" works. </ref>

  1. RHBZ #1164058
jzb KVM
Pass pass
[1]
Pass pass
[2]
  1. Works a treat.
  2. All good here.
dustymabe Openstack Juno on F21
Pass pass
Pass pass
lalatendu VM on virt-manager
Pass pass

</ref>

Pass pass
nkhare vm
Pass pass

Bugs filled during Test Day (20th Nov 2014)

1166073 1166082

Other Common Bugs

1164058

Long comments

  1. All works well except the command - [ sh, -c, 'echo -e "ROOT_SIZE=4G DATA_SIZE=10G" > /etc/sysconfig/docker-storage-setup'] . Thus created the file manually and added ROOT_SIZE=4G DATA_SIZE=10G.
  2. I tried test mentioned on roshi page . Everything worked well but "runcmd: - [ sh, -c, 'echo -e "ROOT_SIZE=4G DATA_SIZE=10G" > /etc/sysconfig/docker-storage-setup']" didn't run for me. So, added "ROOT_SIZE=4G DATA_SIZE=10G" content in etc/sysconfig/docker-storage-setup file manually.