Bug 229431 - s-c-n resets hostname un-necessarily
s-c-n resets hostname un-necessarily
Status: CLOSED WORKSFORME
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: system-config-network (Show other bugs)
5.0
All Linux
medium Severity high
: ---
: ---
Assigned To: Harald Hoyer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-20 19:26 EST by Brad Smith
Modified: 2008-12-16 07:20 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-12-16 07:20:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brad Smith 2007-02-20 19:26:58 EST
Description of problem:
When s-c-n starts, it seems to read the system's hostname as
localhost.localname, even if a different hostname is set in sysconfig/network or
by dhcp. When any network changes are committed, the hostname is changed to 
localhost.localdomain, potentially breaking sudo, X and any other
hostname-dependant services.

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

How reproducible:
Always

Steps to Reproduce:
1. Run s-c-n
2. Look at the dns settings. Host should be localhost.localdomain
3. Add a network interface or anything else that requires saving settings
4. Save settings and close s-c-n
5. Run hostname. 
  
Actual results:
Hostname should be original value unless explicitly changed in s-c-n

Expected results:
Hostname is localhost.localdomain

Additional info:
This was reported to me by someone else and I then verified it, so it's not just
my system.
Comment 1 Brad Smith 2007-02-20 20:25:15 EST
Upgraded to 1.3.99-1. Problem persists. 
Comment 2 Harald Hoyer 2007-02-22 03:54:29 EST
s-c-network looks in /etc/sysconfig/network.
HOSTNAME=<hostname>

I cannot reproduce it...
Comment 3 Brad Smith 2007-02-22 09:08:19 EST
I'm seeing it on my up2dated beta1 install and have had reports of it on RC2,
but I've also heard from someone running RC5 who has does not see the problem,
so hopefully whatever it was has been fixed. 
Comment 4 Phil Knirsch 2008-04-28 06:08:53 EDT
Has this been verified and can be closed according to comment #3?

Thanks,

Read ya, Phil
Comment 5 Phil Knirsch 2008-12-16 07:20:09 EST
Closing due to inactivity. Please reopen if the problem persists.

Thanks & regards, Phil

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