Re: [Spacewalk-list] CENTOS packages being linked to RHEL channels

2010-03-17 Thread Stephen John Smoogen
On Wed, Mar 17, 2010 at 5:30 PM, Mullis, Josh (CCI - Atlanta) wrote: > > > Hello all... > > > I am having an issue where it seems packages from centos and rhel are > getting intermingled. > > Packages from centos are being linked to rhel channels if they have the same > name/version. > The only di

[Spacewalk-list] CENTOS packages being linked to RHEL channels

2010-03-17 Thread Mullis, Josh (CCI - Atlanta)
Hello all... I am having an issue where it seems packages from centos and rhel are getting intermingled. Packages from centos are being linked to rhel channels if they have the same name/version. The only difference is the checksum, which is how I thought it determined the difference between t

Re: [Spacewalk-list] apacheAuth.py always fails with session key error

2010-03-17 Thread Stefan Förster
* Stefan Förster : > for our Spacewalk 0.8 (upgraded from 0.6 to 0.7 and then 0.8), client > authentication always fails, complaining about a bad session key. > > XML-RPC debugging logs are available at: > > http://www.incertum.net/~cite/error.log > > > I had to uncomment the following code in

Re: [Spacewalk-list] Updates not displayed in web interface

2010-03-17 Thread Stefan Förster
* Stefan Förster : > at our Spacewalk 0.8 server (upgraded from 0.6 to 0.7 and then from > 0.7 to 0.8), available updates don't show up in the web interface. We > are generating the reports about updates with our regular reporting > system, using the following SQL against an Oracle 10.2 database: >

[Spacewalk-list] Spacewalk 0.8, CentOS and repodata (yum update fails)

2010-03-17 Thread Bushby, Bruce (London)(c)
Hi I'm still having issues with Spacewalk 0.8 whereby a fresh client is unable to run "yum update". After hearing the issue was supposed to be fixed in Spacewalk 0.8, I rebuilt my server, created a single channel with 3 python rpms and used the UI to "Alter channel Subscriptions" On my client,

Re: [Spacewalk-list] error with centos 5 clients

2010-03-17 Thread John Hodrien
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

Re: [Spacewalk-list] error with centos 5 clients

2010-03-17 Thread Michiel van Es
Hi George, I've scheduled the updates 1 day before it should run. And I use the latest 0.8 version with a normal CentOS 5 updates repository. I find it strange that a grouped update/upgrade of package fails but scheduling the update for the machines one by one does work. Kind regards, Michiel