Created attachment 356519 [details] bug demonstration Description of problem: I'm installing Fedora 12 Alpha TC: http://alt.fedoraproject.org/pub/alt/stage/12-Alpha-TC/Fedora-12-Alpha-x86_64-DVD/ from DVD in virt-manager (using KVM). When trying to install from NFS, I select "modify repository", choose NFS, fill details and click OK. An error message pops up that repomd.xml can't be retrieved (see video). But the NFS *is* mounted in /mnt/source and repomd.xml *is* available. Version-Release number of selected component (if applicable): * anaconda-12.7 * virt host - Fedora 11, libvirt-0.6.2-13.fc11.x86_64 How reproducible: so far always Steps to Reproduce: 1. Boot from F12 Alpha TC DVD 2. Select NFS install and select path 3. See error Actual results: Can't find repository Expected results: Can find repository Additional info: See attached logs and video
Created attachment 356520 [details] logs.tar.gz
Slight change: I have installed from netinst image instead of DVD. But I think it doesn't matter.
i have also seen this bug using install DVD of Fedora 12 Alpha.
Reviewed during F-12-Alpha Blocker bug meeting. Modifying yum repositories during installation will be discouraged for the Alpha in favor of performing any yum repo operations in the post-installation environment. Ideally, one can perform a NFS installation when booting the boot.iso or DVD with the boot argument: "askmethod" However, that appears to be inoperable for F-12-Alpha (see bug#515450). To perform a NFS installation, it is recommended that you install from a PXE server or using the media-less instructions (see http://docs.fedoraproject.org/install-guide/f11/en-US/html/ap-medialess-install.html). Adjusting the title of this defect to match the failure case.
i have tried boot (anaconda) option: repo=nfs:<server>[:options]:/<path> which failed. I checked that the nfs mountpoint is correct, and yes, it contais repodata/repomd.xml
(In reply to comment #5) > i have tried boot (anaconda) option: > repo=nfs:<server>[:options]:/<path> > which failed. It appears that due to bug#515450 ... no matter what you boot a boot.iso or DVD with, it will continue with using the install.img on that media (instead of the method= or repo= parameters). To perform a NFS installation, you may need to try the steps outlined in comment#4. If that fails, there may be a new issue lurking worthy of a new bug report. This bug report will track the REPO edit behavior noted in the attached screencast (see attachment#356519 [details]).
This should be fixed in anaconda-12.17.
Created attachment 359991 [details] dump.txt This is not fixed. In Anaconda 12.20 after modifying default repo with NFS values I get this error: anaconda 12.20 exception report Traceback (most recent call first): File "/usr/lib/python2.6/site-packages/yum/config.py", line 93, in __set__ raise ValueError('Error parsing %r: %s' % (value, str(e))) File "/usr/lib/anaconda/iw/task_gui.py", line 323, in _applyNfs repo.baseurl = "file://%s" % dest File "/usr/lib/anaconda/iw/task_gui.py", line 357, in run if not applyFuncs[type](newRepoObj) or not self._enableRepo(newRepoObj) or not \ File "/usr/lib/anaconda/iw/task_gui.py", line 511, in _editRepo dialog.run() ValueError: Error parsing 'file:///mnt/Fedora - Rawhide - Developmental packages for the next Fedora releasec3ImxN': URL must be http, ftp, file or https not "" Local variables in innermost frame: obj: rawhide self: <yum.config.UrlListOption object at 0x7f70f9b4fed0> e: URL must be http, ftp, file or https not "" value: file:///mnt/Fedora - Rawhide - Developmental packages for the next Fedora releasec3ImxN
I am working on repo editing dialog. Does updates file http://rvykydal.fedorapeople.org/updates.repo.img fix the problem for you? In my tests it does.
Yes Radek, that does solve the problem.
This bug was reviewed at the Fedora 12 Beta Blocker bug meeting on 2009-09-11. < denise> jlaska, rvykydal says he just sent patches for review for 516042
If I remember it well, this traceback should be handled by [1/14] of my patchset https://www.redhat.com/archives/anaconda-devel-list/2009-September/msg00146.html, though this fix of the traceback from comment #8 may just show another error fixed by some of following patches.
The traceback from comment #8 should be fixed in version 12.25 of anaconda.
This bug was reviewed at the Fedora 12 Beta Blocker bug meeting on 2009-09-18. It needs to be retested. Please help us by reporting if the latest package addresses the originally reported issue. Thanks.
I would love to verify the fix but everytime there comes another issue that prevents that. This time it is blocked for me because of bug #524599.
Kamil, I think it is possible to verify this bug with version 12.29 of anaconda present in Sep 24 rawhide. See https://bugzilla.redhat.com/show_bug.cgi?id=524599#c5. Concerning the bug #524599, I am going to push patches that should go into anaconda 12.32.
I tried anaconda 12.31 and basic functionality is ok, but the dialogs are so broken that I don't know whether to report it here again or create new bugs :) I will wait until 12.32 is out (tomorrow I guess) and provide a feedback then, it could solve at least one more dialog problem.
Yep, I know, the dialogs are very broken. I have some more patches going through review right now, could you please create separate bugs for issues you are hitting (with 12.32) and use this bug just for case from description, i.e. confirm if it is fixed in 12.31/32? Thanks for patience.
Testing with anaconda-12.32. I booted the rawhide-i386/boot.iso and was able to add an NFS yum repository (ntap-curly.corp.redhat.com:/vol/fedora/rawhide/nightly/rawhide-20091002/i386/os) without error. I was also able to continue the install to package selection and boot the installed system. Marking this issue as CLOSED RAWHIDE. However, it sounds like there make be additional bugs lurking based on feedback from Kamil (comment#17). Please file any new bugs to track any additional failures observed. Thanks!
Created attachment 363659 [details] gui error I'm sorry. It doesn't work. Anaconda 12.32, can't mount NFS even in shell now. See attachments.
Created attachment 363660 [details] console error
Created attachment 363661 [details] logs
Maybe it's worth mentioning that I had no problems mounting NFS in anaconda 12.31.
This is unrelated. The error in comment #22 is because you need to add -o nolock, which anaconda adds automatically. If you are seeing a different bug from the original one in this report, please open a new report. Thanks.