[Spacewalk-list] server says client should be updated, but nothing happens

[Guy Matz]

So there's no easy way to schedule all machines to update, say once a month
on the first Monday, or something like that?  How do you folks generally
schedule and kick off your updates?

On Mon, Aug 13, 2018 at 5:25 PM David Rock <david at graniteweb.com> wrote:

>
> > On Aug 13, 2018, at 16:09, Guy Matz <guymatz at gmail.com> wrote:
> >
> > Hi!  In the Spacewalk UI I see:
> > Software Updates Available    Packages: 6
> >
> > rhnsd is running on the client but the client does not get updated.
> Running 'yum update' on the client would get it to update, but I think
> rhnsd is supposed to take care of this for me . . .
>
> No. That’s not what rhnsd does.  That just checks into the environment and
> looks for tasks that have been assigned to the client; it doesn’t
> automatically apply anything.  You have to explicitly schedule tasks so
> when rhnsd connects, it runs the tasks that are waiting for it.
>
> > what do I need to do to have the client automatically update?
>
> Short of putting something in cron, not much.  You might be able to create
> a scheduled event, or use the API to set up a task that the client will
> pick up.
>
> > One more question:  Is it possible to have a post-update script run?
>
> You could set up a remote execution script as a wrapper that runs your yum
> update and then afterward have it run something else.  I have often used
> that and applied to a group of systems under SSM in satellite.
>
>
> —
> David Rock
> david at graniteweb.com
>
>
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20180814/9f4713ad/attachment.htm>