Bug 443414 - Network device menu + Set the hostname:
Summary: Network device menu + Set the hostname:
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Fedora Extras Quality Assurance
Keywords: Reopened
Depends On:
Blocks: F9Target
TreeView+ depends on / blocked
Reported: 2008-04-21 13:45 UTC by Jóhann B. Guðmundsson
Modified: 2008-04-25 23:58 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-25 23:58:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jóhann B. Guðmundsson 2008-04-21 13:45:20 UTC
Description of problem:

Network devices menu.


Set the hostname:
  O automaticly via DHCP
  O manually [ localhost.localdomain ]

If you choose to enable the option "automatically via DHCP"
and then chose to [ Edit ] for a specific network device 
then press [ OK ] it sets it self back to "manually [ localhost.localdomain ]"

It also sets it self back to "manually [ localhost.localdomain ]" if you have
chosen to enable the option automatically via DHCP
and press [ Next ] and are now in the select timezone menu and press [ Back ].

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

F9-Preview-Live iso 
( anaconda- )

How reproducible:


Steps to Reproduce:
1. The above.
Actual results:

Expected results:

Additional info:

Comment 1 David Cantrell 2008-04-24 01:14:07 UTC
This is deliberate.  We force users to set a hostname manually, even if you are using DHCP.  You can 
change it back to use DHCP for the hostname, but the default now is manual.  See bug #408921 for 

It doesn't really matter what the hostname is, but we have seen systems (laptops in particular) set up to 
use DHCP for the hostname and that causes a lot of X applications to fail.  This change in anaconda came 
as a request from the desktop team.

Comment 2 Jóhann B. Guðmundsson 2008-04-24 12:01:28 UTC
Would it not be better then to remove the option to set the 
hostname automatically via dhcp altogether ?

Comment 3 David Cantrell 2008-04-24 20:17:22 UTC
No, see bug #408921.

Comment 4 Jóhann B. Guðmundsson 2008-04-25 15:23:25 UTC
Had already read it. 

Failed to see the connection between it and this bug.

I think you misunderstanding the bug report I filed.

My bug report is about after a user has chosen to use
Automatically via DHCP instead of Manually [ localhost.localdomain ],
Anaconda sets the option back to Manually if the user goes back and 
forth in anaconda.

I am not filing a bug against which one should be the default..
If it was the other way around I would still be filing this bug...

I am filing a bug against anaconda always resetting it to default after
a user has chosen not to use the default if he goes back and fourth in anaconda
or in edit tab for the network interface.

Anaconda should be honoring the users chose..

So reopen this bug.

Comment 5 David Cantrell 2008-04-25 23:58:29 UTC
You are absolutely correct, I did read your initial report incorrectly.  My apologies.

OK, I fixed this up in version control, so we should have this working in the next anaconda build.  The 
change ID in git is 3c4deee414ad8c37cfdc55ce2de7d4fbd49af017.  Basically, it was entirely a UI bug.  
Underneath, anaconda was doing what you told it.  But yes, going Back to the network configuration 
screen was resetting the 'Set the hostname' option to manual.

I've fixed it now so the default is manual, but once you change it, we preserve that.  So going Back to the 
network configuration will show the setting you gave it for 'set the hostname'.

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