Bug 117155

Summary: HTTP install reports errors late and without usable information
Product: [Fedora] Fedora Reporter: Fridjon Gudjohnsen <fridjon>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: FC4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-08-15 16:02:15 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 Fridjon Gudjohnsen 2004-02-29 18:12:45 UTC
When installation from HTTP is attempted the installation program 
does not check that the entered path to the fedora directory is a 
directory that can be used for the installation. 

After entering the details of the HTTP server to use the installation 
program proceeds to collect info on mouse/keyboard/monitor/partitions 
etc. It is only at the end of this information collection that the 
user is informed that the directory entered does not contain package 
information required to continue. At that point the user has no way 
of correcting the entered path, she can only retry the reading of 
package information (which will most likely result in the same error).

This is especially bad because the installation directory that should 
be entered is by no means obvious. In my installation I mounted the 
ISOs on another linux box and symlinked them to a directory on 
Apache. The structure visible from the webserver has a root direcory 
named /fedora and under it are separate directories for each disc 
(i.e. /fedora/disc1  /fedora/disc2   /fedora/disc3  /fedora/disc4). 
When I enter the IP-address of the webserver in the first text field 
and "/fedora/" in the second field I get this error. When I 
enter "/fedora/disc1/" the installation seems to proceed normally.

Comment 1 Jeremy Katz 2004-10-18 14:39:15 UTC
Fixed in CVS