similar to: lsbdistcodename and Debian Squeeze

I read somewhere recently about problems with Puppet and Ruby 1.9. I''m wondering if this is still an issue? Thanks. -- 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 puppet-users+unsubscribe@googlegroups.com. For

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 {

sorry to come with such a silly request but i have a code: shorewall-zone { "$name": SHTYPE => ''ipv4'', PARENT => "$PARENT" } and it bring a syntax error : debug: importing

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

Hi all, I''m trying to get puppet working for the first time, and I''ve run into something that''s got me stumped. This is all on Solaris 10/x64. The initial startup of puppetmasterd wasn''t working, and it appeared to be related to the SSL certs not getting generated properly. I managed to trace that down to the fact that facter isn''t finding the

Does anyone have any insight into this error message? err: Could not retrieve catalog from remote server: Error 400 on SERVER: The fact named fact_stomp_server does not appear to be a valid hostname. The value of '''' does not match ''^[a-zA-Z0-9.-]+$''. A common cause of this problem is running puppet agent as a normal user instead of root, or the fact is

Dear List, i was running a few natty systems and upgraded one of them to oneiric. Facter shows the right lsbdistcodename, lsbdistrelease, etc. parameters, but when i''m running puppet agent the modules has access to the previous (natty, etc.) values. As i see on puppetmaster in /var/ lib/puppet/yaml/{facts,node} the output from facter and the agent is cached and won''t update

I have set up puppet to create a facts.yaml file for mcollective using the following line: content => inline_template("<%= scope.to_hash.reject { |k,v| k.to_s =~ /(uptime.*|timestamp|.*free|macaddress.*|ipaddress)/ }.to_yaml %>"), However, it is creating a lot of unnecessary changes by reordering the facts in the yaml output as you can see in the diff output between to

Hi, I was wondering if it is possible to gain access to the nodename as a variable, in order to refer to the name or part of it inside a class. Eg: I have a lot of sites that essentially have the same configuration, except they are in different domains and have different requirements for things like resolv.conf. I can manage this by creating a node definition for each node and specifying some

David Schmitt david wrote on Mon Jun 25 03:32:09 CDT 2007: > For the ongoing modularisation of my config I wrote a > assert_lsbdistcodename class today, which can be used for failing > parts or complete configurations if a certain variable is not set > (lsbdistcodename in this case). Please find the file attached. This is great, however I ran into something strange with this. It

I have finally gotten Ruby 1.8.7 to compile properly with SSL libraries on HPUX so now I am fighting how to get puppet to manage passwords. First I modified the hpux.rb under the providers/user directory to have it use /usr/sam/lbin/useradd.sam to add users and that worked great right off the bat. The problem I am having now is that each time puppet runs it does not seem to be getting the

I am trying to streamline the current distribution specific setup and creation of VE''s within OpenVZ with puppet. My first attempt has gone horribly wrong as you will see below. Here''s the script I wrote to replace the redhat specific setup that OpenVZ used: [jleggett@lxp6d15m3 scripts]$ cat redhat-add_ip.sh #!/bin/bash # # Debug - take out later set -x

Sometimes "facter --yaml" doesn''t list all the values specified on the command line. I can''t find rhyme nor reason why. Here''s a demo to show what I mean: # facter --version 1.5.7 # facter --yaml fqdn macaddress lsbdistcodename --- fqdn: my.host.name.example.com lsbdistcodename: squeeze macaddress: "00:00:00:00:00:00" We had been using the above

I have the following as part of a module: -------------------------------------------------------------------------------- # Ensure "lsb-release" installed package {"lsb-release": ensure => installed, } # Use our sources.list file { "/etc/apt/sources.list": owner => root, group => root, mode =>

hello puppet list My puppet server is now working quite wonderfully. Thanks go out to all who have assisted in getting it to this point. At this point in time my config is now correctly installing packages according to arch,os and release. Centos is working quite well as of now, but I am attempting to get the ubuntu side of things to work as well. I am frankly more familiar with RHEL under

Hi, Is it possible to have an array as the output of a custom fact? And then to pass it into a template in Puppet? I currently have a fact that looks like this: Facter.add("exports") do setcode do case Facter.hostname when (/thishost/i): [ "/local", "/local2" ] end end end & a template like this: <%

Hi List, I''m using puppet 0.23.2 (tarball) on Debian sarge as server and the same version on an etch client. When I try to use the following class : class base { $puppet = "security01.mydomain.com" # bashrc file for global shell settings. file depends on used OS version (etch, sarge etc). file { "/etc/bash.bashrc": ensure =>

Hello, I am having problems with Puppet since upgrading to 3.0.0. When I call an inventory search I get a Error 400. I have used dashboard + Perl Oct 4 08:58:43 puppet01 puppet-master[7008]: Handling request: GET /production/facts_search/search?facts.lsbdistcodename.eq=lenny Oct 4 08:58:43 puppet01 puppet-master[7008]: header too long ii facter

Hello, I have another quick one about puppet dashboard. We are using the Debian one for Squeeze (1.0.4) and as the database has significantly grown, if/when we click on a list of unresponsive nodes to check them, the web interface sits there doing nothing then the puppetmaster process starts timing out for all nodes compiling their catalogs. Has anyone got a workaround for this? Does it involve

Hello, I try to install puppet on freebsd 6.X. All is well but i cannot get the certificte to install and be recognized. I run .19.3. I run the puppetd --test --waitforcert 60 then sign and then i got: err: No certificate; running with reduced functionality. info: Creating a new SSL key at /usr/local/.aqadmin/puppet/conf/ssl/private_keys/xxxxxxxxxxxxxx.pem info: Creating a new certificate