similar to: template does not print variables

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

I noticed that is if I uninstall an MSI that was installed by Puppet, Puppet does not notice. Looking at the source I see it might be checking for a state file to know whether a package is installed or not: C:\ProgramData\PuppetLabs\puppet\var\db\package\msi\SplunkForwarder.yml So one has to rememebr to delete that too.... Is this design not a problem? Thanks, Mohamed. -- You received this

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 {

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

Hello I have been using puppet for a while now, more or less successfully on SLES 11 and CentOS 5.5 currently I am using puppet 2.6.6 I now am trying it out on redhat 6, and now i run into an problem with even the simplest of modules/classes The error I get is : debug: /Stage[main]/Motd/File[/etc/motd]/content: Executing ''diff -u / etc/motd

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

Hi all, I''m trying to build a motd template for all my linux machines. This should contain two type of variables: - client side (from facter), like operatingsystem and architecture - supplied by the master, after parsing a text file (or querying a mysql db), like description and location. So. Where are the template variables evaluated? On the client or on the master? Any hints on how I

I have 2 RHEL 5.4 systems where all facter lsb* items are missing. Any ideas? Sanitized facter output: architecture => i386 domain => missyou.edu facterversion => 1.5.7 fqdn => broken.missyou.edu hardwareisa => i686 hardwaremodel => i686 hostname => broken id => root interfaces => eth0,sit0 ipaddress => 1.2.1.5 ipaddress_eth0 => 1.2.1.5 is_virtual => true

Hello, I did make a stupid fault: not commiting changes to version control :-( After the installation of puppet-dashboard, I added a recipe to add report = true to puppet config files on clients. Now all Puppet clients don''t update because of an error... What can be the various reasons for an ''400'' error?? I guess it has something to do with rights. Jun 28 09:52:36 pm

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

my base/default includes this ntp manifest # cat modules/ntp/manifests/ntp.pp # ntp.pp class ntp { case $operatingsystem { centos, redhat: { $service_name = ''ntpd'' $conf_file = ''ntp.conf.el'' } debian, ubuntu: { $service_name = ''ntp'' $conf_file = ''ntp.conf.debian'' } } package {

Hello, Consider the following; You have a number of sites, all controlled by puppet. You have identified which files that are common to every host, and then which files are common to any particular site. Finally, you have the files which are private to the node in question. What I was wondering was if it would be possible to have some sort of directory hierarchy which has some kind of

This happens to Puppet 2.7.1 (both master and client). I have a file resource that I set to ensure => absent, Puppet removed it correctly with info line that it has a duplicate entry in the filebucket. I then changed the ensure => present, the agent run gave me following error: /usr/bin/puppet:19 err: /Stage[main]/Emb/File[/opt/jetty-distribution-7.4.2.v20110526.tar.gz]/ensure: change from

Hi all, First off, we''re running Puppet 2.7.6 with Ruby 1.8.7 on CentOS 6.0. Now, I''m using tildes in a template to prevent newlines from appearing but ruby/puppet is choking on them. */tmp/puppet$ cat test.erb* Line 1: Line 2 will exist if running on CentOS. <% if operatingsystem == "CentOS" ~%> Line 2: Yay, we''re running CentOS. <% end ~%>

Hi, I want to use a file resource to write a facts.yaml file for Mcollective. For some reason it won''t provide a valid yaml format if I dump my scope to hash and convert to_yaml. file { "/etc/mcollective/facts.yaml" : owner => root, group => root, mode => 400, loglevel => debug, #content => inline_template("<%= scope.to_hash.reject {

Hello Puppet list, I am taking over the puppet configuration of a sysadmin who left, and am having troubles deploying puppet to a new node. We are using puppet v2.7.3 both on the client and the puppetmaster, on Ubuntu 10.10. The node asks for a certificate fine, and I signed it on the puppetmaster. For the following logs extract I ve replaced the FQDN of my node by puppet.example.com. When doing

I''ve gone over the documentation several times now and I can''t figure out how to ''apply'' a manifest to a client. The client does have a signed certificate but the only thing in the /etc/puppet folder on the client is an ssl directory. I have a manifest that works fine on the puppet ''master'' I have added the client into

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 i am creating a template.pp for different OS.. Following is my template.pp file node basenode { case $operatingsystem { fedora: { include fedora } default: { include debian } } include baseapps, sshd, admin, default } <=== line 7 node default inherits basenode {} I receive an error. err: Could not parse for environment production: Syntax error

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