Issue #1527 has been updated by ohadlevy.
luke wrote: > To be clear, the problem here is that you've got code to produce a fact > value, and that code is somehow invalid, which is cause Facter to fail, which > is in turn causing puppetd to fail. Right? > Right > In that case, there are two bugs -- one in Puppet (puppetd should be > resilient to failures in Facter) and one in Facter (it should be resilient to > broken facts). > > Either way, though, it would be hard to have this kind of failure result in > an automatic resyncing of the fact code, and, really, that wouldn't normally > fix the problem -- it just pulled down broken code, and it's reasonable to > assume that, seconds later, the code is still broken. > well, the main problem is that puppetd will never run again on this machine unless you manually remove the fact, so ideally, puppet should try to check once in a while if the fact has changed on the server. > The only reasonable response here is to cache the facts locally and pass them > back up again; or, with more recent versions, the server can use its cached > facts for the client. I would suggest that puppet # do not fail when facter fails, worst case you get a compile error because of a missing fact. # puppet resync facts if facter fail (which is almost the same like today when you have factsync, e.g. puppet syncs the facts and reloaded after factsync). I think that have a cache of facts is way too complex for this problem... and not needed, I don't really wants my clients to compile something with broken facts, i just want an automated way to fix it if it happens (e.g. resync of the new good facts). ---------------------------------------- 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: community 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 -~----------~----~----~----~------~----~------~--~---
