Issue #1499 has been updated by pnasrat. Status changed from Accepted to Closed
Facter 1.5.2 is the current release (1.5.1 fixed #1422) please update ---------------------------------------- Bug #1499: puppetd should fail when Facter fails http://projects.reductivelabs.com/issues/show/1499 Author: lludwig Status: Closed Priority: Normal Assigned to: Category: agent Target version: 0.24.6 Complexity: Unknown Affected version: 0.24.4 Keywords: Hi, The issue I am having is a server when puppet/facter runs and the server has a high load. Based upon facter 1.5 the timeouts have been adjusted and is causing some issues. In our case we have a puppet recipe that's using this facter. http://reductivelabs.com/trac/puppet/wiki/Recipes/RaidFact To determine what raid controller is installed. It has a case statement. If the raid controller is found install smartd, else remove it. The problem is if facter timesout with this request, it should not uninstall. I would suggest facter pass something, instead of nil, like 'timeout' or something unique to make the puppet recipe know what happened. That way it's a different result than than 'nil' and can create a case statement for it. The recipe must assume nil means no raid controller was found. Is this a modification in the RaidFact or facter itself? From what I can tell it's a facter change. ---------------------------------------- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
