<div dir="ltr">Yes, it is spacewalk proxy 2.2 to spacewalk 2.2. </div><div class="gmail_extra"> <div class="gmail_quote">On Fri, Dec 5, 2014 at 2:47 PM, Stephen Herr <<a href="mailto:sherr@redhat.com" target="_blank">sherr@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is your Proxy 2.2 instance connected to a Spacewalk 2.2 server? It is not supported to have a Spacewalk version < Proxy version. -Stephen On 12/05/2014 12:09 PM, Michael Guidero wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> We have a similar issue, for Scientific Linux 7. The package in question is vim-common-7.4.160-1.el7.x86_64.rpm Log message: 2014/12/04 18:18:20 -07:00 8897 10.30.20.192 <<a href="http://10.30.20.192" target="_blank">http://10.30.20.192</a>>: broker/rhnRepository.getPackagePath('ERROR', 'Package not in mapping: vim-common-7.4.160-1.el7.x86_64.rpm') The source distro has a vim-common package named: vim-common-7.4.160-1.el7:2.x86_64 We also get a warning for a "not well-formed" comps.xml, a closer inspection of the comps.xml file downloaded to the kickstarting system indicates that it is lzma-compressed and would be valid if it was not compressed. On Fri, Dec 5, 2014 at 5:04 AM, Linder, Rolf <<a href="mailto:Rolf.Linder@united-security-providers.ch" target="_blank">Rolf.Linder@united-security-providers.ch</a> <mailto:<a href="mailto:Rolf.Linder@united-security-providers.ch" target="_blank">Rolf.Linder@united-security-providers.ch</a>>> wrote: Dear spacewalker’s____ __ __ We’ve been using spacewalk for the couple of years, now using Spacewalk 2.2. Since our servers are growing we have to enhance our environment to use spacewalk proxy servers.____ __ __ While testing the proxy server, we setup a test spacewalk system kickstarted a child which we then configured according <a href="https://fedorahosted.org/spacewalk/wiki/HowToInstallProxy" target="_blank">https://fedorahosted.org/spacewalk/wiki/HowToInstallProxy</a> as a proxy (so far we have two systems, spacewalk server and spacewalk proxy).____ __ __ After this we kickstart a “real” child which works fine when using the spacewalk server (including re-provisioning via WebUI). If we want to re-provision the system using the proxy we end up with the following failure:____ __ __ (out of /var/log/rhn/rhn_proxy_broker.log from proxy)____ broker/rhnRepository.getPackagePath('ERROR', 'Package not in mapping: iputils-20071127-17.el6_4.2.x86_64.rpm') ____ __ __ the client stops with the message that the RPM could not be opened. ____ http-access log show the GET request, but squid-logs does not show any entry regarding this.____ __ __ Any help would be highly appreciated!____ __ __ Kind regards,____ Rolf ____ __ __ _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a> <mailto:<a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a>> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> -- Michael Guidero Sococo IT <a href="tel:650-265-7013%20Ext%201000" value="+16502657013" target="_blank">650-265-7013 Ext 1000</a> _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> </blockquote> _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> </blockquote></div> -- <div class="gmail_signature"><div dir="ltr"> Michael Guidero Sococo IT 650-265-7013 Ext 1000 </div></div> </div>