Red Hat Bugzilla – Bug 1452770
Document and fix a small bug when using driverdisk kickstart command
Last modified: 2018-05-02 00:58:29 EDT
Description of problem: Presently you can use a driverdisk by specifying a "partition" using a LABEL/UUID, though it should be noted that this behavior isn't officially documented in Pykickstart. That said, we should make an effort to document it. In an effort to make sure the behavior is bug-free however, I uncovered an issue when specifying a partition by LABEL using non-alphanumeric characters, e.g.: You should be able to write this to KS and get the same output KS after installation: driverdisk "CDLABEL=Fedora 23 x86_64:/path/to/rpm" In theory, you should be able to write this to KS and get the same output after installation, but it fails to parse. Version-Release number of selected component (if applicable): pykickstart-1.99.66.12-1 How reproducible: Always Steps to reproduce: The best way how to test this is by running Anaconda with this command in it. 1) Create kickstart file with line 'driverdisk "CDLABEL=Fedora 86_64:/path/to/rpm"' 2) Create partition or external USB on the testing machine 3) Format this partition with label "Fedora 86_64" 4) Run this kickstart installation 5) Verify output kickstart file Actual results: The "driverdisk" kickstart command usage is not documented properly. Expected results: The "driverdisk" kickstart command should be documented and should work correctly for LABEL/UUID.
Let's document this as a known issue for 7.4.