Okay, I'm stymied. I set up a rule to kick a new .repo file out to
my
clients into /etc/yum.repos.d/ called 'lwm.repo'.
The rule says:
class lwm-repos{
file { "/etc/yum.repos.d/lwm.repo" :
owner => "root",
group => "root",
mode => 444,
On Apr 13, 2:23 am, Patrick wrote:
> It looks to me like yum itself is broken. Try installing something using the
> yum command-line client.
Oddly, it looked like we had a problem with one of the repos (404
error), which somehow trickled all the way back. I also put in the
'refreshonly=>true'
Wait, scratch that, ignore this. I still had the module commented out
in nodes.pp
Sorry for the false alarm! Updates are running correctly! Stand
down!
(thanks to everyone for their help on the repos - we seem okay now)
On Apr 13, 9:24 am, dbs wrote:
> On Apr 13, 2:23 am, Patrick wr
I've been banging my head against the wall on this one for a while,
and
I think I just figured it out.
I had configured my puppet clients with namespaceauth to allow
puppetrun
from the puppetmaster to force an update. The problem is, anytime I
ran
the puppetrun command, I'd get:
d...@bos-occam01
Just to put my $0.02 in... the 'exec' command is similar in my setup -
but I do a little bit of maintenance as well (like a customized
lsassd.conf file) - Note I also unwrapped the .rpm files so I could
put them in a serviced repo... :
class likewise {
$rpmlist = [ "likewise-lwio",
We need to make sure all our MySQL servers have a specific user /
password / grant setup available (this is because we use centralized
monitoring via Zenoss, and Zenoss needs a login on all the servers).
I found a github reference to a package that might do it (
http://github.com/camptocamp/puppet
On Jun 13, 11:39 am, Jens Meydam wrote:
> We have invested heavily in virtualization infrastructure, in
> particular VMWare ESX. How well does Puppet work with VMWare ESX? I
> have found some material, but not as much as I hoped for. I am
> wondering if this is perhaps a combination we should b
I have a 3 different puppetmasters running different groups of
machines (dev, testing, and production). I'd like to very simply say
"Give me a brief summary of the status of the nodes you manage."
I've been having nightmare dependency problems trying to get things
like Dashboard running that seem
