Jira (PDB-4871) Investigate queries using two Hikari connections per request
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4871 Investigate queries using two Hikari connections per request Change By: Jarret Lavallee CS Priority: Needs Priority 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.370205.1598390523000.72273.1604545260035%40Atlassian.JIRA.
Jira (PUP-10713) Fine grained environment timeout issues
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10713
Fine grained environment timeout issues
Change By:
Josh Cooper
Puppet's environment cache has three methods for evicting a single expired environment, all expired environments, or all environments, but they don't mutate the cache in a consistent way:1. Whenever {{Puppet::Environments::Cached#get_conf(name)}} is called to lookup the {{EnvironmentConf}} for an environment, we clear that environment if it is now expired via {{evict_if_expired(name)}}, but the method doesn't update the {{@next_expiration}} instance variable. As a result, the optimization in {{clear_all_evicted}} may cause us to call the {{cache_expiration_service.expired?(name.to_sym}} twice.2. Whenever {{Puppet::Environments::Cached#get(name)}} is called, we clear all environments that are now expired via {{clear_all_expired}}. This method updates the cache consistently.3. Whenever {{Puppet::Environments::Cached#clear_all}} is called, the {{cache_expiration_service}} is never notified of the eviction, which could lead to puppetserver holding onto environment names in memory. The method also does not clear environment related settings (for each environment). So anyone calling `Puppet[:rich_data]` for example could "see" the value from the now evicted environment. The {{clear_all}} method is used when Puppet[:rich_data] is set and also in unit tests.4. The {{Puppet::Environments::Cached#clear}} method does not remove the environment entry from the {{@expirations}} sorted set and doesn't recalculate the {{@next_expiration}} time, or clear the enviroment related settings. The {{clear}} methods does not appear to be used in puppet, as it was decided earlier to only support a REST API for cache eviction.
Add Comment
Jira (PUP-10713) Fine grained environment timeout issues
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10713 Fine grained environment timeout issues Change By: Josh Cooper Labels: 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.374883.1602635146000.7.1604537700083%40Atlassian.JIRA.
Jira (PUP-10713) Fine grained environment timeout issues
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10713 Fine grained environment timeout issues Change By: Josh Cooper Fix Version/s: PUP 7.0.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.374883.1602635146000.72223.1604537700127%40Atlassian.JIRA.
Jira (PDB-4677) Document postgresql 11+ requirement for platform 7
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4677 Document postgresql 11+ requirement for platform 7 Change By: Josh Cooper Labels: platform7 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.72215.1604537520311%40Atlassian.JIRA.
Jira (FACT-2839) Fix to_hash performance for OSX platform
Title: Message Title Josh Cooper updated an issue Facter / FACT-2839 Fix to_hash performance for OSX platform Change By: Josh Cooper Labels: platform7 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.375222.1603109274000.72213.1604537520223%40Atlassian.JIRA.
Jira (FACT-2826) Implement Facter.flush
Title: Message Title Josh Cooper updated an issue Facter / FACT-2826 Implement Facter.flush Change By: Josh Cooper Labels: platform7 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.373811.1601648662000.72210.1604537520087%40Atlassian.JIRA.
Jira (FACT-2840) Fix to_hash performance for Solaris platforms
Title: Message Title Josh Cooper updated an issue Facter / FACT-2840 Fix to_hash performance for Solaris platforms Change By: Josh Cooper Labels: platform7 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.375223.1603109437000.72211.1604537520137%40Atlassian.JIRA.
Jira (PDB-4961) Change deprecation warning for PG 9.6 to non fatal error message for Puppet 7
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4961 Change deprecation warning for PG 9.6 to non fatal error message for Puppet 7 Change By: Josh Cooper Labels: platform7 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.376722.160409420.72214.1604537520267%40Atlassian.JIRA.
Jira (FACT-2798) Check Facter.info, Facter.log_exception and set color option default to true
Title: Message Title Josh Cooper updated an issue Facter / FACT-2798 Check Facter.info, Facter.log_exception and set color option default to true Change By: Josh Cooper Labels: platform7 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.371835.1600163096000.72212.1604537520179%40Atlassian.JIRA.
Jira (FACT-2826) Implement Facter.flush
Title: Message Title Josh Cooper updated an issue Facter / FACT-2826 Implement Facter.flush Change By: Josh Cooper Labels: platform7 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.373811.1601648662000.72209.1604537460311%40Atlassian.JIRA.
Jira (FACT-2798) Check Facter.info, Facter.log_exception and set color option default to true
Title: Message Title Josh Cooper updated an issue Facter / FACT-2798 Check Facter.info, Facter.log_exception and set color option default to true Change By: Josh Cooper Labels: platform7 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.371835.1600163096000.72207.1604537460223%40Atlassian.JIRA.
Jira (FACT-2839) Fix to_hash performance for OSX platform
Title: Message Title Josh Cooper updated an issue Facter / FACT-2839 Fix to_hash performance for OSX platform Change By: Josh Cooper Labels: platform7 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.375222.1603109274000.72208.1604537460267%40Atlassian.JIRA.
Jira (PDB-4961) Change deprecation warning for PG 9.6 to non fatal error message for Puppet 7
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4961 Change deprecation warning for PG 9.6 to non fatal error message for Puppet 7 Change By: Josh Cooper Labels: platform7 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.376722.160409420.72205.1604537460136%40Atlassian.JIRA.
Jira (FACT-2840) Fix to_hash performance for Solaris platforms
Title: Message Title Josh Cooper updated an issue Facter / FACT-2840 Fix to_hash performance for Solaris platforms Change By: Josh Cooper Labels: platform7 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.375223.1603109437000.72206.1604537460179%40Atlassian.JIRA.
Jira (PDB-4677) Document postgresql 11+ requirement for platform 7
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4677 Document postgresql 11+ requirement for platform 7 Change By: Josh Cooper Labels: platform7 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.72204.1604537460080%40Atlassian.JIRA.
Jira (FACT-2797) Facter -v has to print the version and the commit SHA of that version
Title: Message Title Josh Cooper updated an issue Facter / FACT-2797 Facter -v has to print the version and the commit SHA of that version Change By: Josh Cooper Labels: platform7 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.371823.1600157075000.72203.1604537340344%40Atlassian.JIRA.
Jira (PDB-4677) Document postgresql 11+ requirement for platform 7
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4677 Document postgresql 11+ requirement for platform 7 Change By: Josh Cooper Labels: platform7 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.72186.1604537100065%40Atlassian.JIRA.
Jira (PUP-10713) Fine grained environment timeout issues
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10713
Fine grained environment timeout issues
Change By:
Josh Cooper
Puppet's environment cache has several three methods for evicting an a single expired environment, all expired environments, or all environments, but they do not don't mutate the cache in a consistent way:1. Whenever {{Puppet::Environments::Cached#get_conf(name)}} to lookup the {{EnvironmentConf}} for an environment is requested , we evict all environments clear that are environment if it is now expired , but the via {{evict_if_expired (name) }} , but the method doesn't update the {{@next_expiration}} instance variable. As a result, the optimization in {{clear_all_evicted}} may cause us to call the {{cache_expiration_service.expired?(name.to_sym}} twice.2. The Whenever {{ clear_all Puppet::Environments::Cached#get(name) }} is called, we clear all environments that are now expired via {{clear_all_expired}}. This method does not notify updates the cache consistently.3. Whenever {{ Puppet::Environments::Cached#clear_all}} is called, the {{ cache_expiration_service}} that it evicted all is never notified of the environments. This eviction, which could lead to puppetserver holding onto environment names unnecessarily in memory . The method also does not clear environment related settings (for each environment). So anyone calling `Puppet[:rich_data]` for example could "see" the value from the now evicted environment. The {{clear_all}} method is used when Puppet[:rich_data] is set and also in unit tests. 3 4 . The {{ Puppet::Environments::Cached# clear}} method does not remove the environment entry from the {{@expirations}} sorted set , it and doesn't recalculate the {{@next_expiration}} time, or clear the enviroment related settings. The - {{ clear_all}} and- {{ clear}} methods does not appear to be used in puppet, as it was decided earlier to only support a REST API for cache eviction. -So we might want to remove {{clear_all}} and {{clear}} to avoid confusion.- The {{clear_all}} method is used when Puppet[:rich_data] is set and also in unit tests.
Add Comment
Jira (PUP-10713) Fine grained environment timeout issues
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10713 Fine grained environment timeout issues Change By: Josh Cooper Epic Link: PUP-10593 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.374883.1602635146000.72163.1604536140204%40Atlassian.JIRA.
Jira (PUP-10713) Fine grained environment timeout issues
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10713
Fine grained environment timeout issues
Change By:
Josh Cooper
Puppet's environment cache has several methods for evicting an environment, but they do not mutate the cache in a consistent way:1. Whenever an environment is requested, we evict all environments that are now expired, but the {{evict_if_expired}} method doesn't update the {{@next_expiration}} instance variable. As a result, the optimization in {{clear_all_evicted}} may cause us to call the {{cache_expiration_service.expired?(name.to_sym}} twice.2. The {{clear_all}} method does not notify the {{cache_expiration_service}} that it evicted all of the environments. This could lead to puppetserver holding onto environment names unnecessarily. The method also does not clear environment related settings (for each environment).3. The {{clear}} method does not remove the environment entry from the {{@expirations}} sorted set, it doesn't recalculate the {{@next_expiration}} time, or clear the enviroment related settings.The - {{clear_all}} and - {{clear}} methods do does not appear to be used in puppet, as it was decided earlier to only support a REST API for cache eviction. - So we might want to remove {{clear_all}} and {{clear}} to avoid confusion. - The {{clear_all}} method is used when Puppet[:rich_data] is set and also in unit tests.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10713) Fine grained environment timeout issues
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10713 Fine grained environment timeout issues Change By: Josh Cooper Fix Version/s: PUP 6.20.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.374883.1602635146000.72164.1604536140247%40Atlassian.JIRA.
Jira (PDB-4871) Investigate queries using two Hikari connections per request
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4871 Investigate queries using two Hikari connections per request Change By: Josh Cooper Fix Version/s: PDB 7.0.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.370205.1598390523000.72159.1604536020037%40Atlassian.JIRA.
Jira (PUP-9573) win32-service gem needs updating
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9573 win32-service gem needs updating Change By: Josh Cooper Epic Link: PUP-7586 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.301020.1553109081000.72120.1604533260067%40Atlassian.JIRA.
Jira (PUP-9573) win32-service gem needs updating
Title: Message Title Josh Cooper commented on PUP-9573 Re: win32-service gem needs updating I removed this from the Epic, since this is only an issue for puppet 5/6, as the gem has already been removed from puppet 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.301020.1553109081000.72121.1604533260112%40Atlassian.JIRA.
Jira (PUP-10720) Update `cadir` default to return the new location post-migration
Title: Message Title Josh Cooper commented on PUP-10720 Re: Update `cadir` default to return the new location post-migration Merged to main in ad5b16091d. Passed CI in f664d6a216 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.375129.1602802813000.72117.1604533140022%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10772 fresh puppet agent installation fails when msgpack is enabled on puppetserver Change By: Josh Cooper Fix Version/s: PUP 7.0.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.376434.1603966281000.72113.1604532780040%40Atlassian.JIRA.
Jira (PDB-4871) Investigate queries using two Hikari connections per request
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4871 Investigate queries using two Hikari connections per request Change By: Zachary Kent Fix Version/s: PDB 7.0.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.370205.1598390523000.72112.1604532720103%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Josh Cooper commented on PUP-10772 Re: fresh puppet agent installation fails when msgpack is enabled on puppetserver Passed CI in f664d6a216. It is possible there is some non-deterministic behavior when puppetserver/JRuby sorts the array of formats based on their weights (as we've seen something similar in PUP-8615). I'm going to mark this agent-side issue as resolved. Tim Meusel please do let us know if you can repro the server side issue, and create a PUP ticket linked to this one. Thanks for your help debugging this! 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.376434.1603966281000.72111.1604532720059%40Atlassian.JIRA.
Jira (PDB-4941) Evaluate current table-specific parameters (autovacuum, etc.)
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4941 Evaluate current table-specific parameters (autovacuum, etc.) Change By: Austin Blatt Fix Version/s: PDB 7.0.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.375746.160339316.71528.1604511960030%40Atlassian.JIRA.
Jira (PDB-4937) Add a default statement timeout to user queries
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4937 Add a default statement timeout to user queries Change By: Austin Blatt Fix Version/s: PDB 6.14.0 Fix Version/s: PDB 7.0.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.375530.1603302604000.71527.1604511900113%40Atlassian.JIRA.
Jira (PDB-4688) Remove deprecated config settings
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4688 Remove deprecated config settings Change By: Austin Blatt Fix Version/s: PDB 7.0.0 Fix Version/s: PDB 8.0.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.356709.1587757722000.71526.1604511900066%40Atlassian.JIRA.
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title Josh Cooper commented on PUP-10627 Re: write public information to puppet_dir/public Follow up PR merged to main in https://github.com/puppetlabs/puppet/commit/f664d6a21656f80b54b396529c84ee7e24108921 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.369665.1597829487000.71514.1604510700186%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Tim Meusel commented on PUP-10772 Re: fresh puppet agent installation fails when msgpack is enabled on puppetserver So some testing. First let me explain my current setup: agents send all requests to an haproxy haproxy forwards requests with /puppet-ca to one specific puppetserver all other requests go to another group of puppetservers the puppetserver for CA requests has the msgpack gem installed and was restarted after it was installed. I purged it on all other puppetservers and restarted them. Log from an existing/working puppet agent, where I also purged the msgpack gem: Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing Debug: catalog supports formats: rich_data_json json rich_data_msgpack pson yaml dot Debug: Closing connection for https://*:8140 Debug: Creating new connection for https://*:8140 Debug: Starting connection for https://*:8140 Debug: Using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 Debug: HTTP POST https://*:8140/puppet/v3/catalog/*?environment=production returned 200 OK Debug: Caching connection for https://*:8140 besides that, the run works fine. Now I took the same agent, without msgpack installed, and it was talking directly to the CA server with msgpack installed:
Jira (PUP-10774) Long query time for AD groups
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10774 Long query time for AD groups Change By: Mihai Buzgau 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.377144.160449921.71402.1604504280207%40Atlassian.JIRA.
Jira (FACT-2851) Failure when structured custom fact has a wrong layout
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2851 Failure when structured custom fact has a wrong layout Change By: Andrei Filipovici Summary: Failure when structured custom fact hasa wrong layout 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.377156.1604503817000.71397.1604503920088%40Atlassian.JIRA.
Jira (FACT-2851) Failure when structured custom fact has
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2851 Failure when structured custom fact has Change By: Andrei Filipovici Sprint: PR - Triage 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.377156.1604503817000.71394.1604503860196%40Atlassian.JIRA.
Jira (FACT-2851) Failure when structured custom fact has
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2851 Failure when structured custom fact has Issue Type: Bug Assignee: Unassigned Created: 2020/11/04 7:30 AM Priority: Normal Reporter: Andrei Filipovici When creating a structured custom fact with: # frozen_string_literal: true Facter.add(:'my_fact.f1') do setcode do 'f1_value' end end
Jira (FACT-2850) Failed fact inside a structured custom fact is shown as null
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2850 Failed fact inside a structured custom fact is shown as null Change By: Andrei Filipovici Acceptance Criteria: Fact my_fact.f1 is not displayed. 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.377154.1604503217000.71382.1604503380145%40Atlassian.JIRA.
Jira (FACT-2850) Failed fact inside a structured custom fact is shown as null
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2850 Failed fact inside a structured custom fact is shown as null Issue Type: Task Assignee: Unassigned Created: 2020/11/04 7:20 AM Priority: Normal Reporter: Andrei Filipovici To reproduce the issue, create a custom fact file with: # frozen_string_literal: true Facter.add(:'my_fact.f1.l2') do setcode do nil.size end end
Jira (FACT-2850) Failed fact inside a structured custom fact is shown as null
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2850 Failed fact inside a structured custom fact is shown as null Change By: Andrei Filipovici Issue Type: Task Bug 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.377154.1604503217000.71381.1604503260125%40Atlassian.JIRA.
Jira (FACT-2850) Failed fact inside a structured custom fact is shown as null
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2850 Failed fact inside a structured custom fact is shown as null Change By: Andrei Filipovici Sprint: PR - Triage 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.377154.1604503217000.71380.1604503260120%40Atlassian.JIRA.
Jira (PUP-10728) Write transaction Store in JSON
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-10728 Write transaction Store in JSON Change By: Bogdan Irimie Sub-team: ghost 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.376157.1603778598000.71345.1604501220076%40Atlassian.JIRA.
Jira (PUP-3542) Write statefile in JSON
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-3542 Write statefile in JSON Change By: Bogdan Irimie Sub-team: ghost 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.56207.141419759.71346.1604501220119%40Atlassian.JIRA.
Jira (FACT-2399) Structure Utils files in an organized way
Title: Message Title Bogdan Irimie commented on FACT-2399 Re: Structure Utils files in an organized way The Util modules in the Resolvers folder should have the following namespace: module Facter module Resolvers module Utils module UtilModule 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.347475.1582641067000.71340.1604500980085%40Atlassian.JIRA.
Jira (FACT-2400) Resolvers are not structured consistently
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2400 Resolvers are not structured consistently Change By: Bogdan Irimie Sprint: PR - Triage 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.347476.1582641357000.71338.1604500800025%40Atlassian.JIRA.
Jira (FACT-2298) Update rake task for generating facts and tests
Title: Message Title Bogdan Irimie commented on FACT-2298 Re: Update rake task for generating facts and tests Delete de rake tasks that creates facts and spec tests 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.342164.1579100768000.71336.1604500740033%40Atlassian.JIRA.
Jira (FACT-2399) Structure Utils files in an organized way
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2399 Structure Utils files in an organized way Change By: Bogdan Irimie Sprint: PR - Triage 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.347475.1582641067000.71337.1604500740079%40Atlassian.JIRA.
Jira (FACT-2298) Update rake task for generating facts and tests
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2298 Update rake task for generating facts and tests Change By: Bogdan Irimie Sprint: PR - Triage 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.342164.1579100768000.71335.1604500680083%40Atlassian.JIRA.
Jira (FACT-1986) Test C++ Facter with custom facts
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1986 Test C++ Facter with custom facts Change By: Bogdan Irimie Sprint: PR - Triage 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.320311.1565329873000.71332.1604500500027%40Atlassian.JIRA.
Jira (FACT-2849) Move all components from LegacyFacter module to Facter module
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2849 Move all components from LegacyFacter module to Facter module Issue Type: Task Assignee: Unassigned Created: 2020/11/04 6:30 AM Priority: Normal Reporter: Bogdan Irimie 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-2421) Break Facter API in different modules
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2421 Break Facter API in different modules Change By: Bogdan Irimie Sprint: PR - Triage 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.347908.1582886415000.71328.1604500140024%40Atlassian.JIRA.
Jira (FACT-2558) Fact classes that resolve more than one fact should be split
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2558 Fact classes that resolve more than one fact should be split Change By: Bogdan Irimie Sprint: PR - Triage 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.355608.1586935915000.71327.1604500080028%40Atlassian.JIRA.
Jira (FACT-2306) Add support for AWS IMDSv2
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2306 Add support for AWS IMDSv2 Change By: Bogdan Irimie Sprint: PR - Triage 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.342859.1579626792000.71326.1604500020024%40Atlassian.JIRA.
Jira (PUP-10774) Long query time for AD groups
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10774 Long query time for AD groups Change By: Luchian Nemes Comment: A comment with security level 'Developers' was removed. 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.377144.160449921.71325.1604499960088%40Atlassian.JIRA.
Jira (PUP-10774) Long query time for AD groups
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10774
Long query time for AD groups
Change By:
Luchian Nemes
Using CentrifyDC’s provided NSS module to access user and group information from Active Directory through LDAP has surfaced some PE installations timeouts. This seems to happen due Puppet’s internal user group lookup implementation which queries AD for all available groups at every run and taking too long to process a high amount of data. Said implementation points us to [puppet/lib/puppet/util/posix.rb|https://github.com/puppetlabs/puppet/blob/d8068536284ad3601d447308ab9d3d6f9cdcf02d/lib/puppet/util/posix.rb#L12-L27]:{code: java ruby }# Returns an array of all the groups that the user's a member of. def groups_of(user) groups = [] Puppet::Etc.group do |group|groups << group.name if group.mem.include?(user) end uniq_groups = groups.uniq if uniq_groups != groupsPuppet.debug(_('Removing any duplicate group entries')) end uniq_groups end{code} This needs to be replaced by the C API implementation [getgrouplist(3)|https://www.man7.org/linux/man-pages/man3/getgrouplist.3.html] using FFI calls to lookup the groups of a single user instead of [getent(1)|https://man7.org/linux/man-pages/man1/getent.1.html] which is first retrieving all available groups and then determines which ones the user belongs to.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10774) Long query time for AD groups
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10774
Long query time for AD groups
Change By:
Luchian Nemes
Using CentrifyDC’s provided NSS module to access user and group information from Active Directory through LDAP has surfaced some PE installations timeouts. This seems to happen due Puppet’s internal user group lookup implementation which queries AD for all available groups at every run and taking too long to process a high amount of data. Said implementation points us to [puppet/lib/puppet/util/posix.rb|https://github.com/puppetlabs/puppet/blob/d8068536284ad3601d447308ab9d3d6f9cdcf02d/lib/puppet/util/posix.rb#L12-L27]:{code:ruby}# Returns an array of all the groups that the user's a member of.def groups_of(user) groups = [] Puppet::Etc.group do |group|groups << group.name if group.mem.include?(user) end uniq_groups = groups.uniq if uniq_groups != groupsPuppet.debug(_('Removing any duplicate group entries')) end uniq_groups end{code} This needs to be replaced by the C API implementation [getgrouplist(3)|https://www.man7.org/linux/man-pages/man3/getgrouplist.3.html] using FFI calls to lookup the groups of a single user instead of [getent(1)|https://man7.org/linux/man-pages/man1/getent.1.html] which is first retrieving all available groups and then determines which ones the user belongs to.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10774) Long query time for AD groups
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10774
Long query time for AD groups
Change By:
Luchian Nemes
Using CentrifyDC’s provided NSS module to access user and group information from Active Directory through LDAP has surfaced some PE installations timeouts. This seems to happen due Puppet’s internal user group lookup implementation which queries AD for all available groups at every run and taking too long to process a high amount of data. Said implementation points us to [puppet/lib/puppet/util/posix.rb|https://github.com/puppetlabs/puppet/blob/d8068536284ad3601d447308ab9d3d6f9cdcf02d/lib/puppet/util/posix.rb#L12-L27]: {code:java}# Returns an array of all the groups that the user's a member of.def groups_of(user) groups = [] Puppet::Etc.group do |group|groups << group.name if group.mem.include?(user) end uniq_groups = groups.uniq if uniq_groups != groupsPuppet.debug(_('Removing any duplicate group entries')) end uniq_groups end{code} This needs to be replaced by the C API implementation [getgrouplist(3)|https://www.man7.org/linux/man-pages/man3/getgrouplist.3.html] using FFI calls to lookup the groups of a single user instead of [getent(1)|https://man7.org/linux/man-pages/man1/getent.1.html] which is first retrieving all available groups and then determines which ones the user belongs to.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10774) Long query time for AD groups
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10774
Long query time for AD groups
Change By:
Luchian Nemes
Using CentrifyDC’s provided NSS module to access user and group information from Active Directory through LDAP has surfaced some PE installations timeouts. This seems to happen due Puppet’s internal user group lookup implementation which queries AD for all available groups at every run and taking too long to process a high amount of data. Said implementation points us to [puppet/lib/puppet/util/posix.rb|https://github.com/puppetlabs/puppet/blob/d8068536284ad3601d447308ab9d3d6f9cdcf02d/lib/puppet/util/posix.rb#L12-L27]:{code:java}# Returns an array of all the groups that the user's a member of.def groups_of(user) groups = [] Puppet::Etc.group do |group|groups << group.name if group.mem.include?(user) end uniq_groups = groups.uniq if uniq_groups != groupsPuppet.debug(_('Removing any duplicate group entries')) end uniq_groups end{code} This needs to be replaced by the C API implementation [getgrouplist(3)|https://www.man7.org/linux/man-pages/man3/getgrouplist.3.html] using FFI calls to lookup the groups of a single user instead of [getent(1)|https://man7.org/linux/man-pages/man1/getent.1.html] which is first retrieving all available groups and then determines which ones the user belongs to.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10774) Long query time for AD groups
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10774
Long query time for AD groups
Change By:
Luchian Nemes
Using CentrifyDC’s provided NSS module to access user and group information from Active Directory through LDAP has surfaced some PE installations timeouts. This seems to happen due Puppet’s internal user group lookup implementation which queries AD for all available groups at every run and taking too long to process a high amount of data. Said implementation points us to [puppet/lib/puppet/util/posix.rb|https://github.com/puppetlabs/puppet/blob/d8068536284ad3601d447308ab9d3d6f9cdcf02d/lib/puppet/util/posix.rb#L12-L27]: {code:java} # Returns an array of all the groups that the user's a member of. def groups_of(user) groups = [] Puppet::Etc.group do |group| groups << group.name if group.mem.include?(user) end uniq_groups = groups.uniq if uniq_groups != groups Puppet.debug(_('Removing any duplicate group entries')) enduniq_groups end{code} This needs to be replaced by the C API implementation [getgrouplist(3)|https://www.man7.org/linux/man-pages/man3/getgrouplist.3.html] using FFI calls to lookup the groups of a single user instead of [getent(1)|https://man7.org/linux/man-pages/man1/getent.1.html] which is first retrieving all available groups and then determines which ones the user belongs to.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10774) Long query time for AD groups
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10774
Long query time for AD groups
Change By:
Luchian Nemes
Using CentrifyDC’s provided NSS module to access user and group information from Active Directory through LDAP has surfaced some PE installations timeouts. This seems to happen due Puppet’s internal user group lookup implementation which queries AD for all available groups at every run and taking too long to process a high amount of data. Said implementation points us to [puppet/lib/puppet/util/posix.rb|https://github.com/puppetlabs/puppet/blob/d8068536284ad3601d447308ab9d3d6f9cdcf02d/lib/puppet/util/posix.rb#L12-L27] : {code:java}# Returns an array of all the groups that the user's a member of . def groups_of(user) groups = [] Puppet::Etc.group do |group| groups << group.name if group.mem.include?(user) end uniq_groups = groups.uniq if uniq_groups != groups Puppet.debug(_('Removing any duplicate group entries')) enduniq_groups end{code} This needs to be replaced by the C API implementation [getgrouplist(3)|https://www.man7.org/linux/man-pages/man3/getgrouplist.3.html] using FFI calls to lookup the groups of a single user instead of [getent(1)|https://man7.org/linux/man-pages/man1/getent.1.html] which is first retrieving all available groups and then determines which ones the user belongs to.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10774) Long query time for AD groups
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10774 Long query time for AD groups Change By: Luchian Nemes Using CentrifyDC’s provided NSS module to access user and group information from Active Directory through LDAP has surfaced some PE installations timeouts. This seems to happen due Puppet’s internal user group lookup implementation which queries AD for all available groups at every run and taking too long to process a high amount of data.Said implementation points us to [puppet/lib/puppet/util/posix.rb|https://github.com/puppetlabs/puppet/blob/d8068536284ad3601d447308ab9d3d6f9cdcf02d/lib/puppet/util/posix.rb#L12-L27]. This needs to be replaced by the C API implementation [getgrouplist(3)|https://www.man7.org/linux/man-pages/man3/getgrouplist.3.html] using FFI calls to lookup the groups of a single user instead of [getent(1)|https://man7.org/linux/man-pages/man1/getent.1.html] which retrieved is first retrieving all available groups and then determined determines which one ones the user belongs to. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10774) Long query time for AD groups
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10774
Long query time for AD groups
Change By:
Luchian Nemes
Using CentrifyDC’s provided NSS module to access user and group information from Active Directory through LDAP has surfaced some PE installations timeouts. This seems to happen due Puppet’s internal user group lookup implementation which queries AD for all available groups at every run and taking too long to process a high amount of data. Said implementation points us to : {code:ruby}# Returns an array of all the groups that the user's a member of.def groups_of(user) groups = [ ] Puppet::Etc puppet/lib/puppet/util/posix . group do rb | group|groups << group https://github . name if group com/puppetlabs/puppet/blob/d8068536284ad3601d447308ab9d3d6f9cdcf02d/lib/puppet/util/posix . mem rb#L12-L27] . include?(user) enduniq_groups = groups.uniq if uniq_groups != groupsPuppet.debug(_('Removing any duplicate group entries')) end uniq_groupsend{code} This needs to be replaced by the C API implementation [getgrouplist(3)|https://www.man7.org/linux/man-pages/man3/getgrouplist.3.html] using FFI calls to lookup the groups of a single user instead of [getent(1)|https://man7.org/linux/man-pages/man1/getent.1.html] which retrieved all available groups and then determined which one the user belongs to.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10774) Long query time for AD groups
Title: Message Title
Luchian Nemes created an issue
Puppet / PUP-10774
Long query time for AD groups
Issue Type:
Task
Assignee:
Unassigned
Created:
2020/11/04 6:13 AM
Priority:
Normal
Reporter:
Luchian Nemes
Using CentrifyDC’s provided NSS module to access user and group information from Active Directory through LDAP has surfaced some PE installations timeouts. This seems to happen due Puppet’s internal user group lookup implementation which queries AD for all available groups at every run and taking too long to process a high amount of data. Said implementation points us to:
# Returns an array of all the groups that the user's a member of.def groups_of(user) groups = [] Puppet::Etc.group do |group|groups << group.name if group.mem.include?(user) enduniq_groups = groups.uniq if uniq_groups != groupsPuppet.debug(_('Removing any duplicate group entries')) end
uniq_groupsend
This needs to be replaced by the C API implementation getgrouplist(3) using FFI calls to lookup the groups of a single user instead of getent(1) which retrieved all available groups and then determined which one the user belongs to.
Jira (FACT-2848) Improve performance of cache manager
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2848 Improve performance of cache manager Change By: Bogdan Irimie Sprint: ghost-4.11 , PR - Triage 2 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.376315.160389490.71298.1604499060134%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2847 Facter 4 breaks rspec on fact test Change By: Bogdan Irimie Sprint: ghost-4.11 , PR - Triage 2 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.376201.1603820546000.71308.1604499060471%40Atlassian.JIRA.
Jira (PUP-3542) Write statefile in JSON
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-3542 Write statefile in JSON Change By: Bogdan Irimie Sprint: ghost-4.11 , PR - Triage 2 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.56207.141419759.71302.1604499060207%40Atlassian.JIRA.
Jira (FACT-2705) Blog post for Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2705 Blog post for Facter 4 Change By: Bogdan Irimie Sprint: ghost-14.10, ghost-21.10, ghost-28.10, ghost-4.11 , PR - Triage 2 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.365211.1594212543000.71303.1604499060251%40Atlassian.JIRA.
Jira (FACT-2838) Some facts are volatile (changes almost every fact upload)
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2838 Some facts are volatile (changes almost every fact upload) Change By: Bogdan Irimie Sprint: ghost-28.10, ghost-4.11 , PR - Triage 2 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.375143.160283799.71300.1604499060157%40Atlassian.JIRA.
Jira (FACT-2846) Facter 4 fails to parse linux tun* interfaces on our openvpn server
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2846 Facter 4 fails to parse linux tun* interfaces on our openvpn server Change By: Bogdan Irimie Sprint: ghost-28.10, ghost-4.11 , PR - Triage 2 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.375629.1603354499000.71306.1604499060383%40Atlassian.JIRA.
Jira (FACT-2813) Show backtrace in CI for acceptance test errors
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2813 Show backtrace in CI for acceptance test errors Change By: Bogdan Irimie Sprint: ghost-7.10, ghost-14.10, ghost-21.10, ghost-28.10, ghost-4.11 , PR - Triage 2 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.372970.1600961477000.71305.1604499060339%40Atlassian.JIRA.
Jira (PUP-10728) Write transaction Store in JSON
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-10728 Write transaction Store in JSON Change By: Bogdan Irimie Sprint: ghost-4.11 , PR - Triage 2 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.376157.1603778598000.71299.1604499060152%40Atlassian.JIRA.
Jira (FACT-2833) Investigate performance for hypervisor fact
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2833 Investigate performance for hypervisor fact Change By: Bogdan Irimie Sprint: ghost-14.10, ghost-21.10, ghost-28.10, ghost-4.11 , PR - Triage 2 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.374205.1602078248000.71304.1604499060294%40Atlassian.JIRA.
Jira (FACT-2843) scope6 fact should be per binding not per interface
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2843 scope6 fact should be per binding not per interface Change By: Bogdan Irimie Sprint: ghost-28.10, ghost-4.11 , PR - Triage 2 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.375310.1603200299000.71301.1604499060166%40Atlassian.JIRA.
Jira (FACT-2845) Release Facter 4.0.45
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2845 Release Facter 4.0.45 Change By: Bogdan Irimie Sprint: ghost-28.10, ghost-4.11 , PR - Triage 2 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.375486.1603288319000.71307.1604499060427%40Atlassian.JIRA.
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10627 write public information to puppet_dir/public Change By: Luchian Nemes Release Notes Summary: A new folder named `public`, with 0755 access rights, has been added and is now the default location for the 'last_run_summary.yaml' report which now has `640` 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.369665.1597829487000.71278.1604498520036%40Atlassian.JIRA.
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title Luchian Nemes commented on PUP-10627 Re: write public information to puppet_dir/public Great catch Trevor Vaughan! Opened https://github.com/puppetlabs/puppet/pull/8433 for this. 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.369665.1597829487000.71216.1604486220031%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Martin Alfke commented on FACT-2847 Re: Facter 4 breaks rspec on fact test Solution for .sync.yml: --- spec/spec_helper.rb: mock_with: ':rspec' Gemfile: optional: ':development': - gem: facter version: '> 4.0.43' platforms: mri_25 This uses facter 4 on puppet 6 only. Add Comment
