[Spacewalk-list] Issues upgrading to next point release

[Jan Pazdziora]

On Fri, Aug 03, 2012 at 09:32:15AM +0000, Ree, Jan-Albert van wrote:
> 
> > Good investigation. Not sure what version you Spacewalk server is but
> > we bumped up the taskomatic memory for 1.7.
> 
> I am running 1.7 now, upgraded from an initial 1.6 install. The java memory was set at 256/512 which I bumped up to 512/1024

Mea culpa -- the increase to 1G is not in 1.7, we have it in nightly.

> > If the taskomatic was failing and not regenerating the repo data,
> > I don't really see how the re-registered machine could have gotten the
> > content though. ;-)
> 
> Solved that too... with a new sl-release I got a new yum repository file, so I wasn't getting the packages from my Spacewalk server but from an external SL repository, sorry for the confusion. And the re-registering was needed since the /etc/redhat-release contained a different version compared to the old systemid file which was generated upon initial registration.

That explains it all.

Thank you!

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat