From Fedora Project Wiki

Line 117: Line 117:
| [[User:dustymabe|dustymabe]]
| [[User:dustymabe|dustymabe]]
| Openstack Juno on F21
| Openstack Juno on F21
| {{result|pass|dustymabe}}
| {{result|pass|dustymabe}}
| {{result|pass|dustymabe}}
| {{result|pass|dustymabe}}   
| {{result|pass|dustymabe}}   

Revision as of 03:18, 8 May 2015

Fedora Test Days
Echo-testing-48px.png
Easily deploy and manage your Docker containers

Date 07 May 2015
Time all day

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


Note.png
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 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
  • A Beta RC3 image (TC1 builds failed so must use Beta RC3):
    • 64 bit qcow2 [1]
    • 64 bit raw.xz [2]

Links for "how to setup" for the Test Day

AMIs for Test Day

Region AMI name
us-east-1 ami-76cef41e
us-west-1 ami-6919fb2d
us-west-2 ami-2580aa15
eu-west-1 ami-817b1bf6
eu-central-1 ami-82c7fb9f
ap-southeast-1 ami-a6714cf4
ap-northeast-1 ami-f6a164f6
ap-southeast-2 ami-a97a0793
sa-east-1 ami-b79a1faa

How to test?

We need to test several things on the Fedora Atomic release before Fedora 22 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 beta image located here: [3]. 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

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
dustymabe Openstack Juno on F21
Pass pass dustymabe
Pass pass dustymabe
Fail fail dustymabe
[1]
Pass pass dustymabe
Pass pass dustymabe
guohua HP workstation with Fedora 22
-
-
-
-
-
maxamillion ThinkPad T440s with Fedora Rawhide (KVM)
rtnpro ThinkPad T440p with Fedora 21 (Vagrant: libvirt/KVM)
Pass pass rtnpro
Pass pass rtnpro
Pass pass rtnpro
Pass pass rtnpro
Pass pass rtnpro

Atomic Host Tests

For the Atomic Tests, download the latest image from here

User Hardware Image Boots Upgrade Works Rollback Works References
dustymabe Openstack Juno on F21
Pass pass dustymabe
Pass pass dustymabe
Pass pass dustymabe
rtnpro ThinkPad T440p with Fedora 21 (Vagrant-libvirt/KVM)
Pass pass rtnpro
Pass pass rtnpro
Pass pass rtnpro
guohua HP workstation with Fedora 22
-
-
-
maxamillion ThinkPad T440s with Fedora Rawhide (KVM)
mmicene Dell Latitude E6440 with Fedora 21 KVM
Pass pass mmicene
Pass pass mmicene
Pass pass mmicene
oystercatcher Intel dual core desktop fc22 kvm
Pass pass oystercatcher
Pass pass oystercatcher
Pass pass oystercatcher
royboy626 ...Atomic-20141203-21 on Fedora 21
Pass pass royboy626
[1]
Pass pass royboy626
[2]
Pass pass royboy626
  1. See references Atomic Docker Tests
  2. All listed User Roshi tests passed

Atomic Docker Tests

For the Atomic Tests, download the latest image from here

User Hardware docker-storage-setup Docker Lifecycle Docker Image Test References
dustymabe Openstack Juno on F21
Pass pass dustymabe
Warning warn dustymabe
[1]
Pass pass dustymabe
maxamillion ThinkPad T440s with Fedora Rawhide (KVM)
mmicene Dell Latitude E6440 with Fedora 21 KVM
Pass pass mmicene
Pass pass mmicene
Pass pass mmicene
oystercatcher Intel dual core desktop fc22 kvm
Pass pass oystercatcher
Pass pass oystercatcher
Pass pass oystercatcher
rtnpro ThinkPad T440p with Fedora 21 (Vagrant-libvirt/KVM)
Pass pass rtnpro
Pass pass rtnpro
Pass pass rtnpro
royboy626 ...Atomic-20141203-21 on Fedora 21
Pass pass royboy626
[1]
Pass pass royboy626
[2]
Pass pass royboy626
  1. Got here too early, downloaded file was 20141203-21
  2. SeLinux caused virt net problem. is preventing /usr/bin/qemu-system-x86_64 from using the execmem \ Boot base metal host with selinux=0 on linux line cured.

Bugs filled during Test Day (7th May 2015)

BZ#1219700

Other Common Bugs

  • BZ#1216151
  • BZ#1205454 Workaround: Use "docker run -it --rm busybox sleep 15" or another longer running command instead of "docker run -it --rm busybox true" for testing

Long comments