[Spacewalk-list] rhn_check

[James Hogarth]

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