From Fedora Project Wiki
(Add an example and unify the kickstart case steps) |
No edit summary |
||
| (15 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:Associated_release_criterion|Beta|kickstart-delivery}} | |||
{{Template:Associated_release_criterion|Beta|scripted-installation}} | |||
{{Template:Associated_release_criterion|Beta|unattended-installation}} | |||
{{QA/Test_Case | |||
|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. | 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. | ||
|actions= | |||
# Prepare a valid kickstart file. For help creating a kickstart file, examine the file {{filename|/root/anaconda-ks.cfg}} on a previously installed system. This file contains the kickstart instructions used to install that system. For additional guidance on kickstart syntax, see [[Anaconda/Kickstart]]. | # Prepare a valid kickstart file. For help creating a kickstart file, examine the file {{filename|/root/anaconda-ks.cfg}} on 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. | # Copy the kickstart file to a publicly-accessible place on your HTTP host. | ||
# Boot the system and add a <code>ks</code> argument like the following to the boot command line | # Boot the system and add a <code>inst.ks</code> argument like the following to the boot command line:<pre>inst.ks=http://server.tld/path/to/your/ks.cfg</pre> | ||
{{admon/note|Prepared sample kickstart|You can use the following kickstart for a default installation from DVD. Please note that this will erase all your disks. The root password is 'fedora'. <pre>http://mkrizek.fedorapeople.org/default.ks</pre>}} | |||
|results= | |||
# The {{filename|ks.cfg}} is successfully obtained from the specified location | |||
# The ks.cfg is successfully obtained from the specified location | # The installer should honor the kickstart commands provided in the {{filename|ks.cfg}} file | ||
# The | # If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input. | ||
}} | |||
[[Category:Kickstart Delivery]] | [[Category:Kickstart Delivery]] | ||
Revision as of 08:21, 11 December 2013
Associated release criterion
This test case is associated with the Fedora_41_Beta_Release_Criteria#kickstart-delivery 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_41_Beta_Release_Criteria#kickstart-delivery 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_41_Beta_Release_Criteria#scripted-installation 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_41_Beta_Release_Criteria#scripted-installation 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_41_Beta_Release_Criteria#unattended-installation 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_41_Beta_Release_Criteria#unattended-installation 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 from DVD. Please note that this will erase all your disks. The root password is 'fedora'.
You can use the following kickstart for a default installation from DVD. 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.