Bug 1452770 - Document and fix a small bug when using driverdisk kickstart command
Summary: Document and fix a small bug when using driverdisk kickstart command
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pykickstart
Version: 7.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: David Cantrell
QA Contact: Release Test Team
Filip Hanzelka
Depends On:
TreeView+ depends on / blocked
Reported: 2017-05-19 15:14 UTC by Jiri Konecny
Modified: 2019-05-02 00:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Specifying a driverdisk partition with non-alphanumeric characters generates an invalid output Kickstart file When installing Red Hat Enterprise Linux using the *Anaconda* installer, you can add a driver disk by including a path to the partition containing the driver disk in the Kickstart file. At present, if you specify the partition by LABEL or CDLABEL which has non-alphanumeric characters in it, for example: driverdisk "CDLABEL=Fedora 23 x86_64:/path/to/rpm" the output Kickstart file created during the *Anaconda* installation will contain incorrect information. To work around this problem, use only alphanumeric characters when specifying the partition by LABEL or CDLABEL.
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Jiri Konecny 2017-05-19 15:14:14 UTC
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):

How reproducible:

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.

Comment 2 Petr Bokoc 2017-06-13 11:03:00 UTC
Let's document this as a known issue for 7.4.

Note You need to log in before you can comment on or make changes to this bug.