Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
NFS Mounting of ISO (and just about ALL NFS installs) are broken in Anaconda. Here is why and how to fix it. With this fix, you will be able to do a completely automated network-only install. I did this using PXEBOOT, DHCP, TFTP, and NFS.
There are two separate problems that people are getting mixed together, and so I will detail them here. Once this is fixed, you can probably close the following related Bug IDs: 811242, 846103, 957290, and 1121008
First, the root (dracut?) is trying to append ",nfsvers=3" to the nfs options. This has 2 problems. First, the comma can cause issues if there are no nfs options passed on the command line. Second, nfs3 is outdated and uses a different path naming scheme than nfs4. Most current systems use NFS4 and admins will need to remember to add the additional base directory required by older NFS systems.
Consider: How many users need to have this option automatically placed onto the NFS command line? Wouldn't it be better to allow users that need this to add it rather than force options people no longer need? Remove the code that is appending this.
Next in line is an invalid parsing of the nfs command in the kickstart configuration file. The installer menu is taking this code :
nfs --server=192.168.13.150 --dir=/Public/ISOs/CentOS-7.0-1406-x86_64-Everything.iso --opts="nolock,rsize=65536,wsize=65536"
and the menu says that the server:/path field is
/Public/ISOs/CentOS....iso:nolock,rsize...65536
It says the mount options are 192.168.13.150
It has changed server->path, path->options, options->server
The immediate fix is to REMOVE this line from the kickstart file and specify the information on the kernel command line, remembering to add the extra base directory for the forced nfs3.
Example of my PXE boot file:
default linux
label linux
kernel vmlinuz
append ksdevice=enp0s3 load_ramdisk=1 initrd=initrd.img ks=nfs:nolock,rsize=65536,wsize=65536:192.168.13.150:/storage/Public/ISOs/centos-ks.cfg repo=nfsiso:nolock,rsize=65536,wsize=65536:192.168.13.150:/storage/Public/ISOs/CentOS-7.0-1406-x86_64-Everything.iso
Once the parsing is fixed and the ",nfsver=3" is removed, people will have a lot more success.
Thank you!
The swapped options was fixed by bug 1121008 and will be in 7.1
The nfsvers=3 is needed to work around problems with nfs4 (see bug 811242). You can use nfs4: or your own options and it won't add it.
Not settings options is working fine for me, and looking at the current behavior it looks like dracut's munge_nfs_options is fixing the ,nfsvers=3 for us. Lucky, but not ideal behavior so that should be fixed eventually.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2284.html