Jira (PDB-5349) PuppetDB blocks primary on restart
Title: Message Title Nick Walker commented on PDB-5349 Re: PuppetDB blocks primary on restart The track we've gone down on this issue is basically to make the blocking portion of startup go as fast as possible. We don't sync reports during that blocking part now, we stopped doing GC on startup and possibly other small improvements. It's not clear that starting without syncing "enough" data is safe to allow agents to query against. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.421318.1635347225000.12797.1644436260034%40Atlassian.JIRA.
Jira (PUP-7136) Enable the tracing of lookup calls on a per-node basis
Title: Message Title Nick Walker commented on PUP-7136 Re: Enable the tracing of lookup calls on a per-node basis chuck has anything changed with this in the past 4-5 years? Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.172347.1485459833000.10441.1640198820334%40Atlassian.JIRA.
Jira (PDB-5224) Investigate query performance for "CD4PE - code manager resource"
Title: Message Title Nick Walker commented on PDB-5224 Re: Investigate query performance for "CD4PE - code manager resource" Eric Williamson or Chris Leicester do you know why we are looking for the results of this query? It is apparently pretty slow and I'm wondering if we can get this info another way. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.409157.1627566387000.147148.1633445520053%40Atlassian.JIRA.
Jira (PUP-11163) Prevent thundering herd via deterministic run scheduling
Title: Message Title Nick Walker commented on PUP-11163 Re: Prevent thundering herd via deterministic run scheduling I think this is basically the same request I made in the past via PUP-4212. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.406175.1625677218000.141553.1632863520038%40Atlassian.JIRA.
Jira (PDB-4386) Improve performance of catalog inserts/updates (by using an UPSERT)
Title: Message Title Nick Walker commented on PDB-4386 Re: Improve performance of catalog inserts/updates (by using an UPSERT) I'm a little skeptical of the reasoning here. However, even if we don't go with a full UPSERT it appears that we are updating, deleting, and maybe inserting a single row at a time instead of doing them as a single operation. It seems like at a minimum we could fetch all the records, do an UPSERT as one operation for insert and update ( instead of one operation per row that needs to be updated or inserted ), and then a delete as a single operation. I suspect it would still be better to write a single temp table that represents the new catalog and then an UPSERT followed by a delete but even without that I think removing all of the single row inserts and updates would be a boost. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.310840.155925674.42521.1622051100051%40Atlassian.JIRA.
Jira (PUP-8600) plugin-sync the data-types from all modules
Title: Message Title Nick Walker commented on PUP-8600 Re: plugin-sync the data-types from all modules adding this without making pluginsync faster seems like a risk since we'll be adding a lot of files. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.242740.1521815941000.11629.1618595700091%40Atlassian.JIRA.
Jira (FACT-3003) Don't split keys for already structured json/yaml external facts
Title: Message Title
Nick Walker commented on FACT-3003
Re: Don't split keys for already structured json/yaml external facts
If the users intent is to make a structured fact with a dot in the name of the fact there are 2 ways 1. ruby custom fact
Facter.add( "a.b" ) do
setcode do
{ c = true }
end
end
2. an external fact ( either a script of a json/yaml file )
{ "a.b": { "c": true } } Given these two examples it does not make sense to treat a json/yaml file on disk differently than the Facter.add example. If the users intent is to have a structured fact with dots in the name we have no way of knowing that from either of these examples. Both examples appear the same and both will result in the fact a = { b => { c => true } } } in Facter 4 which is new behavior compared to Facter 3 which would have made a.b = { c => true } . This ticket is closed as won't fix because we're assuming we want to keep the behavior of Facter 4 treating dots specially. If we want to revert that behavior it's a different request altogether.
Jira (FACT-3003) Don't split keys for already structured json/yaml external facts
Title: Message Title Nick Walker assigned an issue to Nick Walker Facter / FACT-3003 Don't split keys for already structured json/yaml external facts Change By: Nick Walker Assignee: Nick Walker 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.393500.1617226466000.179711.1617293640138%40Atlassian.JIRA.
Jira (PUP-8600) plugin-sync the data-types from all modules
Title: Message Title Nick Walker commented on PUP-8600 Re: plugin-sync the data-types from all modules Josh Cooper thoughts? I feel like this was on your radar already for some reason. 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.242740.1521815941000.178841.1617214920228%40Atlassian.JIRA.
Jira (FACT-3000) Dot notation implemented in Facter 4 is incomplete
Title: Message Title
Nick Walker updated an issue
Facter / FACT-3000
Dot notation implemented in Facter 4 is incomplete
Change By:
Nick Walker
Primary problem: - There is no way to override, block, or cache facts that contain a dot in the name or sub-key Facter 4 introduced compositive fact structuring via dot-notation as a feature. However, the dot-notation implementation used is incomplete, and behaves differently from dot-notation elsewhere in the ecosystem.Specifically, Facter 4 dot-notation splits key segments incorrectly, because it does not recognize the use of double or single quotes to indicate keys which contain literal dot characters.The reference implementation for dot-notation is found in Puppet, [here|https://github.com/puppetlabs/puppet/blob/85bd9ed07e3e6c956f1972624a50be914292e1ab/lib/puppet/pops/lookup/sub_lookup.rb#L6-L44].Full dot-notation should be supported everywhere Facter 4 currently evaluates dot-notation strings to segment structured fact names. This includes external fact output (text, json, yaml), as well as {{Facter.add()}}.*Today's behavior*Consider the following plain-text custom fact file:{code}foo.bar._one_=1foo.bar.two=2foo."i.have.dots"=3"me.too"=4{code}Today, Facter 4 returns the following for these facts.{code:json}{ "foo": {"bar": { "one": "1", "two": "2"},"\"i": { "have": {"dots\"": "3" }} }, "\"me": {"too\"": "4" }}{code}This is incorrect.*Correct behavior*Full and correct support for dot-notation SHOULD give:{code:json}{ "foo": {"bar": { "one": "1", "two": "2"},"i.have.dots": "3" }, "me.too": "4"}{code}
Add Comment
Jira (PUP-10985) `puppet facts diff` does not output facts that only exist in Facter 4
Title: Message Title
Nick Walker created an issue
Puppet / PUP-10985
`puppet facts diff` does not output facts that only exist in Facter 4
Issue Type:
Task
Assignee:
Unassigned
Created:
2021/03/25 12:07 PM
Priority:
Normal
Reporter:
Nick Walker
The Problem Given the following facts
Given the following facts:
cat /opt/puppetlabs/facter/facts.d/foo.bar.txt
foo.bar=true
cat /opt/puppetlabs/facter/facts.d/c.d.json
{
"c.d":
Jira (PUP-10985) `puppet facts diff` does not output facts that only exist in Facter 4
Title: Message Title Nick Walker assigned an issue to Mihai Buzgau Puppet / PUP-10985 `puppet facts diff` does not output facts that only exist in Facter 4 Change By: Nick Walker Assignee: Mihai Buzgau 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.392859.1616699279000.174573.1616699340113%40Atlassian.JIRA.
Jira (PUP-10973) `puppet facts diff` output should be pretty
Title: Message Title Nick Walker updated an issue Puppet / PUP-10973 `puppet facts diff` output should be pretty Change By: Nick Walker Issue Type: Task Improvement 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.392811.1616691172000.174333.1616691240029%40Atlassian.JIRA.
Jira (PUP-10973) `puppet facts diff` output should be pretty
Title: Message Title
Nick Walker created an issue
Puppet / PUP-10973
`puppet facts diff` output should be pretty
Issue Type:
Task
Assignee:
Unassigned
Created:
2021/03/25 9:52 AM
Priority:
Normal
Reporter:
Nick Walker
The Problem The output of `puppet facts diff` is all smashed on one line instead of being human readable.
[root@master20198-latest-centos ~]# puppet facts diff
{"foo.bar":{"new_value":null,"old_value":"true"},"pe_postgresql_info.data_partition_available_bytes":{"new_value":59176595456,"old_value":59176505344},"platform_tag":{"new_value":"centos-7-x86_64","old_value":"el-7-x86_64"},"puppet_inventory_metadata.packages.last_collection_time":{"new_value":"0.4702s","old_value":"0.588s"}}
I have to run it through another tool like python or jq to effectively read the output
[root@master20198-latest-centos ~]# puppet facts diff | python -m json.tool
Jira (PDB-5070) Determine query that provides (dotted) factpaths
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-5070
Determine query that provides (dotted) factpaths
Change By:
Nick Walker
h1. Background Facter 4 auto-converts facts with dots in the *name* to make it a structured fact.So {code}foo.bar = true{code} becomes {code}foo = { bar => true }{code} However, you can still have dots in keys inside of a structured fact so{code} baz = { zzz.yyy => true } {code} does not change in facter 4 because keys inside of a structured fact can contain dots without getting auto-converted. Only the top level name of a fact is auto-converted when it contains dots. h1. What we need to do We need to construct a pdb query that can determine if customers currently have facts with dots in the name of the fact but not worry about keys inside of a structured fact. This is so we can find cases where users with puppet < 7 will be affected by this change and can prepare appropriately because they know they are affected.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-5070) Determine query that provides (dotted) factpaths
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-5070
Determine query that provides (dotted) factpaths
Change By:
Nick Walker
Facter 4 auto-converts facts with dots in the *name* to make it a structured fact.So {code}foo.bar = true{code} becomes {code}foo = { bar => true }{code} However, you can still have dots in keys inside of a structured fact so{code} baz = { zzz.yyy => true } {code} does not change in facter 4 because keys inside of a structured fact can contain dots without getting auto-converted. Only the top level name of a fact is auto-converted when it contains dots.
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
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Nick Walker assigned an issue to Mihai Buzgau Facter / FACT-2994 selinux fact is not properly detected by Facter 4 Change By: Nick Walker Assignee: Mihai Buzgau 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.391989.1616519382000.171881.1616520720325%40Atlassian.JIRA.
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Nick Walker updated an issue Facter / FACT-2994 selinux fact is not properly detected by Facter 4 Change By: Nick Walker Priority: Normal Critical 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.391989.1616519382000.171874.1616520660098%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title Nick Walker commented on PUP-10946 Re: Recursive file resources generate dangerous numbers of resource events We have a best practice recommendation around recursive file resources. https://github.com/puppetlabs/best-practices/blob/master/recursive-file-resources.md I wonder if we can move that more officially into the Puppet documentation and then beyond that if it would make sense to include something like this defined type more officially in Puppet as well or we could just mark it supported on the forge and point to it from the documentation. https://forge.puppet.com/modules/npwalker/recursive_file_permissions 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.389668.1614728039000.159727.1615220040029%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Nick Walker commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails Vadym Chepkov reports this is still happening in his install. He's going to report back when he upgrades to PE 2019.8.5 if this is still happening. 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.381638.1608653215000.153260.1614367620120%40Atlassian.JIRA.
Jira (PDB-4595) Update PDB terminus to pull data out of the template key recorder
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-4595 Update PDB terminus to pull data out of the template key recorder Change By: Nick Walker Team: Froyo 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.337543.1575402727000.146389.1613750700120%40Atlassian.JIRA.
Jira (PUP-10156) Record function calls with KeyRecorder
Title: Message Title Nick Walker updated an issue Puppet / PUP-10156 Record function calls with KeyRecorder Change By: Nick Walker Team: Froyo 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.337548.1575403967000.146390.1613750700129%40Atlassian.JIRA.
Jira (PUP-10155) Record template evaluations with KeyRecorder
Title: Message Title Nick Walker updated an issue Puppet / PUP-10155 Record template evaluations with KeyRecorder Change By: Nick Walker Team: Froyo 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.337541.1575402488000.146388.1613750700060%40Atlassian.JIRA.
Jira (PUP-10012) Impact Analysis: Functions and Templates
Title: Message Title Nick Walker updated an issue Puppet / PUP-10012 Impact Analysis: Functions and Templates Change By: Nick Walker Team/s: Froyo CD4PE 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.323829.156778568.146387.1613750580107%40Atlassian.JIRA.
Jira (FACT-2934) Facter::Core::Execution does not set status variables in Facter 4
Title: Message Title Nick Walker commented on FACT-2934 Re: Facter::Core::Execution does not set status variables in Facter 4 Mihai BuzgauGheorghe Popescu 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.385912.1612301794000.131307.1612302780148%40Atlassian.JIRA.
Jira (FACT-2918) FACTER_ environmental facts overrides don't work with external facts
Title: Message Title Nick Walker commented on FACT-2918 Re: FACTER_ environmental facts overrides don't work with external facts Kenneth Pepiton thanks for the response. It wasn't clear from the description that this used to work and it is a regression. During triage we thought it never worked in Puppet. I was able to reproduce that it worked in PE 2018.1.10 and does not work in PE 2019.8.4. [root@master-masterbranch-centos ~]# puppet --version 6.20.0 [root@master-masterbranch-centos ~]# cat /opt/puppetlabs/server/pe_build 2019.8.5-rc2-160-g4af732b [root@master-masterbranch-centos ~]# FACTER_test_fact=blah puppet facts show | grep test "test_fact": "blah", [root@master-masterbranch-centos ~]# mkdir /etc/puppetlabs/facter [root@master-masterbranch-centos ~]# mkdir /etc/puppetlabs/facter/facts.d [root@master-masterbranch-centos ~]# vim /etc/puppetlabs/facter/facts.d/test_fact.txt [root@master-masterbranch-centos ~]# FACTER_test_fact=blah puppet facts show | grep test "test_fact": "foo",
Jira (FACT-2918) FACTER_ environmental facts overrides don't work with external facts
Title: Message Title Nick Walker commented on FACT-2918 Re: FACTER_ environmental facts overrides don't work with external facts While this is inconsistent behavior... it's unclear what use case makes this a problem over just setting an external fact in a file. The recommendation is just to set the external fact in a file to get it to show in the puppet run. We don't intend to fix this as when running from the puppet daemon setting facts from environment variables is likely not an expected use case. 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.383195.1610609261000.117883.1611071280252%40Atlassian.JIRA.
Jira (PUP-10819) Improve error handling when a 3x function is deferred
Title: Message Title Nick Walker commented on PUP-10819 Re: Improve error handling when a 3x function is deferred We should provide a clear error that we could not load a 3x function so that users have a better idea of what to do next. For any built-in functions that are still 3x we should convert them to 4x functions. This will avoid the issue for any built-in functions but we'll still have the error case above for 3x functions from stdlib or other modules. Generally speaking we should look to convert functions people want to 4x instead of trying to work on loading 3x functions. 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.380575.1607560522000.107813.1609862760022%40Atlassian.JIRA.
Jira (PUP-10842) Issue with puppet creating production folder when multiple environment paths are set
Title: Message Title Nick Walker updated an issue Puppet / PUP-10842 Issue with puppet creating production folder when multiple environment paths are set Change By: Nick Walker Priority: Normal Major 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.381531.1608552353000.104827.1608570240030%40Atlassian.JIRA.
Jira (PUP-10813) Unit test error with file resource content using find_template()
Title: Message Title Nick Walker commented on PUP-10813 Re: Unit test error with file resource content using find_template() hi GeorgesZ. Can you upload a module example of this code? And can you confirm that the module actually works when run via puppet? We're having a hard time telling what the reproduction case is as the example code above includes two variables which aren't defined. If you can provide a module with just the minimum code to reproduce an issue that'd be great. We want to make sure it runs via puppet and then we can look at how rspec is failing. 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.380125.1607383066000.98374.1608049380024%40Atlassian.JIRA.
Jira (PUP-10677) Gem provider should install gems on the system ruby on Windows
Title: Message Title Nick Walker updated an issue Puppet / PUP-10677 Gem provider should install gems on the system ruby on Windows Change By: Nick Walker Summary: Gem provider should install gems on the system ruby on Windows 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.361146.1591175992000.91831.1607116560043%40Atlassian.JIRA.
Jira (PUP-10178) split function shouldn't coerce strings to regex
Title: Message Title Nick Walker commented on PUP-10178 Re: split function shouldn't coerce strings to regex Ben Ford what's the play here? I think we shouldn't change the default behavior so we don't break people relying on the weird behavior. So do we just close this or should we reword this to be about augmenting the function or adding a new one to accomplish whatever needs to be accomplished? 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.339939.1576610242000.47941.1601658420045%40Atlassian.JIRA.
Jira (FACT-2823) SPIKE - Investigate turning facter into a single binary
Title: Message Title Nick Walker updated an issue Facter / FACT-2823 SPIKE - Investigate turning facter into a single binary Change By: Nick Walker Having a standalone executable of Facter would allow for easily shipping Facter down to a node and gathering facts. This would enable Bolt to gather facts for nodes without installing the full puppet-agent package. Possible options: [https://github.com/pmq20/ruby-packer]This is a spike to determine how technically feasible it is to make Facter into a single binary. We can start by looking into making a binary for EL. 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
Jira (FACT-2823) SPIKE - Investigate turning facter into a single binary
Title: Message Title Nick Walker created an issue Facter / FACT-2823 SPIKE - Investigate turning facter into a single binary Issue Type: New Feature Assignee: Unassigned Created: 2020/09/30 8:57 AM Priority: Normal Reporter: Nick Walker Having a standalone executable of Facter would allow for easily shipping Facter down to a node and gathering facts. This would enable Bolt to gather facts for nodes without installing the full puppet-agent package. Possible options: https://github.com/pmq20/ruby-packer This is a spike to determine how technically feasible it is to make Facter into a single binary. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH
Title: Message Title Nick Walker commented on PUP-6488 Re: Gem provider should allow alternative gem command; should not rely on $PATH For reference this issue causes the following issue in environments that have puppetserver_gem installed and do not upgrade to v1.1.1. Could not prefetch package provider 'puppetserver_gem': No command gemcmd defined for provider puppetserver_gem Failed to apply catalog: No command gemcmd defined for provider puppetserver_gem 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
Jira (PUP-10604) Include the puppetserver_gem package provider with core Puppet
Title: Message Title Nick Walker commented on PUP-10604 Re: Include the puppetserver_gem package provider with core Puppet Looks like we can close MODULES-2276 and need to open a new ticket to deprecate puppetserver_gem on the forge? cc Ben Ford 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.367865.1596151607000.32504.1599661800120%40Atlassian.JIRA.
Jira (PUP-10593) Puppet 7 Server
Title: Message Title Nick Walker updated an issue Puppet / PUP-10593 Puppet 7 Server Change By: Nick Walker Team/s: Froyo 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.366800.1595350687000.1367.1595614140033%40Atlassian.JIRA.
Jira (PDB-4809) Corrective change every puppet run "GRANT CONNECT ON DATABASE "pe-puppetdb" TO "pe-puppetdb"' (corrective)"
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-4809 Corrective change every puppet run "GRANT CONNECT ON DATABASE "pe-puppetdb" TO "pe-puppetdb"' (corrective)" Change By: Nick Walker Team: HA Installer and Management 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.365371.1594291829000.103823.1594305960036%40Atlassian.JIRA.
Jira (PUP-10306) Environments should track their version
Title: Message Title Nick Walker updated an issue Puppet / PUP-10306 Environments should track their version Change By: Nick Walker Epic Link: PE CODEMGMT - 26632 1270 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.347141.1582240386000.68596.1590170520027%40Atlassian.JIRA.
Jira (PUP-10266) Environment cache should store previous versions of environments
Title: Message Title Nick Walker updated an issue Puppet / PUP-10266 Environment cache should store previous versions of environments Change By: Nick Walker Epic Link: PE CODEMGMT - 26632 1270 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.344927.1580776369000.68595.1590170460250%40Atlassian.JIRA.
Jira (PUP-10312) The agent should ensure it uses the same version of its environment thoughout a run
Title: Message Title Nick Walker updated an issue Puppet / PUP-10312 The agent should ensure it uses the same version of its environment thoughout a run Change By: Nick Walker Epic Link: PE CODEMGMT - 26632 1270 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.347421.1582585759000.68588.1590170280185%40Atlassian.JIRA.
Jira (PUP-8014) Create an environment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Nick Walker updated an issue Puppet / PUP-8014 Create an environment_ttl setting to clear short-lived puppet environments from memory Change By: Nick Walker Labels: ondeck1 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.214193.1506980344000.68553.1590169260085%40Atlassian.JIRA.
Jira (PUP-10504) remote filebucket operation generates errors in puppet 6.15
Title: Message Title Nick Walker commented on PUP-10504 Re: remote filebucket operation generates errors in puppet 6.15 I installed 2019.5, enabled filebucket, then upgraded to 2019.7 and I cannot reproduce the error. 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.358524.158931650.60608.1589318520022%40Atlassian.JIRA.
Jira (PUP-1519) Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number
Title: Message Title Nick Walker updated an issue Puppet / PUP-1519 Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number Change By: Nick Walker Fix Version/s: PUP 6.16.0 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.24581.1390679442000.59851.1589294040059%40Atlassian.JIRA.
Jira (PUP-9648) Drop PSON support
Title: Message Title Nick Walker commented on PUP-9648 Re: Drop PSON support Would this cause older versions of the agent to no longer be able to connect to platform 7 masters? 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.305621.1555690549000.59159.1589223180022%40Atlassian.JIRA.
Jira (PUP-10432) RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Title: Message Title Nick Walker updated an issue Puppet / PUP-10432 RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems Change By: Nick Walker Release Notes: Bug Fix Release Notes Summary: RedHat subscription Manager update causes ensure => latest to do nothingAfter upgrading RedHat subscription Manager to using ensure => latest on the package provider on a RHEL agent would cause the package resource to never see possible updates. 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.356228.1587487722000.44535.1587581820030%40Atlassian.JIRA.
Jira (PDB-4687) Deprecate Java 8 for puppetdb in Platform 7
Title: Message Title Nick Walker created an issue PuppetDB / PDB-4687 Deprecate Java 8 for puppetdb in Platform 7 Issue Type: Story Assignee: Unassigned Created: 2020/04/22 7:55 AM Priority: Normal Reporter: Nick Walker We currently support java 8 and java 11. As time proceeds forward we will support the next LTS version of java and when that happens we may choose to drop support for java 8. In the meantime we should deprecate java 8 in platform 7 so users know we can drop it if/when it becomes too costly in CI or due to maintenance. We don't need to change anything other than documenting the deprecation and maybe emitting a warning in the logs about it. Add Comment This message was sent by
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Nick Walker commented on PUP-8094 Re: Lookup ignores environment from the classifier when using rule with trusted facts Josh Cooper do you think we can proceed forward with what you proposed? 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.214573.1507141532000.26502.1585687620079%40Atlassian.JIRA.
Jira (PUP-8918) Finalize separation of CA from Ruby
Title: Message Title Nick Walker commented on PUP-8918 Re: Finalize separation of CA from Ruby We've reviewed this and decided it's not a priority at this time. We're going to complete moving the CA directory and symlinking it back into the ssl directory but that's all from this epic that we plan to accomplish for the time being. 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.259819.1528471767000.21815.1585246680084%40Atlassian.JIRA.
Jira (PUP-8681) Allow passing the server_facts into Puppet when initializing settings.
Title: Message Title Nick Walker commented on PUP-8681 Re: Allow passing the server_facts into Puppet when initializing settings. Justin Stoller we need more info. Is the full problem that we have a dependency on facter and we want to get rid of that dependency or does solving just this problem provide benefit outside of that. 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.248060.152511167.21762.1585244880183%40Atlassian.JIRA.
Jira (PDB-4677) Document postgresql 11+ requirement for platform 7
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-4677 Document postgresql 11+ requirement for platform 7 Change By: Nick Walker Summary: Document postgresql 11+ requrement requirement for platform 7 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.350992.1585081668000.19932.1585086180585%40Atlassian.JIRA.
Jira (PUP-10257) Write timestamp to file in environment when beginning compilation
Title: Message Title Nick Walker commented on PUP-10257 Re: Write timestamp to file in environment when beginning compilation Justin Stoller should we rewrite the ticket description/title and move it to server? 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.343770.1580166495000.31428.1582130341603%40Atlassian.JIRA.
Jira (PUP-10225) Puppetserver 6 performance regression
Title: Message Title Nick Walker commented on PUP-10225 Re: Puppetserver 6 performance regression We have this page: https://puppet.com/docs/puppetserver/latest/tuning_guide.html What changes are you recommending? 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.341411.1578473781000.16655.1581003180308%40Atlassian.JIRA.
Jira (PUP-10225) Puppetserver 6 performance regression
Title: Message Title Nick Walker commented on PUP-10225 Re: Puppetserver 6 performance regression Iain Buclaw is everything stable after you changed your java args? If so shall we close this out or do you have any new information to share? 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.341411.1578473781000.14980.1580925720287%40Atlassian.JIRA.
Jira (PDB-4640) Add a file index to catalog_resources for CD4PE Impact Analysis
Title: Message Title Nick Walker commented on PDB-4640 Re: Add a file index to catalog_resources for CD4PE Impact Analysis oh cool well if we have test data and infracore I'd think we should consider additional optimizations in addition to the index 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.344131.1580319012000.5818.1580338980279%40Atlassian.JIRA.
Jira (PUP-10257) Write timestamp to file in environment when beginning compilation
Title: Message Title Nick Walker commented on PUP-10257 Re: Write timestamp to file in environment when beginning compilation I don't quite understand this proposal. Would it make sense to instead write a timestamp to the n-1 version of code when the n version of code is being deployed? So basically you write a timestamp indicating when the code was superseded as opposed to writing a timestamp at the beginning of every compile? I'd imagine the ideal state is you write down metadata on all the compiles that are currently happening at the time you deploy new code and then during a garbage collection process later you just confirm the compiles that were happening at the time you deployed the new code are no longer running. My guess would be we don't have a way to know the compiles that were running or a way to confirm they are no longer running? 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.343770.1580166495000.2939.1580233200831%40Atlassian.JIRA.
Jira (PDB-4635) puppetdb_avg_mem larger than baseline values
Title: Message Title Nick Walker commented on PDB-4635 Re: puppetdb_avg_mem larger than baseline values I wouldn't expect a decrease in shared_buffers for postgresql to increase PuppetDB's use of memory. The tuning PR reduces connections from PuppetDB to postgresql which should lower the memory use by a few megabytes. The rest of the tuning doesn't apply to a standard install of PE. I would expect the difference in 2019.3 to be related to the change to java 11 and the default GC change. 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.343321.1579814655000.35562.1579816500911%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent created PDK-1591 for PDK support of this option. 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.253867.1527713421000.30288.1579624381935%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent Gheorghe Popescu I see. Should there be another ticket for finding those places in Puppet that use legacy fact names and updating them to use structured fact names? 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.253867.1527713421000.30229.1579622160204%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent Gheorghe Popescu to confirm my understanding of this change... The user will be required to add "legacy" to the blocklist in facter.conf. This will make it so that legacy facts are not sent to the master during catalog compilation and thus not stored in PuppetDB? I don't understand what is meant by "`Facter.value` will still return the fact value in order not to break puppet" 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.253867.1527713421000.30171.1579620240308%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent I think not having facts as top-scope variables would have to be another opt-in change. That change provides a different benefit to users than what this ticket is trying to achieve around reducing data in PuppetDB. So, I think we're in agreement, as part of this ticket we should not change facts being top scope variables. 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.253867.1527713421000.26889.1579194600591%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent Henrik Lindberg yes, that's why this ticket is to provide an opt-in way to disable legacy facts. I believe the next step is to provide a reasonable to run PDK spec tests with legacy facts disabled so users can fix any problems disabling creates and ensure each module they have doesn't regress on that. We'll also want to provide guidance along the lines of exactly what you are talking about to inform users how they will need to change their puppet code or templates. 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.253867.1527713421000.26753.1579186860743%40Atlassian.JIRA.
Jira (PDB-4600) Investigate OOM errors during resource_events partitioning migration
Title: Message Title Nick Walker commented on PDB-4600 Re: Investigate OOM errors during resource_events partitioning migration Zachary Kent can we add fixversions on there? 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.339229.1576177499000.13194.1578346140199%40Atlassian.JIRA.
Jira (PDB-4606) Partition the reports table
Title: Message Title Nick Walker commented on PDB-4606 Re: Partition the reports table Could we add a configuration setting that truncates the reports table before performing this migration? The reason I ask is because we suggest to many users that they truncate the reports table before large migrations with the reports table ( or postgresql upgrades) and performing the truncation requiring dropping an FK and recreating it unless you want to delete the entire contents of your database. If it seems reasonable then adding documentation like "add this setting to puppetdb before upgrading" is a lot more palatable than run these SQL commands to remove all reports before the long migration. 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.340126.1576694351000.7294.1576791420175%40Atlassian.JIRA.
Jira (PDB-4602) Guard PuppetDB migrations against simultaneous writers
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-4602 Guard PuppetDB migrations against simultaneous writers Change By: Nick Walker Team/s: HA 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.339273.1576193168000.9518.1576260300247%40Atlassian.JIRA.
Jira (PDB-2398) PuppetDB should enable emergency deletion of historical data
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-2398
PuppetDB should enable emergency deletion of historical data
Change By:
Nick Walker
When a disk fills up on a database server, it is useful to have an option for reducing the disk space used without deleting data used by catalog compilation or requiring an increase in disk space. Disk increases can be infeasible or may require a long change cycle during which the Puppet infrastructure is inoperative. It's also useful to TRUNCATE the reports table before a major upgrade that will need to migrate the reports table or if the upgrade contains a PostgreSQL upgrade that will copy the entire database. h2. Historical ContextIn PuppetDB 2.x disk usage could be reduced in an emergency by truncating the reports table, which is often the largest table in the database by several orders of magnitude. This would return large amounts of space to the operating system, enabling further maintenance operations, while keeping exported resources intact for catalog compilation:{noformat}# PE 3.8.x# sudo -u pe-postgres /opt/puppet/bin/psql -d pe-puppetdbcould not change directory to "/root"psql (9.2.14)Type "help" for help.pe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 5(1 row)pe-puppetdb=# TRUNCATE TABLE reports CASCADE;NOTICE: truncate cascades to table "resource_events"NOTICE: truncate cascades to table "latest_reports"TRUNCATE TABLEpe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 5(1 row){noformat}In 2015.3.x, the TRUNCATE operation now cascades beyond the tables related to reporting and wipes out exported resources, which negatively impacts catalog compilation:{noformat}# PE 2015.x# sudo -u pe-postgres /opt/puppetlabs/server/bin/psql -d pe-puppetdbcould not change directory to "/root": Permission deniedpsql (9.4.5)Type "help" for help.pe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 6(1 row)pe-puppetdb=# TRUNCATE TABLE reports CASCADE;NOTICE: truncate cascades to table "certnames"NOTICE: truncate cascades to table "resource_events"NOTICE: truncate cascades to table "factsets"NOTICE: truncate cascades to table "catalogs"NOTICE: truncate cascades to table "facts"NOTICE: truncate cascades to table "catalog_resources"TRUNCATE TABLEpe-puppetdb=# SELECT count(*) FROM catalog_resources WHERE exported = true; count--- 0(1 row){noformat}h2. Desired FunctionalityPuppetDB should allow for emergency removal of historical data without impacting catalog compilation or requiring changes to disk space allocation.h1. Workaround / Proposed Implementation {code}echo "BEGIN TRANSACTION;ALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT "certnames_reports_id_fkey" FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;COMMIT TRANSACTION;" >
Jira (PDB-4600) Investigate OOM errors during resource_events partitioning migration
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-4600 Investigate OOM errors during resource_events partitioning migration Change By: Nick Walker Team: HA 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.339229.1576177499000.9141.1576202280283%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Nick Walker Team: HA 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.320599.1565648011000.44686.1574706480943%40Atlassian.JIRA.
Jira (PUP-1137) Maintenance task for the filebucket
Title: Message Title Nick Walker commented on PUP-1137 Re: Maintenance task for the filebucket I'd recommend making a cron resource that deletes files older than you want. The tidy resource uses an intense amount of computing power compared to `find -delete` which uses practically no compute and completes instantly. I think this is roughly the find command you want. https://github.com/puppetlabs/puppetlabs-puppet_metrics_collector/blob/master/templates/tidy_cron.epp#L14 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.21572.1387294399000.23129.1573152120580%40Atlassian.JIRA.
Jira (PUP-9152) Agents should re-download CRLs when they are newer than the local copy
Title: Message Title Nick Walker commented on PUP-9152 Re: Agents should re-download CRLs when they are newer than the local copy I'm fine with that. However, I'm not sure how I became the assignee on this ticket. 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.276059.1537211763000.106946.1568932980943%40Atlassian.JIRA.
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Nick Walker commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs Can we just add a limit 2000 to the summary query? That should make it even more lightweight 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.220461.1509743938000.105062.1568845740540%40Atlassian.JIRA.
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Nick Walker commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs It seems like when we're looking for commands to sync we should do a select columns from table LIMIT and then sync those commands and commit the change and keep looping until we don't have sync work left to do. That way we commit changes in small batches and don't leave a long running transaction. Austin Blatt is that reasonable? 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.220461.1509743938000.104837.1568840820617%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title Nick Walker commented on PDB-4504 Re: add-resource-events-pk migration does not use batched inserts Rob Browning any possibility of getting this fixed before the next PE release? 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.324827.1568659575000.100334.1568666401872%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-4504 add-resource-events-pk migration does not use batched inserts Change By: Nick Walker Priority: Normal Major 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.324827.1568659575000.100315.1568666401613%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title Nick Walker assigned an issue to Rob Browning PuppetDB / PDB-4504 add-resource-events-pk migration does not use batched inserts Change By: Nick Walker Assignee: Rob Browning 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.324827.1568659575000.100321.1568666401715%40Atlassian.JIRA.
Jira (PDB-4502) PuppetDB command size metrics are missing
Title: Message Title Nick Walker assigned an issue to Rob Browning PuppetDB / PDB-4502 PuppetDB command size metrics are missing Change By: Nick Walker Assignee: Rob Browning 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.323996.156781861.90117.1568042400376%40Atlassian.JIRA.
Jira (BOLT-1300) Update install docs to point to puppet-tools repo
Title: Message Title Nick Walker commented on BOLT-1300 Re: Update install docs to point to puppet-tools repo I haven't told anyone about it. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.20862.1563407340435%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4386) Improve performance of catalog inserts/updates ( by using an UPSERT )
Title: Message Title Nick Walker created an issue PuppetDB / PDB-4386 Improve performance of catalog inserts/updates ( by using an UPSERT ) Issue Type: Improvement Assignee: Unassigned Attachments: pgbadger_catalog_resources_slow_query.png Created: 2019/05/30 3:52 PM Priority: Normal Reporter: Nick Walker The Problem After upgrade from PE 2019.0 to 2019.1 we're seeing a large uptick in the following query from running PGBadger on the postgresql logs. Where as before the upgrade we were only seeing a few hundred instances of that slow query. Suggested Solution Currently we query for the existing catalog_resources and compare to what we have in PDB to determine what we should update in the table. Then we send an update query with just those resources to update. https://github.com/puppetlabs/puppetdb/blob/efd35d761be93e4a7757f086ffb9030bb2b34133/src/puppetlabs/puppetdb/scf/storage.clj#L470 https://github.com/puppetlabs/puppetdb/blob/efd35d761be93e4a7757f086ffb9030bb2b34133/src/puppetlabs/puppetdb/scf/storage.clj#L636-L649 We can replace that logic with an INSERT INTO ... ON CONFLICT statement so that we send a single request to the database and it determines what to update instead of PuppetDB. Add Comment
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Nick Walker commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Yes, the install instructions should point to the new repo which works for everyone and doesn't break anything for anyone. We can provide notes for OSS users that if they want a repo with puppet-agent in it as well they can use the existing repo. If that note is ignored it doesn't break anything for anyone. Worst case scenario is that the user would end up with two puppet repos. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22881.1559067721195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Nick Walker commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo I'm confused. I thought we were going to make a new repo with bolt and pdk in it. Then we were going to update the install instructions for Bolt to always refer to that repo so that PE users couldn't accidentally read instructions for installing that would inevitably break their PE install. The new repo just upgrades the existing note about how installing the OSS repo might cause you problems to saying we have a defined way for PE users to install but it doesn't really stop a non-attentive users from skipping the "install for PE" section and going to "install on *nix" section and ending up in the same problematic state. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22490.1559064240351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9707) Add ability for puppet-agent to detect an empty pluginsync directory and bulk download plugins
Title: Message Title
Nick Walker updated an issue
Puppet / PUP-9707
Add ability for puppet-agent to detect an empty pluginsync directory and bulk download plugins
Change By:
Nick Walker
h1. BackgroundIn PE we added the ability for the agent to bulk download plugins before installing the agent via the frictionless installation script. On the master, a tarball of the plugins is created and placed in a directory for jetty to serve so the frictionless agent install script can pull it down. h1. Suggested ImprovementThe instead of only doing this via the installation script we could move the logic into the puppet-agent so that the agent could detect that no plugins are present and instead of doing a one by one download the bulk pluginsync should be performed. h1. Out of scope My suggestion would be that this functionality is added first with an assumption that the tarball will already be present on the master and it can be put there by a separate process other than puppetserver itself making the tarball. Then in the future we can improve puppetserver to make the tarball if we want to. SERVER-2539 h1. ImpactIn order to show the impact of using the current bulk_pluginsync implementation we install the puppetlabs-windows module and then perform pluginsync via puppet or via bulk_pluginsync. When we look at the results we can see a puppet agent run without bulk_pluginsync takes around 90 seconds and with bulk_pluginsync it takes about 14 seconds. The download and extraction of the pluginsync tarball takes under 1 second and a reasonable part of the agent run after bulk_pluginsync seems to be validating the plugins. Puppet-agent ( one file at a time )```/etc/puppetlabs/code/environments/production/modules└─┬ puppetlabs-windows (v6.1.0) ├── puppet-download_file (v3.2.0) ├── puppet-windows_env (v3.2.0) ├── puppet-windowsfeature (v3.2.2) ├── puppetlabs-acl (v2.1.0) ├─┬ puppetlabs-chocolatey (v3.3.0) │ ├── puppetlabs-powershell (v2.3.0) │ ├── puppetlabs-registry (v2.1.0) │ └── puppetlabs-stdlib (v5.2.0) ├─┬ puppetlabs-dsc (v1.9.2) │ └── puppetlabs-reboot (v2.1.2) ├── puppetlabs-iis (v4.5.1) └── puppetlabs-wsus_client (v1.1.0)[root@master201910-centos ~]#[root@master201910-centos ~]#[root@master201910-centos ~]#[root@master201910-centos ~]# rm -rf /opt/puppetlabs/puppet/cache/facts.d/ lib/ locales/ preview/ puppet-module/ state/[root@master201910-centos ~]# rm -rf /opt/puppetlabs/puppet/cache/[root@master201910-centos ~]# time puppet agent -tInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginNotice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: createdNotice: /File[/opt/puppetlabs/puppet/cache/lib/facter/aio_agent_build.rb]/ensure: defined content as '{md5}cdcc1ff07bc245c66cc1d46be56b3af5'Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/aio_agent_version.rb]/ensure: defined content as '{md5}d05c8cbf788f47d33efd46a935dda61e'Notice:
Jira (PUP-9707) Add ability for puppet-agent to detect an empty pluginsync directory and bulk download plugins
Title: Message Title
Nick Walker updated an issue
Puppet / PUP-9707
Add ability for puppet-agent to detect an empty pluginsync directory and bulk download plugins
Change By:
Nick Walker
h1. BackgroundIn PE we added the ability for the agent to bulk download plugins before installing the agent via the frictionless installation script. On the master, a tarball of the plugins is created and placed in a directory for jetty to serve so the frictionless agent install script can pull it down. h1. Suggested ImprovementThe instead of only doing this via the installation script we could move the logic into the puppet-agent so that the agent could detect that no plugins are present and instead of doing a one by one download the bulk pluginsync should be performed. h1. Out of scope My suggestion would be that this functionality is added first with an assumption that the tarball will already be present on the master and it can be put there by a separate process other than puppetserver itself making the tarball. Then in the future we can improve puppetserver to make the tarball if we want to. SERVER-2539h1. ImpactIn order to show the impact of using the current bulk_pluginsync implementation we install the puppetlabs-windows module and then perform pluginsync via puppet or via bulk_pluginsync. When we look at the results we can see a puppet agent run without bulk_pluginsync takes around 90 seconds and with bulk_pluginsync it takes about 14 seconds. The download and extraction of the pluginsync tarball takes under 1 second and a reasonable part of the agent run after bulk_pluginsync seems to be validating the plugins. Puppet-agent ( one file at a time ) ``` {code} /etc/puppetlabs/code/environments/production/modules└─┬ puppetlabs-windows (v6.1.0) ├── puppet-download_file (v3.2.0) ├── puppet-windows_env (v3.2.0) ├── puppet-windowsfeature (v3.2.2) ├── puppetlabs-acl (v2.1.0) ├─┬ puppetlabs-chocolatey (v3.3.0) │ ├── puppetlabs-powershell (v2.3.0) │ ├── puppetlabs-registry (v2.1.0) │ └── puppetlabs-stdlib (v5.2.0) ├─┬ puppetlabs-dsc (v1.9.2) │ └── puppetlabs-reboot (v2.1.2) ├── puppetlabs-iis (v4.5.1) └── puppetlabs-wsus_client (v1.1.0)[root@master201910-centos ~]#[root@master201910-centos ~]#[root@master201910-centos ~]#[root@master201910-centos ~]# rm -rf /opt/puppetlabs/puppet/cache/facts.d/ lib/ locales/ preview/ puppet-module/ state/[root@master201910-centos ~]# rm -rf /opt/puppetlabs/puppet/cache/[root@master201910-centos ~]# time puppet agent -tInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginNotice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: createdNotice: /File[/opt/puppetlabs/puppet/cache/lib/facter/aio_agent_build.rb]/ensure: defined content as '{md5}cdcc1ff07bc245c66cc1d46be56b3af5'Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/aio_agent_version.rb]/ensure: defined content as '{md5}d05c8cbf788f47d33efd46a935dda61e'Notice:
Jira (PUP-9707) Add ability for puppet-agent to detect an empty pluginsync directory and bulk download plugins
Title: Message Title Nick Walker created an issue Puppet / PUP-9707 Add ability for puppet-agent to detect an empty pluginsync directory and bulk download plugins Issue Type: Improvement Assignee: Unassigned Created: 2019/05/15 10:24 AM Priority: Normal Reporter: Nick Walker Background In PE we added the ability for the agent to bulk download plugins before installing the agent via the frictionless installation script. On the master, a tarball of the plugins is created and placed in a directory for jetty to serve so the frictionless agent install script can pull it down. Suggested Improvement The instead of only doing this via the installation script we could move the logic into the puppet-agent so that the agent could detect that no plugins are present and instead of doing a one by one download the bulk pluginsync should be performed. Out of scope My suggestion would be that this functionality is added first with an assumption that the tarball will already be present on the master and it can be put there by a separate process other than puppetserver itself making the tarball. Then in the future we can improve puppetserver to make the tarball if we want to. SERVER-2539 Add Comment
Jira (PUP-9689) String to integer conversion fails
Title: Message Title Nick Walker moved an issue Puppet / PUP-9689 String to integer conversion fails Change By: Nick Walker Affects Version/s: PE 2018.1.7 Affects Version/s: PE 2018.1.5 Key: ENTERPRISE PUP - 1254 9689 Project: Puppet Enterprise 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
Jira (BOLT-1245) Bolt puppetfile install should install to "modules" by default
Title: Message Title Nick Walker commented on BOLT-1245 Re: Bolt puppetfile install should install to "modules" by default Alex Dreyer Can we get a new config option to bolt something like `puppetfile_install_path` ( or I think r10k calls it moduledir) which defaults to the first item in the modulepath but can be overridden? Then in 2.0 we could make the breaking change so that it defaults to modules instead of the first item. I also like Nick Lewis suggestion to check to see if there's something in the directory r10k is going to deploy to and fail if it wasn't previously deployed by r10k and require user interaction. 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 (BOLT-1245) Bolt puppetfile install should install to "modules" by default
Title: Message Title Nick Walker updated an issue Puppet Task Runner / BOLT-1245 Bolt puppetfile install should install to "modules" by default Change By: Nick Walker CS Priority: Needs Priority 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-9583) Write the environment_timeout cache to disk on shutdown and reload it on startup
Title: Message Title Nick Walker commented on PUP-9583 Re: Write the environment_timeout cache to disk on shutdown and reload it on startup Henrik Lindberg Josh Cooper thoughts? 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 (PDB-3041) Implement a priority queue with a deadline for command processing
Title: Message Title Nick Walker commented on PDB-3041 Re: Implement a priority queue with a deadline for command processing I think given the situation it might make sense to prioritize different commands. If a customer doesn't use exported resources or pdb query much they may not care about catalogs. Each customer might make a different determination on what is important but we should ship a good default. 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 (BOLT-1227) Document how Bolt will use local SSH config
Title: Message Title Nick Walker created an issue Puppet Task Runner / BOLT-1227 Document how Bolt will use local SSH config Issue Type: Improvement Assignee: Unassigned Created: 2019/04/03 10:39 AM Priority: Normal Reporter: Nick Walker The Problem Bolt will use local SSH config under certain circumstances and we should list when and how that works. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9583) Write the environment_timeout cache to disk on shutdown and reload it on startup
Title: Message Title Nick Walker created an issue Puppet / PUP-9583 Write the environment_timeout cache to disk on shutdown and reload it on startup Issue Type: Improvement Assignee: Unassigned Created: 2019/03/26 11:10 AM Priority: Normal Reporter: Nick Walker The Problem When you restart puppetserver you pay a price for reloading the environment_timeout cache and you pay it for each jruby that the puppetserver is running so the more jrubies you have the higher the price of restarting puppetserver. The Improvement If we could save off the environment_timeout cache to disk at shutdown and then reload it on startup we'd skip a lot of time spent re-parsing puppet code. The caveat I can think of is just whether someone change code on disk while the puppetserver was down. Not sure if we can detect that state and clear the cache or not. Within puppetserver that shouldn't be a problem when using code manager since you have to have puppetserver up to change the code. Add Comment
Jira (PDB-4280) Ensure PE upgrade will work properly with reports migration
Title: Message Title Nick Walker commented on PDB-4280 Re: Ensure PE upgrade will work properly with reports migration In order to allow a newer PuppetDB to initiate a sync with an older PuppetDB I suppose we could require that the non-initiating PuppetDB send some new field in it's response to the initiating PuppetDB and if it's not present then don't sync either. This new field could be something like "sync_version" that when present we could use to determine if the PuppetDBs should sync with each other and when not present we know we shouldn't sync with that version of PuppetDB. 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 (PDB-4280) Ensure PE upgrade will work properly with reports migration
Title: Message Title Nick Walker commented on PDB-4280 Re: Ensure PE upgrade will work properly with reports migration Based on what I'm seeing in PE we only configure sync on the replica node. Looking something like this: [root@pe-replica ~]# cat /etc/puppetlabs/puppetdb/conf.d/sync.ini [sync] server_urls = https://master201903-centos.puppetdebug.vlan:8081 intervals = 2m And sync is not configured on the primary. So if the primary is upgraded to a version of PuppetDB that has the new hash then I think it can require that the initiating PuppetDB sync sends along its schema_migration number. If no schema_migration number is sent along then the new PuppetDB version should not sync. Make sense? Add Comment This message was
Jira (PDB-4268) Add some kind of metric tracking the number of concurrent enqueues
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-4268 Add some kind of metric tracking the number of concurrent enqueues Change By: Nick Walker This metric is about getting a count of the number of `/cmd` API requests that are waiting to write to disk because all the slots provided by the `concurrent-writes` setting are full.A continuously positive number for this metric would indicate a need to increase `concurrent-writes`, get a faster disk, or separate your queue onto a different disk than other I/O heavy processes. 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
Jira (BOLT-1108) Add site-modules to the module path for bolt
Title: Message Title Nick Walker commented on BOLT-1108 Re: Add site-modules to the module path for bolt https://github.com/puppetlabs/control-repo/pull/71 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 (PDB-3526) Add online index rebuild capability to PuppetDB
Title: Message Title Nick Walker commented on PDB-3526 Re: Add online index rebuild capability to PuppetDB While not native to PuppetDB, we will have pg_repack in Puppet Enterprise with 2018.1.7 and 2019.02 which provides the ability to rebuild indexes online. Closing this as won't fix since we can use a 3rd party tool to solve the issue. 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 (PDB-3526) Add online index rebuild capability to PuppetDB
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3526 Add online index rebuild capability to PuppetDB Change By: Nick Walker Labels: cstop10 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-2175) Consider Adding Provider To The Default Output of `puppet resource package`
Title: Message Title Nick Walker commented on PUP-2175 Re: Consider Adding Provider To The Default Output of `puppet resource package` what's the fixversion on this? 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 (PDB-3928) Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3928 Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern Change By: Nick Walker Fix Version/s: PDB 5.1.z 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-8014) Create an environment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Nick Walker updated an issue Puppet / PUP-8014 Create an environment_ttl setting to clear short-lived puppet environments from memory Change By: Nick Walker Priority: Normal Major 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 (PDB-3745) Various tables in the puppetdb database get autovacuumed too frequently
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3745 Various tables in the puppetdb database get autovacuumed too frequently Change By: Nick Walker CS Priority: Needs Priority 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.
