Description of problem: This may not be in the correct product, so please move it if it is not. When attempting to mount nfs shares from the %post section of anaconda, mounting fails as it requires the locking daemon to be running to be able to mount shares. There is work around to use the "mount -o nolock,udp" command, although this was not previously required in RHEL 2.1 - 4. Customer considers this change in behavior a regression. Version-Release number of selected component (if applicable): anaconda-11.1.2.87-1 How reproducible: Every time. Steps to Reproduce: 1. Create custom kickstart, use install method HTTP 2. In %post section, mount something via nfs 3. Kickstart system Actual results: System stops, and wont mount nfs in kickstart, things go wobbly. Expected results: Mount remote nfs server. Additional info: Worked in 2.1,3 & 4. Seems like the defaults for NFS now default to locking.
This requires a 5.3 release note once they open up. Here is the text: The NFS default for RHEL5 is "locking". Therefore, to mount nfs shares from the %post section of anaconda, use the "mount -o nolock,udp" command to start the locking daemon before using nfs to mount shares.
This bz is or a release note only. Setting dev-ack so the bugbot doesnt close this. Alex, can you please qa-ack this for the same reason? Thanks!
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Release Notes: Changed the source (Installation_Notes.xml) to the text in the Release Notes field above.
Added New Release Notes Contents.
I have verified this in the online release notes and am thus closing this BZ. Denise