From Fedora Project Wiki
(add the 'associated criterion' block) |
(add the 'associated criterion' block) |
||
| Line 1: | Line 1: | ||
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Beta_Release_Criteria#Kickstart_delivery}} | {{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Beta_Release_Criteria#Kickstart_delivery}} | ||
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Beta_Release_Criteria#Scripted_installation}} | {{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Beta_Release_Criteria#Scripted_installation}} | ||
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Beta_Release_Criteria#Unattended_installation}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
Revision as of 23:04, 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.
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.
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 test will verify that anaconda can download the requested kickstart file using a HTTP url. It requires a valid kickstart file and a working HTTP host.
How to test
- Prepare a valid kickstart file. For help creating a kickstart file, examine the file
/root/anaconda-ks.cfgon a previously installed system. This file contains the kickstart instructions used to install that system. For additional guidance on kickstart syntax, see Anaconda/Kickstart. - Copy the kickstart file to a publicly-accessible place on your HTTP host.
- Boot the system and add a
inst.ksargument like the following to the boot command line:inst.ks=http://server.tld/path/to/your/ks.cfg
Prepared sample kickstart
You can use the following kickstart for a default installation. Please note that this will erase all your disks. The root password is 'fedora'.
You can use the following kickstart for a default installation. Please note that this will erase all your disks. The root password is 'fedora'.
http://mkrizek.fedorapeople.org/default.ks
Expected Results
- The
ks.cfgis successfully obtained from the specified location - The installer should honor the kickstart commands provided in the
ks.cfgfile - If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input.