Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10719 Puppet's feature detection can leave rubygems in a bad state Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Fixes a rubygems caching issue that could prevent the agent from applying a catalog if a gem is managed using the native package manager, such as yum or apt. 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.374990.1602706184000.58532.1603154520028%40Atlassian.JIRA.
Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title Josh Cooper commented on PUP-10719 Re: Puppet's feature detection can leave rubygems in a bad state Merged to master in https://github.com/puppetlabs/puppet/commit/396538b945e0f7d6d28cb5e8abd7e7c975536f3b 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.374990.1602706184000.58531.1603154340031%40Atlassian.JIRA.
Jira (PDB-4881) Add primary key to catalog_inputs
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4881 Add primary key to catalog_inputs Change By: Rob Browning 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.371421.1599665914000.58525.1603152480096%40Atlassian.JIRA.
Jira (PDB-4895) Use top level hash to check catalog inputs submission
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission Change By: Rob Browning 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.371939.1600194545000.58524.1603152480041%40Atlassian.JIRA.
Jira (PDB-4881) Add primary key to catalog_inputs
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4881 Add primary key to catalog_inputs Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: Some additional indexing has been added to the catalog inputs storage which should improve query performance in some cases. 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.371421.1599665914000.58523.1603152240472%40Atlassian.JIRA.
Jira (PDB-4895) Use top level hash to check catalog inputs submission
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission Change By: Rob Browning Release Notes Summary: Most of PuppetDB can now detect when the time, the hiera inputs of in a catalog won't have not changed because it requires a user with respect to commit a change to the control repo. We should hash the entire set previous catalog , store that hash in the certnames table and check that to identify if there's anything that has changed before we go through the expense of avoid storing a new set of inputs them again . Team: HA 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 (PDB-4895) Use top level hash to check catalog inputs submission
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission Change By: Rob Browning Issue Type: New Feature 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.371939.1600194545000.58495.1603151700040%40Atlassian.JIRA.
Jira (PDB-4895) Use top level hash to check catalog inputs submission
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission Change By: Rob Browning Release Notes Summary: Most of the time, the hiera inputs of a catalog won't have changed because it requires a user to commit a change to the control repo. We should hash the entire set, store that hash in the certnames table and check that to identify if there's anything that has changed before we go through the expense of storing a new set of inputs. 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.371939.1600194545000.58496.1603151700097%40Atlassian.JIRA.
Jira (PDB-4872) Provide certificate-allowlist and facts-blocklist as config aliases
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4872 Provide certificate-allowlist and facts-blocklist as config aliases Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: The `certificate-whitelist` and `facts-blacklist` configuration options have been deprecated in favor of `certificate-allowlist` and `facts-blocklist`. See also: https://puppet.com/blog/removing-harmful-terminology-from-our-products/ 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.370301.1598463666000.58494.1603151580029%40Atlassian.JIRA.
Jira (PDB-4908) sync: defer to gc when gc is waiting to drop a partition
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4908 sync: defer to gc when gc is waiting to drop a partition Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: PuppetDB sync will now defer to the report and resource event garbage collections in order to avoid blocking their access to the locks they require. (Puppet Enterprise only) 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.373837.1601665651000.58486.1603151340276%40Atlassian.JIRA.
Jira (PDB-4909) sync: respect sync timeout when there are no changes
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4909 sync: respect sync timeout when there are no changes Change By: Rob Browning Release Notes Summary: The sync `entity-time-limit` is now additionally enforced by default by interruption of the thread performing sync. See also: https://puppet.com/docs/puppetdb/latest/configure.html#PDB_EXT_INTERRUPT_LINGERING_SYNC_PULL (Puppet Enterprise only) 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.373844.1601670899000.58477.1603151220084%40Atlassian.JIRA.
Jira (PDB-4906) Set an adjustable statement_timeout for all commands
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4906 Set an adjustable statement_timeout for all commands Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: SQL commands issued during an attempt to process a command (store a report, update a factset, etc.) will now time out after 10 minutes by default, causing the command to be retried or discarded. See also: https://puppet.com/docs/puppetdb/latest/configure.html#PDB_COMMAND_SQL_STATEMENT_TIMEOUT_MS 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.373499.1601482673000.58475.1603151160042%40Atlassian.JIRA.
Jira (PDB-4907) Set a timeout for the fact path gc
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4907 Set a timeout for the fact path gc Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: The fact path garbage collection process will now time out after 5 minutes by default if it cannot acquire the locks it requires. See also: https://puppet.com/docs/puppetdb/latest/configure.html#PDB_FACT_PATH_GC_SQL_LOCK_TIMEOUT_MS 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.373502.1601483556000.58473.1603150980025%40Atlassian.JIRA.
Jira (PDB-4909) sync: respect sync timeout when there are no changes
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4909 sync: respect sync timeout when there are no changes Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: The sync `entity-time-limit` is now additionally enforced by default by interruption of the thread performing sync. See also: https://puppet.com/docs/puppetdb/latest/configure.html#PDB_EXT_INTERRUPT_LINGERING_SYNC_PULL 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.373844.1601670899000.58472.1603150860026%40Atlassian.JIRA.
Jira (PDB-4903) Set a lock_timeout for gc partition drops
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4903 Set a lock_timeout for gc partition drops https://puppet.com/docs/puppetdb/latest/configure.html#sync-settings-puppet-enterprise-only Change By: Rob Browning Release Notes Summary: The report and resource event garbage collections will now time out if they have to wait longer than 5 minutes (by default) to acquire the required table lock. This prevents them from blocking other related queries indefinitely, and prevents them from participating an any permanent deadlocks. See also: https://puppet.com/docs/puppetdb/latest/configure.html#PDB_GC_DAILY_PARTITION_DROP_LOCK_TIMEOUT_MS 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
Jira (PDB-4931) Incrementally drop partitions oldest-first
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4931 Incrementally drop partitions oldest-first Change By: Rob Browning Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374925.1602690481000.58413.1603148340520%40Atlassian.JIRA.
Jira (PDB-4903) Set a lock_timeout for gc partition drops
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4903 Set a lock_timeout for gc partition drops Change By: Rob Browning Release Notes: Bug Fix Release Notes Summary: The report and resource event garbage collections will now time out if they have to wait longer than 5 minutes (by default) to acquire the required table lock. This prevents them from blocking other related queries indefinitely, and prevents them from participating an any permanent deadlocks. Issue Type: Improvement 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
Jira (PDB-4902) Handle resource event purges in one pass when possible
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4902 Handle resource event purges in one pass when possible Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: PuppetDB now unifies report and resource event clean up during a full garbage collection, instead of handling each in a separate transaction. This ensures it only waits on the exclusive lock to drop relevant event partitions once. 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.373095.1600987225000.58373.1603147860036%40Atlassian.JIRA.
Jira (PDB-4901) Only gc the oldest report/event partition in the normal case
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4901 Only gc the oldest report/event partition in the normal case Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: PuppetDB will only drop the oldest report or events partition during the normal, periodic gc when there's more than one candidate. This is intended to decrease the length of time we might block pdb operations since with the current arrangement, the drop will attempt to acquire an exclusive lock on the entire table (i.e. reports, not just the partition), and so will block all subsequent access to that table, until it finishes. 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 (PDB-4901) Only gc the oldest report/event partition in the normal case
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4901 Only gc the oldest report/event partition in the normal case Change By: Rob Browning Fix Version/s: PDB 6.13.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.373094.160098693.58358.1603147440031%40Atlassian.JIRA.
Jira (PDB-4897) Double-check catalog-inputs query structures
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4897 Double-check catalog-inputs query structures Change By: Rob Browning Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371951.1600196831000.58357.1603147320279%40Atlassian.JIRA.
Jira (PDB-4936) docs: postgresql config has issues
Title: Message Title Jean Bond updated an issue PuppetDB / PDB-4936 docs: postgresql config has issues Change By: Jean Bond Summary: docs: postgresql config has issues 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.375147.1602850504000.58320.1603146420140%40Atlassian.JIRA.
Jira (PDB-4936) postgresql config has issues
Title: Message Title Jean Bond moved an issue PuppetDB / PDB-4936 postgresql config has issues Change By: Jean Bond Key: DOCUMENT PDB - 1158 4936 Method Found: Needs Assessment Scrum Team: PuppetDB Workflow: Documentation Scrum Team Workflow Project: Documentation PuppetDB 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
Jira (PDB-4935) [docs issue]
Title: Message Title Jean Bond moved an issue PuppetDB / PDB-4935 [docs issue] Change By: Jean Bond Component/s: PuppetDB Component/s: PuppetDB Key: DOCUMENT PDB - 1161 4935 Method Found: Needs Assessment Scrum Team: PuppetDB Workflow: Documentation Scrum Team Workflow Project: Documentation PuppetDB Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4935) user error during installation
Title: Message Title Jean Bond updated an issue PuppetDB / PDB-4935 user error during installation Change By: Jean Bond Summary: [docs issue] user error during installation 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.58316.1603146360224%40Atlassian.JIRA.
Jira (PUP-9481) Setting certname in multiple sections bypasses validation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9481 Setting certname in multiple sections bypasses validation 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.295431.1549619002000.58168.1603134780025%40Atlassian.JIRA.
Jira (PUP-9469) Remove the setting to turn off func 3x API validation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9469 Remove the setting to turn off func 3x API validation Change By: Josh Cooper Team: Froyo Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.294057.1548939109000.58153.1603133520108%40Atlassian.JIRA.
Jira (PUP-7930) Array delete does not work according to spec when right hand side is hash
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7930 Array delete does not work according to spec when right hand side is hash Change By: Josh Cooper Team: Froyo Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.210105.1505103024000.58152.1603133520052%40Atlassian.JIRA.
Jira (PDB-4934) PuppetDB does not support username@hostname auth for Azure PostgreSQL
Title: Message Title
Kevin Reeuwijk updated an issue
PuppetDB / PDB-4934
PuppetDB does not support username@hostname auth for Azure PostgreSQL
Change By:
Kevin Reeuwijk
As a customer, I want to be able to use Azure PostgreSQL as my external PostgreSQL database for Puppet Enterprise. When attempting to use Azure PostgreSQL as an external database for PuppetDB (PE 2019.8.1), I encountered the problem that Azure requires the username for the Postgres connection to be in the {{username@hostname}} form, due to the way they publish access to PostgreSQL (as described [here|https://github.com/chef/chef-server/issues/1559]). I can manually modify {{database.ini}} to set the username to that format, but then you’ll see this in the logs:{noformat}clojure.lang.ExceptionInfo: Connected to database as "pe-puppetdb-migrator", not migrator "pe-puppetdb-migrator@pdb01"{noformat}It seems we have the same limitations as Chef has (see linked issue). This requirement from Azure stems from their architecture:{noformat}Azure Database for PostgreSQL has a gateway in front of the actual database servers that forwards connections from username@hostname to hostname as username.This means that once the connection is established, you will actually be connected as username, not username@hostname, and any database queries involving users should just use username (e.g. granting permissions).{noformat} Some issues I’ve encountered while trying to get this to work: * The [docs|https://puppet.com/docs/pe/2019.8/installing_postgresql.html#create_pe_databases_on_the_postgresql_instance] don’t tell you to also create a {{pe-puppetdb-migrator}} user * The [docs|https://puppet.com/docs/pe/2019.8/installing_postgresql.html#create_pe_databases_on_the_postgresql_instance] assume a Linux OS for the {{psql}} commands to create the users & databases. However, Azure PostgreSQL runs on Windows, which causes the locales to have different names. For Azure PostgreSQL, the {{ENCODING}} line needs to be changed to: {{ENCODING 'utf8' LC_CTYPE 'English_United States.1252' LC_COLLATE 'English_United States.1252' template template0;}} * You can’t specify {{username@hostname}} for the {{xxx_regular_db_user}} and {{xxx_migration_db_user}} settings in {{pe.conf}}, the {{@hostname}} part gets cutoff during installation. * I can manually re-add the {{@hostname}} back to the username in {{database.ini}} but then the queries also expect this for the connection, which they should not. And I can probably assume that another puppet run would overwrite the settings in {{database.ini}} again.
Jira (PDB-4934) PuppetDB does not support username@hostname auth for Azure PostgreSQL
Title: Message Title Kevin Reeuwijk created an issue PuppetDB / PDB-4934 PuppetDB does not support username@hostname auth for Azure PostgreSQL Issue Type: Bug Affects Versions: PDB 6.11.3 Assignee: Unassigned Components: PuppetDB Created: 2020/10/19 10:10 AM Priority: Normal Reporter: Kevin Reeuwijk As a customer, I want to be able to use Azure PostgreSQL as my external PostgreSQL database for Puppet Enterprise. When attempting to use Azure PostgreSQL as an external database for PuppetDB (PE 2019.8.1), I encountered the problem that Azure requires the username for the Postgres connection to be in the username@hostname form, due to the way they publish access to PostgreSQL (as described here). I can manually modify database.ini to set the username to that format, but then you’ll see this in the logs: clojure.lang.ExceptionInfo: Connected to database as "pe-puppetdb-migrator", not migrator "pe-puppetdb-migrator@pdb01" It seems we have the same limitations as Chef has (see linked issue). This requirement from Azure stems from their architecture:
Jira (PDB-4933) query with `in` operator fails
Title: Message Title
Vadym Chepkov created an issue
PuppetDB / PDB-4933
query with `in` operator fails
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/10/19 9:45 AM
Priority:
Normal
Reporter:
Vadym Chepkov
When trying to execute simple query with `in` operator receive a failure:
# puppet-query "inventory[certname]{ facts.location in ['home', 'linode']}"
2020/10/19 16:38:01 ERROR - [GET /pdb/query/v4][500] getQuery default
# rpm -qf /opt/puppetlabs/client-tools/bin/puppet-query
pe-client-tools-19.8.2-1.el8.x86_64
# rpm -qa|grep puppetdb
Jira (FACT-2823) SPIKE - Investigate turning facter into a single binary
Title: Message Title Gheorghe Popescu commented on FACT-2823 Re: SPIKE - Investigate turning facter into a single binary Some limitations: the stable version comes with ruby 2.4 and bundler 1.5(there is a nightly with ruby 2.7 and bundler 2) facter uses a different gemspec for agent(which is not loaded when using ruby-packer to build the executable) 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.373494.1601481425000.57798.1603113180050%40Atlassian.JIRA.
Jira (PUP-10694) Prepare release announcement (Puppet Platform 5.5.22)
Title: Message Title Claire Cadman commented on PUP-10694 Re: Prepare release announcement (Puppet Platform 5.5.22) Release notes PR: https://github.com/puppetlabs/puppet-docs/pull/1006 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.374283.1602109968000.57791.1603111800024%40Atlassian.JIRA.
Jira (PUP-10704) Prepare release announcement (Puppet Platform 6.19.0)
Title: Message Title Claire Cadman commented on PUP-10704 Re: Prepare release announcement (Puppet Platform 6.19.0) Release notes preview: https://puppet-docs-preview.netlify.app/docs/puppet/latest-preview/release_notes_puppet.html#release_notes_puppet_x-19-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.374319.1602110121000.57788.1603111560054%40Atlassian.JIRA.
Jira (FACT-2841) Drop internal configuration based on JSON or HOCON
Title: Message Title Gheorghe Popescu created an issue Facter / FACT-2841 Drop internal configuration based on JSON or HOCON Issue Type: Improvement Assignee: Unassigned Created: 2020/10/19 5:25 AM Priority: Normal Reporter: Gheorghe Popescu The os hierarchy used for detecting the platforms that facter is running on is stored in JSON. Facter groups for blocking are stored as HOCON. In order to have a more robust internal configuration, this can be dropped in favour of using a configuration module that stores the data in constants. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2823) SPIKE - Investigate turning facter into a single binary
Title: Message Title Gheorghe Popescu commented on FACT-2823 Re: SPIKE - Investigate turning facter into a single binary Can be built easily on OSX too, using the vmpooler images. In terms of performance, the standalone executable has a slight improvement over running from gem using bundler, around 5%(tested on OSX 10.15 and Centos 8) 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.373494.1601481425000.57772.1603109820023%40Atlassian.JIRA.
Jira (FACT-2839) Fix to_hash performance for OSX platform
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2839 Fix to_hash performance for OSX platform Change By: Andrei Filipovici Sprint: ready for 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.375222.1603109274000.57770.1603109520104%40Atlassian.JIRA.
Jira (FACT-2840) Fix to_hash performance for Solaris platforms
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2840 Fix to_hash performance for Solaris platforms Change By: Andrei Filipovici Sprint: ready for 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.375223.1603109437000.57771.1603109520147%40Atlassian.JIRA.
Jira (FACT-2839) Fix to_hash performance for OSX platform
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2839 Fix to_hash performance for OSX platform Change By: Andrei Filipovici Acceptance Criteria: If possible, difference between facter 3 and 4 for the to_hash method, on OSX is no bigger than 500 300 ms. 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.57769.1603109520058%40Atlassian.JIRA.
Jira (FACT-2840) Fix to_hash performance for Solaris platforms
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2840 Fix to_hash performance for Solaris platforms Issue Type: Task Assignee: Unassigned Created: 2020/10/19 5:10 AM Environment: On Solaris platforms, facter 3 method to_hash takes 0.36 seconds to complete. Same method takes 0.89 seconds to complete on facter 4. Labels: platform7 Priority: Normal Reporter: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2839) Fix to_hash performance for OSX platform
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2839 Fix to_hash performance for OSX platform Issue Type: Task Assignee: Unassigned Created: 2020/10/19 5:07 AM Labels: platform7 Priority: Normal Reporter: Andrei Filipovici On OSX platforms, on average the to_hash method takes 0.83 seconds to complete, for facter 3. Facter 4 needs 1.91 seconds to complete. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-1846) inconsistent results between facter and puppet facts
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-1846 inconsistent results between facter and puppet facts Change By: Andrei Filipovici Assignee: Andrei Filipovici 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.246793.1524245996000.57729.1603104720032%40Atlassian.JIRA.
Jira (PUP-9051) Refactor the SMF provider to implement enableable semantics
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Puppet / PUP-9051 Refactor the SMF provider to implement enableable semantics Change By: Ciprian Badescu Assignee: Ciprian Badescu 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.270546.1533855292000.57707.1603102440032%40Atlassian.JIRA.
Jira (FACT-2815) Timing on cached facts is inconsistent, sometime it is displayed, others it is not
Title: Message Title Bogdan Irimie commented on FACT-2815 Re: Timing on cached facts is inconsistent, sometime it is displayed, others it is not `virtualisation` is the name of a groups of facts virtualization - virtual - is_virtual - cloud With the fix from this PR timing is showed for the facts that can be resolved from the `virtualisation group`. cached fact 'virtual', took: (0.46) seconds cached fact 'is_virtual', took: (0.03) seconds Add Comment
Jira (PUP-10716) Fix json output of puppet facts show action
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Puppet / PUP-10716 Fix json output of puppet facts show action 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.374908.160268028.57658.1603088760148%40Atlassian.JIRA.
