Hide Forgot
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.
Thanks for finding this, things got jumbled up when converting the kickstart command to an anaconda repo option.