From Fedora Project Wiki
m (add wiki template use) |
(offer an example kickstart file (slightly improved to the previous mkrizek's one), use setup section) |
||
| (8 intermediate revisions by 4 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 | {{QA/Test_Case | ||
|description= | |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(S) url. It requires a valid kickstart file and a working HTTP(S) host. | ||
|setup= | |||
# Prepare a valid kickstart file. | |||
#* You can use an example kickstart from here: <pre>https://fedorapeople.org/groups/qa/kickstarts/example-minimal.ks</pre> This will install a minimal installation from the Internet repos. '''It will reformat all your disks, be sure to run this in a VM, and make sure you have no important data in there.''' The root password of the installed system will be ''fedora''. | |||
#* If you want to create your own kickstart, you can 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 (or use the example one provided above). | |||
|actions= | |actions= | ||
# Boot the system and add a <code>inst.ks=url</code> argument to the boot command line. Example: <pre>inst.ks=https://server.tld/path/to/your/ks.cfg</pre> | |||
# Boot the system and add a <code>ks</code> argument | |||
|results= | |results= | ||
# The | # The kickstart file is successfully obtained from the specified location | ||
# The installer should honor the | # The installer should honor the commands provided in the kickstart file | ||
# If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input. | # If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input. | ||
}} | }} | ||
[[Category:Kickstart Delivery]] | [[Category:Kickstart Delivery]] | ||
Latest revision as of 14:03, 5 May 2016
Associated release criterion
This test case is associated with the Fedora_42_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_42_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_42_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_42_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_42_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_42_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(S) url. It requires a valid kickstart file and a working HTTP(S) host.
Setup
- Prepare a valid kickstart file.
- You can use an example kickstart from here:
https://fedorapeople.org/groups/qa/kickstarts/example-minimal.ks
This will install a minimal installation from the Internet repos. It will reformat all your disks, be sure to run this in a VM, and make sure you have no important data in there. The root password of the installed system will be fedora. - If you want to create your own kickstart, you can 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.
- You can use an example kickstart from here:
- Copy the kickstart file to a publicly-accessible place on your HTTP host (or use the example one provided above).
How to test
- Boot the system and add a
inst.ks=urlargument to the boot command line. Example:inst.ks=https://server.tld/path/to/your/ks.cfg
Expected Results
- The kickstart file is successfully obtained from the specified location
- The installer should honor the commands provided in the kickstart file
- If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input.