From Fedora Project Wiki
(Added networking stuff)
No edit summary
Line 45: Line 45:
* Log in as 'ec2-user' using the ssh key you specified on launch
* Log in as 'ec2-user' using the ssh key you specified on launch
* 'sudo su' (this should work without requiring a root password)
* 'sudo su' (this should work without requiring a root password)
* Ensure that SELinux is enabled and functional?
* Ensure that SELinux is enabled and functional
* Ensure that your instance has network connectivity:
* Ensure that your instance has network connectivity:
** Check if your DNS is resolving: {{command| nslookup fedoraproject.org}}
** Check if your DNS is resolving: {{command| nslookup fedoraproject.org}}

Revision as of 10:46, 2 July 2011

Cloud SIG EC2 Image Fedora Test Day
Echo-testing-48px.png
Fedora EC2

Date YYYY-MM-DD
Time all day

Website Cloud SIG
IRC #fedora-test-day (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 EC2 Images

Who's available

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


Prerequisite for Test Day

  • Free time
  • An Amazon EC2 account
  • Internet connectivity for connecting to EC2 images.
  • Standard Fedora repositories must be available.

How to test?

Test Day EC2 Images

Fedora EC2 images for test day are publicly accessible, but not broadly advertised. To launch an instance, log into the AWS Management Console.

  • Choose the EC2 tab.
  • In the left pane, select the US-East-1 region.
  • In the main window, select launch instance.
  • Click on the "Community AMIs" tab.
  • Enter one of the ami IDs below into the text box and follow the prompts to launch the image:
    • Fedora 16 x86_64: FIXME: AMI ID
    • Fedora 16 i386: FIXME: AMI ID

Testing the Images

  • Launch one of the mentioned AMIs on EC2.
  • Log in as 'ec2-user' using the ssh key you specified on launch
  • 'sudo su' (this should work without requiring a root password)
  • Ensure that SELinux is enabled and functional
  • Ensure that your instance has network connectivity:
    • Check if your DNS is resolving: nslookup fedoraproject.org
    • Check the network settings: ifconfig and ping -c 4 fedoraproject.org
  • Run the test-cases.

Test Cases

Test Results

If you have problems with any of the tests, report a bug to Bugzilla.

Need help?

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, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.

Things that work

Use the following table to record tests successfully completed.

Tester Test Performed / Description Result References
Sample User QA:Testcase_Yum_basics
Pass pass
Sample User QA:Testcase_rsyslog
Pass pass
Sample User QA:Testcase_OpenSSH
Pass pass

Problems Identified

Use the following table to record tests that highlight defects or otherwise inconsistent behaviours.

Tester Test Performed / Description Result References
Sample User QA:Testcase_Yum_basics
Pass pass
Sample User QA:Testcase_rsyslog
Pass pass
Sample User QA:Testcase_OpenSSH
Pass pass