I tried running the spacewalk fsck utility. I tried your suggestions as well. Unfortunately so far nothing has changed. I tried deleting one of the systems from spacewalk and re-registering it. After registering, it still shows the same discrepancy. A good number of updates listed in the GUI as being applicable, with only 2 showing on the client side with yum check-update.
I tried clearing out the yum cache on the client side, to no net effect. I have another client that needed quite a number of updates. I applied the updates with yum update. After the update was complete, I now see the same discrepancy between the yum client list and the package updates showing available and applicable from the GUI. All of the servers involved have been rebooted, so everything has been restarted. At least once. Any suggestions about why yum queries are getting different results than I see in the spacewalk GUI? And how to get things back in synch? Robert Boyd Sr. Systems Engineer PeopleFluent p. 919-645-2972 | c. 919-306-4681 e. robert.b...@peoplefluent.com<mailto:robert.b...@peoplefluent.com> [http://mktg.peoplefluent.com/rs/peopleclick/images/140410_PF4colorLOGOx150.png]<http://www.peoplefluent.com/> Click here<http://www.peoplefluent.com/> to experience the power of the new PeopleFluent Mirror Suite ™ Visit: www.peoplefluent.com<http://www.peoplefluent.com/> | Read: PeopleFluent Blog<http://peoplefluent.com/resources/peoplefluent-blog> | Follow: @PeopleFluent<http://twitter.com/peoplefluent> From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paul Robert Marino Sent: Wednesday, April 01, 2015 1:00 PM To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Yum client reports no update, But Spacewalk GUI reports that there are check if a repomd sync job is stuck this can occasionally happen on larger repos if Java isn't properly tuned. the quick way to fix it is to restart taskomatic then resync the repo Failing that you need to delete the directory containing the repomd file and resync the repo again to fully regenerate it. On Wed, Apr 1, 2015 at 12:29 PM, Boyd, Robert <robert.b...@peoplefluent.com<mailto:robert.b...@peoplefluent.com>> wrote: I’m having this same problem – a number of clients show in the GUI to need quite a number of updates. However at the client end yum check-update shows 1 2 or 3 packages needing update. And when I attempt to run the update I get dependency errors. Some of the clients are showing an update for bind-libs.i686 when they only have the x86_64 package installed. The appropriate update package for the correct architecture is on the spacewalk server and I can see in the GUI that it is listed as an update for the client, but the client can’t see it. I’ve done all of the suggestions (and then some) for clearing this problem from the client end. This suggestion about the cache looks like the first hopeful suggestion I’ve seen. And for the record, we’re running on Spacewalk 2.0 currently.
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
