Issue #1527 has been updated by luke. Status changed from Needs more information to Accepted Priority changed from Normal to High
Actually, I think the way to fix this is to iterate over each fact, rather than using Facter.to_hash - that way we can protect ourselves from any individual fact failing. Should we use some kind of 'failed' value for those facts that fail, or should we just skip them, or what? Anyone concerned about getting a broken configuration if a fact is missing? ---------------------------------------- Bug #1527: puppet fails to run if store facts wont compile http://projects.reductivelabs.com/issues/show/1527 Author: ohadlevy Status: Accepted Priority: High Assigned to: community Category: Target version: 0.25.0 Complexity: Unknown Affected version: 0.24.4 Keywords: It seems that if puppet has synced a fact which does not compile, puppet will not run. fixing the fact on the puppet server does not solve the problem and one needs to delete the copied fact on the client to get factsync working again. I would expect puppet to sync the fact again in a case of fact execution problem and not to exit ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
