<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16788" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>It looks like this might still be an
issue.</FONT></DIV>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2>I'm currently running 0.3 spacewalk and while
registering new clients, they were showing up as "unknown".</FONT></DIV>
<DIV><FONT face=Arial size=2>The hostname was resolving just fine locally, but
apparently not when I registered with my spacewalk server.</FONT></DIV>
<DIV>Just to clarify, I'm not running NIS, WINS, LDAP, or DNS for hostname
resolution. Just the local /etc/hosts file on the client and server in a
test environment. When I did some initial testing I was able to
register the host just fine and it's FQDN would show up in spacewalk under
Systems. But then when I started to kickstart some
clients, after registration they would display
as "unknown". Only thing different was that the kickstart clients
were using DHCP. So I made a couple of quick config changes to
a static IP and a FQDN, restarted networking, then deleted the
old profile and re-registered the client. Hostname still showed up as
"unknown" to the spacewalk server.</DIV>
<DIV> </DIV>
<DIV></FONT><FONT face=Arial size=2>So I did some searching and I
found this thread in the archive which sounded like the exact
same problem.</FONT></DIV></DIV>
<DIV><FONT face=Arial size=2><A
href="https://www.redhat.com/archives/spacewalk-list/2008-September/msg00010.html">https://www.redhat.com/archives/spacewalk-list/2008-September/msg00010.html</A></FONT></DIV>
<DIV><FONT face=Arial size=2>After reading through this thread. I noticed
that the /etc/hosts file was mentioned. So I added the static IP and
FQDN to /etc/hosts (on the client) and re-registered again. This time it
worked! So it appears that the rhnreg_ks or something that it calls, is
looking for a FQDN in /etc/hosts. If it isn't found then it registers as
"unknown", even though the FQDN is resolving locally . Not sure
about environments running other name resolution schemes, but for
local files, this seems to be the case.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>During all my testing, /etc/nsswitch.conf had the
following entry:</FONT></DIV>
<DIV><FONT face=Arial size=2>hosts: files
dns<BR></FONT></DIV>
<DIV><FONT face=Arial size=2>Here's a diff of the systemid
file after registration with and without a FQDN entry in
/etc/hosts:</FONT></DIV>
<DIV><FONT face=Arial size=2>[root@devapp03 rhn]# diff
/etc/sysconfig/rhn/systemid /etc/sysconfig/rhn/systemid.save<BR>22c22<BR><
<value><string>674945840661aa688e9149a7b6ececb5</string></value><BR>---<BR>>
<value><string>575e2ab7a5907170bbc4e7daf048a99a</string></value><BR>26c26<BR><
<value><string>devapp03.testdomain.com</string></value><BR>---<BR>>
<value><string>unknown</string></value><BR>30c30<BR><
<value><string>ID-1000010084</string></value><BR>---<BR>>
<value><string>ID-1000010083</string></value><BR></FONT></DIV>
<DIV><FONT face=Arial size=2>-Mike</FONT></DIV>
<DIV><FONT face=Arial size=2> </DIV></FONT></BODY></HTML>