Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language

[Jeremy Barlow (JIRA)]

Title: Message Title

Jeremy Barlow commented on PUP-6582   Re: The environment cache erroneously caches the resultant values of functions defined purely in the puppet language Both Ryan Whitehurst and I were able to reproduce this just with a stock Puppet Server 2.4.0 / Puppet Agent 1.5.3 / Puppet 4.5.3 install without the versioned code service / code-id functionality being enabled on the server. For reference, here are the files I was using: /etc/puppetlabs/code/environments/production/environment.conf environment_timeout = unlimited /etc/puppetlabs/code/environments/production/manifests/site.pp include uptime /etc/puppetlabs/code/environment/production/modules/uptime/manifests/init.pp class uptime { notify { 'current uptime': message => uptime::my_system_uptime() } } /etc/puppetlabs/code/environment/production/modules/uptime/functions/my_system_uptime.pp function uptime::my_system_uptime() { $facts['system_uptime'] } When I do a verbose agent run against the master, I see the agent's uptime echoed back: Notice: /Stage[main]/Uptime/Notify[current uptime]/message: defined 'message' as '{"days"=>0, "hours"=>0, "seconds"=>2908, "uptime"=>"0:48 hours"}' With "environment_timeout" set to "unlimited", I get the same content in the message for each run. With "environment_timeout" set to "0", however, I get a new/updated time for each run. I see this behavior both via the puppetserver service and via pure Ruby Puppet / WEBrick - just running /opt/puppetlabs/puppet/bin/puppet master --no-daemonize from the command line. Given that the problem appears with the pure Ruby setup, it would seem that Puppet Server shouldn't be related to the problem. I don't believe anything in either of these configurations would have directly invoked any new Direct Puppet-specific functionality. The versioned code service (which enables the use of code-ids) was not enabled when testing with Puppet Server and would not have been in play at all when testing via the pure Ruby / WEBrick configuration. Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.