FAQ
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".

at which point it re-write the puppet.conf and downgrades back to
2.7.19 (which, is cool that is WORKS, isn't what i want).

Now, I don't HAVE the environment defined sever side for this node.
with 2.7.x clients, everything is production unless the client
specifies otherwise. Is this a new behavior on 3.0?

all looks like:

http://projects.puppetlabs.com/issues/3910#note-82

https://github.com/puppetlabs/puppet/commit/43e15f57c0f3866423a8bd67d3cdb5b2e06b31cc

http://projects.puppetlabs.com/issues/16275

but has this not been merged to the release 3.0.0 code yet?

Thanks!

--
Matthew Nicholson

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Search Discussions

  • Jeff McCune at Oct 4, 2012 at 4:32 pm

    On Thu, Oct 4, 2012 at 8:46 AM, Matthew Nicholson 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+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
  • Matthew Nicholson at Oct 4, 2012 at 4:39 pm
    correct, no enc, just nodes.pp (node_terminus=plain)(ugh, yes, i know).

    previously had the following in puppet.conf on our master(s):

    environment = production
    manifest = /etc/puppet/environments/$environment/manifests/site.pp
    modulepath=/etc/puppet/environments/$environment/modules


    so things would always default to production unless specified. i
    commented out the environment = production line just to test, and
    there were no changes.

    On Thu, Oct 4, 2012 at 12:31 PM, Jeff McCune wrote:
    On Thu, Oct 4, 2012 at 8:46 AM, Matthew Nicholson
    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+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.


    --
    Matthew Nicholson

    --
    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+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
  • Matthew Nicholson at Oct 4, 2012 at 6:12 pm
    File a bug report ? or is this an already tracked issue?

    On Thu, Oct 4, 2012 at 12:39 PM, Matthew Nicholson
    wrote:
    correct, no enc, just nodes.pp (node_terminus=plain)(ugh, yes, i know).

    previously had the following in puppet.conf on our master(s):

    environment = production
    manifest = /etc/puppet/environments/$environment/manifests/site.pp
    modulepath=/etc/puppet/environments/$environment/modules


    so things would always default to production unless specified. i
    commented out the environment = production line just to test, and
    there were no changes.

    On Thu, Oct 4, 2012 at 12:31 PM, Jeff McCune wrote:
    On Thu, Oct 4, 2012 at 8:46 AM, Matthew Nicholson
    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+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.


    --
    Matthew Nicholson


    --
    Matthew Nicholson

    --
    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+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
  • Jeff McCune at Oct 4, 2012 at 6:59 pm

    On Thu, Oct 4, 2012 at 11:12 AM, Matthew Nicholson wrote:
    File a bug report ? or is this an already tracked issue?
    If you could file a bug report and then reply here with the ticket
    number, that will help tremendously. In the meantime I'm going to
    start investigating and try to reproduce the issue here.

    Thanks for reporting this,
    -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+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
  • Matthew Nicholson at Oct 4, 2012 at 9:17 pm
    https://projects.puppetlabs.com/issues/16789
    On Thu, Oct 4, 2012 at 2:58 PM, Jeff McCune wrote:
    On Thu, Oct 4, 2012 at 11:12 AM, Matthew Nicholson
    wrote:
    File a bug report ? or is this an already tracked issue?
    If you could file a bug report and then reply here with the ticket
    number, that will help tremendously. In the meantime I'm going to
    start investigating and try to reproduce the issue here.

    Thanks for reporting this,
    -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+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.


    --
    Matthew Nicholson

    --
    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+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppuppet-users @
categoriespuppet
postedOct 4, '12 at 3:46p
activeOct 4, '12 at 9:17p
posts6
users2
websitepuppetlabs.com

2 users in discussion

Matthew Nicholson: 4 posts Jeff McCune: 2 posts

People

Translate

site design / logo © 2022 Grokbase