I have occasionally found the yum clean all does not seem to properly clean out the yum-rhn-plugin cache, so I delete /var/cache/yum/<channelname> to make sure.

Jonathan

On Tue 13 Sep 2011 09:38:31 AM CDT, Jason M. Nielsen wrote:
I just have the location of the key as well and no additional information and clients can use the channels without issue. Any time GPG keys have been an issue the error witnessed was explicit about lack of signing so doubtful thats related to your issue.

Have you restarted the Spacewalk services? Seems some have had issues with this when taskomatic is having problems or is not running.

On 09/13/2011 08:22 AM, Pierre Casenove wrote:
Hello,
I've made a network capture. I have a doubt:
In the base channel, i've put the following information in the GPG
related information:
GPG key URL:file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
GPG key ID:(none entered)
GPG key Fingerprint:(none entered)

On the clients, the GPG key are imported:
# rpm -q --queryformat "%{SUMMARY}\n" gpg-pubkey
gpg(Red Hat, Inc. (release key) <[email protected]
<mailto:[email protected]>>)

So I don't think that the issue is related to the GPG

I can't find any docs indicating what should be put in the GPG related
information on the spacewalk server? Are these information mandatory?

Thanks

Pierre

2011/9/13 Pierre Casenove <[email protected] <mailto:[email protected]>>

Thanks for the answer:
1) I checked the details of the base channel, the repo cache is sync'ed:
Last Modified:2011-09-12 11:11:24 CEST
Last Repo Build:2011-09-12 11:11:24 CEST
Repo Cache Status:Completed

2) For information, I used rhnpush and not reposync to push the rpms
in the base channel.

3) I don't have any process related to a repo sync running on my server.

I don't know what's wrong....

Pierre


2011/9/13 Jason M. Nielsen <[email protected]
<mailto:[email protected]>>

Doubt these are the only situation but under SW 1.4. 1)RHEL4
which required deleting and registering the system again.
2)Channels/Repos were still in a process of sync'ing their repo
cache. You can see this from the Channels details page.

I just had a similar issue but in my case I was seeing updates
available SW side but not client. I did all the typical yum
clean all, profile syncs, rhn_check checks, channel repo cache
sync etc and so forth. I even restarted the SW services. Nothing
worked.

I then noticed that reposyncs were still running (ie: ps auxwww
| grep repo). Somehow they appear to have been causing problems
with this even though the repos were unrelated to the clients I
saw issues on. Within minutes of the reposync's finishing all
updates showed up.



On 09/13/2011 01:57 AM, Pierre Casenove wrote:

Hello,
After a day, the clients still don't see the updates.
I've checked /var/log/up2date file on the client, but
couldn't find
anything interesting.
From the spacewalk gui, when I select the latest kernel
package and
then click on "Target Systems" tabs, my clients are listed,
though
spacewalk says they doesn't need any update (I've attached a
screenshot
to be clear).

Thanks in advance for your help,

Pierre


2011/9/12 Pierre Casenove <[email protected]
<mailto:[email protected]> <mailto:[email protected]
<mailto:[email protected]>>>


Hello,
I have a spacewalk 1.5 installation on PGSQL backend.
I have a base channel containing RHEL 5 x64 rpms.
My test clients have RHEL 5.6 installed.
I've rhnpushed the rpm of RHEL 5.7 in the base channel.
The problem is that in the web ui, no packages are
marcked for updates.
When I connect on a client, and launched yum update
command, here is
the (filtered) output:
Transaction Summary
Install 1 Package(s)
Upgrade 178 Package(s)
Total download size: 287 M
Is this ok [y/N]: N

Here is the log when running rhn_check -vvvv :
hostname ~ # rhn_check -vvvv
D: opening db environment /var/lib/rpm/Packages joinenv
D: opening db index /var/lib/rpm/Packages rdonly
mode=0x0
D: locked db index /var/lib/rpm/Packages
D: opening db index /var/lib/rpm/Providename
rdonly mode=0x0
D: do_call packages.checkNeedUpdate ('rhnsd=1',) {}
Loaded plugins: rhnplugin
D: opening db environment /var/lib/rpm/Packages joinenv
D: opening db index /var/lib/rpm/Packages rdonly
mode=0x0
D: opening db index /var/lib/rpm/Providename
rdonly mode=0x0
D: closed db index /var/lib/rpm/Providename
D: closed db index /var/lib/rpm/Packages
D: closed db environment /var/lib/rpm/Packages
D: May free Score board((nil))
Config time: 0.069
Setting up Package Sacks
D: login(forceUpdate=False) invoked
D: readCachedLogin invoked
D: Checking pickled loginInfo, currentTime= 1315834359.91 ,
createTime= 1315834345.24 , expire-offset= 3600.0
D: readCachedLogin(): using pickled loginInfo set to
expire at
1315837945.24
D: rpcServer: Calling XMLRPC up2date.listChannels
pkgsack time: 0.076
rpmdb time: 0.000
repo time: 0.003
D: local action status: (0, 'rpm database not modified
since last
update (or package list recently updated)', {})
D: rpcServer: Calling XMLRPC registration.welcome_message
D: closed db index /var/lib/rpm/Providename
D: closed db index /var/lib/rpm/Packages
D: closed db environment /var/lib/rpm/Packages
D: May free Score board((nil))



I've ran rhn_check 6 hours after rhnpushing the updates.
Is there a
problem in my setup? Where could I find useful information?

Thanks in advance for you help,

Pierre



_________________________________________________
Spacewalk-list mailing list
[email protected] <mailto:[email protected]>
https://www.redhat.com/__mailman/listinfo/spacewalk-__list
<https://www.redhat.com/mailman/listinfo/spacewalk-list>




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

--
Jonathan DeHaan
Linux Systems Engineer

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

Reply via email to