similar to: Facter 1.6.9 complains about "No LSB modules are available."

Hi. When running "puppetd --server <puppetmaster> --waitforcert 50 --test" on a puppet client we get the following error: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect''

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

Facter 1.6.9rc1 is a maintenance release candidate with bug fixes and improvements. It includes contributions from the following people: Jeff Weiss, Joachim de Groot, Ken Barber, Matthaus Litteken, Moses Mendoza, and Stefan Schulte. This release is available for download at: http://downloads.puppetlabs.com/facter/facter-1.6.9rc1.tar.gz See the Verifying Puppet Download section at:

Hi all, I''m trying to find a nice way to model different stages (like: live, test, dev) of puppet modules. Initially I thought of different branches inside one (Git) repository... - either being checked out on one puppetmaster into different directories being used as different puppet environments - or being checked out on different puppetmasters but then colleagues of mine

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

greetings folks. wanted to have aix detect if it was under powervm using facter. came up with this hack for facter 1.6.9 which work for vscsi and npiv enabled vm''s under powervm (so far)... havent checked the dev facter so something may be in a different branch already for facter on this topic... -- You received this message because you are subscribed to the Google Groups

This fixes a very small bug: On non-linux OSes, facter was printing to STDERR a message that lsb_release was missing. This is now fixed. -- On Bureaucracy.... The Pythagorean theorem contains 24 words. Archimedes Principle, 67. The Ten Commandments, 179. The American Declaration of Independence, 300. And recent legislation in Europe concerning when and where to smoke, 23,942.

I read on lwn.net that swfdec has support for watching youtube.com videos. Good work! I have not been able to get the Adobe 32-bit mozilla plugin working under 64-bit gutsy so I figured I'd give swfdec a go. A quick search of the archives and bugzilla turns up nothing obviously similar to my problem. Viewing this page: http://www.youtube.com/watch?v=82Opqy5mFZM&feature=related I

I just realized that if you don''t have redhat-lsb on your (Fedora 7) box, all those lsb* facts don''t show up. Should I make redhat-lsb a requirement for the facter rpm to guard against that ? David

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

From looking at the Facter code, it looks like the ''operatingsystemrelease'' fact is currently a mirror of the ''kernelrelease'' fact. I''d like to implement this fact so that it returns the major version of the operating system, eg: Debian Sarge: operatingsystemrelease => 3.1 Debian Etch: operatingsystemrelease => 4.0 RHEL3 update 8:

Hello all: > We operate in an environment where we might sometimes wish to do > certain tasks based solely upon the MAJOR version number of an OS > release, disregarding the minor portion of the version number. For > instance, CentOS 4.0 through 4.5 would all be ''CentOS 4'' to some > scripts, and CentOS 5.0 and greater would all be ''CentOS 5''.

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

Thanks! ?"jammy" made it work. ? For some reason, ?lsb_release -cs is returning "victoria" rather than "jammy", and $> sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Ign:2 http://packages.linuxmint.com victoria InRelease Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Hit:4 http://packages.linuxmint.com victoria

https://projects.puppetlabs.com/issues/2476 This does seem to confuse a fair few new users. What would be a better name for "--test"? -- 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

On Mon, 04 Dec 2023 13:41:47 -0500 Steve Gutreuter <sgutreuter at gmail.com> wrote: > $> sudo /usr/bin/add-apt-repository "deb > https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release > -cs)-cran40/" Looks like `lsb_release -cs` returns a Mint codename for you. Thankfully, since we know that Linux Mint 21 is based on Ubuntu 22.04 "Jammy Jellyfish", it

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

On 1/16/20 5:03 PM, Gianluca Cecchi wrote: > On Thu, Jan 16, 2020 at 11:08 PM Peter <peter at pajamian.dhs.org> wrote: > >> On 17/01/20 8:06 am, Lamar Owen wrote: >>> On 1/16/20 6:49 AM, Peter wrote: >>>> On 16/01/20 4:14 am, Brian Stinson wrote: >>>>> Release for CentOS Linux 8 (1911) >>>>> >>>>> We are pleased

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

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