On Mon, 2009-08-17 at 15:59 -0500, Pradeep Kilambi wrote: > hrm seems like a separate issue. Sounds to me like your checksum > generated on the server does'nt match the client. When you created the > cloned channel, what checksum type did you choose. There are two types > of supported checksums so far. sha1 which has a wider compatibility > and sha256 which has a higher scurity but only newer clients can > handle that metadata. So when you cloned and if your parent was using > sha256 the clone as its done now picks up the parent checksum and if > thats not compatible with the clients, you will get "Error Performing > Checksum" . So if you're using el5 as your clients, make sure your > checksum is set to sha1. > > ~ Prad
I thought that might originally be the case, but even after verifying that I'm using "sha1" and clearing all caches to include the cache on my Spacewalk server, and watching it regen... none of that helped. Only until I deleted the cloned channels and recreated them, ensuring "sha1" was selected did they work. -- Andy Speagle "THE Student" - UCATS Wichita State University
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
