Environment: Puppet 3.8.4 Puppetserver 1.1.3 We were using an old version of the Foreman modules that included a custom function cache_data.rb. This function called for 2 arguments. We are in the process of upgrading the Foreman modules, which removes this custom cache_data function in favor of including a new module "extlib" which comes with an upgraded cache_data function that calls for 3 arguments.
In testing the upgrade, I merged my new code into an existing development environment, then pushed that code to the puppetmaster. When attempting to apply the new environment, puppet failed to compile the catalog because of the argument mismatch. I went back to the puppetmaster and made sure to run the v1 api environment_cache to expire all existing puppet caches, and confirmed that the puppetserver.log file showed all caches were marked as expired. Back on the dev server, the problem persisted. Next, I restarted the puppetserver service, which fixed the issue. The dev server was able to properly apply the catalog. My question is if this is a known issue where the 'environment_cache' api call does not expire custom functions, or if this is working as designed? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/df8b72f3-c411-4912-9fac-a7d9e5af39d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
