1

modules not getting processed by puppet-agent

view story
linux-howto

http://serverfault.com – On our puppet box ( under the puppet/modules folder ) , I have added a module for installing a package. I then added the classes needed for the resources into the init.pp ( and other derived class files ) into the manifests folder. I configured these classes and the corresponding nodes associated with them in the puppet dashboard. When I run puppet-agent with the environment flag , I see that puppet does not run my module. It is running couple of other modules defined similarly on the box alongside my module , but not my module. What configuration is needed so puppet-agent picks up a module (HowTos)

taskli's picture
Submitted by taskli on 01/08/2013

Stories similar to modules not getting processed by puppet-agent

I am attempting to use Chocolatey ( http://chocolatey.org ) as a package provider for Puppet, but I continually get this error when running the Puppet agent on my Win 7 box.

i'm on a ubuntu machine when i fail to install jenkins with puppet with the following error:

/etc/puppet/modules/jenkins/manifests# puppet agent --no-daemonize --verbose notice: Starting Puppet client version 2.7.1 info: Caching catalog for fqdn.myhost.com err: Could not run Puppet configuration client: Parameter unless failed: 'apt-key list | grep -Fqe 'D50582E6'' is not qualified and no path wa

Puppet agent freeze on Ubuntu 30 weeks 2 days ago

I have 40 Ubuntu 12.04 servers. These servers are managed with puppet. Sometimes I have problem with puppet agent. puppet agent spawn child process (sh) and this process fails. Sh is zombie process. Puppet doesn't work, I must restart puppet agent to make it works.

I use puppet to manage files, packages and services. Problematic agent didn't make any change before fails, server is up to date.

I am trying to run a script with puppet.

Prefix: I searched this out, but the fact that there are any number of things that can cause this problem, I have been unable to find a solution to this particular case.

I have a puppet master (3.0.2-1; RHEL6) and the /etc/puppet/manifests/site.pp file contains the following:

import 'nodes/nodes.pp' $puppetserver = 'puppet.example.dom'

Naturally, the server domain is not what is in use, but ha

I've got a file that notifies the puppet agent.

In the network module, the proxy settings are included in the .gemrc file like this:

file { "/root/.gemrc": content => "http_proxy: $http_proxy\n", notify => Service['puppet'], }

The problem is that puppet stops and does not restart.

Aug 31 12:05:13 snch7log01 puppet-agent[1117]: (/Stage[main]/Network/File[/root/.gemrc]/content) conten

After upgrading a node to Puppet 3.0.0 from the Puppet Labs YUM repository, the node that gets upgraded throws a munging error: [ashinn@dis1 ~]$ sudo puppet agent --test --trace Error: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: Parameter path failed on File[/var/lib/puppet/state/graphs]: Munging failed for value "/var/lib/puppet/state/

Quick brief - for testing purpose, I installed puppet agent on 5 nodes (Debian Squeeze + puppet 2.7.20-1puppetlabs1), and puppet master on 1 server (same version).

On puppetmaster side in every manifest I check if $::osfamily == 'Debian'.

Running into an issue using two VM's running REL6. I set up the master and agent correctly and was able to cert the agent.