Jira (PUP-6277) Add ability to describe conflicts between resources (e.g. augeas <-> file)
Title: Message Title
David Gardner updated an issue
Puppet / PUP-6277
Add ability to describe conflicts between resources (e.g. augeas <-> file)
Change By:
David Gardner
It would be nice to be able to *cause* conflicts between resources where they actually manage the same items and shouldn't be used in such an overlapping way.e.g. Something like:{code:puppet}augeas { "sshd_config": context => "/files/etc/ssh/sshd_config", changes => ["set PermitRootLogin no", ], conflict => File['/etc/ssh/sshd_config'],}file { "/etc/ssh/sshd_config":ensure => filecontent => template("ssh/sshd_config.erb"),}{code}This could also be added internally by resources automatically for known types.Any conflict with something which does not exist in the catalog should not cause an error.Currently these do not conflict and so you can end up with confusing (and order-dependent?) behaviour.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6277) Add ability to describe conflicts between resources (e.g. augeas <-> file)
Title: Message Title
David Gardner updated an issue
Puppet / PUP-6277
Add ability to describe conflicts between resources (e.g. augeas <-> file)
Change By:
David Gardner
It would be nice to be able to *cause* conflicts between resources where they actually manage the same items and shouldn't be used in such an overlapping way.e.g. Something like:{{ augeas { "sshd_config": context => "/files/etc/ssh/sshd_config", changes => ["set PermitRootLogin no", ], conflict => File['/etc/ssh/sshd_config'],}file { "/etc/ssh/sshd_config":ensure => filecontent => template("ssh/sshd_config.erb"),}}}This could also be added internally by resources automatically for known types.Any conflict with something which does not exist in the catalog should not cause an error.Currently these do not conflict and so you can end up with confusing (and order-dependent?) behaviour.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6277) Add ability to describe conflicts between resources (e.g. augeas <-> file)
Title: Message Title
David Gardner updated an issue
Puppet / PUP-6277
Add ability to describe conflicts between resources (e.g. augeas <-> file)
Change By:
David Gardner
It would be nice to be able to *cause* conflicts between resources where they actually manage the same items and shouldn't be used in such an overlapping way.e.g. Something like: { { code:puppet} augeas { "sshd_config": context => "/files/etc/ssh/sshd_config", changes => ["set PermitRootLogin no", ], conflict => File['/etc/ssh/sshd_config'],}file { "/etc/ssh/sshd_config":ensure => filecontent => template("ssh/sshd_config.erb"),} {code } } This could also be added internally by resources automatically for known types.Any conflict with something which does not exist in the catalog should not cause an error.Currently these do not conflict and so you can end up with confusing (and order-dependent?) behaviour.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6277) Add ability to describe conflicts between resources (e.g. augeas <-> file)
Title: Message Title
David Gardner created an issue
Puppet / PUP-6277
Add ability to describe conflicts between resources (e.g. augeas <-> file)
Issue Type:
New Feature
Assignee:
Unassigned
Components:
Language
Created:
2016/05/09 2:17 AM
Priority:
Normal
Reporter:
David Gardner
It would be nice to be able to cause conflicts between resources where they actually manage the same items and shouldn't be used in such an overlapping way.
e.g. Something like: {{ augeas { "sshd_config": context => "/files/etc/ssh/sshd_config", changes => [ "set PermitRootLogin no", ], conflict => File['/etc/ssh/sshd_config'], }
file { "/etc/ssh/sshd_config": ensure => file content => template("ssh/sshd_config.erb"), }
}}
This could also be added internally by resources automatically for known types. Any conflict with something which does not exist in the catalog should not cause an error.
Currently these do not conflict and so you can end up with confusing (and order-dependent?) behaviour.
Jira (PUP-6277) Add ability to describe conflicts between resources (e.g. augeas <-> file)
Title: Message Title
David Gardner updated an issue
Puppet / PUP-6277
Add ability to describe conflicts between resources (e.g. augeas <-> file)
Change By:
David Gardner
It would be nice to be able to *cause* conflicts between resources where they actually manage the same items and shouldn't be used in such an overlapping way.e.g. Something like:{{augeas { "sshd_config": context => "/files/etc/ssh/sshd_config", changes => ["set PermitRootLogin no", ], conflict => File['/etc/ssh/sshd_config'],}file { "/etc/ssh/sshd_config":ensure => filecontent => template("ssh/sshd_config.erb"),}}}This could also be added internally by resources automatically for known types.Any conflict with something which does not exist in the catalog should not cause an error.Currently these do not conflict and so you can end up with confusing (and order-dependent?) behaviour.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.: { { code:bash} ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown {code } } This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.:{code :bash }# ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown{code}This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: {code} Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown' {code} Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.:{code:bash} # ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown{code}This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.:{{# ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown }}This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.:{{# ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown}}This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.:{{ # ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown}}This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title David Gardner updated an issue Facter / FACT-1394 Warning printed when 'ip route show' output contains "linkdown" Change By: David Gardner When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.: # ip ro sho default via 192.168.1.1 dev eth2 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown 192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133 192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdownThis causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.: {{ # ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown }} This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title David Gardner created an issue Facter / FACT-1394 Warning printed when 'ip route show' output contains "linkdown" Issue Type: Bug Affects Versions: FACT 3.1.5 Assignee: Unassigned Created: 2016/04/18 2:35 AM Environment: Debian Sid with PC1 install of Puppet 4.x and puppet-agent latest versions from jessie apt repo (includes facter 3.1.5) Priority: Normal Reporter: David Gardner When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.: ip ro sho default via 192.168.1.1 dev eth2 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown 192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133 192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followed by key/value pairs, got '192.168.0.0/24 dev
Jira (FACT-696) facts.d module external facts get put in client dir which facter doesn't look at by default
Title: Message Title David Gardner commented on FACT-696 Re: facts.d module external facts get put in client dir which facter doesn't look at by default puppet facts find hostname does show this information so this looks like a fine replacement. Many thanks! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (FACT-696) facts.d module external facts get put in client dir which facter doesn't look at by default
Title: Message Title David Gardner updated an issue Facter / FACT-696 facts.d module external facts get put in client dir which facter doesn't look at by default Change By: David Gardner Assignee: DavidGardner JoshCooper Add Comment 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.
Jira (FACT-696) facts.d module external facts get put in client dir which facter doesn't look at by default
Title: Message Title David Gardner commented on an issue Re: facts.d module external facts get put in client dir which facter doesn't look at by default (These are from the original example I've been trying this with) It's executable for puppet and root: ``` ls -la /var/lib/puppet/facts.d/ total 12 drwxr-xr-x 2 root root 4096 Sep 1 14:40 . drwxr-xr-x 18 puppet puppet 4096 Jun 9 22:09 .. -rwxr-xr-x 1 root root 342 Sep 1 14:40 hyperthreading.sh ``` And an strace on the facter run shows that it doesn't look in `/var/lib/puppet/facts.d` where puppet is placing this for a module-provided fact, or for any sh scripts there: ``` strace facter -p hyperthreading 21 | grep hyper execve(/usr/bin/facter, [facter, -p, hyperthreading], [/* 27 vars */]) = 0 stat(/usr/lib/ruby/site_ruby/1.8/facter/hyperthreading.rb, 0x7fffd2c9dc70) = -1 ENOENT (No such file or directory) stat(/var/lib/puppet/lib/facter/hyperthreading.rb, 0x7fffd2c9dc70) = -1 ENOENT (No such file or directory) strace facter -p hyperthreading 21 | grep facts.d open(/etc/facter/facts.d, O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3 open(/etc/puppetlabs/facter/facts.d, O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory) So: Is the puppet agent placing these files in the wrong location? Or, Should facter be looking in the puppet facts.d sync location? Or, Should I always be using the --external-dir option to facter to get these facts? When running puppet via strace and following forks I see it look at and then write the file into `/var/lib/puppet/facts.d` and not `/var/lib/puppet/facts` as facter does. All of these are being run as the same user (root) for these tests. Add Comment
Jira (FACT-696) facts.d module external facts get put in client dir which facter doesn't look at by default
Title: Message Title David Gardner commented on an issue Re: facts.d module external facts get put in client dir which facter doesn't look at by default [Do I assign this back now or will it be seen by you watching it?] 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.
Jira (FACT-696) facts.d module external facts get put in client dir which facter doesn't look at by default
Title: Message Title David Gardner commented on an issue Re: facts.d module external facts get put in client dir which facter doesn't look at by default (found by adding a shell-script fact to module/facts.d/fact.sh, which then syncs to the given directory on the client but isn't picked up by factor without the external-dir option) 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
Jira (FACT-696) facts.d module external facts get put in client dir which facter doesn't look at by default
Title: Message Title David Gardner created an issue Facter / FACT-696 facts.d module external facts get put in client dir which facter doesn't look at by default Issue Type: Bug Affects Versions: 2.2.0 Assignee: Eric Sorenson Created: 01/Sep/14 8:01 AM Environment: Facter 2.2.0 Puppet 3.6.2 CentOS 6.5 Priority: Normal Reporter: David Gardner 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 lookup of the facts in puppet manifests. However, this seems non-sensical and that the facter default should be to look in the directory which fact scripts are placed into automatically; especially as this is the recommended method of adding external script facts via module magic sync rather than placing them into /etc/facter/facts.d explicitly.
