similar to: Slight oversight in the type documentation

No problem installing open puppet and using it. patterns run aok. when trying to use the installer for pe, on the puppetmaster, installs ok. when trying to use the installer for pe, on the puppet agent, installs ok but no cert sent as shown by puppet cert list on puppetmaster. also puppet agent --test on puppet agent shows err: could not retrieve catalog from remote server: error 400 on

Now that the install_options parameter can be applied to all package providers, does anyone have advice on the best way to specify options to yum? For example, considering the common pattern of leaving a repo disabled most of the time, if I wanted to pass --enablerepo=epel to yum, would I set install_options => [''--enablerepo=epel''] or install_options =>

Just started a rollout of centos 6.x across our Puppet deployment (100-odd servers). what fact would people suggest I use to distinguish 5.x from 6.x (quite a lot of subsystems are different between major releases)? lsb* facts don''t seem to be present on centos 6 - is this an EPEL bug, or have they just been removed in Facter? Thanks! -- You received this message because you are

0.25.5 changed the default vardir from /var/puppet to /var/lib/puppet and it''s caused the odd issue we have to fix in the Mac pkg preflights. After re-reading ''man hier'' I''m tempted to change the default on OS X to: /var/db/puppet instead. /var/ multi-purpose log, temporary, transient, and spool files ...

Hi, I needed a function to check if a file is existing on the Debian box I am configuring. So I used this one module Puppet::Parser::Functions newfunction(:file_exists, :type => :rvalue) do |args| if File.exists?(args[0]) return 1 else return 0 end end end It work greats for some service where apache2 doesn''t work for me. I am using it this way

I have a freshly installed and updated CentOS 5.4 system running puppet 0.25.5. I followed the passenger docs here: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Passenger Upon starting the client, the following appears in the apache error log. [Thu Jun 24 10:48:40 2010] [error] [client 10.10.4.45] Premature end of script headers: production [ pid=6785 file=ext/apache2/Hooks.cpp:706

Dear community, I use puppet to deploy iptables on every server. This is working fine. In the manifest I defined an iptables service which leads to my init script. The thing is each time I run puppet I got : notice: /Stage[main]/Iptables/Service[netfilter]/ensure: ensure changed ''stopped'' to ''running'' I would like to add a status command to my startup script

So, I''ve been looking into the params pattern for writing modules, ie. having a params.pp file that init.pp inherits from as a place to use custom logic to set variables, and it seems very useful. I do have one question that I''m hoping someone can answer. If, for example, I look at an example42 module, everything is in params.pp. On the other hand, looking at, say,

Hi! Which database would you recommend to use mysql or postgresql for puppet? Estimated number of nodes 30000, they send reports every 30 minutes. Thanks -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to

Was... Bash$ puppet node create This "create" action no longer exists. Has it been depreciated? Is the only way to create a node through puppetmaser now? Thanks, D -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/g3lJoO-j_u4J. To post

Has anyone used facter to gather and build host specific yaml files before, was wondering how others were gathering and building this info for their host. Any suggestions are appreciated. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group,

Hiera-Puppet 1.0.0rc1 is a feature release candidate designed to accompany Puppet 3.0 and Hiera 1.0. It includes Puppet functions for hiera and also the puppet backend for hiera lookups. Downloads are available: * Source http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0rc1.tar.gz * Apt and yum development repositories * Apple package

Hi, It''s easy enough to modify, say, the "exclude" variable in /etc/yum.conf with something like: augeas { yum_exclude_kernel: context => ''/files/etc/yum.conf/main'', changes => ''set exclude kernel*'' } However, I''d like a more flexible system where I can "build" the list of excludes from

I upgraded Puppet master from 2.7.6 to 2.7.20 on CentOS5.8_x86_64. But when I tried to launch ''puppet agent -t'' on one of staging servers, the puppet daemon did not work and got heaps errors. I have no idea what made it wrong and how to fix it. Retrieving plugin [0m Failed to generate additional resources using ''eval_generate: Error 500 on SERVER: <!DOCTYPE HTML

I see that there are an assorted bunch of "provider" types for resource type user. Are there not any "local file" providers for it? I have need of ensuring that certain local user accounts get created on all machines, reguardless of what the system "/bin/password" and "useradd" type mechanisms are set to. It would be really nice to find a pre-written

I currently have a child class of a parent one. The parent defines some variable that I need to use in the child class. I am also using gepetto. Gepetto is complaining about the syntax of the child variable. It is saying that "$parentVar" should be "$::parentVar" however, when changing to what Gepetto wants to use this breaks my classes. Does anyone know the proper

Hi all, I''m interested pushing my user list out of my users manifest and into Hiera. Unfortunately I haven''t been able to get it to work the way I thought it would. The error suggests that perhaps create_resources cannot create virtual resources, but the docs I''ve read so far don''t address it. The class (in init.pp): class users { $system_users =

Hi all, Using Puppet 2.5, I have a class which creates users: # cat modules/users/manifests/init.pp class users { user { ''ringo'': ensure => present, uid => ''1506'', groups => [''admin''], shell => ''/bin/bash'', home => ''/home/ringo'', managehome

I''m trying to use create_resources to create a series of files with semi-custom content based on a template. This is what I have: foo.conf.erb: Name "<%= name %>" WorkingDir "<%= working_dir %>" ... a bunch of static entries YAML: configs: config1: Name: app1 WorkingDir: /var/app1 config2: Name: app2 WorkingDir: /var/app2

PuppetDB 0.9.2 is the third beta release on the road to 1.0. Changes include new features and bug fixes. For details on changes in this release, please see the release notes below. # Downloads Available in native package format at http://yum.puppetlabs.com http://apt.puppetlabs.com Source (same license as Puppet): http://github.com/puppetlabs/puppetdb Available for use with Puppet