On Thu, Oct 4, 2012 at 8:46 AM, Matthew Nicholson <matthew.a.nichol...@gmail.com> wrote: > So, we use dynamic environments based off of git branches. Thus, for > the 3.0 upgrade, i've got a puppet3 branch. So far, on the change in > there is to have nodes running from it upgrade to puppet 3.0.0, > > so, I can take a node, and do: > > puppet agent --test --environment=puppet3 > and this will install 3.0.0, as well as edit the environment in > /etc/puppet/puppet.conf on the node to be "puppet3" > > However, subsequent runs, with with --environment=puppet3 passed, or > relying on the puppet.conf setting, of the now 3.0.0 node, results in: > > Warning: Local environment: "puppet3" doesn't match server specified > node environment "production", switching agent to "production".
This definitely looks like a bug in 3.0.0. The behavior we intend is that an ENC can override the client specified environment, but it sounds like you are not using an ENC. Is that correct? If you are using an ENC, could you verify that the ENC is not setting the environment parameter? -Jeff -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
