| DATE | TIME | WHERE |
| Thu Oct 8, 2009 | ALL DAY | #fedora-test-day) |
What to test?[edit]
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[edit]
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion.
- Development - Hans De Goede, Dave Lehman
- Quality Assurance - Adam Williamson, James Laska
What's needed to test[edit]
- 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?[edit]
boot.iso[edit]
See the instructions on the Rawhide page for information on downloading and booting a rawhide boot.iso. Or ...
Live Image[edit]
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.
Since this event involves testing the installer, an updates.img is provided to address bugs found during the test day. If testing on the i686 platform, type:
updates=http://people.fedoraproject.org/~jwrdegoede/raid-test-day-upd-i686.img. If testing on x86_64, type: updates=http://people.fedoraproject.org/~jwrdegoede/raid-test-day-upd-x86_64.img. Check out Anaconda/Updates for further details on using an updates.img.Test[edit]
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:
- QA:Testcase_Partitioning_RootfsOnRaid0
- QA:Testcase_Partitioning_RootfsOnRaid10
- QA:Testcase_Partitioning_RootfsOnRaid5
- QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid0Raid1
- QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid5Raid0
- QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid1Raid0
- QA:Testcase_Partitioning_Rootfs2ndVolumeRaid10Raid5
- QA:Testcase_Partitioning_Rootfs2ndVolumeRaid10Raid10
- QA:Testcase_Partitioning_RootfsOn1stVolUsrOn2ndVolRaid5Raid10
- QA:Testcase Partitioning Rootfs On RAID6
- QA:Testcase_Anaconda_partitioning_dmraid_rootfs
- QA:Testcase Partitioning LVM LV on RAID PV
- QA:Testcase_Anaconda_rescue_mode
Report your results[edit]
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).
Results[edit]
Problems identified[edit]
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 |
| User:jlaska | HW | QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid0Raid1 - crash while attempting to format existing RAID device | RHBZ #522609 |
| User:jstodola | Traceback when creating sw RAID partitions: DeviceTreeError: duplicate paths in device tree | RHBZ #527913 | |
| User:atorkhov | HW | Traceback when editing partitions: RuntimeError: Returning partitions to state prior to edit failed | RHBZ #498026 |
| User:jstodola | Traceback when creating 2 RAID devices and after that new swap partition: AttributeError: 'NoneType' object has no attribute 'disk' | RHBZ #527952 | |
| User:atorkhov | HW | Anaconda doesn't save partition binding to disk | RHBZ #527961 |
| User:atorkhov | HW | Unable clone disk for raid | RHBZ #527965 |
| User:atorkhov | HW | Device Setup Failed: device has not been created | RHBZ #527969 |
| User:jlaska | [FIXME HW] | QA:Testcase_Partitioning_Rootfs2ndVolumeRaid10Raid10 - Unable to edit existing '/' partition | RHBZ #527991 |
| User:atorkhov | HW | Rescue unable to mount system on bios raid | RHBZ #528017 |
| User:jlaska | HW | Live install failed on DMRAID system | RHBZ #528051 |
| User:Liam | HW | Asking for cache data failed on raid | RHBZ #528117 |
| User:atorkhov | HW | Traceback when creating all (except /boot) devices encrypted: DeviceTreeError: duplicate paths in device tree | RHBZ #526971 |
| Tester | Smolt Profile | Description | Bug reference(s) |
Just worked[edit]
Provide a list of tests or scenarios that behaved flawlessly.