similar to: learning, but puppet does not detect change

I know this comes up periodically, and I''ve read through the wiki (including the Best Practices page) & list archives, but still can''t quite get my head around it. I see lots of references to /modules and $MODULE_PATH, but am not sure what these refer to. Here''s a basic setup I have. Let me know if this looks correct: /etc/puppet/ |-- autosign.conf |--

my base/default includes this ntp manifest # cat modules/ntp/manifests/ntp.pp # ntp.pp class ntp { case $operatingsystem { centos, redhat: { $service_name = ''ntpd'' $conf_file = ''ntp.conf.el'' } debian, ubuntu: { $service_name = ''ntp'' $conf_file = ''ntp.conf.debian'' } } package {

I''ve gone over the documentation several times now and I can''t figure out how to ''apply'' a manifest to a client. The client does have a signed certificate but the only thing in the /etc/puppet folder on the client is an ssl directory. I have a manifest that works fine on the puppet ''master'' I have added the client into

Hi, We are totally sold on Pupet (what a nice concept) and are trying to setup a proof-of-concept. We are trying to learn a bit from other people''s work by integrating external modules. One of the modules we wanted to start with was the ''ntp'' module from David Schmitt. It clearly uses some functionalities from the ''common'' module, which we also

This is in reference to David Schmitt''s writeup [1] I like that writeup a lot; I just had a few comments/clarifications: * Namespaces: For now, we just use a flat namespace for modules, i.e. you can''t have modules within modules, and you always know that in a fully qualified name ''foo::bar::baz'' that ''foo'' is the module name and

I''ve seen mention of this error in several places, with different causes. So before I posted here, I attempted to resolve this on my own. I corrected the change from puppet:///files to puppet:/// in my manifests *.pp files. No changes were made to the auth.conf file, and I did note in the ChangeLog that: Auth.conf differentiates between names and IPs – There’s a new allow_ip

Hi all, I think i''m forgetting something. If i do: "puppet apply manifiests/site.pp" it works perfectly, loading modules i have include in site.pp file. site.pp: cat manifiests/site.pp node default { include ntp, motd } But it does not work if i run puppet agent. puppet agent --test --server=debianita.user.arinso --environment production Info: Retrieving plugin Info:

I''m trying to try out puppet and can''t seem to get to square one. I''ve been using cfengine for years and have just upgraded about 80 Debian machines to etch and wanted to try puppet. So, I have two Debian ''etch'' machines one a server and the other a client. I''m running puppet 0.23.2 installed from the unstable packages. As a first step

Hi there, After quite a long time out of puppet business I''m back, and the first thing I''m doing is rephrasing my puppet manifests using modules. I started with the NTP module (a classic, I guess). I have (more or less) the following: In modules/ntp/manifests/init.pp: $ntp_localtime = "/usr/share/zoneinfo/Europe/Madrid" class ntp { ... some stuff using the

Hi, How would I do this: wgetfile { "$name-$file": url => $url, file => $file, target => $target, options => $options, before => Component["md5check-$name"] } wgetfile { "$name-$md5file": url => $url, file =>

Hi I''m having the following problem and tried already several workarounds, as well benp- tried to help me on irc. I copied the ntp modul from DavidS repo and adapted it in the Service part to run as well under openbsd. Which was just adding some binary if openbsd is the operatingsystem. However then I wanted to run it as well on a gentoo system (on centos, debian and openbsd it was

Hello folks, I''ve blended/updated the Glossary of Terms (<http://reductivelabs.com/trac/puppet/wiki/GlossaryOfTerms>). It seems the definition of "manifests" is a bit different amongst members. Some people consider a "manifest" to be a configuration file written in puppet, e.g. any .pp file. But at my organization, we''ve considered the totality

I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now at 3.0.0. Not sure if this is a version change or syntax error that I am experiencing. We''ll use ''ntp'' as the example and the "build" host is a VM. The old way: class baseline::ntpd { package { "ntp": ensure => $virtual ? { physical => present,

Hello folks, At Stanford, we use modules to define every possible service, package, feature in the traditional sense (apache, ntp, iptables, etc). Then, for clients (such as other departments) and "services" (such as our mailman infrastructure, our ldap infrastructure, etc), we use manifests in /master/manifests and distributable files in /dist/ and templates in /master/templates.

Hi all, I have a slightly confusing Problem with fileserving. # /etc/puppet/manifests/classes/ntp.pp class ntp { file { "ntp.conf": path => "/etc/ntp.conf", source => "puppet://$puppet_server/files/ntp.conf", ensure => present, mode => 644, owner => root, group => root, } } Creating missing Files

I upgrade our infrastructure (mostly RHEL5, some RHEL6) from 3.1 to puppet-3.2.1-1.el5. Ruby sits at ruby-1.8.7.370-1.el5. I ran some tests and everything seemed good so I pushed it out. Since then, all my puppet clients are failing with this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `[]'' for nil:NilClass at

hello, we just wanted to rollout our new puppetized dmz. therefore i change all ip adresses from the test network to the live ips. after restarting puppetmasterd it seems that the fileserver hangs: client log: debug: //true_base/update-check/File[/sbin/update_check.pl]/require: requires Package[libmail-sendmail-perl] debug: //true_base/puppetd/File[/etc/puppet/puppetd.conf]/require: requires

Hi, I have been fighting this issue without success for several days. I am sure some of you have dealt with something similar: I have 2 manifest one for vim which works like a charm : class vim { if $operatingsystem == "Debian" { package {"vim": ensure => present, } package

I have these three modules with the following structure: |-- modules | |-- create_resources | | |-- LICENSE | | |-- Modulefile | | |-- README | | |-- lib | | | `-- puppet | | | `-- parser | | | `-- functions | | | `-- create_resources.rb | | |-- spec | | | |-- spec.opts | | | |-- spec_helper.rb | | | `-- unit

So far we have a similar situation, for each different server one fabric and one puppet file, where the fabric file simply applies it in a brutal way. with settings(user=''root''): put(''qa.pp'', ''qa.pp'') put(''puppet apply qa.pp'') And puppet files don''t use anything like classes or modules, but