Jira (PUP-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Benjamin Rechsteiner commented on PUP-4707 Re: environment_timeout in puppet.conf not honored if environmentpath does not exist at startup Josh Cooper as i can see in puppet 7 environment_timeout and environment_ttl still not honored whether environmentpath is set or not. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.83430.1433557323000.5761.1675084200024%40Atlassian.JIRA.
Jira (PUP-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Josh Cooper commented on PUP-4707 Re: environment_timeout in puppet.conf not honored if environmentpath does not exist at startup The environment_timeout setting will be removed in puppet 7 replaced with environment_ttl, which will be global/not per-environment, so it won't have the ordering issues described here. 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.83430.1433557323000.45638.1601408700119%40Atlassian.JIRA.
Jira (PUP-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4707 environment_timeout in puppet.conf not honored if environmentpath does not exist at startup Change By: Josh Cooper Sub-team: Coremunity 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 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-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title John Duarte updated an issue Puppet / PUP-4707 environment_timeout in puppet.conf not honored if environmentpath does not exist at startup Change By: John Duarte Labels: triaged 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-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-4707 environment_timeout in puppet.conf not honored if environmentpath does not exist at startup Change By: Moses Mendoza Team: Puppet Developer Experience 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-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4707 environment_timeout in puppet.conf not honored if environmentpath does not exist at startup Change By: Henrik Lindberg Team: Puppet Developer Support 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-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-4707
environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Change By:
Charlie Sharpsteen
CS Severity:
2
CS Impact:
Havingno{{environmentpath}}seemslikeasituationthatisunlikelytoariseinproduction.Theremediationforthisisalsoprettysimple:restartthepuppetmasterafterfixingthemissingdirectory.
CS Priority:
Minor
CS Frequency:
1
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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
Jira (PUP-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Christopher Price commented on PUP-4707 Re: environment_timeout in puppet.conf not honored if environmentpath does not exist at startup FYI if anyone is thinking about fixing this, PE-10214 might be of interest. I'm wondering if we can get rid of this TTL stuff altogether. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Henrik Lindberg commented on PUP-4707 Re: environment_timeout in puppet.conf not honored if environmentpath does not exist at startup Christopher Price The TTL was introduced as a way to not having to do excessive file stats (a performance bottleneck the way it was implemented), and the fact that any file change at any time could invalidate the compilation and make it start over. The most bizarre effect being that you can end up with a mix of old and new. I much more prefer an atomic change which requires that updates to the running code is managed and letting compilations finish before changing the source. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4707 environment_timeout in puppet.conf not honored if environmentpath does not exist at startup Change By: Kylo Ginsberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Kevin Corcoran commented on PUP-4707 Re: environment_timeout in puppet.conf not honored if environmentpath does not exist at startup ping Kylo Ginsberg Ruth Linehan look what I did! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Kevin Corcoran commented on PUP-4707 Re: environment_timeout in puppet.conf not honored if environmentpath does not exist at startup As Ruth Linehan was just pointing out, deleting the $environmentpath/production directory might also cause this as well. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Kevin Corcoran created an issue Puppet / PUP-4707 environment_timeout in puppet.conf not honored if environmentpath does not exist at startup Issue Type: Bug Affects Versions: PUP 4.1.0, PUP 4.0.0 Assignee: Unassigned Created: 2015/06/05 7:22 PM Priority: Normal Reporter: Kevin Corcoran If environmentpath does not exist when the Puppet Master is started, environment_timeout in puppet.conf has no effect. e.g. Running with environment_timeout = 1y in puppet.conf still exhibits the default behavior of not caching environments (environment_timeout = 0). Here are steps to reproduce; I've used Puppet Server for this, but I'm reasonably certain the problem is in Puppet itself, not Puppet Server, and I'd expect the same behavior in any other type of Puppet master. #1 - Delete environmentpath rm -rf /etc/puppetlabs/code/environments
