search for: no_such_tag

...p; puppet_unit=puppetagent /usr/bin/systemctl enable ${puppet_unit} /sbin/chkconfig --level 345 puppet on # export a custom fact called 'is_installer' to allow detection of the installer environment in Puppet modules export FACTER_is_installer=true # passing a non-existent tag like "no_such_tag" to the puppet agent only initializes the node /opt/puppetlabs/bin/puppet agent --config /etc/puppetlabs/puppet/puppet.conf --onetime --tags no_such_tag --server urzlxdeploy.rz.uni-leipzig.de --no-daemonize sync # Inform the build system that we are done. echo "Informing Foreman...

Hi, I was at the Puppet talk at Oscon and I would like to try using Puppet for PXE on RHEL machines and I was wondering if there are standard minimal Kickstart recipes from which Puppet can then take over. Thanks, Jason van Zyl jason at maven.org

I install puppet as part of a Fedora and CentOS kickstart install and this use to provide a nicely configured client immediately after the first reboot from the kickstart completion. However with 0.22.3 i now see the following error on puppets 1st run, as a result the client is not configured. The problem is easily rectified by connecting to each client and restarting puppet. I have also

As I sit here staring at my manifests (and pondering a module to control Glassfish), I''m pondering the best way to do a first-run of puppet to get the initial repositories and puppet configuration downloaded. My theory is that I''ll modify rc.local (or replace firstboot-tui, we don''t use it with automated builds) to run puppetd twice - once to request the certificate,

Hi guys, I''m installing Puppet on RHEL5 systems using KickStart but struggle with the first boot. Here''s my situation: 1) kickstart installs the system, including puppet from our local repo 2) after reboot I have to login and set the hostname and IP 3) then run puppet, register it with the server and bring in the config 4) configure puppet for automatic start I have to