Issue #1527 has been updated by ohadlevy.
If a custom fact which does not compile has been copied to the client, puppetd will fail instead of trying to resync the fact again. steps to reproduce, edit one of the custom facts (on the client, not on the server), and "break it". try to run puppet and puppet will fail to load the fact and exit. ideally, puppet should check if there is a new version of the fact in case that it cant run it. ---------------------------------------- Bug #1527: puppet fails to run if store facts wont compile http://projects.reductivelabs.com/issues/show/1527 Author: ohadlevy Status: Needs more information Priority: Normal Assigned to: ohadlevy Category: Target version: 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 -~----------~----~----~----~------~----~------~--~---
