[Spacewalk-list] Issues with Scientific Linux 6.4

[Michael Mraka]

Paul Robert Marino wrote:
% the yum clean all was the first thing i tried
% 
% interestingly i did find an error in the taskomatic logs the error itself
% is a little puzzling
% this happens over and over again but only on scientific Linux channels
% 
% "
...
% "/usr/lib/python2.6/site-packages/spacewalk/satellite_tools/reposync.py",
% line 112, in sync
% INFO   | jvm 1    | 2013/04/23 00:30:31 |     self.error_msg("ERROR: %s" %
% e.value)
% INFO   | jvm 1    | 2013/04/23 00:30:31 | AttributeError:
% 'exceptions.IOError' object has no attribute 'value'
...
% I updated my test instance to spacewalk 1.9 and it seems to have fixed it
% but a new error appears in the reposync log

This looks like error fixed in 39088b67a5f28d5f0ecb8a2a2fc959db815f2098
(in Spacewalk 1.9).

% "
% Linking packages to channel.
% Repo http://ftp.scientificlinux.org/linux/scientific/6.4/x86_64/os/ has
% comps file comps-sl6-x86_64.xml.gz.
% ERROR: Not a gzipped file
% Sync completed.
% Total time: 1:46:18
% 
% "
% 
% Note: I'm still seeing this on my production instance which is still
% running 1.9 .
% Also to fix it i had to completely remove all the packages from the
% channels effected and resync them but I didn't need to delete the packages
% from the system just from the channels.
...

I've investigated this issue a bit and it seem to be caused by bz2
compressd updateinfo.xml file.

I hope it's now fixed in master by
e300b8cd4623122b7b28b445d6647d1832799e82.

Regards,

--
Michael Mráka
Satellite Engineering, Red Hat