Jira (FACT-696) facts.d module "external" facts get put in client dir which facter doesn't look at by default

[Josh Cooper (JIRA)]

Title: Message Title

Josh Cooper commented on an issue   Re: facts.d module "external" facts get put in client dir which facter doesn't look at by default David Gardner hmm, so I see the same behavior that you do, ie external facts are available when executing puppet, but not when executing facter, even when the -p argument is used: [root@centos64-x64 facts.d]# puppet agent -t Info: Retrieving pluginfacts Notice: /File[/var/lib/puppet/facts.d/hyperthreading.sh]/ensure: defined content as '{md5}242e6945dbb4817aa0d30e58fb3b788b' Info: Retrieving plugin Info: Loading facts Info: Caching catalog for centos64-x64.localdomain Info: Applying configuration version '1412013273' Notice: Finished catalog run in 0.03 seconds [root@centos64-x64 facts.d]# puppet apply -e 'notice($hyperthreading)' Notice: Scope(Class[main]): 1 Notice: Compiled catalog for centos64-x64.localdomain in environment production in 0.02 seconds Notice: Finished catalog run in 0.03 seconds [root@centos64-x64 facts.d]# ls -la /var/lib/puppet/facts.d/ total 12 drwxr-xr-x 2 root root 4096 Sep 29 17:55 . drwxr-x--- 11 puppet puppet 4096 Sep 29 17:48 .. -rwxr-xr-x 1 root root 35 Sep 29 17:55 hyperthreading.sh [root@centos64-x64 facts.d]# /var/lib/puppet/facts.d/hyperthreading.sh hyperthreading=1 [root@centos64-x64 facts.d]# facter hyperthreading   [root@centos64-x64 facts.d]# facter -p hyperthreading There is a bit of a chicken and egg problem here. Normally when you run puppet, it tells facter where the external facts directory is, and facter loads external facts from there. When you run facter standalone, it has no knowledge about where puppet downloaded external facts to, so external facts are not loaded. However, when running facter with the -p argument, I would expect it to load puppet (in the context of the current facter run) and set the external facts directory. It doesn't do this currently, so I think that is a bug, but development is shifting over to native facter, and I don't know the status of external fact support in native facter. Kylo Ginsberg want to weigh in here? Add Comment   Facter / FACT-696 facts.d module "external" facts get put in client dir which facter doesn't look at by default Fact scripts placed in the recommended path of <MODULEPATH>/<MODULE>/facts.d/ get added to clients into the /var/lib/puppet/facts.d directory, but then this directory is only searched for .rb ruby fact snippets by default. If facter is run explicitly as:   facter --external-dir /var/lib/puppet/facts.d/ <factname> ..then this works fine, as does l... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.