similar to: facter --yaml leaves some fields blank

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, when running the command "ip a" on a debian VM, I get this 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast

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

It''s barfing on this: Error 400 on SERVER: Could not parse for environment production: Syntax error at ''{''; expected ''}'' Here''s the node.pp node "ccc.unix.ccc.ccc.edu" { class { "web_server": net_static => { "eth0" => { "macaddress" =>

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''ve just committed Facter 1.3.8. All of the work for this release was done by James Turnbull, so everyone should thank him for getting it done. Here''s the changelog: Fixed Rdoc::usage bug on CentOS 5 - closed Puppet #753 and Facter #40 Added support to return multiple interfaces and their IP addresses and MAC addressess as facts. Returns

Hello all, I use puppetmaster on a Debian Squeeze server (packaged from Debian 2.6.2-4) I am using a template for Debian Servers which works great for Lenny in order to update my sources.list automagically, here goes: deb http://ftp.ie.debian.org/debian <%= lsbdistcodename %> main contrib non-free deb http://security.debian.org/ <%= lsbdistcodename %>/updates main Now the problem

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 =>

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''m having a problem with variable interpolation that I haven''t found a good solution to. I want to use a variable as part of the name of a fact, but the interpolation doesn''t work as expected. I''ve allowed for passing the mac address into my define() but if it''s not provided I want to look it up via facter. if

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

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

Hi all! I have quation: how i may use nested variables/facts? For example, I have variable $iface. It''s variable declared in node brakets, and, use with defenition. iface may be eth0, eth1(Linux), em0, ... <freebsd>, ... is fact: facter | grep eth0 | grep mac macaddress_eth0 => 54:52:00:3D:CB:40 We don''nt know name of $iface in our module (to generate network

Just poking around on the Docs site and went to the facter recipe for VMware. (http://reductivelabs.com/trac/puppet/wiki/IsVmwareGuestRecipe) If you look at the bottom, the author states that they were unable to get case statements to match as a regex. case $macaddress { "00:0C:29:*":{ file{ "/etc/running_inside_vmware": ensure => present } } }

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

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

int he example below I run facter looking for the fact "sp_serial_number". as you can see, the command facter sp_serial_number returns nothing, but the fact is there and is returned when just running facter and grepping for the fact. Some fact seem to work and others do not. any ideas? marcuspro:~ allan$ facter --version 1.5.7 marcuspro:~ allan$ facter sp_serial_number marcuspro:~

packages.debian.org is lagging in terms of what it''s showing, but.... $ rmadison -u debian {puppet,facter} | grep unstable puppet | 0.25.4-1 | unstable | source, all facter | 1.5.7-1 | unstable | source, all they''re both up there now. -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

Hi, I''d like to upcase a variable before it is saved, but I''m not sure how to access the incoming param or where this work should be performed: In my update method, I have: @device = Device.find(params[:id]) params[:device[macaddress]].upcase <-- problem code if @device.update_attributes(params[:device]) ....usual stuff here ''macaddress'' is the

Hi Rowland, thank you for your fast answer. More see below. On 10.09.2018 19:18, Rowland Penny via samba wrote: > [..] ERR: Object class violation : "objectclass_attrs: attribute >> 'macAddress' on entry 'CN=DEMO-02,CN=Computers,DC=dmiserver,DC=lan' >> does not exist in the specified objectclasses!" on DN >>