similar to: Variables available in configs...

There''s a problem installing puppet on Solaris 10 -- in this situation, we aren''t really doing anything with puppet there. The version we''re using is: ruby 1.8.7 (2011-02-18 patchlevel 334) [i386-solaris2.9] Here''s the first error: # gem update puppet > > Updating installed gems > > Updating puppet > > Building native extensions. This

Group - I''m putting a presentation together for $work (a large .gov) and I want to make sure I get my facts (pun intended) straight ... Are the following steps for Facter-Client-Server interaction correct (I have a feeling not): 1. Client puppet run is initiated (via regular schedule, puppetrun, or puppetd) 2. The client contacts the server and downloads any custom facts it does not

Folks, I''ve been looking at creating a set of man pages for puppet and I''m trying to come up with a reasonable hierarchy. I''d appreciate any suggestions. So far, here''s what I''ve come up with: - puppet(1) - puppetca(1) - puppetdoc(1) - puppetrun(1) - puppetca.conf(5) - puppetd.conf(5) - puppetmasterd.conf(5) - puppetd(8) -

So when puppetd crashes/whatever, and a pid file is left behind, SMF in Solaris will try restarting puppet, but fail. And then it sits there restarting it forever. I''m not sure if I can adjust the flap detection in SMF.. it isn''t disabling the service for "restarting too quickly" because it takes so long to start. Probably because I''m NFS-mounting ruby. The

Hey there, I''m new to hiera and I'' m looking to configure it to use multiple environments. I''m able to query hiera keys from using the hiera CLI, however my clients seem to be having problems identifying the look up variables. *On the puppet master, CLI query* [root@puppet-dev puppet]# hiera -a sshpackages environment=development ["openssh",

"Service and class definitions are scoped just as variable assignments are." But what about types? Here''s an example: class solserver inherits server { remotefile { "/etc/shadow": mode => 400, group => staff, source => "solall/etc/shadow.server" } Is it possible to just override the "/etc/shadow" definition for

Hello... I need some help with tags. as an example: # pseudo code class ssh { file { "/etc/ssh/ssh_config": # normal stuff tag("dangerous") } file { "/etc/ssh/sshd_config": # normal stuff tag("dangerous") } file { "/etc/ssh/ssh_known_hosts": # normal stuff tag("safe") } } on client: puppetd --tags

I have this config: # BL00070 - Disable NFS service {["nfs","nfslock","netfs","portmap"]: ensure => stopped, enable => false, } user {"rpc": ensure => absent, provider => "useradd" } user {"rpcuser": ensure => absent, provider => "useradd" } file

Hi all, Not sure if this is a bug in puppet, yum, or just something I''m doing wrong. I''m trying to use puppet to update a package to a particular version and exec a command when that update is applied. The problem is, puppet calls yum which successfully updates the package, but puppet then thinks the update has failed and hence doesn''t trigger the exec. Next

$ puppet --help /opt/csw/lib/ruby/gems/1.8/gems/puppet-0.20.1/bin/puppet:103: undefined method `feature'' for Puppet:Module (NoMethodError) from /opt/csw/lib/ruby/1.8/getoptlong.rb:460:in `each'' from /opt/csw/lib/ruby/1.8/getoptlong.rb:457:in `each'' from /opt/csw/lib/ruby/gems/1.8/gems/puppet-0.20.1/bin/puppet:97 from /opt/csw/bin/puppet:18

Is there a Best Practices method for doing this? :) I''m trying to configure clients by ssh''ing to them from the puppetmaster. My steps are: ssh $host ''svccfg import ...'' sleep puppetca --sign $host scp namespaceauth.conf $host ssh $host ''svcadm restart puppet'' The problem is that I''d like to stop and log an error if the cert signing

Hello, I would like to know on what platforms Puppet runs. I cannot seem to find the information on Puppet''s web site. Bcfg2 has it on it''s front page :-) I know there are .debs and .rpms, but are, for instance, Solaris, FreeBSD and AIX supported? Thanks. -- Guillaume Pratte Recherche et développement Révolution Linux Toutes les opinions et les prises de position

Hi, I''m having trouble getting puppetrun to work, it returns: # puppetrun --debug --host serverb debug: Puppet::Network::Client::Runner: defining puppetrunner.run Triggering serverb debug: Calling puppetrunner.run warning: peer certificate won''t be verified in this SSL session err: Could not call puppetrunner.run: #<RuntimeError: HTTP-Error: 500 Internal Server Error >

Hi, I want to introduce "Proxmox" as new value in $::operatingsystem. "Proxmox" is based on Debian, so the normal value is currently "Debian". To change that, I just write a custom fact based on the facter fact "operatingsystem" Facter.add(:operatingsystem) do > ... > setcode do > ... > elsif

Just upgraded to 2.7.6 and the yumrepo type does not write out our yum configs correctly, anyone experiencing this? Documentation hasn''t changed from what I can tell for this type. # facter -version 1.6.2 # puppetd --version 2.7.6 # facter architecture x86_64 # facter operatingsystem Fedora # facter operatingsystemrelease 14 ==== My manifest ==== yumrepo {

I''ve run into an odd one on one of my new RHEL 6 boxes. Puppet and Facter seem to disagree about the value of a fact. Puppet version: 2.7.9 Facter version: 1.6.4 Module: puppetlabs-apache apache::params falls through its if structure: if $::osfamily == ''redhat'' or $::operatingsystem == ''amazon'' { ... } elsif $::osfamily ==

Hi all, I''ve finally gotten around to releasing Facter 1.5. As the version bump implies, this is a relatively significant release (for a 2.3k line program, anyway). Mostly, the biggest change is refactoring the code internally so that all of the functionality is split into separate classes in separate files. Also, the facts are all loaded on-demand, which provides dramatic

I''ve got a single puppet master (2.7.19 + facter 1.6.11) controlling a number of nodes (2.7.17 + facter 1.6.8-10). On all of thse, fact absed variables work as expected (such as $::operatingsystem and $::fqdn). However, on my puppet master, when I run ''puppet agent --test'' all fact based variables are combing back as empty strings. For example. I have a line in a

In the documentation, there is an example such as this: case $operatingsystem { sunos: { include solaris } # apply the solaris class redhat: { include redhat } # apply the redhat class default: { include generic } # apply the generic class } I''ve seen the $operatingsystem variable used elsewhere. What actually puts the value into the $operatingsystem variable? Does

Hi, I''ve just changed my debian preseed configuration to install the debian unstable package of puppet v0.22.1. As part of the preseed I have a late command that clobbers the /etc/init.d/puppet file into using the puppet standalone program and not the puppetd (as this is what I''m using). Since the upgrade to 0.22.1 every boot hangs during the initd. Going into standalone mode