Univention Bugzilla – Bug 32228
Univention Net Installer in 3.2 fails to mount its NFS share
Last modified: 2013-11-19 06:44:00 CET
Created attachment 5366 [details] Screenshot of failed NFS mount I tried a PXE installation using Univention Net Installer with current 3.2. The installation source was assigned via NFS in the installation profile via the following configuration stanza: cdrom_device='nfs:10.200.3.32:/var/lib/univention-repository' However, the installations hangs since the NFS mount fails. I've tracked it down to a problem closely related to Bug 28500: The client in the initial ramdisk and the NFS server negotiate the use of NFS4 and this fails (see attached screenshot) We probably need to pass "nfsvers=3" to the mount call.
It works after starting the nfs-kernel-server with the diverted debian init script: root@master131:~# /etc/init.d/nfs-kernel-server.debian restart Stopping NFS kernel daemon: mountd nfsd. Unexporting directories for NFS kernel daemon.... Exporting directories for NFS kernel daemon.... Starting NFS kernel daemon: nfsd mountd. root@master131:~#
The NFS scripts and defaults have been synchronized from the Debian version. While updating the files, several if baseConfig.has_key(...) and baseConfig[...] == ...: were converted to if configRegistry.get(...) == ...: (There are 3 more unfixed occurrences in nfs-shares.py) Some dh related cruft has been cleaned up. svn43327, univention-nfs_6.0.1-1.87.201308201358 ChangeLog: The start script for the NFS server has been synchronized with the upstrean version to support newer Linux kernels and start all services needed for the PXE installer to work
The NFS share of the installer is now mounted correctly.
UCS 3.2 has been released: http://docs.univention.de/release-notes-3.2-en.html http://docs.univention.de/release-notes-3.2-de.html If this error occurs again, please use "Clone This Bug".