From Fedora Project Wiki

No edit summary
m (internal link cleaning)
 
(30 intermediate revisions by 12 users not shown)
Line 1: Line 1:
{{Infobox_group
{{Infobox_group
| name = Fedora Test Days
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_21_test_days]]
| caption = [[FIXME|FIXME]]
| caption = Easily deploy and manage your Docker containers
| date = <<FIXME>>
| date = 20 November 2014
| time = all day
| time = all day
| website = [[QA/Fedora_19_test_days]]
| website = [[QA/Fedora_21_test_days]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| irc = [irc://irc.freenode.net/#atomic #atomic] ([http://webchat.freenode.net/?channels=atomic webirc])
| fedora_mailing_list = test
| fedora_mailing_list = cloud
}}
}}


Line 14: Line 14:
== What to test? ==
== What to test? ==


Today's instalment of Fedora Test Day will focus on '''<<FIXME>>'''
Today's instalment of Fedora Test Day will focus on '''Fedora Atomic Host'''


== Who's available ==
== Who's available ==


The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
* Cloud SIG - [[User:Jzb|Joe Brockmeier]] (jzb), [[user:mattdm|Matthew Miller]] (mattdm), [[user:dustymabe|Dusty Mabe]] (dustymabe), [[User:kilted1|Scott Suehle]] (kilted1)
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
* Quality Assurance - [[User:Roshi|Roshi]] (roshi)
* Just a user - [[User:Znmeb|Ed Borasky]] (znmeb^)


== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  


List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
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.


* Usb key
* OpenStack installation [outside the scope of test day to set up!]
* Usb externally connected HD IDE/SATA
* Virt-Manager or KVM setup to run the qcow2 image.
* Empty HD IDE/SATA/SCSI
* Run [http://github.com/Rorosha/testCloud testCloud] locally
* Free space on HD


Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
* An updated [https://kojipkgs.fedoraproject.org//work/tasks/8904/8118904/Fedora-Cloud-Atomic-20141112-21.x86_64.qcow2 test image], or later nightly live image if one is released before 20 November.


* An updated [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
== Links for "how to setup" for the Test Day ==


== How to test? ==
* Refer [http://www.projectatomic.io/docs/quickstart/ quickstart guide] for setup Atomic with Virt-manager or KVM
* Don't know how to create cloud init iso? refer [https://www.technovelty.org//linux/running-cloud-images-locally.html running-cloud-images-locally]
 
== AMIs for Test Day ==


High level details on how a contributor can get involved.  This can include (but not limited to):


* Areas to target with exploratory testing
{| class="wikitable"
* A list of pre-defined test cases to execute
!Region
* How to report back results
!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
|}


Here's another common chunk (again, replace XX as above):
== How to test? ==


=== '''Update your machine''' ===
We need to test several things on the Fedora Atomic release before Fedora 21 Final.


If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
* 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?


=== '''Live image''' ===
=== '''Grab the Image''' ===


Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
To test Fedora Atomic, we're going to use a Koji build located here: [https://kojipkgs.fedoraproject.org//work/tasks/8904/8118904/Fedora-Cloud-Atomic-20141112-21.x86_64.qcow2]. You can also use one of the AMIs if you would prefer to do your testing on Amazon Web Services.


== Test Cases ==
== Test Cases ==


Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see [[:Category:Test_Cases]].
Fedora Cloud Working Group member Dusty Mabe has [https://gist.github.com/dustymabe/bf955b6afa8177ecf6fc 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 ==
== Test Results ==


Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
=== Atomic Tests ===


If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. 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. Once you have completed the tests, add your results to the Results 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 [[Template:result|result template]] to enter your result, as shown in the example result line.
{|
! User
! Hardware
! [[User:Roshi/QA/AtomicTests/Atomic_Image_Boots|Image Boots]]
! [[User:Roshi/QA/AtomicTests/Atomic_Upgrade|Upgrade Works]]
! [[User:Roshi/QA/AtomicTests/Atomic_Rollback|Rollback Works]]
! References
|-
| [[User:larsks|larsks]]
| openstack
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:ssamanta|ssamanta]]
| testvm1
| {{result|pass}} 
|
|
| <references/>
|-
| [[User:Anil|Anil]]
| Virt-Manager
| {{result|pass}}  {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:amrithajij|amrithajij]]
| KVM
| {{result|warn}}  <ref group="long">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.</ref>
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:lnie|lnie]]
| KVM
| {{result|pass}} 
| {{result|pass}} 
|
| <references/>
|-
| [[User:roshi|roshi]]
| KVM
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:sinnykumari|sinnykumari]]
| KVM
| {{result|warn}}  <ref group="long">I tried test mentioned on [[User:Roshi/QA/AtomicTests/Atomic_Image_Boots|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.</ref>
|
|
| <references/>
|-
| [[User:sten|sten]]
| openstack RHOSP5 x64
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:jzb|jzb]]
| KVM
| {{result|pass}}  <ref>Yup. Happy result there.</ref>
| {{result|pass}}  <ref>atomic upgrade worked a treat. All happy.</ref>
| {{result|pass}} 
| <references/>
|-
| [[User:jkalliyat|jkalliyat]]
| KVM
| {{result|warn}}  <ref>Executed the 'runcmd' manually to make it work. </ref>
|
|
| <references/>
|-
| [[User:dustymabe|dustymabe]]
| Openstack Juno on F21
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:Prasanth|Prasanth]]
| VM on KVM
| {{result|warn}}  <ref>Executed the 'runcmd' manually to make it work.</ref>
| {{result|pass}} 
|
| <references/>
|-
| [[User:lalatendu|lalatendu]]
| VM on virt-manager
| {{result|pass}}  <ref>runcmd issue</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
|}
 
=== Docker Tests ===


{|
{|
! User
! User
! [[QA:Testcase_sample_1|Sample test 1]]
! Hardware
! [[QA:Testcase_sample_2|Sample test 2]]
! [[User:Roshi/QA/AtomicTests/Atomic_Docker_Storage_Setup|docker-storage-setup]]
! [[QA:Testcase_sample_3|Sample test 3]]
! [[User:Roshi/QA/AtomicTests/Atomic_Docker_Lifecycle|Docker Lifecycle]]
! [[QA:Testcase_sample_4|Sample test 4]]
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:larsks|larsks]]
| {{result|none}}  
| openstack
| {{result|pass}}  <ref>Appears to have run automatically (and successfully).</ref>
| {{result|pass}}  <ref>Started/interacted with/stopped fedora and ubuntu containers.</ref>
| <references/>
|-
| [[User:amrithajij|amrithajij]]
| KVM
| {{result|warn}}  <ref>Manually expanded the qcow2 image fron host and then ran journalctl -o cat --unit docker-storage-setup.service.</ref>
| {{result|pass}} 
| <references/>
|-
| [[User:roshi|roshi]]
| KVM
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:sinnykumari|sinnykumari]]
| KVM
| {{result|warn}} <ref>In test case https://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Docker_Storage_Setup
 
changes get reflected after rebooting VM</ref>
|
| <references/>
|-
| [[User:sten|sten]]
| openstack RHOSP5 x64
| {{result|pass}} 
| {{result|pass||1164058}}
 
That confused me, but just using "sudo docker foo" works. </ref>
| <references/>
|-
| [[User:jzb|jzb]]
| KVM
| {{result|pass}}  <ref>Works a treat.</ref>
| {{result|pass}}  <ref>All good here.</ref>
| <references/>
|-
| [[User:dustymabe|dustymabe]]
| Openstack Juno on F21
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:lalatendu|lalatendu]]
| VM on virt-manager
| {{result|pass}}
</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| <references/>
| {{result|fail}} <ref>{{bz|12345}}</ref>
|-
| [[User:nkhare|nkhare]]
| vm
|  
| {{result|pass}}
| <references/>
| <references/>
|-
|-
|}
|}
=== Bugs filled during Test Day (20th Nov 2014) ===
[https://bugzilla.redhat.com/show_bug.cgi?id=1166073 1166073]
[https://bugzilla.redhat.com/show_bug.cgi?id=1166082 1166082]
=== Other Common Bugs ===
[https://bugzilla.redhat.com/show_bug.cgi?id=1164058 1164058]
== Long comments ==
<references group="long" />


[[Category:Fedora 21 Test Days]]
[[Category:Fedora 21 Test Days]]

Latest revision as of 21:42, 19 September 2016

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

Today's instalment of Fedora Test Day will focus on Fedora Atomic Host

Who's available[edit]

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

Prerequisite for Test Day[edit]

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

AMIs for Test Day[edit]

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

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

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

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

Atomic Tests[edit]

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

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)[edit]

1166073 1166082

Other Common Bugs[edit]

1164058

Long comments[edit]

  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.