Issue #16789 has been updated by Jeff McCune. Description updated Target version changed from 3.x to 3.0.x Keywords set to environment autoritative
I hope to have this investigated the call of business today. If it is a bug in 3.0.0 I hope to see this fixed in 3.0.1, but we can't make promises at this point in time. Thanks for letting us know about the issue. -Jeff ---------------------------------------- Bug #16789: server overridding client set environments https://projects.puppetlabs.com/issues/16789#change-72652 Author: Matthew Nicholson Status: Unreviewed Priority: High Assignee: Category: environments Target version: 3.0.x Affected Puppet version: 3.0.0 Keywords: environment autoritative Branch: Running a 3.0.0 client with a specific environment yields: [root@nichols2tst ~]# puppet --version 3.0.0 [root@nichols2tst ~]# puppet agent --test --environment=puppet3 Warning: Local environment: "puppet3" doesn't match server specified node environment "production", switching agent to "production". the same results occurs with environment set in the clients puppet.conf I can verify we ware NOT using a ENC setting environments (node_terminus = plain, just nodes.pp for us) Doing the same on a 2.7.19 client works as expected (the client uses the environment specified) # References * [Puppet Users - environment set by client issues on nodes running 3.0.0](https://groups.google.com/d/topic/puppet-users/vRL5k2bnKTk/discussion) -- 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.
