Jira (FACT-408) facter-2.0.1.rc2 Solaris lspci command not found

[Adrien Thebo (JIRA)]

Title: Message Title

Adrien Thebo commented on an issue   Re: facter-2.0.1.rc2 Solaris lspci command not found In Facter 1.x, it is harmless to execute commands that do not exist because `Facter::Util::Resolution.exec` will check to see if the command exists and returns nil if it does not. Unfortunately this has lead to some sloppy code where all commands would be attempted, which clutters up the executing logic. In Facter 2.0 the behavior of .exec was changed to raise an error if a command did not exist, but this aggravated the situation you've described. As part of FACT-409 we're reverting that behavior change so this issue should be taken care of. You are right though, it's silly to attempt to run lscpi on Solaris in any case, and that code should be refactored. Add Comment   Facter / FACT-408 facter-2.0.1.rc2 Solaris lspci command not found The follow error says it all /var/ruby/1.8/gem_home/bin/facter -p Could not load Puppet: can't activate facter (~> 1.6, runtime) for ["puppet-3.4.3"], already activated facter-2.0.1.rc2 for [] Could not retrieve fact='virtual', resolution='<anonymous>': Could not execute 'lspci 2>/dev/null': command not found Could not retrieve fact='virtual', resolut... 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.