Jira (FACT-2895) Add networking.primary6 fact
Title: Message Title Kenyon Ralph commented on FACT-2895 Re: Add networking.primary6 fact Bogdan Irimie https://github.com/puppetlabs/facter/pull/2241 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.380478.1607513744000.104075.1608284880289%40Atlassian.JIRA.
Jira (FACT-2905) File modification date check
Title: Message Title
Andrei Filipovici created an issue
Facter / FACT-2905
File modification date check
Issue Type:
Task
Assignee:
Unassigned
Created:
2020/12/18 5:33 AM
Priority:
Normal
Reporter:
Andrei Filipovici
In the caching acceptance tests we need to check that the caching files are not accidentally being rewritten. Acceptance test ttls_cache_missing_facts.rb uses {agent.ls_ld} which returns the modification date in HH:MM format, which is not sufficient. We need the modification date stamp at least in seconds.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-9176) puppet module install should list unsatisfiable dependencies if installation fails
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9176 puppet module install should list unsatisfiable dependencies if installation fails Change By: Mihai Buzgau Sprint: NW - 2020-12-09, NW - 2020-12-23 , NW - 2021-01-20 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.51451.1410900284000.104123.1608300660243%40Atlassian.JIRA.
Jira (PUP-10725) Add a new `alias` setting type(AliasSetting?)
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10725 Add a new `alias` setting type(AliasSetting?) Change By: Mihai Buzgau Sprint: NW - 2020-12-09, NW - 2020-12-23 , NW - 2021-01-20 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.375626.1603351885000.104122.1608300660202%40Atlassian.JIRA.
Jira (FACT-2905) File modification date check
Title: Message Title
Andrei Filipovici updated an issue
Facter / FACT-2905
File modification date check
Change By:
Andrei Filipovici
In the caching acceptance tests we need to check that the caching files are not accidentally being rewritten.Acceptance test ttls_cache_missing_facts.rb uses \{agent.ls_ld} which returns the modification date in HH:MM format, which is not sufficient.We need the modification date stamp at least in seconds. Also in that test we need to also make specific fact requests not just all facts requests.
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.381457.1608298408000.104137.1608301380034%40Atlassian.JIRA.
Jira (FACT-2901) Rewrite tests for linux networking resolver
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2901 Rewrite tests for linux networking resolver Change By: Bogdan Irimie Sprint: ghost-18.12 , ready for triage 3 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.380781.1607935108000.104204.1608310620395%40Atlassian.JIRA.
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2882 Gem-based Facter 4.0.x does not return the complete FQDN Change By: Bogdan Irimie Sprint: ghost-9.12, ghost-18.12 , ready for triage 3 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.379598.1606874598000.104203.1608310620351%40Atlassian.JIRA.
Jira (FACT-2862) Acceptance test for custom fact with core fact in custom group
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2862 Acceptance test for custom fact with core fact in custom group Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ghost-18.12 , ready for triage 3 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.378486.160553229.104200.1608310620259%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ghost-18.12 , ready for triage 3 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.378290.1605282375000.104201.1608310620303%40Atlassian.JIRA.
Jira (FACT-2857) Acceptance test for cache with user query
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2857 Acceptance test for cache with user query Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ghost-18.12 , ready for triage 3 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.378287.1605280544000.104202.1608310620308%40Atlassian.JIRA.
Jira (FACT-2902) There should be only one family
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2902 There should be only one family Change By: Bogdan Irimie Sprint: ghost-18.12 , ready for triage 3 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.380784.1607939331000.104207.1608310620449%40Atlassian.JIRA.
Jira (FACT-2899) Add integration tests for Facter on jruby
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2899 Add integration tests for Facter on jruby Change By: Bogdan Irimie Sprint: ghost-18.12 , ready for triage 3 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.380674.1607699228000.104205.1608310620439%40Atlassian.JIRA.
Jira (FACT-2861) Acceptance test for partial cache invalidation
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2861 Acceptance test for partial cache invalidation Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ghost-18.12 , ready for triage 3 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.378477.160552265.104199.1608310620215%40Atlassian.JIRA.
Jira (FACT-2900) Add acceptance test for aggregated facts
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2900 Add acceptance test for aggregated facts Change By: Bogdan Irimie Sprint: ghost-18.12 , ready for triage 3 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.380779.160793260.104206.1608310620444%40Atlassian.JIRA.
Jira (PUP-10840) Remove Pathname#cleanpath workaround
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10840 Remove Pathname#cleanpath workaround Change By: Josh Cooper Team: Coremunity 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.381404.1608232444000.104305.1608315780051%40Atlassian.JIRA.
Jira (PUP-10840) Remove Pathname#cleanpath workaround
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10840 Remove Pathname#cleanpath workaround Change By: Josh Cooper Sprint: Platform Core KANBAN 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.381404.1608232444000.104306.1608315780069%40Atlassian.JIRA.
Jira (PUP-10822) Puppet spec are failing with bundler 2.2.0
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10822 Puppet spec are failing with bundler 2.2.0 Change By: Josh Cooper Release Notes: Not Needed 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.380612.1607610291000.104308.1608315840084%40Atlassian.JIRA.
Jira (PUP-10822) Puppet spec are failing with bundler 2.2.0
Title: Message Title Josh Cooper commented on PUP-10822 Re: Puppet spec are failing with bundler 2.2.0 This was a regression in bundler 2.2.0. It's been fixed, and the pin was removed from puppet in https://github.com/puppetlabs/puppet/pull/8466 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.380612.1607610291000.104307.1608315840041%40Atlassian.JIRA.
Jira (PDB-4996) Improve docs for PE sync_status endpoint
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4996 Improve docs for PE sync_status endpoint Change By: Zachary Kent Labels: docs 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.381480.1608326803000.104496.1608326820105%40Atlassian.JIRA.
Jira (PDB-4996) Improve docs for PE sync_status endpoint
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4996 Improve docs for PE sync_status endpoint Issue Type: Improvement Assignee: Unassigned Created: 2020/12/18 1:26 PM Priority: Normal Reporter: Zachary Kent We should add a PE section to the PDB status endpoint docs which describes what information is returned in the `sync_status` section in PE. See here for where we add the `sync_status` information in pdbext. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4948) Improve report/resource_event GC coordination with in flight queries
Title: Message Title Zachary Kent commented on PDB-4948 Re: Improve report/resource_event GC coordination with in flight queries The work proposed in the PR related to this ticket implements a query killer which will cancel any in flight queries repeatedly while GC explicitly locks the tables it needs in order to drop a report/resource_event partition. The work there is close to being done but still needs to be reviewed and there are a couple details which should be addressed before it's merged (see TODO comments in PR). I still have some concerns related to the query killing approach implemented in the PR which I'll attempt to explain below. The main issue with the PDB GC process on partitioned tables is that the drop table command in Postgres requires an AccessExclusiveLock which needs to wait on any in flight queries and will block any subsequent queries until the lock is granted. If there are long running queries in front of the lock request this can hurt PDB response times and in the worst case cause outages. In recent releases we've added timeouts to the PDB GC process so it won't wait forever on a lock and have attempted to limit/cancel our internal sync queries when GC and sync overlap. The sync summary query has been the worst offender we know of wrt long running queries. There is ongoing work to make sync summary query transaction even shorter which should further limit the impact it can have on GC. See PDB-2420 (It's not described well in the ticket, but the work there should greatly reduce the amount of time a sync summary query is held open). When the improvements to the sync summary query is released there should be fewer situations where queries can cause GC to wait for more than 5 minutes (current default timeout) on the lock it needs. Due to the way the reports table and its partitions are structured we need to get an AccessExclusiveLock on reports, certnames, environments, producers, and reports_statuses during GC. When you explicitly lock these tables in Postgres the locking is done one-by-one even if you issue the lock statement for multiple tables at once. See parameters name section of: PG lock docs Because each table is locked individually the query killer needs to account for any queries which could come in between locking the individual tables. This means that in flight queries will need to get cancelled multiple times while we individually lock all the tables required for GC. We're unsure exactly how this will impact the clients talking to PDB. There are quite a few race conditions we'll need to consider with this approach and we'll need to audit all the clients talking to PDB in PE to make sure they have the retry logic to handle this. The fact we need to issue the command to kill queries multiple times and are unable to get the needed locks in a single command makes this approach less predictable and more risky. With the ongoing work to limit query times we could consider leaving the current timeout approach in place and save this work off to the side in the chance we hit an issue that requires a hotfix related to the GC timeouts in the future. We haven't yet heard reports of issues with GC starvation in those customers running the GC timeout approach released in PE 2019.8.2. It's possible that if we improve PDB query perf we may never need to take on this added complexity/risk. cc/ Margaret Lee ^^ is a rough explanation of why I think it might be wise to hold off on implementing this until we know for sure that it's needed.
