Issue #3144 has been updated by Jesse Wolfe. Target version set to queued
---------------------------------------- Bug #3144: Cached catalogs from incorrect environment can be used on compile failure http://projects.puppetlabs.com/issues/3144 Author: Cedric Jeanneret Status: Accepted Priority: Normal Assigned to: Category: plumbing Target version: queued Affected version: 0.25.4 Keywords: Branch: Hello, I just discovered a nice bug in puppet. we use different environment in our development workflow (say production and toto). While developing in my env (toto), I use to go on the node, and do: puppetd -t --environment toto --noop So far, so good. Unfortunately, there's an error in production (aka default env) (which I'm trying to correct in toto), so that puppet cannot run on "production" environment. What happens: When puppet's launched via our cronjob (we don't use daemon mode - cron does a simple "puppetd -t" each 30 minutes) it seems that puppet take the previous catalogue which was successfully ran. In my case, the catalogue generated on "toto" environment ! What should happen: as previous run was done with "--noop", it shouldn't take generated catalogue Is it really normal ? Thank you. -- 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.
