Bug 74305 - The Aliases value is not populated correctly when neat is used to specify a new entry into the hosts file.
The Aliases value is not populated correctly when neat is used to specify a n...
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Ben Levenson
: 74420 (view as bug list)
Depends On:
Blocks: rcn-7.3
  Show dependency treegraph
Reported: 2002-09-19 21:08 EDT by dfladebo
Modified: 2007-04-18 12:46 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-14 16:04:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description dfladebo 2002-09-19 21:08:24 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513

Description of problem:
When neat is used to specify a new entry into the hosts file and all three of
the Address, Hostname and Aliases values are populated via the popup dialog, the
Aliases value is not stored (or at least is not displayed in the list under the
Aliases column) correctly.

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

How reproducible:

Steps to Reproduce:
1.start neat
2.Got the Hosts Tab
3.Click [Add]
4.Fill in all three values and save.

Actual Results:  Does not save the Aliases value.

Expected Results:  Should save the Aliases value.

Additional info:
Comment 1 Phil Knirsch 2002-10-04 08:57:31 EDT
Reassigning to the correct component...

Read ya, Phil
Comment 2 Harald Hoyer 2002-10-23 05:37:11 EDT
first beta of erratum is available at:

Most of the bugs reported have been removed, but as in every software change,
there could be new bugs introduced.

Please report bugs against this with explicitly stating the 1.0.1 version... Thx
and please test.
Comment 3 Harald Hoyer 2002-11-20 13:10:20 EST
*** Bug 74420 has been marked as a duplicate of this bug. ***
Comment 4 John Flanagan 2003-02-14 16:04:26 EST
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


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