Turns out it was the repodata cache on the spacewalk server. I blew it away and restarted the taskomatic service. Came back from lunch and the yumupdatesd on my test box had already pulled down all the packages it was missing.
Thank you all for your direction and assistance with this! - Jonathan On Wed, Feb 3, 2010 at 20:41, Jonathan Scott <[email protected]> wrote: > I was thinking it could be something with the packages. The errata > publishing script I use does separate the two, however. > > I did an initial side-by-side comparison in the beginning, where there was > clearly an updated package available on the satellite (in the appropriate > channel [i386 Updates]), the most obvious is the 2.6.18-164.11.1 kernel > sitting out there. My test system has 2.6.18-164.10 and won't update. > > - Jonathan > >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
