[Spacewalk-list] rhn_check

[Kennedy, Ryan]

Interesting... after changing the IP address and restarting the network init.d script to make the changes take effect, it appears that osad stopped getting jabber messages.  I suspected this due to the fact that I had to run rhn_check on the client to get the requested hardware list refresh to happen.  I then initiated a reboot from Spacewalk that wasn't happening either.  After about 5 minutes I decided to check osad out.  It was running so I went ahead and restarted it.  Within 2 seconds of restarting I got a message about the system going down for a reboot.  I guess maybe osad should have a hard dependency on networking and restart when it restarts.

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of James Hogarth
Sent: Wednesday, February 03, 2010 12:28 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] rhn_check

On 3 February 2010 20:08, Kennedy, Ryan <rkennedy at paml.com> wrote:
> Is there any way to force an update of a system's IP address (e.g. I changed
> the IP address and want it to update in Spacewalk) w/o manually
> intervening?  What worked was scheduling a hardware list refresh for the
> system and then running rhn_check from that host (or wait for it to do it
> automatically).  It didn't auto-fire with osad, so I am assuming
> osa-dispatcher must be using the old IP (as Spacewalk has no notion of the
> new one at this point).  Once I ran rhn_check from the system it updated the
> IP in Spacewalk and all is well.
>
>

osad doesn't make use of or know the IP address of the client. What it
does know is the name of the system registered in the jabber database
and if there is a proxy involved the name in the jabber database of
teh proxy.

When osa-dispatcher detects a job due that has been scheduled it will
look up the name (not system name but an auto generated one) in the
database and send a message to that 'user' on the jabber session that
an update is pending. When the jabber client (osad) gets this message
it triggers rhn_check on that system which then checks in with the
registered spacewalk server to get any updates due and process them.

To update the IP address, hostname or other information like that a
'hardware refresh' is need - this can be done on the client with
rhn-profile-sync.

That, at least, is my understanding - I'm sure one of the RH engineers
will correct me if I have misunderstood at all.

James

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
DISCLAIMER:
Information contained in this message may be privileged and confidential. 
If the reader of this message is not the intended recipient, be notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If this communication is received in error, please 
notify the sender immediately by replying to the message and deleting 
from your computer. Thank you