Issue #5213 has been reported by Jordan Sissel. ---------------------------------------- Bug #5213: Exported 'environment' value is write-once https://projects.puppetlabs.com/issues/5213
Author: Jordan Sissel Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.6.2 Keywords: Branch: In testing tonight, I deployed a change that changed the environment for a server. The new environment should have been 'staging1'. Running puppet with storeconfigs on (like the rest of my puppet runs) does not update this value: <pre> mysql> select name, environment from hosts where name = "ops.staging1.loggly.net"; +-------------------------+-------------+ | name | environment | +-------------------------+-------------+ | ops.staging1.loggly.net | production | +-------------------------+-------------+ </pre> Strange. After deleting the entry in the hosts table and rerunning puppet, the new 'environment' value takes effect. If I then try to run puppet with --environment somethingdifferent, the value stays as previous. This value appears write-once. This is unexpected and I believe it is a bug. Reproduced on puppet 2.6.2, ubuntu 10.04, ruby 1.8.7, activerecord (3.0.1), ruby-mysql (2.9.3) -- 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.
