Machines not using local mirror

[Bai Shen]

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?

Thanks.

[Denmat]

Hi,

Cobbler can put the desired repo in /etc/yum.repo.d - but I have in the past explicitly cleared that directory (from the cobbler post install (kickstart really)) and managed the repos via puppet only. 

First thing puppet did was install the right repo. It was the cleanest way I found.

HTH

Den

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

[jcbollinger]

Puppet just invokes the host's native package management tool with appropriate options for managing the specified package.  For instance, "yum  -y --install foo" on a yum-based system.  You should be able to see the actual command Puppet issues by turning on debug output.

If you need a different command or extra options then you'll need to explain that to Puppet.  On the other hand, if you expect the command Puppet is issuing to do what you want, then probably something is screwed up with your repository configuration.  You should review the config files, and you can test by issuing appropriate package management commands manually.

A repository misconfiguration might arise from many sources, but in the simplest terms, if your repositories are not configured correctly then either your Cobbler configuration is wrong or something else (maybe Puppet) changed the repository configuration after provisioning.  Puppet only manages things you explicitly tell it to manage, so if it has modified your repo configuration then that's because of something in one of your Puppet manifests.


John