Bug 1045528 - NFS repo information mixed up when mount options are given in kickstart
Summary: NFS repo information mixed up when mount options are given in kickstart
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: David Shea
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-20 16:21 UTC by Utku Altunkaya
Modified: 2014-01-30 20:32 UTC (History)
5 users (show)

Fixed In Version: anaconda-21.19-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-30 20:32:02 UTC
Type: Bug


Attachments (Terms of Use)

Description Utku Altunkaya 2013-12-20 16:21:03 UTC
When doing a kickstart install of Fedora 20 using an NFS repo, if the kickstart file specifies mount options for the NFS repo, Anaconda mixes up the order of NFS parameters. For example, the kickstart command

nfs --server=filesrv --dir=/Linux/Fedora/20/iso/x86_64 --opts="ro,nolock"

is wrongly parsed and turned into the mount command

mount -t nfs -o filesrv,nolock /Linux/Fedora/20/iso/x86_64:ro,nolock /mnt/install/source

As a result, the repo cannot be mounted and the "Installation Source" spoke displays an exclamation mark icon with the message "Error setting up base repository". Inside the spoke, the NFS address and options are displayed in the exact same, but wrong, manner.

There are two working alternatives:

1. Omit the NFS mount options
nfs --server=filesrv --dir=/Linux/Fedora/20/iso/x86_64

2. Shuffle NFS parameters around to match the buggy ordering
nfs --server="ro,nolock" --dir=filesrv --opts=/Linux/Fedora/20/iso/x86_64

For the record, this bug did not exist in the Fedora 19 installer.

Comment 1 David Shea 2014-01-23 22:52:46 UTC
Thanks for finding this, things got jumbled up when converting the kickstart command to an anaconda repo option.


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