On Tue, 16 Mar 2010, George wrote:

If you tried the update right after the packages became available in the
repos (lets say you ran a manual spacewalk-repo-sync before or something
like that) this is normal, in my experience it takes around 15 minutes
to actually update the repo metadata on the machine ... so spacewalk has
the new packages, but the clients don't have that information yet (even
though they already show it in the webinterface). I already discussed on
irc that an update package or install package action should trigger an
'yum clean all' before the action takes place, thus ensuring the repo
metadata on the client machine is getting updated before it actually
tries the install/update ...

A yum clean all wouldn't be enough, since AFAIK, the old repo data would be
available until the new repodata had finished rebuilding.  It possibly needs
more joined up thinking at the server end.  Don't issue a package command
while repodata needs rebuilding, and then possibly a clean of repodata at the
client side for repos it knows to have changed recently.

Furthermore of note in the same category actually:
if you try an update of a package and the package is not available yet
as metadata the scheduled update will show succes in stead of failed,
because it sees it has the latest version and cosiders this a succes
even though it did not update anything and the version is not the one
reported in the webinterface yet. (some better checking should be
applied here)

Yep, I think that should be a fail.  At least if it's a fail, you can just
reschedule failed actions.

I encountered most of these things because I maintain a custom repo on
spacewalk with 'homebuilt' packages which got pushed manually seconds
before I tried to install / update them ...

Me too.

Perhaps this info is a bit outdated, I still run SW 0.7 right now but I
don't think this got fixed in 0.8

I've yet to upgrade to 0.8 either.

jh

_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to