similar to: Puppet Windows: msi packages removal

Hi, am trying this rule: firewall { ''100 allow ssh from GUNET'': proto => ''tcp'', dport => ''22'', source => [''10.0.0.0/8'',''192.168.0.0/16'',], action => accept, } and it only seems to add a rule for the first subnet. The second is silently

Sorry for being off topic. am trying the following and yaml fails to construct the object: The inventory document, from Puppet dashboard inventory service, looks like: --- !ruby/object:Puppet::Node::Facts name: pirates.uis.example.com values: productname: VMware Virtual Platform kernelmajversion: "2.6" My code: class PuppetFacts(yaml.YAMLObject): yaml_tag =

Hi Team, Tried following the steps here http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows for deploying an agent on windows (windows server 2008 r2) but really finding it hard to make it work (the agent deployment itself went fine after following the steps). I have a working puppet-server on RH 6 and have tested few RH clients which work fine. The very first hurdle is that i

C:\Users\ml623>puppet --version 2.7.7 Puppet complains about a package resource I am trying to use saying: Invalid parameter install_options The resource is defined as: package { "splunk": name => $gu_splunk::client::splunk_package, provider => ''msi'', ensure => installed, source =>

Hello list, I am having a problem with template file. Why are variables not interpolated? [root@puppet manifests]# cat /etc/motd memory free = <%= memoryfree %> domain = <%= domain %> operating system = <%= operatingsystem %> This is the template file [root@puppet manifests]# cat ../templates/motd.erb memory free = <%= memoryfree %> domain = <% domain %>

I''m trying to use something like this... package { "blah": ensure => "1.2.3*" } ...and I know that doesn''t work because it looks for a package literally with that value "1.2.3*". What I want is to say, install the latest package in the 1.2.3 branch but don''t automatically upgrade to anything later than that. e.g. 1.2.3-01, 1.2.3-05

Hey guys. I am starting out with puppet and am in the process of writing a bootstrap script for the clients and a capistrano recipe for the server. I have the client bootstrap done which installs ruby, puppet, sets a host name, and then points the client at the puppet server and now I am in the process of setting up the puppet server. My first attempt was to set up a git project for puppet, an

I thought I read somewhere in Puppet docs/wiki... that it is "recommended" to avoid spaces in file paths, or some similar verbiage, but now I cant find it. Does Puppet have any known issues with spaces in file paths? It would of course scare Windows admins away... So I hope I am wrong in thinking I read that. Thanks a lot, Mohamed. -- You received this message because you are

In our environ, there are several services that are deployed via an NFS mount, so that the executables and configs are consistent across the board. Is there any reason why this couldn''t be done with Puppet? For example, each individual system would contain its own /etc/puppet and rc.d and pid files -- but the primary deployment would come from NFS. For that matter, as Enterprise

I have this in a template: ===============cut here===================== # Allow ICMP traffic -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT <% if netbackup_master_servers %> <% netbackup_master_servers.each do |master_server| -%> # Allow communication with NetBackup master server <%= master_server[0] %> -A RH-Firewall-1-INPUT -p tcp -m tcp -s <%= master_server[1]

What does this message mean: [root@pirates puppet]# rm -rf /var/lib/puppet/ssl/ [root@pirates puppet]# puppet cert --version 2.6.3 [root@pirates puppet]# puppet cert notice: Signed certificate request for ca notice: Rebuilding inventory file Invalid method to apply It seems to have created the ca and other things just fine. Thanks, Mohamed. -- You received this message because you are

Hello all, This is not a puppet proper issue of course.. but I was wondering if any of you could share some thoughts... When you deploy a system like Puppet at a large park of systems, you instantly increase the efficacy of mistakes and bugs in destroying the environment.... How do you deal with that? I would be interested in any experience or input, especially puppet proper best practices...

I could swear this worked fine earlier.. Now facter, and hence puppet, do not see the domain name anymore: What could cause this? C:\Temp>facter --version 1.6.2 C:\Temp>facter | findstr kernel kernel => windows kernelmajversion => 6.1 kernelrelease => 6.1.7601 kernelversion => 6.1.7601 C:\Temp>facter fqdn NCS-VDI-05.none C:\Temp>facter hostname NCS-VDI-05

Is it normal that "facter --puppet" does not show the environment variable? is there a way to have it include it? Thanks a lot, Mohamed. -- 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

Hello All, I am trying to put puppet into push mode only. The instructions I''ve seen have said to put listen=true in puppet.conf but that doesn''t seem to have stopped the pull every 30 minutes. What else needs to be set? Thanks, Jim -- “Twenty years from now you will be more disappointed by the things that you didn’t do than by the ones you did do. So throw off the bowlines.

We are using ruby-entreprise, instead of redhat''s default ruby.... I was trying to deploy the needed gem using: /opt/ruby-enterprise/bin/gem install --no-rdoc --no-ri /tmp/ruby-augeas-0.3.0.gem But found out this would require gcc to be installed! How can I preb-build this gem to remove the need for gcc on the nodes? is there an option of the gem command to generate a distributable

Hi guys! I need configure one command exec with onlyif parameter. I want test file size exist or no. Ho i do this? Tks in advanced. Douglas -- 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

Anybody knows what this error, bellow, means, the target file, C:/Splunk/etc/system/local/inputs.conf, does exist. sometimes, if I delete the file, it does actually create it, but never update it if it exists and changed... The resource is defined as:     file { "splunk_inputs":        owner   => SYSTEM,        group => SYSTEM,        mode    => 664,        require =>

am I doing something wrong? this seems to never find my .$env file: source => [ "puppet:///modules/gu_puppet/puppet.conf.$fqdn", "puppet:///modules/gu_puppet/puppet.conf.$environment", "puppet:///modules/gu_puppet/puppet.conf.$operatingsystem", "puppet:///modules/gu_puppet/puppet.conf" ] It

A little while back I asked how to make puppet not report on a resource.. and was shown the loglevel metaparam: Quoting bellman@nsc.liu.se: There is a metaparameter called ''loglevel''. If you set that to something lower than "notice" (i.e. either "info" or "debug"), then Puppet won''t report that it applied the resource... So I made my