Issue #5410 has been updated by Paul Nasrat.
I agree with the case for non-zero code for no matching facts, however the case of the fact above is really a poorly written fact (not to say there aren't those in facter core atm!) which isn't handling stuff gracefully. A resolution failing should not cause an error code from facter as it is normal operation to try multiple resolutions. ---------------------------------------- Bug #5410: facter does not use return codes https://projects.puppetlabs.com/issues/5410 Author: Garrett Honeycutt Status: Needs design decision Priority: Normal Assignee: Paul Nasrat Category: binary Target version: Keywords: Branch: It appears that facter always returns zero Reproduction: <pre> # facter operatingsystem CentOS # echo $? 0 # facter thisfactdoesnotexist # echo $? 0 </pre> Supposing that the fact 'thisfactdoesnotexist' is not a valid fact name, the return code should not be zero. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
