[Puppet Users] Facter 4.0.44

*Facter 4.0.44* [image: Base 64 encoded!]*Added* - Added disk_type field to disk fact #2145 [image: Base 64 encoded!]* Fixed* - (FACT-2806) Fix os.release.minor on amazon 6 #2133 - (

[Puppet Users] Facter 4.0.43

*Facter 4.0.43* *Fixed* - (FACT-2810) Fix dmi.board_asset_tag and dhcp #2125 - (FACT-2817) Only invalidate session cache on clear and reset. #2121 - (maint) Fix virtual_detector #2128

[Puppet Users] Facter 4.0.42

*Facter 4.0.42* *Added* - (FACT-2792) Show not supported message for facter -p #2119 *Fixed* - (FACT-2805) Read available memory from MemAvailable #2109 - (maint) Avoid deadlock of F

[Puppet Users] Facter 4.0.40

*Facter 4.0.40* *Added* - (FACT-2774) Extend facter API with resolve. [#2054] *Fixed* - (FACT-2798) Set color to true, fix Facter.log_exception #2105 - (FACT-2816) - Fix ec2 fact is

[Puppet Users] Facter 4.0.39 is now available

*Facter 4.0.39* *Added* - (FACT-2746) Added cloud resolver #2082 - (FACT-2317) Add Facter.define_fact method #2102 - (FACT-2326) Add Facter.each method #2100

[Puppet Users] Facter 4.0.38 is now available

*Facter 4.0.38* *Added* - (FACT-2319) Added debugonce method #2085 - (FACT-2327) added list method #2088 - (FACT-2320) Added warnonce method #2084

[Puppet Users] Facter 4.0.36 is now available

Hello, The Facter team is happy to announce the release of Facter 4.0.36 Here's what changed: Added - (FACT-2747) Add missing legacy facts on all platforms #2034 - (FACT-2721) Added Sola

[Puppet Users] Facter 4.0.35 is now available

Hello, The Facter team is happy to announce the release of Facter 4.0.35 Here's what changed: Added - (FACT-2726) Add solaris dmi facts #2025 - (FACT-2722) Add disks fact for Solaris #20

[Puppet Users] Facter 4.0.34

Hello everyone, We are happy to announce that Facter 4.0.34 has been released. Here's what's new: Added - (FACT-2739) Extend os hierarchy to consider multiple os families #2016 - Add FreeBSD memory facts #2020

[Puppet Users] Facter 4.0.33

Hi everyone, We are happy to announce that Facter 4.0.33 is released. [https://media3.giphy.com/media/SRO0ZwmImic0/giphy.gif?cid=4ac7172f842a1f3f2e5a515424725e8bf787762ead3ac390&rid=giphy.gif] Here’s what’s new: Added * (FACT-2040) Added solaris memory resolver #1999

[Puppet Users] Facter 4.0.29 is now available

Hello, The Facter team is happy to announce the release of Facter 4.0.29 Here is what changed: Added - (FACT-2218) virtual fact for OSX #1945 - (FACT-2232) Add Aix networking facts #193

Re: [Puppet Users] Facter 4.0.27 is now available

Hi Eirik, Facter 4 is the successor of Facter 3. Facter 3 was written in C++, and Facter 4 is implemented from scratch in Ruby. Facter 4 is a "big deal" :D because: - it aim for 100% compatibility with Facter 3 - as Facter 4 is written in Ruby, it is packaged as a Gem and can replace Facter 2.

[Puppet Users] Facter 4.0.28 is now available

Hello, The Facter team has released a new version of facter: *4.0.28 .* This release fixes a bug that was introduced in 4.0.27, which was yanked from rubygems. Special thanks to smortex for finding and fixing the probl

Re: [Puppet Users] Facter 4.0.27 is now available

Hi, I've trying since the initial Facter 4 release to find information on how I can use it - with Puppet, specifically. Is that documented anywhere? It would also be useful to know what "the big deal" with Facter 4 is. This is also something that was referenced in previous announcements here bu

[Puppet Users] Facter 4.0.27 is now available

Hello, The Facter team is happy to announce the release of *Facter 4.0.27 .* Here is what changed: New features - Networking facts for OSX #1929 - FreeBSD disks and partitions facts #553

[Puppet Users] Facter 4.0.26

Hi everyone, We are happy to announce that Facter 4.0.26 is released. [https://media3.giphy.com/media/hZj44bR9FVI3K/giphy.gif?cid=4ac7172f7ad43394f3f6fc072eb3e62d3b3cf1a810744e45&rid=giphy.gif] Here’s what’s new: Added * (FACT-2608) Add is_virtual fact #535

[Puppet Users] Facter 4.0.21 is now available

Hello, The Facter team is happy to announce the release of Facter 4.0.21 Here is what changed: Added - (FACT-2599) Run GitHub Actions on Ubuntu 16 and Osx 10 #497 - (FACT-2247) Add ne

[Puppet Users] Facter 4.0.20 is now available

Hello, The Facter team is happy to announce the release of Facter 4.0.20 Here is what changed: *Added* - Add BSD kernelversion and kernelmajversion facts #462 - Add support for

Re: [Puppet Users] Facter 4.0.19 is now available

Those look like beagle pups. Yours ? Super cute. I love all animals, especially if they are well behaved, but I am a Cat Person. ___ Dan White : d_e_wh...@icloud.com “Sometimes I think the surest sign that intelligent life exists elsewhere in th

[Puppet Users] Facter 4.0.15 is now available

Hi everyone, We’re glad to announce that Facter 4.0.15 is now available on Rubygems. Here’s what’s new: Added * (FACT-2541) Add TYPE for legacy facts #439 * (FACT-2535) Allow interpolation of Facter.fact('fact_name') #435

[Puppet Users] Facter 4.0.14 is now available

Hi, Facter team is happy to announce that Facter 4.0.14 is now available. Here is what changed: Added - (FACT-2512) Handle Raspbian as Debian #421 - (FACT-2231) Add AIX mountpoints fact #398

[Puppet Users] Facter 4.0.13 is now available

Hi, The Facter team is happy to announce Facter 4.0.13. This release contains multiple fixes requested by the community. *Features:* - FreeBSD inherits facts from Solaris, but it is a different platform - ElementaryOS uses Debian facts *Fixes:* - Fix internal fact caching for linux n

[Puppet Users] Facter 4 release

Hi, I am very happy to announce the first release of Facter 4 . The team has worked tirelessly these last couple of weeks to make the transition for projects that use Facter as a gem (for example Modules CI pipelines) as smooth as possible. If you

[Puppet Users] Facter 4 release update

Facter 4 release is *postponed* until the *18th of March*. The release date was moved because we noticed some unit test failures on some of Puppet supported modules when using Facter 4 pre-release. Current status: - integration tests for Puppet supported modules that use Litmus and Puppet a

[Puppet Users] Facter 4 pre-release

Hi, We are very happy to inform you that in the last week we have deployed a pre-release version of Facter 4 to rubygems. Facter 4 is still under development and our first goal is to replace Facter 2.x in Puppet gem with Facter 4. Starting with Puppet 6.1

Re: [Puppet Users] facter to return version of an installed package

jcbollinger wrote: > On Thursday, May 16, 2019 at 10:50:45 AM UTC-5, Helmut Schneider > wrote: > > > I don't want to install netplan but if it exists do the needful: > > I reiterate Ben Ford's comments: This is generally considered an > anti-pattern. > > It is better from an administrative pe

Re: [Puppet Users] facter to return version of an installed package

On Thursday, May 16, 2019 at 10:50:45 AM UTC-5, Helmut Schneider wrote: > > I don't want to install netplan but if it exists do the needful: > I reiterate Ben Ford's comments: This is generally considered an anti-pattern. It is better from an administrative perspective for you to know which

Re: [Puppet Users] facter to return version of an installed package

Chris Taylor wrote: > if $operatingsystem == "Ubuntu" { > if versioncmp($facts['os']['release']['full'], '18') >= 0 { > package { 'netplan': > ensure => present, > } > file { "/etc/netplan/windows-dhcp.yaml": > mode=> '0644', > owner => "${rootUID}", >

Re: [Puppet Users] facter to return version of an installed package

You'd be better declaring netplan as a requires: if $operatingsystem == "Ubuntu" { if versioncmp($facts['os']['release']['full'], '18') >= 0 { package { 'netplan': ensure => present, } file { "/etc/netplan/windows-dhcp.yaml": mode=> '0644', owner => "${roo

Re: [Puppet Users] facter to return version of an installed package

Ben Ford wrote: > To be sure, this pattern doesn't always work and you don't always have > control over the full system. What's your use case that you're trying > to solve? if $operatingsystem == "Ubuntu" { if versioncmp($facts['os']['release']['full'], '18') >= 0 { file { "/etc/netplan/win

Re: [Puppet Users] facter to return version of an installed package

You cannot pass a variable to facter, because that's not how its model is designed. Facter is a tool that runs to gather relatively static system information, called facts. A fact with a given name has a given value. In other words, you need one unique fact for every value you're gathering. (though

[Puppet Users] facter to return version of an installed package

Hi, before I reinvent the wheel: Does anyone know a custom fact that returns the version of an installed package (if it is installed)? I assume it would be something like Facter.add(:package_version) do setcode do osfamily = Facter.value(:osfamily) case osfamily when /ubuntu|debia

Re: [Puppet Users] Facter resolved to an invalid value

Team could you please share the script path for changing the value. On Tuesday, May 13, 2014 at 10:12:44 AM UTC-5, Viktor Jevdokimov wrote: > > Thanks! > > > 2014-05-13 17:49 GMT+03:00 David Schmitt >: > >> On 2014-05-13 16:34, Viktor Jevdokimov wrote: >> >>> On some CentOS servers we started to r

[Puppet Users] facter details copy to central location

Hey Guys, I have certain requirement to get puppet client inventory like "facter operatingsystem, facter ipaddress, etc : copied all details to some where in file on Puppet master server . Please advise -- You received this message because you are subscribed to the Google Groups "Puppet User

[Puppet Users] Facter error: empty packages.json

Hi I've recently been using puppet-agent-1.9.2 on an Ubuntu-14.04 machine and whenever I run puppet agent I receive the following error: Error: Facter: error while processing "/opt/puppetlabs/facter/facts.d/packages.json" for external facts: The document is empty. The file it refers to is indeed

[Puppet Users] Facter global

Hi dear, how create facter global in puppet? I need create password in one server (mysql) and other server (apache/php) need to know password. How need this password configured in mysql server? -- Atenciosamente, Rafael Tomelin skype: rafael.tomelin E-mail: rafael.tome...@gmail.com RHCE - Re

Re: [Puppet Users] facter compatibility and nest facts info

On Mon, Oct 17, 2016 at 1:09 PM, Jakov Sosic wrote: > On 10/17/2016 07:52 PM, rakare2...@gmail.com wrote: > >> Hi, >> >> Is there any issues with facter 2.4.6 + puppet 3.6.2 for writing >> manifest files? since facter 2.4.6 has nested facts. At present I have >> facter 2.1.0 + puppet 3.6.2. I am

Re: [Puppet Users] facter compatibility and nest facts info

On 10/17/2016 07:52 PM, rakare2...@gmail.com wrote: Hi, Is there any issues with facter 2.4.6 + puppet 3.6.2 for writing manifest files? since facter 2.4.6 has nested facts. At present I have facter 2.1.0 + puppet 3.6.2. I am planning to upgrade facter with 2.4.6. So before that I just want to c

[Puppet Users] facter compatibility and nest facts info

Hi, Is there any issues with facter 2.4.6 + puppet 3.6.2 for writing manifest files? since facter 2.4.6 has nested facts. At present I have facter 2.1.0 + puppet 3.6.2. I am planning to upgrade facter with 2.4.6. So before that I just want to confirm if there is any compatibility issues Also i

Re: [Puppet Users] facter ignores all executable facts with exception of ruby scripts

On Wed, Sep 14, 2016 at 6:31 AM, 'Peter Krauspe' via Puppet Users wrote: > Hi , > > I'm using facter puppet 3.8 7 with factor 2.4.6 on CentOS 7 > > According to puppet/facter docu it's possible to add executable custom facts > using ruby/shell/python scripts and just *.txt files. > > I tried the f

[Puppet Users] facter ignores all executable facts with exception of ruby scripts

Hi , I'm using facter puppet 3.8 7 with factor 2.4.6 on CentOS 7 According to puppet/facter docu it's possible to add executable custom facts using ruby/shell/python scripts and just *.txt files. I tried the following: /ruby.rb /python.py

[Puppet Users] Facter Questions Don't Correspond to Learning VM

Hi, So I'm working through the self-paced learning on the learn.puppet site, and am at 'An Introduction to Facter'. The learning VM is running in Virtualbox. At the exercises, I am told to cd into /etc/puppetlabs/puppet/modules and look at the structure of motd. There is no such directory.

[Puppet Users] facter 3 behaviour change in vlan interface legacy facts

This is something I found after upgrading a number of puppet agents from 3.8.5 to 4.4.2 using the puppet-agent-1.4.2-1.el6.x86_64.rpm rpm on CentOS 6. The legacy fact names around vlan interfaces are not the same as the facter2 versions of those facts. facter < 3: ipaddress_eth0_413 facter >=

Re: [Puppet Users] facter 3.2 global custom facts directory?

I thought it might too, but turns out probably not: https://projects.puppetlabs.com/issues/11449 On Sat, May 28, 2016 at 06:22:45AM -0700, dkoleary wrote: >Hey; >Thanks; yes, that was a typo.  Responding from an ipad on a shaky >surface... bit surprised that was the only one. >Any

Re: [Puppet Users] facter 3.2 global custom facts directory?

Hey; Thanks; yes, that was a typo. Responding from an ipad on a shaky surface... bit surprised that was the only one. Any rate, I now have fact scripts in /etc/facter/facts.d $ ltree /etc/facter/facts.d drwxr-xr-x. 2 root root 4096 May 28 08:07 /etc/facter/facts.d drwxr-xr-x. 3 root root 4096

Re: [Puppet Users] facter 3.2 global custom facts directory?

Just to confirm that's a typo below? You have an "s" in facter. /etc/facter/facts.d On Fri, May 27, 2016 at 03:15:11PM -0700, dkoleary wrote: > Thanks for the response. I'm pretty sure I tried /etc/faster/facts.d; but, > I'll confirm that. > > Thanks again. > > -- > You received this messag

Re: [Puppet Users] facter 3.2 global custom facts directory?

Thanks for the response. I'm pretty sure I tried /etc/faster/facts.d; but, I'll confirm that. Thanks again. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to p

Re: [Puppet Users] facter 3.2 global custom facts directory?

All the custom facts here in /etc/facter/facts.d have worked just fine across the facter 2.4.4 -> facter 3.1.6 upgrade. https://docs.puppet.com/facter/3.1/custom_facts.html On Fri, May 27, 2016 at 12:28:50PM -0700, dkoleary wrote: >Hey; >I'm drafing some custom facts that I would like to

[Puppet Users] facter 3.2 global custom facts directory?

Hey; I'm drafing some custom facts that I would like to have available to everyone even outside of puppet. The facts themselves work just fine for root and will work for normal users if I specify the --external-dir option: $ sudo facter env tst $ facter --e

Re: [Puppet Users] facter 3 and at_exit

I've created https://tickets.puppetlabs.com/browse/FACT-1381 Thanks again. On Fri, Apr 1, 2016 at 5:42 PM Clay Caviness wrote: > On Fri, Apr 1, 2016 at 5:33 PM Peter Huene > wrote: > >> This is caused by how custom facts are resolved in Facter 3: namely that >> custom facts are resolved all at

Re: [Puppet Users] facter 3 and at_exit

On Fri, Apr 1, 2016 at 5:33 PM Peter Huene wrote: > This is caused by how custom facts are resolved in Facter 3: namely that > custom facts are resolved all at once and no further calls from Ruby into > Facter's native implementation are expected when all resolutions have > completed. The Facter

Re: [Puppet Users] facter 3 and at_exit

Hi Clay, On Fri, Apr 1, 2016 at 1:57 PM, Clay Caviness wrote: > I've come across an issue with facter 3, when using at_exit. Basically, > any at_exit blocks that refer to anything not in the top-level namespace > (pardon my terminology) trigger an 'uninitialized constant' NameError. I > think th

[Puppet Users] facter 3 and at_exit

I've come across an issue with facter 3, when using at_exit. Basically, any at_exit blocks that refer to anything not in the top-level namespace (pardon my terminology) trigger an 'uninitialized constant' NameError. I think this is a namespace issue of some sort, but it's beyond my ken. To recreat

Re: [Puppet Users] facter value - not returning expected result

Hey Peter, In the original code you provided me, the '$?' was the thing that was confusing me. After some reading (and realizing my stupidity), I understand now that whatever is returned from #exec is what's passed to the block as the return value. If I run my #exec on from a bash shell, afte

Re: [Puppet Users] facter value - not returning expected result

Hi Mike, On Thu, Mar 24, 2016 at 3:58 PM, Mike Reed wrote: > Hey Peter, > > I've done some additional reading and I believe I understand what's > happening now. > > Thank you very much for the information and help. > Glad you got things working; let me know if there are any other questions that

Re: [Puppet Users] facter value - not returning expected result

Hey Peter, I've done some additional reading and I believe I understand what's happening now. Thank you very much for the information and help. Cheers, Mike On Thursday, March 24, 2016 at 2:25:38 PM UTC-7, Mike Reed wrote: > > Hey Peter, > > Thank you for the reply and the information. > >

Re: [Puppet Users] facter value - not returning expected result

Hey Peter, Thank you for the reply and the information. In terms of the piped greps, the second string is actually our internal domain name (which I removed and replaced with ) for security sake. I'm a little confused by code above as I'm still not getting what I would expect from your code

Re: [Puppet Users] facter value - not returning expected result

Hi Mike, On Thu, Mar 24, 2016 at 12:30 PM, Mike Reed wrote: > Hey Peter, > > Thank you for the reply. > > If I run the command on a machine that I know is 'joined' to the domain > and run 'echo $?' immediately after, I get a return of '0'. > If you're going solely off of grep's exit status, try

Re: [Puppet Users] facter value - not returning expected result

Hey Peter, Thank you for the reply. If I run the command on a machine that I know is 'joined' to the domain and run 'echo $?' immediately after, I get a return of '0'. Thank you again, Mike On Thursday, March 24, 2016 at 12:13:53 PM UTC-7, Peter Huene wrote: > > Hi Mike, > > On Thu, Mar 24,

Re: [Puppet Users] facter value - not returning expected result

Hi Mike, On Thu, Mar 24, 2016 at 11:59 AM, Mike Reed wrote: > Hey all, > > I'm a little stumped on why this fact is returning the incorrect value and > I was hoping somebody would have some advice on this one. > > The fact is very basic and looks like this: > > # custom fact for detecting if mac

[Puppet Users] facter value - not returning expected result

Hey all, I'm a little stumped on why this fact is returning the incorrect value and I was hoping somebody would have some advice on this one. The fact is very basic and looks like this: # custom fact for detecting if machine is joined to the domain require 'facter' Facter.add(:pbis_joined) do

Re: [Puppet Users] facter doesn't show custom facts?

Hi, thanks for reading :-) Traditionally, you had to invoke `facter -p` to receive Puppet's custom fact from the facter CLI. When we penned the book, PL had just removed that option in favor of `puppet facts`. Shortly after, it became clear that the latter does not quite cover all bases, an

[Puppet Users] facter doesn't show custom facts?

I wouldn't call myself a puppet user yet. I finished the "learning vm" tutorial, and I'm reading "Puppet 4 Essentials". In P4E, I read that "facter" and "puppet facts" don't do the same thing. The book says that the former doesn't support custom facts. This seems odd to me, although I wonder

Re: [Puppet Users] Facter 3 and Puppet 3.8.2

Hi, I'm not so sure, but looking at the release notes, there does not seem to be a breaking change in the 3.0 release that would disrupt compatibility with Puppet 3.x. So, yes, I believe this should Just Work. https://docs.puppetlabs.com/facter/3.0/release_notes.html#facter-300 Cheers, Felix

Re: [Puppet Users] Facter - custom fact regex

Hey Hristo, This did not work for me but I wanted to thank you for the info. It turns out the fact wasn't being sync'd correctly to the client and therefore not all my changes were being reflected locally. Thank you again for the info. Cheers, Mike. On Wednesday, January 13, 2016 at 3:26:1

[Puppet Users] Facter - custom fact regex

IMHO the fact "network" is a default fact from facter >= 3. i would change the name. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@go

Re: [Puppet Users] Facter - custom fact regex

Try : setcode { network } >From puppett docs: 1. A call to Facter.add('fact_name'), which determines the name of the fact 2. A setcode statement for simple resolutions, which is evaluated to determine the fact’s value. On Wed, Jan 13, 2016 at 12:42 AM, Mike Reed wrote: > Hello al

[Puppet Users] Facter - custom fact regex

Hello all, I'm having some trouble with a custom fact and I was hoping somebody could tell me what I'm doing wrong. Here is an example of the code: require 'facter' Facter.add('network') do setcode do hostname = Facter.value(:hostname) ipaddress = Facter.value(:ipaddress) case

[Puppet Users] Facter 3 and Puppet 3.8.2

Hi, I would like to know if i can install facter 3 with puppet version of 3.8.2 ? Thanks, Costya. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-use

Re: [Puppet Users] Facter 3.1 gem

On Tue, Oct 20, 2015 at 4:24 AM, Mickaël Canévet wrote: > What will happen when puppet (5?) will require facter 3+? > Will puppet still be available on rubygems.org or only within AIO > packages? > This would be very annoying for puppet module development... > There is one small improvement comi

Re: [Puppet Users] Facter 3.1 gem

What will happen when puppet (5?) will require facter 3+? Will puppet still be available on rubygems.org or only within AIO packages? This would be very annoying for puppet module development... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To

Re: [Puppet Users] Facter 3.1 gem

Hey thank you for your response. Is the ruby 2.4 version of facter still sufficient for the latest puppet version? Will it continue to be? Will further development go into ruby facter or only in the compiled C++ version of facter? Thanks again. On Monday, October 19, 2015 at 1:52:37 PM UTC

Re: [Puppet Users] Facter 3.1 gem

On Mon, Oct 19, 2015 at 9:02 AM seincin wrote: > Curious why there has not been a Facter 3.X gem made available? > Facter 3 is written in C++ and relies on a VERY modern version of GCC, as well as new versions of a number of libraries. These are not available on most of the platforms Puppet supp

[Puppet Users] Facter 3.1 gem

Curious why there has not been a Facter 3.X gem made available? Any timeline on a release? Thanks in advance. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email t

Re: [Puppet Users] facter 3 and linux disagree about interfaces

On Tue, Jul 21, 2015 at 12:26 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > > > If you have access to Facter 2.x on this same system, I'd be curious to > see if it would output the secondary interface / address information. If > not, I think we could consider Facter's 3.x behavior

Re: [Puppet Users] facter 3 and linux disagree about interfaces

> > > If you have access to Facter 2.x on this same system, I'd be curious to see > if it would output the secondary interface / address information. If not, I > think we could consider Facter's 3.x behavior to be a bug and fix it by > moving the secondary interfaces to where they belong. On

Re: [Puppet Users] facter 3 and linux disagree about interfaces

On Tue, Jul 21, 2015 at 11:47 AM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > > > Le 21 juil. 2015 à 20:33, Peter Huene a > écrit : > > > > > Thus there would be no "eth0:1" in the interfaces list; it would just > show up as the first element in the secondary array. e.g. eth0:1 bec

Re: [Puppet Users] facter 3 and linux disagree about interfaces

> Le 21 juil. 2015 à 20:33, Peter Huene a écrit : > > Thus there would be no "eth0:1" in the interfaces list; it would just show up > as the first element in the secondary array. e.g. eth0:1 becomes > eth0.secondary.0, eth0:2 becomes eth0.secondary.1, etc. > > Thoughts on this approach? It

Re: [Puppet Users] facter 3 and linux disagree about interfaces

On Tue, Jul 21, 2015 at 11:06 AM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > I agree that Facter could do a better job merging the secondary > "interface" into the primary one here. It shares the networking fact code > with a few other platforms (mainly OSX and the BSDs) and it cur

Re: [Puppet Users] facter 3 and linux disagree about interfaces

> I agree that Facter could do a better job merging the secondary "interface" > into the primary one here. It shares the networking fact code with a few > other platforms (mainly OSX and the BSDs) and it currently doesn't do any > specific logic for Linux to merge bonded interfaces together. >

Re: [Puppet Users] facter 3 and linux disagree about interfaces

On Tue, Jul 21, 2015 at 9:50 AM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > On a linux, if I enumerate interfaces using standards tools I get : > ~# ip link list > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > 2: eth0: m

[Puppet Users] facter 3 and linux disagree about interfaces

On a linux, if I enumerate interfaces using standards tools I get : ~# ip link list 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc mq master bond0 state UP qlen 1000 link/ether 00:1c:c4:74:83:80 brd ff:ff:ff:ff:

[Puppet Users] facter productname failing in CentOS 5

> There have been a number of regression fixes including fixes to command > execution, inclusion of the -p option, porting the xendomains fact, OS fact > fixes, and the fqdn fact reporting incorrectly on some systems. > > If there's an issue you're running into that you don't see being addresse

Re: [Puppet Users] Facter 3.0 breaks custom facts and dropped a needed core fact

Hi Peter! On Thursday, June 25, 2015 at 9:45:51 PM UTC-7, Peter Huene wrote: > > Hi Ken! > > On Thu, Jun 25, 2015 at 11:53 AM, Ken Bowley > wrote: > >> While testing puppet 4 to see if it was ready for production (still not), >> I now get to deal with the new Facter 3.0. >> >> Hopefully ruby bas

Re: [Puppet Users] Facter 3.0 breaks custom facts and dropped a needed core fact

Hi Ken! On Thu, Jun 25, 2015 at 11:53 AM, Ken Bowley wrote: > While testing puppet 4 to see if it was ready for production (still not), > I now get to deal with the new Facter 3.0. > > Hopefully ruby based facter won't be totally abandoned, since the C++ > based version is going to be an annoyan

[Puppet Users] Facter 3.0 breaks custom facts and dropped a needed core fact

While testing puppet 4 to see if it was ready for production (still not), I now get to deal with the new Facter 3.0. Hopefully ruby based facter won't be totally abandoned, since the C++ based version is going to be an annoyance on non-PL supported systems. The first thing I noticed is that a c

[Puppet Users] facter 3.0 not using /etc/facter/facts.d by default

I just upgraded to puppet4.2 aio on some machines to fix a bug we have been having with puppet. But this introduced a new problem. It seems like out custom facts are not being loaded by puppet or facter. We have 3 external facts manually set in files. [root@x facts.d]# ll /etc/facter/f

Re: [Puppet Users] Facter throwing MySQL errors

I'm still not convinced this is a broken fact. I ran it in --trace with "memoryfree" which definitely doesn't build a MySQL connection, and this is the output: [jg4461@radius-jg4461 ~]$ facter -p --debug --trace memoryfree Found no suitable resolves of 1 for ec2_metadata value for ec2_metadata

Re: [Puppet Users] Facter throwing MySQL errors

Try facter -p —debug or even facter -p —debug —trace to identify the broken fact which does the mysql connection. hth, Martin On 29 May 2015, at 13:51, Jonathan Gazeley wrote: > Yes, I tried running facter -p and it produces the same error. The same error > also crops up when puppet or mcol

Re: [Puppet Users] Facter throwing MySQL errors

Yes, I tried running facter -p and it produces the same error. The same error also crops up when puppet or mcollective execute facter too. Thanks, Jonathan On 29/05/15 12:25, Martin Alfke wrote: Have you tried running facter -p This will also pull the pluginsynced facts. (I am unsure which v

Re: [Puppet Users] Facter throwing MySQL errors

Have you tried running facter -p This will also pull the pluginsynced facts. (I am unsure which version has puppet facter) On 29 May 2015, at 11:21, Jonathan Gazeley wrote: > Hi folks, > > Since upgrading to Puppet 3.8.1 my Facter (2.4.4) has been throwing this > error every run: > > [jg44

[Puppet Users] Facter throwing MySQL errors

Hi folks, Since upgrading to Puppet 3.8.1 my Facter (2.4.4) has been throwing this error every run: [jg4461@webdev-ispms ~]$ facter ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) ERROR 2002 (HY000): Can't connect to local MySQL server th

Re: [Puppet Users] Facter : no operatingsystemrelease on CentOS 7

If you install from an ISO, redownload it Le 26/05/2015 20:28, Claude a écrit : I just found out about the source of the bug : https://tickets.puppetlabs.com/browse/FACT-893. Indeed a yum update solves the problem but since I must run puppet before that, I found the following workaroud is als

Re: [Puppet Users] Facter : no operatingsystemrelease on CentOS 7

I just found out about the source of the bug : https://tickets.puppetlabs.com/browse/FACT-893. Indeed a yum update solves the problem but since I must run puppet before that, I found the following workaroud is also valid: ln -s -f /etc/centos-release /etc/redhat-release Thanks Le mardi 26 mai

Re: [Puppet Users] Facter : no operatingsystemrelease on CentOS 7

Hi, http://lists.centos.org/pipermail/centos-announce/2015-April/021010.html https://tickets.puppetlabs.com/browse/FACT-893 Just run yum update Le 26/05/2015 18:32, Claude a écrit : Hi, I'm testing the Openstack CentOS 7 image with Puppet 3.7.5. My problem is with Facter not identifying

[Puppet Users] Facter : no operatingsystemrelease on CentOS 7

Hi, I'm testing the Openstack CentOS 7 image with Puppet 3.7.5. My problem is with Facter not identifying correctly the operating system : [root@test2 vendor_ruby]# facter --version 2.4.4 [root@test2 vendor_ruby]# ruby --version ruby 2.0.0p598 (2014-11-13) [x86_64-linux] [root@test2 vendor_rub

Re: [Puppet Users] facter: unordered hashes lead to changes

I *did* misunderstand! Thanks for pointing that out! Much better now! On Wed, Apr 8, 2015 at 8:57 AM, jcbollinger wrote: > > > On Tuesday, April 7, 2015 at 2:53:38 PM UTC-5, Guy Matz wrote: >> >> Ahhh!! The version of facter on my new servers is 2.4 . . old servers >> have 1.7 . . .any

Re: [Puppet Users] facter: unordered hashes lead to changes

On Tuesday, April 7, 2015 at 2:53:38 PM UTC-5, Guy Matz wrote: > > Ahhh!! The version of facter on my new servers is 2.4 . . old servers > have 1.7 . . .anyone know how to get facter 2.x to stringify facts? > I've tried adding 'stringify_facts = true' to my puppet.conf, but that did >

Re: [Puppet Users] facter: unordered hashes lead to changes

Ahhh!! The version of facter on my new servers is 2.4 . . old servers have 1.7 . . .anyone know how to get facter 2.x to stringify facts? I've tried adding 'stringify_facts = true' to my puppet.conf, but that did not change behaviour . . . On Tue, Apr 7, 2015 at 2:08 PM, Christopher Wood

Re: [Puppet Users] facter: unordered hashes lead to changes

Sounds like this is set to true (over here I set it to false everywhere to take advantage of the non-string facts): https://docs.puppetlabs.com/references/latest/configuration.html#stringifyfacts On Tue, Apr 07, 2015 at 01:56:43PM -0400, Guy Matz wrote: >Hi!  I'm seeing the following at the

  1   2   3   4   5   >