From Fedora Project Wiki
m (Adjust category) |
m (internal link cleaning) |
||
| Line 5: | Line 5: | ||
== Steps To Reproduce == | == Steps To Reproduce == | ||
Use any of the already existing [ | Use any of the already existing [[Anaconda/Features/EncryptedBlockDevices#head-3754cffc4686ac4c76bebcc9605e3f82f0b066b0|encryption test scenarios]] but perform the installation using kickstart not manually. For the newbies: | ||
# Perform a manual installation and choose "Encryption" | # Perform a manual installation and choose "Encryption" | ||
| Line 19: | Line 19: | ||
== Additional info == | == Additional info == | ||
Use [ | Use [[Anaconda/Kickstart|Kickstart]] documentation to see what are the encryption commands and options. | ||
[[Category:Encrypted Block Device]] | [[Category:Encrypted Block Device]] | ||
Latest revision as of 21:29, 19 September 2016
QA/TestCases/KickstartEncryption
Description
This test case will verify that installation on encrypted partitions in possible when using Kickstart.
Steps To Reproduce
Use any of the already existing encryption test scenarios but perform the installation using kickstart not manually. For the newbies:
- Perform a manual installation and choose "Encryption"
- Configure any/all disk partitions to be encrypted.
- After installation is finished grab the resulting /root/anaconda-ks.cfg
- Re-install the system using the kickstart above.
Expected Results
- System is bootable (at leaset runlevel 3)
- User is asked to provide the encryption pass phrase on boot
- Disk partitioning (incl. encryption) matches the one specified in the kickstart file
Additional info
Use Kickstart documentation to see what are the encryption commands and options.