Jira (PUP-7734) puppet.conf bad environment setting breaks ENC correct environment setting
Title: Message Title Josh Cooper commented on PUP-7734 Re: puppet.conf bad environment setting breaks ENC correct environment setting When puppet makes a catalog request, it specifies which environment the agent thinks it's supposed to be in. The server attempts to resolve this environment before checking the ENC. So if the environment directory doesn't exist, then the request will fail. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.197952.1498577662000.80391.1591396560023%40Atlassian.JIRA.
Jira (PUP-7734) puppet.conf bad environment setting breaks ENC correct environment setting
Title: Message Title Josh Cooper commented on PUP-7734 Re: puppet.conf bad environment setting breaks ENC correct environment setting This is a duplicate of PUP-6802 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.197952.1498577662000.80390.1591396440036%40Atlassian.JIRA.
Jira (PUP-7734) puppet.conf bad environment setting breaks ENC correct environment setting
Title: Message Title Anthony Chevalet commented on PUP-7734 Re: puppet.conf bad environment setting breaks ENC correct environment setting Any update? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.197952.1498577662000.137796.1570712280192%40Atlassian.JIRA.
Jira (PUP-7734) puppet.conf bad environment setting breaks ENC correct environment setting
Title: Message Title Henrik Lindberg commented on PUP-7734 Re: puppet.conf bad environment setting breaks ENC correct environment setting The master side is normally authoritative on which env to use for a node. It can however allow a node to select which env to use. Doing so is opening up a security vulnerability though. That said, it is not reasonable that an environment that is not going to be used is flagged as an error when it does not exists if at the same time the ENC is authoritative. When the ENC honours an agent specified environment it must however error if the agent specifies an environment that does not exist. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7734) puppet.conf bad environment setting breaks ENC correct environment setting
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7734 puppet.conf bad environment setting breaks ENC correct environment setting Change By: Henrik Lindberg Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7734) puppet.conf bad environment setting breaks ENC correct environment setting
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7734
puppet.conf bad environment setting breaks ENC correct environment setting
Change By:
Henrik Lindberg
This happens whenever the existing environment doesn't match what the ENC sets, which is fine (names in this post have been changed): {code} Notice: Local environment: 'production' doesn't match server specified node environment 'realenv', switching agent to 'realenv'. {code} If I use "environment = otherrealenv" (something which exists) in the [agent] section of puppet.conf then I get the same error message, which is fine. {code} Notice: Local environment: 'otherrealenv' doesn't match server specified node environment 'realenv', switching agent to 'realenv'. {code} However, when I use an environment that has never existed or previously existed but was removed, things break. {code} Warning: Unable to fetch my node definition, but the agent run will continue:Warning: Find /puppet/v3/node/myhost.me.com?environment=fakeenv_environment=fakeenv resulted in 404 with the message: {"message":"Not Found: Could not find environment 'fakeenv'","issue_kind":"RUNTIME_ERROR"}Info: Retrieving pluginfactsError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve information from environment fakeenv source(s) puppet:///pluginfactsInfo: Retrieving pluginError: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve information from environment fakeenv source(s) puppet:///plugins(Many failing resources here.)Error: Could not retrieve catalog from remote server: Find /puppet/v3/catalog/myhost.me.com?environment=fakeenv_format=pson=%257B... resulted in 404 with the message: {"message":"Not Found: Could not find environment 'fakeenv'","issue_kind":"RUNTIME_ERROR"} {code} The documentation seems to indicate that the ENC environment overrides the agent-requested environment. Not sure if that makes this a documentation bug or a puppet bug, but it's behaviour I did not expect.https://docs.puppet.com/puppet/4.10/configuration.html#environmenthttps://docs.puppet.com/puppet/4.10/nodes_external.html#considerations-and-differences-from-node-definitions"In Puppet 3 and later, ENCs can set an environment for a node, overriding whatever environment the node requested."For use case background:The informational message about how the current environment "doesn't match server specified node environment" was causing some consternation so I used the environment setting to make it go away. (Apparently it sounded like an error message.)This breaks a bit when we have ephemeral environments; somebody may remove an environment (via r10k) but forget to change the ENC classification and do an agent run first. When they remove the environment before those steps the fix is to manually update puppet.conf to remove the environment line, which works against the lesson that people should only use puppet to update server configs.
Jira (PUP-7734) puppet.conf bad environment setting breaks ENC correct environment setting
Title: Message Title Christopher Wood created an issue Puppet / PUP-7734 puppet.conf bad environment setting breaks ENC correct environment setting Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Created: 2017/06/27 8:34 AM Environment: cat /etc/redhat-release CentOS release 6.9 (Final) # uname -a Linux mail10c7 2.6.32-696.3.2.el6.x86_64 #1 SMP Tue Jun 20 01:26:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux rpm -q puppet-agent puppet-agent-1.10.1-1.el6.x86_64 Priority: Minor Reporter: Christopher Wood This happens whenever the existing environment doesn't match what the ENC sets, which is fine (names in this post have been changed):
