Ah ok<br>During the install anaconda looks for the version in the build tree off the ISO not necessarily the latest in your repo. Import the rpms off of the ISO into the base channel and you should be good.<br><br><span style="font-family:Prelude, Verdana, san-serif;"><br><br></span><span id="signature"><div style="font-family: arial, sans-serif; font-size: 12px;color: #999999;">-- Sent from my HP Pre3</div><br></span><span style="color:navy; font-family:Prelude, Verdana, san-serif; "><hr align="left" style="width:75%">On Apr 23, 2014 13:52, Macklin, Jason <jason.macklin@roche.com> wrote: <br><br></span><div dir="ltr">Hi Paul,<div><br></div><div>Just some more information... in trying to track down which files to delete, I noticed that the version the anaconda installer is looking for is actually older then the version in my channels. For example, anaconda gets hung up looking for iputils-20071127-16.el6_4.2.x86_64, but the only version of this package on my spacewalk server is iputils-20071127-17.el6_4.2.x86_64. What am I missing here? Do I need to update my build distro perhaps? I'm really confused as to how and why the RPM repos/channels get so easily out of sync with my PXE build distro. Maybe I'm not understanding the connection properly? Again, thank you for your time and responses!</div>
<div><br></div><div>Cheers,<br>Jason</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 23, 2014 at 9:39 AM, Paul Robert Marino <span dir="ltr"><<a href="mailto:prmarino1@gmail.com" target="_blank">prmarino1@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
When you get that message search for the package in spacewalk and delete the offending one.<br><br>Note this isn't really a spacewalk specific problem it can happen with simple repos on a web server too<br><br><span style="font-family:Prelude,Verdana,san-serif"><br>
<br></span><span><div style="font-family:arial,sans-serif;font-size:12px;color:#999999">-- Sent from my HP Pre3</div><br></span><span style="color:navy;font-family:Prelude,Verdana,san-serif"><hr align="left" style="width:75%">
<div><div class="h5">On Apr 23, 2014 12:20, Macklin, Jason <<a href="mailto:jason.macklin@roche.com" target="_blank">jason.macklin@roche.com</a>> wrote: <br><br></div></div></span><div class="HOEnZb"><div class="h5">
<div dir="ltr">Good day!<div><br></div><div>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!</div>
<div><br></div><div>Cheers,</div><div>Jason<br>
</div></div>
</div></div><br>_______________________________________________<br>
Spacewalk-list mailing list<br>
<a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><table border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody><tr><td width="84" style="width:63.1pt;padding:0in 5.4pt"><p><b><span style="font-size:11pt;font-family:Calibri,sans-serif"><img width="69" height="36" src="cid:image001.gif@01CE4A4B.CB802A60" alt="Description: Description: Description: Description: cid:image001.gif@01CCF213.7AFAF7F0"></span></b><b><span style="font-size:11pt;font-family:Calibri,sans-serif"><u></u><u></u></span></b></p>
</td><td width="554" valign="top" style="width:415.7pt;padding:0in 5.4pt"><p><span style="font-family:Imago;font-size:11pt">Jason Macklin, Senior Server Administrator</span><br></p><p><b><span style="font-size:11pt;font-family:Imago">Roche Molecular Systems<u></u></span></b></p>
<p><span style="font-size:11pt;font-family:Imago">4300 Hacienda Drive, Pleasanton, CA 94588</span></p><p><span style="font-size:11pt;font-family:Imago">Work: 925.730.8458 Cell: 925.353.7409<u></u></span></p><p><span style="font-size:11pt;font-family:Imago"><a href="http://www.molecular.roche.com/" style="color:rgb(17,85,204)" target="_blank">www.molecular.roche.com</a> || <a href="http://www.linkedin.com/pub/jason-macklin/14/151/553/" style="color:rgb(17,85,204)" target="_blank">www.linkedin.com</a></span></p>
</td></tr></tbody></table></div>
</div>