Issue #16789 has been updated by Jeff McCune. Status changed from Investigating to Needs More Information Assignee changed from Jeff McCune to Matthew Nicholson
I'm unable to reproduce this issue with 3.0.0 I've tried the following `puppet.conf` files for the Puppet master: ## Dynamic Environments <pre> [main] certname = mccune.local node_name_value = mccune.local server = mccune.local vardir = $confdir/var.shared ssldir = $vardir/ssl masterport = 8141 environment = production manifest = $confdir/manifests/site.$environment.pp modulepath = $confdir/modules.$environment:/usr/share/puppet/modules [agent] certname = mccune.agent node_name_value = mccune.agent pluginsync = false # vardir = $confdir/var.agent [master] vardir = $confdir/var.master # vim:filetype=conf </pre> ## Static environments: <pre> [main] certname = mccune.local node_name_value = mccune.local server = mccune.local vardir = $confdir/var.shared ssldir = $vardir/ssl masterport = 8141 [agent] certname = mccune.agent node_name_value = mccune.agent pluginsync = false # vardir = $confdir/var.agent [master] vardir = $confdir/var.master # Static Environments [development] manifest = $confdir/manifests/site.development.pp modulepath = $confdir/modules.development:/usr/share/puppet/modules # vim:filetype=conf </pre> ## Agent perspective: <pre> $ puppet agent --test --environment=development Info: Loading facts in /workspace/puppet-3.x/etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb Info: Loading facts in /workspace/puppet-3.x/etc/puppet/modules/stdlib/lib/facter/root_home.rb Info: Caching catalog for mccune.agent Info: Applying configuration version '1349462313' Environment: development /Stage[main]//Node[default]/Notify[site.development.pp]/message: defined 'message' as 'Environment: development' Finished catalog run in 0.38 seconds $ puppet agent --test Info: Loading facts in /workspace/puppet-3.x/etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb Info: Loading facts in /workspace/puppet-3.x/etc/puppet/modules/stdlib/lib/facter/root_home.rb Info: Caching catalog for mccune.agent Info: Applying configuration version '1349462294' Environment: production /Stage[main]//Node[default]/Notify[site.pp]/message: defined 'message' as 'Environment: production' Finished catalog run in 0.37 seconds </pre> # request for additional information Matthew, Could you please post any additional information you have that might help me understand why you're running into this issue? How have you installed Puppet 3.0 on your master? Could you provide an exact replica of your puppet.conf from the master? What command line arguments are you using to start the master? I'll keep trying to reproduce this issue until I hear back from you, but I feel like I'm taking shots in the dark at this point. Any help reproducing the issue will help me tremendously. Thanks, -Jeff ---------------------------------------- Bug #16789: server overridding client set environments https://projects.puppetlabs.com/issues/16789#change-72802 Author: Matthew Nicholson Status: Needs More Information Priority: High Assignee: Matthew Nicholson 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.
