Red Hat Bugzilla – Bug 208094
Anaconda should verify install source before askmethod exists
Last modified: 2008-07-11 16:14:54 EDT
Description of problem:
When selecting HTTP/FTP install source, Anaconda asks for the URL and directory
of install source and proceeds with the installation.
If the installation source fails (due to missing/invalid/etc repo-data), the
installation aborts without giving the user an option to adjust his install
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Download the Rawhide rescue ISO.
2. Select HTTP install.
3. Input a valid URL that does not contain the required repo-data.
Anaconda will proceed to select the installation target, partition the drives,
etc, but once it begins the actual installation, it'll fail on invalid repo-data
and abort the installation.
A. (re)Verify the install source -before- switching to the actual X-based
B. (re)Prompt the user for a valid installation source URL if the URL is
Unfortunately, with the way things are currently laid out and starting to make
things more generic for differing backends, we really can't do this right now.
I've got some thoughts on how to make this better, but they're not FC6 material
I assume you'll keep this open and pick it up when FC7 starts rolling?
An additional example of this same problem is that if you are using a valid
install disk (e.g. CD, DVD) then if the alternative method selected via
askmethod fails, anaconda goes right ahead and starts using the local install
media *without any warning or prompt* (except if you go to the console and look
This can potentially lead to a broken installation if, for example, you have CD1
of a set but not the rest of the CDs...anaconda starts installing off the CD
when it should have been using HTTP, gets to where it needs CD2...CD2 doesn't
exist, so you have a borked install.
*** Bug 231885 has been marked as a duplicate of this bug. ***
*** Bug 209939 has been marked as a duplicate of this bug. ***
*** Bug 428020 has been marked as a duplicate of this bug. ***
Fix in time for F9?
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Is this still a problem in F9?
I'll test it ASAP.
Probably still a problem in F9, but definitely fixed in Rawhide.