Bug 48888 - Host name lookup not working in TUI net. install
Summary: Host name lookup not working in TUI net. install
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
: 49291 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2001-07-12 12:46 UTC by Brent Nordquist
Modified: 2007-04-18 16:34 UTC (History)
0 users

Clone Of:
Last Closed: 2001-07-25 21:33:30 UTC

Attachments (Terms of Use)

Description Brent Nordquist 2001-07-12 12:46:30 UTC
Description of Problem:
During TUI net. installs of Fairfax beta1, anaconda says "Determining host
name", but the host name entry screen presented later is blank.  This
worked in previous Red Hat releases.

How Reproducible:

Steps to Reproduce:
1. Enter host IP address and DNS server IP address when requested.
2. See "Determining host name" message dialog.

Actual Results:
The screen for entering the host name presented later is empty.

Expected Results:
I've verified on this hardware that in Red Hat 6.2, for example, this works
correctly; the screen for entering the host name has the host name pre-filled.

Comment 1 Matt Wilson 2001-07-12 14:43:02 UTC
check for name resolution messages on VC3.

Comment 2 Bill Nottingham 2001-07-12 15:02:53 UTC
FWIW, I see the same thing on both TUI and GUI net installs (with static IP);
the hostname is never looked up.

Comment 3 Brent Nordquist 2001-07-12 16:25:16 UTC
After "determining" dialog, VC3 has:

* reverse name lookup worked


Comment 4 Glen Foster 2001-07-13 19:46:05 UTC
This defect considered MUST-FIX for Fairfax gold-release.

Comment 5 Brent Fox 2001-07-23 14:21:04 UTC
*** Bug 49291 has been marked as a duplicate of this bug. ***

Comment 6 Michael Fulbright 2001-07-25 21:33:25 UTC
Should be fixed, please test when beta 3 comes out.

Comment 7 Brent Fox 2001-08-10 15:18:31 UTC
Closing due to inactivity. Please reopen if you still see the problem with beta 3.

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