On Wed, Sep 19, 2012 at 11:53 AM, Greg Swift <gregswift(a)gmail.com> wrote:
On Wed, Sep 19, 2012 at 12:13 PM, Bai Shen
<baishen.lists(a)gmail.com> wrote:
> I'm not sure if this is a cobbler or puppet issue, so please forgive the
> crossposting.
>
> I configured some repos in cobbler and set the local mirror flag. However,
> when I use puppet to install packages, they don't use my local mirror. This
> means that installs take forever as I'm on a slow connection.
>
> What should I check/test in order to fix this?
So, you configured cobbler to locally mirror the repositories. How
are the repositories configured onto the 'clients' ? Via the cobbler
$yum_config_stanza ? If so then I'd look at the repository
configuration in cobbler. If you want to see what it put look at the
kickstart (either with cli command, cobbler_web, or
/root/cobbler-ks.cfg on built server).
If you are placing the yum repo configuration in another way, look at that.
-greg
Cobbler includes the distros home repos in the tree*, but at a high
priority number (99 I think). If you set your local repos to a lower
number (say 70) they will get used first/instead. Once your system is
up and running, use puppet to bump all the files in /etc/yum.repos.d
except cobbler-config.repo into a subfolder (I call mine 'deprecated')
and then only the repos from the $yum_config_stanza will be available.
If you have specialty repo mirrors like those from PostgreSQL, setting
them to an even lower number (say 50) will have you pulling in the
latest pgsql and not the old version from the distro's repo
(dependency hell may found in that direction if not careful)
*I have not found a way to prevent their initial deployment without
making manual changes to the distros
Ed