Apologies, it’s 6:15am here and I’m only on my first coffee. :) I didn’t fully read your initial email and I thought the errors were occurring during a spacewalk-repo-sync to our sources.
They’re coming from your Spacewalk server, not the external repository. A detail I should’ve picked up on my first read, because the error is coming from your channels, not ours.
And I’ve not actually seen that error before. If it happened on one of my systems, I’d probably first see if clearing the client-side cache fixed it, i.e. “rm -rf /var/cache/yum && yum makecache fast && yum update”. If that didn’t work, I’d create a new test repo and test software channel and sync that to see if the error occurs on a new channel as well.
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia