I've seen similar behaviour and posted about it before but got no response from anyone.
If a package is updated on the server (via rhnpush or reposync) then a rhn-profile-sync is required from the client to have the server show updated packages available for that client. The client can still see the package as available using yum list updates..... I've taken to pushing out a cron job from the spacewalk server to all clients registered that does a rhn-profile-sync and an osad restart to get around the osad issues posted about previously about an hour after the time I have my reposync's scheduled each day. 2009/12/16 Thomas von Steiger <[email protected]> > Hi, > > On my spacewalk 0.7 i found the client package state would not be updatet > on the system overview panel. > If i run rhn-profile-sync on all the clients then its ok. > Which site need to update this state ? > spacewalk server or clients ? > > Thomas > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
