From Fedora Project Wiki

(Test)
(Drop direct Test Days category membership)
 
(51 intermediate revisions by 10 users not shown)
Line 3: Line 3:
 
| DATE || TIME || WHERE
 
| DATE || TIME || WHERE
 
|-
 
|-
| Thu Sep 10, 2009 || ALL DAY || [irc://irc.freenode.net/fedora-test-day #fedora-test-day])
+
| Thu Oct 8, 2009 || ALL DAY || [irc://irc.freenode.net/fedora-test-day #fedora-test-day])
 
|-
 
|-
 
|}
 
|}
Line 9: Line 9:
 
== What to test? ==
 
== What to test? ==
  
Today's instalment of Fedora Test Day will focus on the MDraid
+
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 ==
 
== Who's available ==
  
 
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion.
 
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion.
* Development - [[HansdeGoede | Hans De Goede]]
+
* Development - [[HansdeGoede|Hans De Goede]], [[User:dlehman|Dave Lehman]]
* Quality Assurance - [[User:Adamwill|Adam Williamson]]
+
* Quality Assurance - [[User:Adamwill|Adam Williamson]], [[User:jlaska|James Laska]]
  
 
== What's needed to test ==
 
== What's needed to test ==
  
* MDRaid
+
* Ability to implement some kind of RAID array (software or BIOS or hardware)
 
