From Fedora Project Wiki
(initial rewrite of test case for F19) |
(add the 'associated criterion' block) |
||
| Line 1: | Line 1: | ||
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Final_Release_Criteria#Network_attached_storage}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This install verifies that unauthenticated access to and installation with an iSCSI <ref>http://en.wikipedia.org/wiki/ISCSI</ref> block device works properly. While this test can be performed on systems with iBFT <ref>http://en.wikipedia.org/wiki/ISCSI_Boot_Firmware_Table</ref> support, it is intended for systems that do not support booting iSCSI volumes. For a more exhaustive test iSCSI strategy, refer to [[QA:iSCSI_Installation_Test_plan]]. | |description=This install verifies that unauthenticated access to and installation with an iSCSI <ref>http://en.wikipedia.org/wiki/ISCSI</ref> block device works properly. While this test can be performed on systems with iBFT <ref>http://en.wikipedia.org/wiki/ISCSI_Boot_Firmware_Table</ref> support, it is intended for systems that do not support booting iSCSI volumes. For a more exhaustive test iSCSI strategy, refer to [[QA:iSCSI_Installation_Test_plan]]. | ||
Revision as of 23:18, 25 July 2013
Associated release criterion
This test case is associated with the Fedora_42_MILESTONE_Release_Criteria#CRITERION_NAME release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Fedora_42_MILESTONE_Release_Criteria#CRITERION_NAME release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Description
This install verifies that unauthenticated access to and installation with an iSCSI [1] block device works properly. While this test can be performed on systems with iBFT [2] support, it is intended for systems that do not support booting iSCSI volumes. For a more exhaustive test iSCSI strategy, refer to QA:iSCSI_Installation_Test_plan.
Setup
If a hardware iSCSI target is unavailable, you may setup a software iSCSI target following the instructions at Scsi-target-utils_Quickstart_Guide#Up_and_running_in_3_steps.
How to test
- Start installation using any available means (CD, DVD,
boot.isoetc...) - Advance to the installer hu
- Click on Installation Destination
- Under "Specialized & Network Disks" click on "Add a disk..."
- Click on "Add iSCSI Target..."
- Fill out the Target IP address and click on "Start Discovery"
- Select the correct node in the list of discovered targets
- Select "No Authentication (discovery authentication disabled)" as the Node login authentication type
- Click the "log in" button (not the "OK" button)
- Select the desired virtual disk by using the checkbox on the left hand side of the spoke
- Click "Done"
- At this point, there should be checkmark icons on the iSCSI virtual disk and the local disk needed for boot
- Enter the custom partitioning screen
- Make sure that /boot is on the local disk and '/' is on the iSCSI virtual disk
- Complete installation as desired.
Expected Results
- The installer connects to the iSCSI target without error
- All expected iSCSI disks are included in list of available disks.
- Installation completes without error.
- The installed system boots with all filesystems on the iSCSI device mounted. For assistance troubleshooting network boot issues, consult How_to_debug_Dracut_problems.