That usually happens when the kickstart sees two different packages with the same name with different checksums in the same or different channels used in the kickstart primarily I've seen it happen when a package which was in EPEL gets moved to the EL base distro. It can also happen in new implementations if there was a mistake in the repositories configured.
When you get that message search for the package in spacewalk and delete the offending one.

Note this isn't really a spacewalk specific problem it can happen with simple repos on a web server too



-- Sent from my HP Pre3


On Apr 23, 2014 12:20, Macklin, Jason <[email protected]> wrote:

Good day!

I have an instance of spacewalk 2.1 installed with postresql.  I have created my default channels for CentOS 6 x86_64 along with spacewalk-client and some other basic channels.  I have created my distribution from a copy of CentOS 6.4 x86_64 that I downloaded within the last 3 or 4 months.  Currently when I attempt to PXE build a system the client fails once it begins to attempt installing the RPM packages.  The error is always about the RPM either missing or being corrupt.  I suspect that there is a cache or database entry out of sync somewhere, but have been unable to put my finger on a solution.  Any insight into my problem would be greatly appreciated!

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

Reply via email to