similar to: Puppet fails but succeeds on the 2nd attempt

I am trying to add ability to add virtual users to the git://github.com/erwbgy/puppet-system.git module as I really want the ability to use virtual users and then combine that with "User <| group == ''x'' and group == ''y'' |>" way of realizing the users. This is much more flexible than what I can do with this module out of the box. Using the

I need to programmatically remove cert from Puppet master and remove all information in Puppet DB for a node from another machine which is neither Puppet Master or PuppetDB. It does have a Puppet signed cert since it is also provisioned using Puppet. I can''t find any decent documentation on this. I am using the Community Edition. Any pointers / help is appreciated. Rajul -- You

Trying to figure out the erwbgy/system plugin and just getting stuck.. first run it did some changes, but it ignored parameters for ntp and now its not refreshing if I update the yaml at all, Im slightly lost at what I may be missing :) hiera.yaml --- :hierarchy: - %{certname} - %{environment} - global - %{environment}/common :backends: - yaml :yaml: :datadir:

So, I''m reading that this works, but I''m obviously missing something somewhere, cause its not... I''m testing a masterless setup, and thus far, pluginsync isn''t doing anything. my puppet.conf looks like [main] vardir = /var/lib/puppet logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl classfile = $vardir/classes.txt

Hello all, I''m running puppet for the first ime. I''ve finished the install but I''m stuck at the certificate part. The puppet master (0.24.4-3) is running on Ubuntu Lenny and the puppet client (0.24.8-4.el5) is running on CentOS 5.3. After the install, from the client side, I''ve run: puppetd --server puppetmaster.domain.com --waitforcert 60 --test On the

I am trying out having multiple environments so that I can push a test config to a single server in production. The idea being that I could push out a config change to one server and see if the change works in production. If it does then I can merge the change into the production environment and push the change out to all the clients. So to test this I made a change to a config file in testing

I''ve ran into a strange issue today while using my development environment I was receiving some errors about modules that shouldn''t have been used. After looking it looks like my agent (or master) isn''t respecting the environment I specify and is actually using the main (master) environment. This used to work and I haven''t had any changes beyond a upgrade ..

Hi, I''m trying to use Puppet ability to export and collect resources using PuppetDB. My PuppetDB and Puppet Master are running on the same host and I used the PuppetDB puppet module to install PuppetDB and configure the Puppet master. Each time the puppet agent runs on a client, the facts and the catalog are being pushed in PuppetDB and I can query the PuppetDB server to get

Hi all, I have installed and configure puppet client in new virtual machine, but I have this error when running *puppetd --test (even if I run /etc/init.d/puppet restart) /usr/lib/ruby/1.8/puppet/defaults.rb:136:in `handle'': Invalid environment test (ArgumentError) from /usr/lib/ruby/1.8/puppet/util/settings.rb:299:in `parse'' from

Dear all, I have RedHat Server with Puppet and logging in /var/log/puppet But on Solaris it does not work. I am using the CSWpuppet3 3.3.1 Do you have an idea? cat /etc/puppet/puppet.conf # puppet.conf [main] logdir = /var/log/puppet confdir = /etc/opt/csw/puppet config = $confdir/puppet.conf vardir = /var/opt/csw/puppet ssldir = $vardir/ssl server =

Puppet 3.0.1-rc1 is a bugfix release candidate for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.1 version in our issue tracter at: https://projects.puppetlabs.com/versions/328 Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.1-rc1.tar.gz RPMs are available at http://yum.puppetlabs.com Debs are available

Puppet 3.0.1 is a bugfix release for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.1 version in our issue tracter at: https://projects.puppetlabs.com/versions/328. This release contains contributions from the following people: Andrew Parker, Jeff McCune, Josh Cooper, Matthaus Owens, Moses Mendoza, Nick Fagerlund, Niels Abspoel, Patrick

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Hello, I have been following through some of the documentation trying to make use of puppet in a test environment. I went ahead and tried to install puppet-passenger and puppet dashboard. I think i have succesfully done this, because at mymaster.local:3000/ I get the dashboard webpage (albeit with no nodes or anything reporting) and at https://mymaster.local:8140 I get a cert trying to be

Hi I am a newbie to puppet. I have tried an initial config serving a simple file & dir from the puppetmaster, but the client will not mount. What obvious mistake am I making, I wonder? puppetmaster is a DNS alias for osiris3. Config files: [root@osiris3 puppet]# cat fileserver.conf [config] path /data/puppet/manifests/files allow *.pinnacle.co.uk [root@osiris3 puppet]# cat puppet.conf

Hi, ppl I dont know what to do. I configure a new client do sync with my server. the server accept de client_cert without errors and then when i run the "puppet agent -t" agaion i got this error output info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server

Puppet 3.0.0-rc5 is a feature release candidate for the 3.x series of Puppet. Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.0rc5.tar.gz RPMs are available at http://yum.puppetlabs.com Debs are available at http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.0.0.rc5.gem or by using `gem install --pre

This was my very first post to the lartc mail list... but mailman replied saying there was a problem delivering the message to the recipients... and as I got NO replies at all, I guess no one received it. So I decided to resend it to see if there''s anyone to "bring me into the light" on this one. ;) Can anybody help here? ---------- Forwarded message ---------- From: Edmundo

Hi, I'm trying to solve this one: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615797 As much as I can tell, and unless I have missed something, the issue is a missing -lpulse in the Makefile.target (see attached diff file that fixes the issue). While my patch makes it compile again, I fear that I'm not doing well, and that there must be a better way to fix, that would take care of

Hi, I'm trying to solve this one: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615797 As much as I can tell, and unless I have missed something, the issue is a missing -lpulse in the Makefile.target (see attached diff file that fixes the issue). While my patch makes it compile again, I fear that I'm not doing well, and that there must be a better way to fix, that would take care of