From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.1-0.1.10 i686)
Wolverine seems to behave differently to previous RH distributions in the
1) During clean install, set it up as a DHCP client
2) The DHCP server isn't a "proper" fully featured implementation - it's
actually the DHCP spoof from an Ascend Pipeline 75 which simply returns an
IP address, default gateway and DNS servers. No hostname is returned, and
it certainly doesn't interact with DDNS or anything clever.
Previous distributions have done a gethostbyaddr some time during the init
sequence to determine the hostname (the default resolver will try
/etc/hosts first, and then DNS if there's no match - I'm not using NIS).
However, wolverine doesn't do anything like this, and the hostname ends up
being set as localhost.localdomain
I've done a sys-unconfig which seems to have fixed it. Specifically, I
think it put a HOSTNAME=xxxx line in
/etc/sysconfig/network-scripts/ifcfg-eth0 which it appears to have derived
from a gethostbyaddr call against the address it got from the DHCP "server"
(I've put an entry in /etc/hosts for the address which I know will be
returned by the DHCP, but it is also resolvable to the same name forwards
and reverse by DNS if necessary).
I liked the "old" behaviour where it wasn't necessary to set anything up -
it just went off and sorted itself out without assistance (either from
hosts if the correct entry was there, or DNS if not)
Steps to Reproduce:
1. See description
Our installer team-lead thinks we should really fix this before next release.
This still present in 7.1RC1
-- Russ Herrold
What is in /etc/sysconfig/network, what does pump --status say, and what
does ifconfig say?
Also, does 'host <yourip>' return anything usefull?
I've tested this here and pump does a reverse DNS lookup properly.
I removed the HOSTNAME="<snip>" line after doing my most recent install, and it
worked fine --
--- Perhaps all that is needed is a explanation to '(Leave blank for automatic
DNS-based hostname assignment)', and removing the entry from
A problem with this is that if networking does not get set up (as was the case
with this build -- it had an ISA SMC-Ultra at 10/300, sshd will generate keys
with bad hostnames when first started ...
I will attach the requested output in a second.
-- Russ Herrold
Created attachment 12022 [details]
Did you enter a host name manually during installation?
Yes -- a dummy which I could egrep for to see where it landed.
that is why I manuially removed the line from /etc/sysconfig/network
For me, I told it to used DHCP for eth0 configuration so it didn't give any
opportunity to enter anything at install time:
1) /etc/sysconfig/network contains a line "HOSTNAME=localhost.localdomain"
2) pump --status returns viable numeric entries for every field (pump
--lookup-hostname returns nothing at all, I have no idea whether this is
3) ifconfig shows correct addresses and subnetmasks bound to eth0 and lo
4) host <IP addr of eth0> returns a proper answer (FQDN)
What does 'hostname' say when you log into the system?
QA 0309 upgrade frpm 7.1RC2 --
[herrold@dhcp164 herrold]$ hostname
... that is, the FQDN ...
So what's the bug? Isn't that what the hostname *should* say?
I consider the item closed and resolved -- dunno about Tim C -- the initial
You're the boss ;-)
Can you re-open this, my hostname says localhost.localdomain
I have discovered a "better" workaround (to get sshd keys generated properly).
1) Perform install
2) After install is finished and system reboots - don't let it come up on its
own, boot into single user mode
3) Edit /etc/sysconfig/network, change "HOSTNAME=localhost.localdomain" to
proper hostname (optionally place appropriate entry in /etc/hosts to get it to
use this instead of DNS, or change /etc/resolv.conf to use an appropriate
search path or domain)
4) Reboot and let it start normally for the "first" time
Tim, I can't reproduce this problem. On every system I've tried pump sets the
hostname properly at startup.