Jira (PUP-10212) SSL negotiation fails with "tls_process_ske_dhe:dh key too small"
Title: Message Title Josh Cooper commented on PUP-10212 Re: SSL negotiation fails with "tls_process_ske_dhe:dh key too small" Valters Jansons that seems doable, though I don't know if there are reasons why we're intentionally not doing that, perhaps due to incompatibility with older java versions (just a guess). Thoughts Justin Stoller? 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.336537.1574710008000.139087.1612993500046%40Atlassian.JIRA.
Jira (PDB-5017) Fix missing arg in path hit by admin gc for purge_resource_events
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-5017 Fix missing arg in path hit by admin gc for purge_resource_events Change By: Zachary Kent Assignee: Zachary Kent 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.386915.1612914187000.139067.1612992660040%40Atlassian.JIRA.
Jira (PDB-4655) Audit error handling/shutdown behavior when PDB is broadcasting
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4655 Audit error handling/shutdown behavior when PDB is broadcasting Change By: Eric Thompson Sprint: Release Engineering Hopper 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.347207.1582246732000.138863.1612985760752%40Atlassian.JIRA.
Jira (PDB-4654) Adjust PDB config to allow for multiple write dbs
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4654 Adjust PDB config to allow for multiple write dbs Change By: Eric Thompson Sprint: Release Engineering Hopper, HA Team 2020-05-05 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.347165.1582246233000.138862.1612985760707%40Atlassian.JIRA.
Jira (PDB-4655) Audit error handling/shutdown behavior when PDB is broadcasting
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4655 Audit error handling/shutdown behavior when PDB is broadcasting Change By: Eric Thompson Sprint: 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.347207.1582246732000.138857.1612985760483%40Atlassian.JIRA.
Jira (PDB-4658) Audit metric and dlo behavior with command broadcast
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4658 Audit metric and dlo behavior with command broadcast Change By: Eric Thompson Sprint: 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.347256.1582313765000.138859.1612985760571%40Atlassian.JIRA.
Jira (PDB-4656) Adjust PDB ingest to submit commands to multiple DBs
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4656 Adjust PDB ingest to submit commands to multiple DBs Change By: Eric Thompson Sprint: 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.347208.1582247529000.138858.1612985760528%40Atlassian.JIRA.
Jira (PDB-4659) Create acceptance tests that simulate PDB command broadcast
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4659 Create acceptance tests that simulate PDB command broadcast Change By: Eric Thompson Sprint: Release Engineering Hopper 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.347259.1582314337000.138866.1612985760883%40Atlassian.JIRA.
Jira (PDB-4659) Create acceptance tests that simulate PDB command broadcast
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4659 Create acceptance tests that simulate PDB command broadcast Change By: Eric Thompson Sprint: 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.347259.1582314337000.138860.1612985760619%40Atlassian.JIRA.
Jira (PDB-4658) Audit metric and dlo behavior with command broadcast
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4658 Audit metric and dlo behavior with command broadcast Change By: Eric Thompson Sprint: Release Engineering Hopper 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.347256.1582313765000.138865.1612985760839%40Atlassian.JIRA.
Jira (PDB-4157) Review impact of connection limits in clj-http-client
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4157 Review impact of connection limits in clj-http-client Change By: Eric Thompson Sprint: Release Engineering Hopper 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.280669.1539661927000.138861.1612985760663%40Atlassian.JIRA.
Jira (PDB-4656) Adjust PDB ingest to submit commands to multiple DBs
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4656 Adjust PDB ingest to submit commands to multiple DBs Change By: Eric Thompson Sprint: Release Engineering Hopper 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.347208.1582247529000.138864.1612985760795%40Atlassian.JIRA.
Jira (PDB-4157) Review impact of connection limits in clj-http-client
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4157 Review impact of connection limits in clj-http-client Change By: Eric Thompson Sprint: 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.280669.1539661927000.138848.1612985700038%40Atlassian.JIRA.
Jira (PDB-5022) Finish investigation and fixes related to clj linting
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5022 Finish investigation and fixes related to clj linting Change By: Rob Browning Assignee: Rob Browning 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.387005.1612985036000.138831.1612985340084%40Atlassian.JIRA.
Jira (PDB-5022) Finish investigation and fixes related to clj linting
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5022 Finish investigation and fixes related to clj linting Change By: Rob Browning Sprint: HA 2020-02-24 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.387005.1612985036000.138830.1612985340039%40Atlassian.JIRA.
Jira (PDB-5002) Array match queries stopped working in version 7
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5002 Array match queries stopped working in version 7 Change By: Zachary Kent Sprint: HA 2020-02-24 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.384540.1611348921000.138828.1612985280047%40Atlassian.JIRA.
Jira (PDB-5002) Array match queries stopped working in version 7
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5002 Array match queries stopped working in version 7 Change By: Zachary Kent Story Points: 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.384540.1611348921000.138829.1612985280092%40Atlassian.JIRA.
Jira (PDB-5022) Finish investigation and fixes related to clj linting
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5022 Finish investigation and fixes related to clj linting Issue Type: Task Assignee: Unassigned Created: 2021/02/10 11:23 AM Priority: Normal Reporter: Rob Browning 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.3
Jira (PDB-5017) Fix missing arg in path hit by admin gc for purge_resource_events
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5017 Fix missing arg in path hit by admin gc for purge_resource_events Change By: Zachary Kent Story Points: 1 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.386915.1612914187000.138816.1612984800096%40Atlassian.JIRA.
Jira (PDB-5017) Fix missing arg in path hit by admin gc for purge_resource_events
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5017 Fix missing arg in path hit by admin gc for purge_resource_events Change By: Zachary Kent Sprint: HA 2020-02-24 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.386915.1612914187000.138817.1612984800139%40Atlassian.JIRA.
Jira (PDB-5021) Investigate factsets getting repeatedly pulled in sync with benchmark data
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5021 Investigate factsets getting repeatedly pulled in sync with benchmark data Change By: Zachary Kent Sprint: HA 2020-02-24 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.386997.1612983565000.138813.1612984740093%40Atlassian.JIRA.
Jira (PDB-5021) Investigate factsets getting repeatedly pulled in sync with benchmark data
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5021 Investigate factsets getting repeatedly pulled in sync with benchmark data Change By: Zachary Kent Story Points: 5 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.386997.1612983565000.138812.1612984740049%40Atlassian.JIRA.
Jira (PDB-5004) Test fully realized sync summary query memory usage
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5004 Test fully realized sync summary query memory usage Change By: Zachary Kent Sprint: HA 2021-02-10 , HA 2020-02-24 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.385150.161177046.138784.1612984440160%40Atlassian.JIRA.
Jira (PDB-5021) Investigate factsets getting repeatedly pulled in sync with benchmark data
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-5021 Investigate factsets getting repeatedly pulled in sync with benchmark data Issue Type: Bug Assignee: Unassigned Created: 2021/02/10 10:59 AM Priority: Normal Reporter: Zachary Kent Fill out the description after sprint planning. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4643) unable to connect puppetmaster with puppetdb
Title: Message Title Austin Blatt commented on PDB-4643 Re: unable to connect puppetmaster with puppetdb Java 11 should choose a key size of 2048, which should work for puppetdb 7.1.0. Are you having the same puppet lookup --node issue using java 11 or a different issue? 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.345012.1580837021000.138688.1612981620070%40Atlassian.JIRA.
Jira (PUP-10212) SSL negotiation fails with "tls_process_ske_dhe:dh key too small"
Title: Message Title Valters Jansons commented on PUP-10212 Re: SSL negotiation fails with "tls_process_ske_dhe:dh key too small" Is there a reason as to why the packaged /etc/default/puppetserver for Open-Source Puppet Server (as of 7.0.3) does not include -Djdk.tls.ephemeralDHKeySize=2048? 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.336537.1574710008000.138683.1612981440072%40Atlassian.JIRA.
Jira (PDB-4643) unable to connect puppetmaster with puppetdb
Title: Message Title Valters Jansons commented on PDB-4643 Re: unable to connect puppetmaster with puppetdb Is there a reason as to why the packaged /etc/default/puppetdb for Open-Source PuppetDB does not include -Djdk.tls.ephemeralDHKeySize=2048? 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.345012.1580837021000.138670.1612981200026%40Atlassian.JIRA.
Jira (PDB-4935) user error during installation
Title: Message Title Rob Browning commented on PDB-4935 Re: user error during installation It looks like this might not be entirely related to PuppetDB, since we assume that the PostgreSQL trigram extensions are already available. On Debian derivatives, for example, that used to require installing something like postgresql-contrib-9.6, though now I believe it's included in say postgresql-11 However, if you feel like we've misunderstood the situation, please feel free to re-open the ticket. 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.375213.1603099083000.138664.1612980900201%40Atlassian.JIRA.
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title Mihai Buzgau commented on PUP-10896 Re: Puppet users with forcelocal are no longer idempotent Trey Dockendorf we do consider this as a regression and we've already implemented a fix here: https://github.com/puppetlabs/puppet/pull/8511 We're shooting for a new release in the next couple of days 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.386956.1612964187000.138549.1612978320089%40Atlassian.JIRA.
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title Trey Dockendorf commented on PUP-10896 Re: Puppet users with forcelocal are no longer idempotent Found a solution that works with my example test case: @@ -104,7 +104,7 @@ def localgid user = finduser(:account, resource[:name]) -return user[:gid] if user +return user[:gid].to_i if user false end I will open a pull request Add Comment
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10896 Puppet users with forcelocal are no longer idempotent Change By: Mihai Buzgau Sprint: NW - 2021-02-17 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.386956.1612964187000.138544.1612977960058%40Atlassian.JIRA.
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10896 Puppet users with forcelocal are no longer idempotent Change By: Mihai Buzgau Team: Night's Watch 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.386956.1612964187000.138545.1612977960104%40Atlassian.JIRA.
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title Trey Dockendorf commented on PUP-10896 Re: Puppet users with forcelocal are no longer idempotent For the longest time it has been possible to assign a user to a group using that group's name since it's not always the case a module will enforce a specific GID or UID. It looks like based on this commit: https://github.com/puppetlabs/puppet/commit/0cd7bcefa47b90f3c8d24e60479f41766cbc04f3 the logic was changed to force the gid property to be a numeric ID when using forcelocal=true which I would consider a breaking change since that was not the behavior prior to this commit. From the documentation on the "gid" property: The user’s primary group. Can be specified numerically or by name. Changing the behavior of a core type property in a feature release seems like not a great idea and should be reconsidered and reverted to the previous behavior or the logic for getting local users should be better about mapping a GID to a name and allowing it to be either numeric or a name like was previously allowed. Forcing the use of a numeric ID would essentially make impossible for module authors to create users and set the primary group when using "forcelocal" without also forcing a GID be provided. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title Mihai Buzgau commented on PUP-10896 Re: Puppet users with forcelocal are no longer idempotent Thanks Trey for raising this issue. Fixed in: https://github.com/puppetlabs/puppet/pull/8510 https://github.com/puppetlabs/puppet/pull/8511 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.386956.1612964187000.138527.161297740%40Atlassian.JIRA.
Jira (PDB-5018) Provide way to stop/start command processing using ExecutorService
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5018 Provide way to stop/start command processing using ExecutorService Change By: Bogdan Irimie Provide a way to stop and start command processing, perhaps initially only internally, say via a service method. This should help reduce the complexity/fragility of some of the tests.While we might want to eventually support some public way to control this, that can come later. It's possible the that the [Executor|https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ExecutorService.html] created in the [GatedThreadpool|https://github.com/puppetlabs/puppetdb/blob/main/src/puppetlabs/puppetdb/threadpool.clj#L89] defrecord. Has the ability to pause incoming tasks. We haven't looked through the docs in detail but it would be worth checking out before going with option 1 to see if this is possible. 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 Googl
Jira (PDB-5020) Document / present pe-puppetdb-extensions
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5020 Document / present pe-puppetdb-extensions Change By: Bogdan Irimie Story Points: 1 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.386971.1612971055000.138310.1612971120077%40Atlassian.JIRA.
Jira (PDB-5020) Document / present pe-puppetdb-extensions
Title: Message Title Bogdan Irimie created an issue PuppetDB / PDB-5020 Document / present pe-puppetdb-extensions Issue Type: Task Assignee: Unassigned Created: 2021/02/10 7: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 https://groups.google.com/d/msgid/puppet-bugs/JIRA.386971.16129
Jira (PDB-5019) Document setup creation
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5019 Document setup creation Change By: Bogdan Irimie Story Points: 1 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.386970.1612971013000.138307.1612971060207%40Atlassian.JIRA.
Jira (PDB-5019) Document setup creation
Title: Message Title Bogdan Irimie created an issue PuppetDB / PDB-5019 Document setup creation Issue Type: Task Assignee: Unassigned Created: 2021/02/10 7: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 https://groups.google.com/d/msgid/puppet-bugs/JIRA.386970.1612971013000.138306.16
Jira (PDB-4524) Provide way to stop/start command processing (maybe only internal initially)
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4524 Provide way to stop/start command processing (maybe only internal initially) Change By: Bogdan Irimie Story Points: 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.327600.1569963418000.138302.1612970820055%40Atlassian.JIRA.
Jira (PDB-5018) Provide way to stop/start command processing using ExecutorService
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5018 Provide way to stop/start command processing using ExecutorService Change By: Bogdan Irimie Sprint: ghost-24.02.2021 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.386968.1612970282000.138294.1612970640088%40Atlassian.JIRA.
Jira (PDB-5018) Provide way to stop/start command processing using ExecutorService
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5018 Provide way to stop/start command processing using ExecutorService Change By: Bogdan Irimie Story Points: 5 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.386968.1612970282000.138293.1612970640039%40Atlassian.JIRA.
Jira (PDB-5018) Provide way to stop/start command processing using ExecutorService
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5018 Provide way to stop/start command processing using ExecutorService Change By: Bogdan Irimie It's possible the that the [Executor|https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ExecutorService.html] created in the [GatedThreadpool|https://github.com/puppetlabs/puppetdb/blob/main/src/puppetlabs/puppetdb/threadpool.clj#L89] defrecord. Has the ability to pause incoming tasks. We haven't looked through the docs in detail but it would be worth checking out before going with option 1 to see if this is possible. 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.386968.1612970282000.138283.16129
Jira (PDB-5018) Provide way to stop/start command processing using ExecutorService
Title: Message Title Bogdan Irimie created an issue PuppetDB / PDB-5018 Provide way to stop/start command processing using ExecutorService Issue Type: Task Assignee: Unassigned Created: 2021/02/10 7:18 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 https://groups.google.com/d/msgid/pupp
Jira (PDB-3635) Add ability to disable storage of resource events
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-3635 Add ability to disable storage of resource events Change By: Bogdan Irimie Sprint: ghost-24.02.2021 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.203773.1501712836000.138275.1612969140103%40Atlassian.JIRA.
Jira (PDB-3635) Add ability to disable storage of resource events
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-3635 Add ability to disable storage of resource events Change By: Bogdan Irimie Story Points: 5 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.203773.1501712836000.138274.1612969140044%40Atlassian.JIRA.
Jira (PDB-4268) Add some kind of metric tracking the number of concurrent enqueues
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4268 Add some kind of metric tracking the number of concurrent enqueues Change By: Bogdan Irimie Story Points: 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.296417.1550251531000.138267.1612968180071%40Atlassian.JIRA.
Jira (PDB-4268) Add some kind of metric tracking the number of concurrent enqueues
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu PuppetDB / PDB-4268 Add some kind of metric tracking the number of concurrent enqueues Change By: Oana Tanasoiu Assignee: Oana Tanasoiu 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.296417.1550251531000.138268.1612968180128%40Atlassian.JIRA.
Jira (PDB-4268) Add some kind of metric tracking the number of concurrent enqueues
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4268 Add some kind of metric tracking the number of concurrent enqueues Change By: Bogdan Irimie Sprint: ghost-24.02.2021 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.296417.1550251531000.138269.1612968180171%40Atlassian.JIRA.
Jira (PDB-3418) Add a new-fact-time metric to complement the new-catalog-time metric
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-3418 Add a new-fact-time metric to complement the new-catalog-time metric Change By: Bogdan Irimie Sprint: ghost-27.01.2021, ghost-10.02.2021 , 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.184154.1491345864000.138248.1612966020276%40Atlassian.JIRA.
Jira (PDB-2488) Don't accept trailing garbage in query string
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-2488 Don't accept trailing garbage in query string Change By: Bogdan Irimie Sprint: ghost-27.01.2021, ghost-10.02.2021 , 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.119258.145685283.138251.1612966020408%40Atlassian.JIRA.
Jira (PDB-4172) Allow metrics during startup
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4172 Allow metrics during startup Change By: Bogdan Irimie Sprint: ghost-27.01.2021, ghost-10.02.2021 , 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.282135.1540387252000.138247.1612966020097%40Atlassian.JIRA.
Jira (FACT-2926) Ensure all methods have rubydocs
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2926 Ensure all methods have rubydocs Change By: Bogdan Irimie Sprint: ghost-10.02.2021 , 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.385100.1611738907000.138253.1612966020495%40Atlassian.JIRA.
Jira (PDB-4934) PuppetDB does not support username@hostname auth for Azure PostgreSQL
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4934 PuppetDB does not support username@hostname auth for Azure PostgreSQL Change By: Bogdan Irimie Sprint: ghost-27.01.2021, ghost-10.02.2021 , 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.375238.1603127441000.138250.1612966020364%40Atlassian.JIRA.
Jira (FACT-2916) Block mechanism is slow when there are custom facts that depend on other custom facts
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2916 Block mechanism is slow when there are custom facts that depend on other custom facts Change By: Bogdan Irimie Sprint: ghost-27.01.2021, ghost-10.02.2021 , 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.383064.1610550761000.138252.1612966020452%40Atlassian.JIRA.
Jira (PDB-3159) I'd like to access the performance dashboard over https
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-3159 I'd like to access the performance dashboard over https Change By: Bogdan Irimie Sprint: ghost-27.01.2021, ghost-10.02.2021 , 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.159265.1478038793000.138249.1612966020319%40Atlassian.JIRA.
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title Trey Dockendorf commented on PUP-10896 Re: Puppet users with forcelocal are no longer idempotent This issue was not present with previous versions of Puppet. I have numerous modules with acceptance tests using code similar to this and Puppet 6.20.0 and Puppet 7.3.0 did not have this issue. I also do not see this issue on any of my Puppet 5 acceptance 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.386956.1612964187000.138226.1612964280033%40Atlassian.JIRA.
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title
Trey Dockendorf created an issue
Puppet / PUP-10896
Puppet users with forcelocal are no longer idempotent
Issue Type:
Bug
Affects Versions:
PUP 7.4.0, PUP 6.21.0
Assignee:
Unassigned
Created:
2021/02/10 5:36 AM
Priority:
Major
Reporter:
Trey Dockendorf
Puppet Version: 7.4.0 and 6.21.0 Puppet Server Version: Masterless to demonstrate issue OS Name/Version: CentOS 7 Defining a `forcelocal` user results in Puppet constantly anting to change the GID for the user. Desired Behavior: Idempotent apply of forcelocal user. Actual Behavior:
[root@23aff6d4a202 /]# cat user-group.pp
user { 'keycloak':
ensure => 'present',
name => 'keycloak',
forcelocal => true,
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title
Trey Dockendorf updated an issue
Puppet / PUP-10896
Puppet users with forcelocal are no longer idempotent
Change By:
Trey Dockendorf
*Puppet Version:* 7.4.0 and 6.21.0*Puppet Server Version:* Masterless to demonstrate issue*OS Name/Version:* CentOS 7Defining a `forcelocal` user results in Puppet constantly anting wanting to change the GID for the user.*Desired Behavior:*Idempotent apply of forcelocal user.*Actual Behavior:*{noformat}[root@23aff6d4a202 /]# cat user-group.pp user { 'keycloak': ensure => 'present', name => 'keycloak', forcelocal => true, shell => '/sbin/nologin', gid=> 'keycloak', uid=> undef, home => '/var/lib/keycloak', managehome => true, system => true,}group { 'keycloak': ensure => 'present', name => 'keycloak', forcelocal => true, gid=> undef, system => true,}[root@23aff6d4a202 /]# puppet apply user-group.pp Notice: Compiled catalog for 23aff6d4a202 in environment production in 0.01 secondsNotice: /Stage[main]/Main/Group[keycloak]/ensure: createdNotice: /Stage[main]/Main/User[keycloak]/ensure: createdNotice: Applied catalog in 0.04 seconds[root@23aff6d4a202 /]# puppet apply user-group.pp Notice: Compiled catalog for 23aff6d4a202 in environment production in 0.01 secondsNotice: /Stage[main]/Main/User[keycloak]/gid: gid changed '13' to 'keycloak'Notice: Applied catalog in 0.02 seconds{noformat}I am fairly certain the issue resides in this change: https://tickets.puppetlabs.com/browse/PUP-10857
Add Comment
Jira (PUP-10895) puppet facts command doesn't accept specific options
Title: Message Title Oana Tanasoiu created an issue Puppet / PUP-10895 puppet facts command doesn't accept specific options Issue Type: Bug Assignee: Unassigned Created: 2021/02/10 3:52 AM Priority: Normal Reporter: Oana Tanasoiu `puppet facts` has default action the `show` subcommand. The default action has specific options like `-custom-dir `, `-show-legacy`... The `puppet facts` command fails when a subcommand specific option is provided: ~~ puppet facts --show-legacy Error: Could not parse application options: invalid option: --show-legacy Desired Behavior: `puppet facts` should work with the default action's options and also it should display the options when `–help` is provided.
