search for: lsbrelease

...;No LSB modules are available." on every run. This is on Ubuntu 10.04 and 12.04, probably others as well. This message (on stderr) usually comes from calling "lsb_release -v" when no additional LSB modules are installed. Facter apparently calls "lsb_release -v -s" in facter/lsbrelease.rb. This is neither fatal nor problematic, but very annoying because a typical puppet run used to be silent. Now my Cron mails are full of "No LSB modules are available." I also don''t quite understand the purpose of this lsbrelease fact. At least on a typical Ubuntu system &quo...

Hello, I have a file which varies depending on which OS/version it''s running. I tried to make a nested source parameter like this, but it didn''t work: source => $operatingsystem ? { Debian => "puppet://myserver.com/files/os/debian/etc/ssh/sshd_config", Gentoo => "puppet://myserver.com/files/os/gentoo/etc/ssh/sshd_config", RedHat =>

...ng > /usr/lib/site_ruby/1.8/facter.rb) to expose a new variable named > lsbdistrelease_majorversion which only includes the portion of the LSB > distribution release before the decimal point (if there is a point at > all): > > ======== > 621c621,622 > < { "LSBRelease" => %r{^LSB Version:\t(.*)$}, > --- > > { > > "LSBRelease" => %r{^LSB Version:\t(.*)$}, > 623a625 > > "LSBDistRelease_MajorVersion" => > %r{^Release:\t([0-9]+)}, > ======= > > However, this seems...

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

...en (1): ceefaf1 Update lib/facter.rb, CHANGELOG, facter.spec for 1.6.9rc1 Moses Mendoza (2): 2842c96 Update rpm spec file ac51593 Wrap dmidecode/pciutils in ifarch block Stefan Schulte (2): 515fd65 (#11511) Split lsb facts into multiple files fbaa8fe (#11511) Correct lsbrelease specfile filename -- 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 more opti...

.... Here''s the output of facter -d: value for kernelrelease is still nil value for hostname is still nil value for hostname is still nil value for ipaddress is still nil value for lsbdistdescription is still nil value for hostname is still nil value for hardwaremodel is still nil value for lsbrelease is still nil value for hostname is still nil value for kernel is still nil value for operatingsystem is still nil value for lsbdistrelease is still nil value for kernelrelease is still nil value for operatingsystemrelease is still nil value for lsbdistid is still nil value for hostname is still nil...

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

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

Just started a rollout of centos 6.x across our Puppet deployment (100-odd servers). what fact would people suggest I use to distinguish 5.x from 6.x (quite a lot of subsystems are different between major releases)? lsb* facts don''t seem to be present on centos 6 - is this an EPEL bug, or have they just been removed in Facter? Thanks! -- You received this message because you are