From Fedora Project Wiki

(make it a bit easier!)
Line 54: Line 54:
 
* Alternatively, if using the [[Releases/Rawhide|rawhide]] live image - [[QA:Testcase_Dracut_live_image]]
 
* Alternatively, if using the [[Releases/Rawhide|rawhide]] live image - [[QA:Testcase_Dracut_live_image]]
  
=== Test Cases ===
+
=== Basic testing ===
  
The focus for the dracut test day is to exercise as many different root device partitioning schemas as possible.  The following section lists some sample scenarios and provides guidance on creating the partitioning scheme.  These tests can be performed on [[Releases/Rawhide|rawhide]], {{FedoraVersion|long|12}} Alpha, {{FedoraVersion|long|11}} or using the provided live image.  In all cases, be sure to confirm you are testing with a dracut generated initial ramdisk image.
+
To do a simple test, all you need to do is enable Dracut according to the appropriate test case above, then try and boot your system. Report your result in the results table. To find the root= parameter that was used in your test, run {{command|cat /proc/cmdline}}: it will be shown in the result, usually as the second parameter.
 +
 
 +
=== Advanced testing ===
 +
 
 +
The focus for the dracut test day is to exercise as many different root device partitioning schemas as possible, so if you are confident in your abilities to change the system's partitioning scheme, please try as many variations as possible and report each separately.  The following section lists some sample scenarios and provides guidance on creating the partitioning scheme.  These tests can be performed on [[Releases/Rawhide|rawhide]], {{FedoraVersion|long|12}} Alpha, {{FedoraVersion|long|11}} or using the provided live image.  In all cases, be sure to confirm you are testing with a dracut generated initial ramdisk image.
  
 
{| class="wikitable sortable" border="1"
 
{| class="wikitable sortable" border="1"

Revision as of 17:08, 25 August 2009

DATE TIME WHERE
Thu August 27, 2009 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-qa)

What to test?

Today's installment of Fedora Test Day will focus on the nash/mkinitrd replacement; Dracut. This page will outline several methods for enabling dracut on your system, and describe different root device storage scenarios where feedback is needed. Whether you run fedora on a laptop, or on a stateless nfs-mounted remote filesystem ... dracut will be used.

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 testing, workarounds, bug fixes, and general discussion ...

What's needed to test

  • A system with some kind of network connection
  • Your hardware profile uploaded to Smolt according to these instructions
  • An installed Fedora distribution, either:
    • Rawhide or the live CD available for this test day (see below).
    • Or an previously installed Fedora 11 system (see [Installation guide)

How to test?

Update To Rawhide

See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Alternatively, see below ...

Live Image

Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture SHA256
[FIXME i686] FIXME
[FIXME x86-64] FIXME

Test

Enable Dracut

To test dracut, you will first need to know how to enable dracut support for the distribution you are testing:

Basic testing

To do a simple test, all you need to do is enable Dracut according to the appropriate test case above, then try and boot your system. Report your result in the results table. To find the root= parameter that was used in your test, run cat /proc/cmdline: it will be shown in the result, usually as the second parameter.

Advanced testing

The focus for the dracut test day is to exercise as many different root device partitioning schemas as possible, so if you are confident in your abilities to change the system's partitioning scheme, please try as many variations as possible and report each separately. The following section lists some sample scenarios and provides guidance on creating the partitioning scheme. These tests can be performed on rawhide, Fedora 12 Alpha, Fedora 11 or using the provided live image. In all cases, be sure to confirm you are testing with a dracut generated initial ramdisk image.

Local root volume tests
Root=... Suggested test case
root=/dev/sda1 QA/TestCases/PartitioningExt4OnNativeDevice
root=LABEL=... FIXME
root=UUID=... FIXME
root=/dev/mapper/VolGroup00-LogVol00 (LVM) QA:Testcase_Anaconda_autopart_install
root=/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part1 (udev) FIXME
root=pci-0000:00:1f.2-scsi-0:0:0:0-part1 (udev) FIXME
root=/dev/dm-0 QA:Testcase_Anaconda_autopart_(encrypted)_install
root= (DMRAID) QA:Testcase_Anaconda_partitioning_dmraid_rootfs
root=/dev/md0 (RAID) QA/TestCases/PartitioningRootfsOnRaid1
root=/dev/dm-0 (encrypted LVM on RAID) QA:Testcase_anaconda_encrypted_lvm_on_raid


Network accessible root volume tests
Root=... Suggested test case
iSCSI without iBFT root on iSCSI without iBFT
iSCSI with iBFT FIXME
root on NFS FIXME
root on NBD FIXME

Report your results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component dracut. If you are unsure about exactly how to file the report, 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 your Smolt hardware profile (see above for a link with instructions on submitting your hardware profile to Smolt). The next two columns should reflect the test you performed and the result. For example, if you tested dracut support for booting a root device using the file system label, you would enter root=LABEL=foo. If any bugs are encountered, be sure to consult How_to_debug_Dracut_problems for guidance and add a link to the bug report in the References column (as in the example line).

Results

User Smolt Profile Test scenario References
jlaska HW root=/dev/md0 (RAID) [1]
  1. /dev/md127 != /dev/md0 - see RHBZ #518793