Bug 448523 - stage 1 shows FTP setting window is HTTP url is wrong
Summary: stage 1 shows FTP setting window is HTTP url is wrong
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda
Version: 4.7
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-27 13:09 UTC by Alexander Todorov
Modified: 2008-06-23 18:15 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-23 18:15:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexander Todorov 2008-05-27 13:09:37 UTC
Description of problem:
After booting with method=http:// pointing to a wrong url (e.g. a typo) anaconda
will try to download stage2 and when that fails it will present the user with
FTP settings window to correct the url, not HTTP settings window.

Version-Release number of selected component (if applicable):
anaconda-10.1.1.89-1

How reproducible:
Always

Steps to Reproduce:
1. Boot: linux method=http://wrong-url
2.
3.
  
Actual results:
User is presented with FTP settings window instead of HTTP one.

Expected results:
User is presented with HTTP settings window so they can correct the url

Additional info:
Going back after the FTP window is shown reveals that the installation method is
set to FTP. 
After choosing HTTP and filing a wrong url the user will be correctly presented
with the HTTP settings window, so they can correct the url.

Comment 1 Chris Lumens 2008-06-23 18:15:38 UTC
Yeah I've looked at fixing this before, but the code is just not at all laid out
in a manner that makes it easy.  I don't really think there's much we can do
here since it's more work than it's worth, especially when the workaround is to
just reboot.  You're still in the loader so you haven't gotten very far yet.

The good news is this will be fixed up for RHEL6.


Note You need to log in before you can comment on or make changes to this bug.