Bug 521419

Summary:	nfs network install fails - trying to access a directory(?) not in the ISO
Product:	[Fedora] Fedora	Reporter:	John Dubery <jdubery>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	11	CC:	anaconda-maint-list, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-09-05 20:34:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Dubery 2009-09-05 17:06:57 UTC

Description of problem:
Trying to perform a network install of F11; the target machine was booted using a F11 network install CD, added parameters "linux askmethod". Note that the server is not exporting the DVD ISO image directly, but the ISO is loop mounted because the direct mount doesn't work (see my report - Bug 521418)

I get to the "Starting install process. This may take several minutes..." dialog, this fills its progress bar then everything stops.

The server log has "can't stat exported dir /mnt/Fedora-11-i386-DVD/RHupdates: No such file or directory".

It seems the installer is trying to access a folder that does not exist in the DVD image. When this fails the installer stops dead.

Version-Release number of selected component (if applicable):
- anaconda - as current download ISO images
- F11 DVD ISO image (exported by the server) - current download
- target is running a CD with the F11 network install image - current download

How reproducible:
100%

Steps to Reproduce:
1. as above
2.
3.
  
Actual results:
F11 install fails

Expected results:
F11 install OK

Additional info:
not sure exactly what to assign this to (may actually be an installation guide problem); used anaconda as an "install problem catcher" and likely suspect

Comment 1 Chris Lumens 2009-09-05 20:34:00 UTC

During installation, anaconda looks in a variety of places to get updated python files that are used to patch anaconda itself.  Passing updates= as a parameter is one way that users can control this process.  anaconda additionally tries to grab updates automatically based on the method used to install.  The directory you see is one of those attempts.  Errors here are not fatal.  They just mean you won't get any updates loaded from that directory.

Whatever real failure you're seeing is not caused by this.