* [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or the live CD available for this test day (again see below).
 
* [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or the live CD available for this test day (again see below).
 
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
 
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
* Make sure to back up your existing ''xorg.conf'' file, if you have one, so you can recover if the nouveau driver causes you trouble
 
  
 
== 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''' ===
  
If you do not want to use an installed Rawhide system to test, you can use the latest [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ Rawhide nightly live CD]. Tips on using a live image are available at [[FedoraLiveCD]].
+
If you do not want to use an installed Rawhide system to test, you can use the latest [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ 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]].
 
 
{{admon/warning | Live USB label bug | If you put the image on a USB stick, boot will likely fail with the message ''No root device found. Boot has failed, sleeping forever.'' In this case, use the command {{command|/sbin/dosfslabel}} (if your USB stick is FAT32-formatted) or {{command|/sbin/e2label}} (ext2/3/4-formatted) to find the label for the USB stick. When booting, hit tab twice at the Fedora boot screen to edit the kernel boot parameters, and change the ''root<nowiki>=</nowiki>'' section to read ''root<nowiki>=</nowiki>live:LABEL<nowiki>=</nowiki>(label)'', where (label) is the label you found.  In some cases, you may simply need to use the label provided by ''udev'', so if your key normally mounts as {{filename|/media/KINGSTON}}, for example, use ''KINGSTON'' as the label.}}
 
  
{{admon/note | If you have a slightly older Test Day Live image | This tip may be useful if you have a very recent Live image from a previous test day.
+
{{admon/note|Got updates?|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: <code>updates{{=}}http://people.fedoraproject.org/~jwrdegoede/raid-test-day-upd-i686.img</code>.  If testing on x86_64, type: <code>updates{{=}}http://people.fedoraproject.org/~jwrdegoede/raid-test-day-upd-x86_64.img</code>.  Check out [[Anaconda/Updates]] for further details on using an updates.img.}}
  
If you are a Fedora account holder, you can use <code>rsync</code> over SSH to update your existing ISO image in just a few minutes.  First, <code>cd</code> to the directory containing your existing ISO image file.  Then change its file name to {{filename|testday-20090909-(arch).iso}} and run this command:
 
<pre>rsync -Pv fedorapeople.org:/home/fedora/adamwill/public_html/20090909_test_day_images/testday-20090909-(arch).iso .</pre>}}
 
 
=== Test ===
 
=== Test ===
  
Follow each of these test cases:  
+
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_RootfsOnRaid0]]
* [[QQA:Testcase_Partitioning_RootfsOnRaid10]]
+
* [[QA:Testcase_Partitioning_RootfsOnRaid10]]
 
* [[QA:Testcase_Partitioning_RootfsOnRaid5]]
 
* [[QA:Testcase_Partitioning_RootfsOnRaid5]]
 
* [[QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid0Raid1]]
 
* [[QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid0Raid1]]
Line 52: Line 50:
 
* [[QA:Testcase_Partitioning_Rootfs2ndVolumeRaid10Raid10]]
 
* [[QA:Testcase_Partitioning_Rootfs2ndVolumeRaid10Raid10]]
 
* [[QA:Testcase_Partitioning_RootfsOn1stVolUsrOn2ndVolRaid5Raid10]]
 
* [[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 ===
 
=== Report your results ===
  
If you have problems with any of the tests, report a bug to [http://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=xorg-x11-drv-nouveau xorg-x11-drv-nouveau]. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Follow the instructions on [[Xorg/Debugging|this page]] to ensure you include sufficient information in the report. Once you have completed the tests, add your results to the Results table below, following the example results from Adam Williamson 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, simply enter the word '''PASS'''. If you had trouble, enter the word '''FAIL''', with a footnote indicator, and put a link to the bug report in the comments column (as in the example line). If you could not perform one test (for example, you cannot perform the more advanced tests because the basic one fails, or you cannot perform the multihead test as you have only one display), enter the word '''N/A'''. In the comments column, you can enter the model name and PCI device ID (vendor ID is usually 10DE) of your card, if you know it - you can usually find this information in the output of the command <tt>lspci -nn</tt>.
+
If you have problems with any of the tests, report a bug to [http://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=anaconda 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 [[How to debug installation problems|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 ==
 
== Results ==
 +
 +
=== 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.
 +
 +
{| class="wikitable sortable" border="1"
 +
! Tester !! Smolt Profile !! Description !! Bug reference(s)
 +
|-
 +
| [[User:jlaska]]
 +
| [http://www.smolts.org/client/show/pub_4ec1ae45-ba96-49cb-8e2b-2b4e9e71b3ee HW]
 +
| Live install failed during partitioning -- ''AttributeError: 'NoneType' object has no attribute 'path' ''
 +
| {{bz|517260}}
 +
|-
 +
| [[User:jlaska]]
 +
| [http://www.smolts.org/client/show/pub_4ec1ae45-ba96-49cb-8e2b-2b4e9e71b3ee HW]
 +
| [[QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid0Raid1]] - crash while attempting to format existing RAID device
 +
| {{bz|522609}}
 +
|-
 +
| [[User:jstodola]]
 +
|
 +
| Traceback when creating sw RAID partitions: DeviceTreeError: duplicate paths in device tree
 +
| {{bz|527913}}
 +
|-
 +
| [[User:atorkhov]]
 +
| [http://www.smolts.org/client/show/pub_b0a7dc0f-e849-406e-985c-b9d37b019d6b HW]
 +
| Traceback when editing partitions: RuntimeError: Returning partitions to state prior to edit failed
 +
| {{bz|498026}}
 +
|-
 +
| [[User:jstodola]]
 +
|
 +
| Traceback when creating 2 RAID devices and after that new swap partition: AttributeError: 'NoneType' object has no attribute 'disk'
 +
| {{bz|527952}}
 +
|-
 +
| [[User:atorkhov]]
 +
| [http://www.smolts.org/client/show/pub_b0a7dc0f-e849-406e-985c-b9d37b019d6b HW]
 +
| Anaconda doesn't save partition binding to disk
 +
| {{bz|527961}}
 +
|-
 +
| [[User:atorkhov]]
 +
| [http://www.smolts.org/client/show/pub_b0a7dc0f-e849-406e-985c-b9d37b019d6b HW]
 +
| Unable clone disk for raid
 +
| {{bz|527965}}
 +
|-
 +
| [[User:atorkhov]]
 +
| [http://www.smolts.org/client/show/pub_b0a7dc0f-e849-406e-985c-b9d37b019d6b HW]
 +
| Device Setup Failed: device has not been created
 +
| {{bz|527969}}
 +
|-
 +
| [[User:jlaska]]
 +
| [FIXME HW]
 +
| [[QA:Testcase_Partitioning_Rootfs2ndVolumeRaid10Raid10]] - Unable to edit existing '/' partition
 +
| {{bz|527991}}
 +
|-
 +
| [[User:atorkhov]]
 +
| [http://www.smolts.org/client/show/pub_b64aebbc-02c4-4ad0-a04f-c7b01418d1de HW]
 +
| Rescue unable to mount system on bios raid
 +
| {{bz|528017}}
 +
|-
 +
| [[User:jlaska]]
 +
| [http://www.smolts.org/client/show/pub_4f59d92c-ce00-40e8-8a35-810ac9ae154e HW]
 +
| Live install failed on DMRAID system
 +
| {{bz|528051}}
 +
|-
 +
| [[User:Liam]]
 +
| [http://www.smolts.org/client/show/pub_9a103990-2dba-414f-adb6-d0cb1425d02f HW]
 +
| Asking for cache data failed on raid
 +
| {{bz|528117}}
 +
|-
 +
| [[User:atorkhov]]
 +
| [http://www.smolts.org/client/show/pub_b0a7dc0f-e849-406e-985c-b9d37b019d6b HW]
 +
| Traceback when creating all (except /boot) devices encrypted: DeviceTreeError: duplicate paths in device tree
 +
| {{bz|526971}}
 +
|-
 +
| <!-- [[User:FasUser]] -->
 +
| <!-- [SMOLT-LINK HW]  -->
 +
| <!-- description -->
 +
| <!-- {{bz|1234}} -->
 +
|-
 +
! Tester !! Smolt Profile !! Description !! Bug reference(s)
 +
|-
 +
|}
 +
 +
=== Just worked ===
 +
 +
Provide a list of tests or scenarios that behaved flawlessly.
 +
 +
{| class="wikitable sortable" border="1"
 +
! Tester !! Smolt Profile !! Description
 +
|-
 +
| [[User:jlaska]]
 +
| [http://www.smolts.org/client/show/pub_4ec1ae45-ba96-49cb-8e2b-2b4e9e71b3ee HW]
 +
| iSCSI (no iBFT) still works!
 +
|-
 +
| [[User:atodorov]]
 +
| [http://www.smolts.org/client/show/pub_ee39c890-e2c9-4d07-a5ae-5cd90db9d8d8 HW]
 +
| [[QA:Testcase_Partitioning_RootfsOnRaid0|rootfs on RAID0]]
 +
|-
 +
| [[User:atodorov]]
 +
| [http://www.smolts.org/client/show/pub_dae81bbc-e94a-46ac-8f9a-73ac62dd8ca8 HW]
 +
| [[QA:Testcase_Partitioning_RootfsOnRaid10|rootfs on RAID10]]
 +
|-
 +
| [[User:atodorov]]
 +
| [http://www.smolts.org/client/show/pub_3757a9fa-6e8b-48fa-8642-82207b50e20c HW]
 +
| [[QA:Testcase_Partitioning_RootfsOnRaid5|rootfs on RAID5]]
 +
|-
 +
| [[User:atodorov]]
 +
| [http://www.smolts.org/client/show/pub_18096e4b-a7ba-490d-ad61-9021904297a0 HW]
 +
| [[QA:Testcase_Partitioning_Rootfs_On_RAID6|rootfs on RAID6]]
 +
|-
 +
| [[User:mbanas]]
 +
| [http://www.smolts.org/client/show/pub_ece3c224-4739-4434-b2eb-758321d883be HW]
 +
| [[QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid5Raid0|RootfsOn2ndVolumeRaid5Raid0]], installed without swap partition because of bug 523754
 +
|-
 +
| [[User:mbanas]]
 +
| [http://www.smolts.org/client/show/pub_c1dc969b-c16f-4dfa-8a16-7b782e5fe762 HW]
 +
| [[QA:Testcase_Partitioning_RootfsOn1stVolUsrOn2ndVolRaid5Raid10|RootfsOn1stVolUsrOn2ndVolRaid5Raid10]], installed without swap partition because of bug 523754
 +
|-
 +
| [[User:jlaska]]
 +
| <!-- [SMOLT-LINK HW]  -->
 +
| iSCSI + iBFT detected local and remote volumes ... and formatted successfully
 +
|-
 +
| [[User:mbanas]]
 +
| Virtualbox 3.0.6
 +
| [[QA:Testcase_Partitioning_LVM_LV_on_RAID_PV|LVM_LV_on_RAID_PV]]
 +
|-
 +
| [[User:mbanas]]
 +
| [http://www.smolts.org/client/show/pub_411414ab-a978-46f3-8c6c-fff300dad7d9 HW]
 +
| [[QA:Testcase_Partitioning_Rootfs_On_RAID6|Rootfs_On_RAID6]]
 +
|-
 +
| [[User:mbanas]]
 +
| kvm i386
 +
| [[QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid1Raid0|RootfsOn2ndVolumeRaid1Raid0]]
 +
|-
 +
| [[User:jlaska]]
 +
| [http://www.smolts.org/client/show/pub_4f59d92c-ce00-40e8-8a35-810ac9ae154e HW]
 +
| [[QA:Testcase_Partitioning_Rootfs2ndVolumeRaid10Raid10]] (with dmraid+ encryption!)
 +
|-
 +
| [[User:jlaska]]
 +
| [http://www.smolts.org/client/show/pub_4f59d92c-ce00-40e8-8a35-810ac9ae154e HW]
 +
| [[QA:Testcase_Anaconda_partitioning_dmraid_rootfs]]
 +
|-
 +
| [[User:Liam]]
 +
| [http://www.smolts.org/client/show/pub_9a103990-2dba-414f-adb6-d0cb1425d02f HW]
 +
| [[QA:Testcase_Partitioning_RootfsOnRaid0]]
 +
|-
 +
| [[User:Liam]]
 +
| [http://www.smolts.org/client/show/pub_9a103990-2dba-414f-adb6-d0cb1425d02f HW]
 +
| [[QA:Testcase_Partitioning_RootfsOnRaid5]]
 +
|-
 +
| [[User:Liam]]
 +
| [http://www.smolts.org/client/show/pub_9a103990-2dba-414f-adb6-d0cb1425d02f HW]
 +
| [[QA:Testcase_Anaconda_rescue_mode]]
 +
|-
 +
| [[User:jkoten]]
 +
| KVM x86_64
 +
| [[QA:Testcase_Partitioning_RootfsOnRaid0]]
 +
|-
 +
| [[User:jkoten]]
 +
| KVM x86_64
 +
| [[QA:Testcase_Partitioning_RootfsOnRaid10]]
 +
|-
 +
| [[User:jkoten]]
 +
| KVM x86_64
 +
| [[QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid0Raid1]]
 +
|-
 +
| [[User:jkoten]]
 +
| KVM x86_64
 +
| [[QA:Testcase_Anaconda_rescue_mode]]
 +
|-
 +
| <!-- [[User:FasUser]] -->
 +
| <!-- [SMOLT-LINK HW]  -->
 +
| <!-- description -->
 +
|-
 +
! Tester !! Smolt Profile !! Description
 +
|-
 +
|}
 +
 +
[[Category:Fedora 12 Test Days]]

Latest revision as of 21:17, 26 June 2015

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.

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.

Note.png
Got updates?
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:

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.

Tester Smolt Profile Description
User:jlaska HW iSCSI (no iBFT) still works!
User:atodorov HW rootfs on RAID0
User:atodorov HW rootfs on RAID10
User:atodorov HW rootfs on RAID5
User:atodorov HW rootfs on RAID6
User:mbanas HW RootfsOn2ndVolumeRaid5Raid0, installed without swap partition because of bug 523754
User:mbanas HW RootfsOn1stVolUsrOn2ndVolRaid5Raid10, installed without swap partition because of bug 523754
User:jlaska iSCSI + iBFT detected local and remote volumes ... and formatted successfully
User:mbanas Virtualbox 3.0.6 LVM_LV_on_RAID_PV
User:mbanas HW Rootfs_On_RAID6
User:mbanas kvm i386 RootfsOn2ndVolumeRaid1Raid0
User:jlaska HW QA:Testcase_Partitioning_Rootfs2ndVolumeRaid10Raid10 (with dmraid+ encryption!)
User:jlaska HW QA:Testcase_Anaconda_partitioning_dmraid_rootfs
User:Liam HW QA:Testcase_Partitioning_RootfsOnRaid0
User:Liam HW QA:Testcase_Partitioning_RootfsOnRaid5
User:Liam HW QA:Testcase_Anaconda_rescue_mode
User:jkoten KVM x86_64 QA:Testcase_Partitioning_RootfsOnRaid0
User:jkoten KVM x86_64 QA:Testcase_Partitioning_RootfsOnRaid10
User:jkoten KVM x86_64 QA:Testcase_Partitioning_RootfsOn2ndVolumeRaid0Raid1
User:jkoten KVM x86_64 QA:Testcase_Anaconda_rescue_mode
Tester Smolt Profile Description