Issue #17210 has been updated by Josh Cooper. Status changed from Unreviewed to Accepted
if functions require utility code, then deleting the functions or regenerating a scope object for each compile won't be sufficient, as we could get newer functions and older utility code. Really, we need to compile in a separate process to ensure environments are isolated. See also <http://projects.puppetlabs.com/issues/4248#note-29> ---------------------------------------- Bug #17210: Updated functions are not reloaded within a worker process https://projects.puppetlabs.com/issues/17210#change-76723 Author: Erik Dalén Status: Accepted Priority: Normal Assignee: Category: compiler Target version: Affected Puppet version: 3.0.1 Keywords: function loading compiler scope Branch: If a custom function is updated in an environment the workers will continue to use the old version if they had that loaded already. So with multiple passenger workers you get a situation where some puppet runs use the old version of the function and some use the new version, but all use the new versions of the manifest code. To solve this the scope instance for the environment should probably be destroyed after each compilation so the new versions are always loaded in on a new compile. Or just delete the functions from the object. -- 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://projects.puppetlabs.com/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.
