From Fedora Project Wiki

m (Added dlehman)
(Add boot.iso step)
Line 27: Line 27:
== How to test? ==
== How to test? ==
=== '''Update your machine''' ===
=== {{filename|boot.iso}} ===
See the instructions on the [[Releases/Rawhide#Direct_daily_Rawhide_install|Rawhide]] page for information on downloading and booting a rawhide {{filename|boot.iso}}.  Or ...
See the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
=== '''Live Image''' ===
=== '''Live Image''' ===

Revision as of 15:04, 7 October 2009

Thu Oct 8, 2009 ALL DAY #fedora-test-day)

What to test?

Today's instalment of Fedora Test Day will focus on all types of RAID. This mainly includes installing to systems using mdraid, dmraid and hardware raid. Even if not installing the system, but you still would like to test post-installed RAID operations, you are invited to share your findings below.

If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test with your system and provide feedback.

Who's available

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

What's needed to test

  • Ability to implement some kind of RAID array (software or BIOS or hardware)
  • Rawhide (tips on installing Rawhide below), or the live CD available for this test day (again see below).
  • Your hardware profile uploaded to Smolt according to these instructions

How to test?


See the instructions on the Rawhide page for information on downloading and booting a rawhide boot.iso. Or ...

Live Image

If you do not want to use an installed Rawhide system to test, you can use the latest Rawhide nightly live CD. This will only allow you to test use of RAID arrays from a running system, not creation and use of RAID arrays during installation. Tips on using a live image are available at FedoraLiveCD.


Follow any of these test cases which you are able to implement. You do not need to test them all if you do not have time or capability:

Report your results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component anaconda. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Follow the instructions on this page to ensure you include sufficient information in the report.

Once you have completed the tests, add your results to the Results tables below, following the example results below 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 your Smolt hardware profile (see above for a link with instructions on submitting your hardware profile to Smolt). For each test case, if your system worked correctly, tell us what worked by adding a description of your test scenario to the Just worked table. If you had trouble, add your findings to the Problems identified table. Please add a short description of the failure and include a link to the bug report (as in the example line).


Problems identified

Using your own test scenario, or any of the test cases listed above, please outline problems/failures you encounter using the table below.

Tester Smolt Profile Description Bug reference(s)
User:jlaska HW Live install failed during partitioning -- AttributeError: 'NoneType' object has no attribute 'path' RHBZ #517260
Tester Smolt Profile Description Bug reference(s)

Just worked

Provide a list of tests or scenarios that behaved flawlessly.

Tester Smolt Profile Description
User:jlaska HW iSCSI (no iBFT) still works!
Tester Smolt Profile Description