Created attachment 356480 [details] kickstart file Description of problem: This bug is the same as bug 507093? if so, we have this issue even since f10? f12 rawhide anaconda kickstart does not support NFS install Version-Release number of selected component (if applicable): f12 alpha How reproducible: 100% Steps to Reproduce: 1.boot system with f12 alpha to start a kickstart installation 2.when welcome appears,press [tab] key to add options,add ks=http://xxxx/ks.cfg to the end of line, and boot 3. if the kickstart file specified nfs install, installation will fail,the output errors,please see attached pictures.If don't specify install method in kickstart file,installer will install with local media,installation will success. Actual results: Expected results: specify nfs install in kickstart file should install successfully Additional info:
Created attachment 356481 [details] kickstartnfs error
Created attachment 356482 [details] tty2 screen shot
Created attachment 356483 [details] tty4 screen shot,soory the above one is tty3 screen shot
Created attachment 356484 [details] tty5 screen shot
Can you attach /tmp/program.log to this bug report? There's plenty of reasons why mount may have failed, and whatever error message you got should be in that file. Thanks.
Created attachment 356606 [details] all files in /tmp
The message also shows up when the nfs location set in ks is just incorrect, can't this be your case?
(2, None) is still a pretty terrible error message, regardless. What does your nfs mount look like? Is this an nfsiso install? What happens if you run the same mount command by hand on tty2?
(In reply to comment #8) > (2, None) is still a pretty terrible error message, regardless. > > What does your nfs mount look like? Is this an nfsiso install? # mount 10.66.70.83:/lili/f12/i386 /tmp/foo # ls a /tmp/foo/ . RPM-GPG-KEY-fedora RPM-GPG-KEY-fedora-test-i386 .. RPM-GPG-KEY-fedora-10-primary RPM-GPG-KEY-fedora-test-ia64 EFI RPM-GPG-KEY-fedora-i386 RPM-GPG-KEY-fedora-test-ppc GPL RPM-GPG-KEY-fedora-ia64 RPM-GPG-KEY-fedora-test-ppc64 images RPM-GPG-KEY-fedora-ppc RPM-GPG-KEY-fedora-test-primary isolinux RPM-GPG-KEY-fedora-ppc64 RPM-GPG-KEY-fedora-test-x86_64 media.repo RPM-GPG-KEY-fedora-primary RPM-GPG-KEY-fedora-x86_64 Packages RPM-GPG-KEY-fedora-test TRANS.TBL README-BURNING-ISOS-en_US.txt RPM-GPG-KEY-fedora-test-10-primary repodata RPM-GPG-KEY-fedora-test-11-primary
We have positive test results from NFS installs performed manually and via kickstart. Something may be unique about the conditions of this failure. In the log file I see: 05:24:45 INFO : anaconda called with cmdline = ['/usr/bin/anaconda', '--stage2', 'cdrom:///dev/sr0:/mnt/stage2', '--kickstart', '/tmp/ks.cfg', '-T', '--selinux', '--repo', 'nfs:10.66.70.83:/lili/f12/i386'] Does this mean ... * booting the installer with CD/DVD * providing a kickstart file * kickstart file references an nfs repository I suspect the difference might be that we are booting CD/DVD. Where the positive NFS test results were all medialess boot methods (see http://docs.fedoraproject.org/install-guide/f11/en-US/html/ap-medialess-install.html)
I would be interested in seeing what the behavior under F11 was. I don't think we've changed much in repo configuration recently, aside from some patches Jeremy had for CDs that are very suspicious here. See 9756532b6fdd94ba7ab3b85bbc720785f781c52d for details.
(In reply to comment #11) > I would be interested in seeing what the behavior under F11 was. I don't think > we've changed much in repo configuration recently, aside from some patches > Jeremy had for CDs that are very suspicious here. > > See 9756532b6fdd94ba7ab3b85bbc720785f781c52d for details. F11 is the same
Radek has been taking a look at a lot of these sorts of issues lately.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I am not able to reproduce the bug and without more logging information about failing mount then we provide in f12-alpha I am clueless. I've fixed logging of mount in rawhide/f13, so the only chance of moving ahead with this bug I see is reproducing with anaconda of version 13.9 or newer.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.