We ran into issues where "yum update" updated the centos-release RPM, which in turn would push updated .repos to /etc/yum.repos.d/. This would cause a similar issue to the errors described. The solution we came up with, was to put the following in the post section of the default kickstart: If there is a better idea, I am all ears. mkdir -p /some/where/ echo "reposdir=" /some/where/" >> /etc/yum.conf Some benefits, by doing this has been that 3rd party vendor apps that install their own /etc/yum.repos.d/ will not cause any delays or issues with running yum commands (if they cannot reach the site). If the client is able to reach the site, then a request process will move the 3rd party .repo in /some/where. - Thanks From: Jan Hutaų <jhutar@redhat.com> To: Emmett Hogan <ehogan@gmail.com> Cc: spacewalk-list@redhat.com Date: 02/24/2016 01:29 AM Subject: Re: [Spacewalk-list] rhn_check fails Sent by: spacewalk-list-bounces@redhat.com <hr noshade> <tt>This email originated from outside of the company. Please use discretion if opening attachments or clicking on links. On 2016-02-23 22:45 -0800, Emmett Hogan wrote: > Forgive me if this is a silly question, but I finally got a bare metal > system to build from my Spacewalk server and wanted to push some extra > packages to it. The request queued up like it should, then eventually > failed with a python error. In doing some digging, it was trying to > resolve [1]mirrorlist.centos.org. I don't understand why it would be > trying to go back to centos for the packages....I thought that it would > go to my Spacewalk server for all it's updates. > I even tried running: > # rhn_check > Could not retrieve mirrorlist > [2]</tt><a href="http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=st"><tt>http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=st</tt></a><tt> > ock error was > 14: curl#6 - "Could not resolve host: [3]mirrorlist.centos.org; Unknown > error" > I checked /etc/sysconfig/rhn/up2date and it references my spacewalk > host: > serverURL=[4]</tt><a href=https://192.168.67.5/XMLRPC><tt>https://192.168.67.5/XMLRPC</tt></a><tt> > I know I've apparently screwed up something, somewhere, but I cannot > seem to find the answer anywhere. > Any help would be greatly appreciated. > -Emmett > >References > > 1. </tt><a href=http://mirrorlist.centos.org/><tt>http://mirrorlist.centos.org/</tt></a><tt> > 2. </tt><a href="http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock"><tt>http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock</tt></a><tt> > 3. </tt><a href=http://mirrorlist.centos.org/><tt>http://mirrorlist.centos.org/</tt></a><tt> > 4. </tt><a href=https://192.168.67.5/XMLRPC><tt>https://192.168.67.5/XMLRPC</tt></a><tt> Hello, to view the actual traceback: # less /var/log/up2date And if you see client trying to reach mirrorlist.centos.org, check if you did not left some repos behind on the client: # yum repolist # cat /etc/yum.repos.d/*.repo Regards, Jan -- Jan Hutar Systems Management QA jhutar@redhat.com Red Hat, Inc. _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com </tt><a href="https://www.redhat.com/mailman/listinfo/spacewalk-list"><tt>https://www.redhat.com/mailman/listinfo/spacewalk-list</tt></a><tt> </tt> ** This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies. **