Sorry, but I think I found the issue with this but not sure.

Ultimately I noticed some reposync's running. None of them were related to the channels or clients for which I was seeing the issue which seemed odd to me. Shortly after the sync's finished the updates showed up client side as expected.

On 09/14/2011 04:56 AM, Martin Minar wrote:
Hello Jason,

----- Original Message -----
From: "Jason M. Nielsen"<[email protected]>
To: [email protected]
Sent: Monday, September 12, 2011 6:49:31 PM
Subject: [Spacewalk-list] SW shows updates, yum does not
Spacewalk 1.4
RHEL5 server
RHEL5 client

I recently updated a system via the Spacewalk GUI and it appeared to
all
work as expected. Shortly thereafter I noticed it was showing 82 more
updates available in the GUI. Odd as none of the channels had been
updated. Apparently newer packages, downloaded long before this client

did you updated some packages not using SW? Say by running yum update on client 
manually.

update was run, did not show up in the update list and were not pushed
out (ie: it installed a slightly older than most current version of
"http" but newer than that which was on the client at the time of
update).

This client now shows no updates via client side command line via Yum.
Yet in the Spacewalk gui the packages are listed as requiring an
update.

Can you give us example of package in SW that is reported as needed for update 
- it's version, the version currently present on client.


I have cleared out yum entirely with yum clean all etc client side.

Did you try to delete entire /var/cache/yum/<channel>  directory or just yum 
clean all?


The channels are subscribed and available etc.

Can you check channel where this package is, check what date/time is in Last Modified 
a Last Build Repo, then go on client to 
/var/cache/yum/<subdirectory_of_this_channel>  and check times of repomd.xml, 
primary and other files using ls -l.


The channels are not in progress for a repo cache refresh, they all
indicate "Completed".

Spacewalk has been restarted several times.

Have you tried rhn-profile-sync?


The only time I have seen anything like this was on RHEL4 and having
to
register clients twice. This is a first on RHEL5.

Anyone have an idea what might be wrong and how to resolve this?

Thanks.

_______________________________________________
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

Reply via email to