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.
Created attachment 712958[details]
fail1
Description of problem: I want to make the kickstart file available on Windows NFS. I am using Windows 2008 Active Directory NTLM authentication. Our AD server is Domain functional level: "Windows Server 2008 R2" and Forest functional level: "Windows Server 2003"
I have tested the following scenarios to mount the share on a RHEL client successfully.
- Standard NTLM authentication "mount -o user=<user>,pass=<pass> //10.224.129.145/kickstart/ test"
- Anonymous access "mount.nfs 10.224.129.145:kickstart test -v"
Version-Release number of selected component (if applicable): RHEL 6.4 boot.iso
How reproducible: I have included all networking information to anaconda to configure an interface and point to KS file from NFS source but it fails to mount NFS source.
Steps to Reproduce:
1. Edit boot stanza. Two options (Authentication and Anonymous)
append initrd=initrd.img dns=10.224.129.101,10.224.129.102 gateway=10.224.129.1 ip=10.224.129.121 noipv6 netmask=255.255.255.0 ksdevice=link ks=nfs:user=<username>,pass=<psw>,dom=<Domain-name>:10.224.129.145:/kickstart/test.ks loglevel=debug
2. append initrd=initrd.img dns=10.224.129.101,10.224.129.102 gateway=10.224.129.1 ip=10.224.129.121 noipv6 netmask=255.255.255.0 ksdevice=link ks=nfs:10.224.129.145:/kickstart/test.ks loglevel=debug
3. Boot
Actual results:
"Error downloading kickstart file"
Debug:
ERROR: failed to mount nfs source
Expected results:
Mount KS file from NFS source and proceed with automatic installation.
Additional info: Connection probably times out, Firewall logs don't report any blocks.
I have included all necessary logs, please note that I managed to kickstart the system successfully after 9:30 using http:// protocol but NFS still doesn't work.
Looks like the mount command is getting constructed wrong:
Running... /bin/mount -n -t nfs -o nolock user=kickstart,pass=letmein:/10.224.129.145/kickstart /tmp/mnt
I have tried that but its still failing.
From anaconda.program.log:
/bin/mount -n -t nfs -o user=kickstart,pass=letmein,nolock 10.224.129.145:/kickstart /tmp/mnt
I have enabled unmapped user access. "Allow unmapped user Unix access (by UID/GID)" and I am able to mount it on a test server using: /bin/mount -n -t nfs 10.224.129.145:/kickstart /tmp/mnt
I modified my KS file by removing options:
ks=nfs:10.224.129.145:/kickstart/ks.cfg
However that too fails in Anaconda.
Comment 21Samantha N. Bueno
2013-07-01 18:43:31 UTC
I'm closing this based on the fact that I'm not seeing enough information in the provided log files to determine where the error might lay within the installer--or even that the problem does lie on our end. Please check the logs for your NFS server, which may hold more/useful information.
Created attachment 712958 [details] fail1 Description of problem: I want to make the kickstart file available on Windows NFS. I am using Windows 2008 Active Directory NTLM authentication. Our AD server is Domain functional level: "Windows Server 2008 R2" and Forest functional level: "Windows Server 2003" I have tested the following scenarios to mount the share on a RHEL client successfully. - Standard NTLM authentication "mount -o user=<user>,pass=<pass> //10.224.129.145/kickstart/ test" - Anonymous access "mount.nfs 10.224.129.145:kickstart test -v" Version-Release number of selected component (if applicable): RHEL 6.4 boot.iso How reproducible: I have included all networking information to anaconda to configure an interface and point to KS file from NFS source but it fails to mount NFS source. Steps to Reproduce: 1. Edit boot stanza. Two options (Authentication and Anonymous) append initrd=initrd.img dns=10.224.129.101,10.224.129.102 gateway=10.224.129.1 ip=10.224.129.121 noipv6 netmask=255.255.255.0 ksdevice=link ks=nfs:user=<username>,pass=<psw>,dom=<Domain-name>:10.224.129.145:/kickstart/test.ks loglevel=debug 2. append initrd=initrd.img dns=10.224.129.101,10.224.129.102 gateway=10.224.129.1 ip=10.224.129.121 noipv6 netmask=255.255.255.0 ksdevice=link ks=nfs:10.224.129.145:/kickstart/test.ks loglevel=debug 3. Boot Actual results: "Error downloading kickstart file" Debug: ERROR: failed to mount nfs source Expected results: Mount KS file from NFS source and proceed with automatic installation. Additional info: Connection probably times out, Firewall logs don't report any blocks.