Jira (PUP-10663) SSL cert agent cannot verify from host.
Title: Message Title Richard Woon commented on PUP-10663 Re: SSL cert agent cannot verify from host. Thanks Josh Cooper I believe Muhammad Amirrul Al Hafiz has solved it once he used puppet-agent v6 Now that it's solved, we also now know why it didn't work. Thanks again 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.371573.1599792916000.34957.1599867840139%40Atlassian.JIRA.
Jira (HI-619) Hiera return all keys (or keys matching pattern)
Title: Message Title Henrik Lindberg commented on HI-619 Re: Hiera return all keys (or keys matching pattern) Hiera is not designed to be able to enumerate all the keys. It can only answer with the value bound to a key (which it arrives at via a large set of rules). You cannot do this by just looking at simple yaml/json files since it is a particular backend that reads those and provides the answer. You can also have backends that are backed by a database, or say LDAP. If you asked for "all keys" you would get a return that potentially consists of very large amounts of data. Further, since lookups are done in a particular context (set of variable values) the result and indeed the set of available keys changes. Thus the answer to the question "give me all keys" is multidimensional - or would need to be constrained with the set of variables that the hiera key resolution depends on - something that is possible for some known variables like facts - but the full set of variables isn't declared anywhere - the backends can do pretty much what they want. It difficult, but not impossible to add "enumeration of keys" to the hiera API, but it would need to have a mechanism for backends to opt in to support it, and also some mechanism for backends to respond with a signal that it would result in too much data. The implementation would be difficult since a backend in hiera 5 is just a simple function with a very clear purpose; too lookup a value. It would probably have to be an additional function that can do the enumeration which each hiera backend function provider would need to implement to support this feature. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10642) Uppercase Default value in conditional documentation a typo?
Title: Message Title
Henrik Lindberg commented on PUP-10642
Re: Uppercase Default value in conditional documentation a typo?
There should be more examples showing those other types of matches.
case $x {
Integer: { ... } # x is an Integer value
String[10]: { ...}# x is a string 10 or more chars long
String: { ... } # x is a string short than 10 (since option above took the longer ones}case [$x, $y] { [String, Integer]: { ... } # x is String and y is an Integer [10, "hello"]: { ... } # x is the integer 10, and y the string "hello" [1, default]: { ... }# x is the integer 1, and y can be any value (could also have been written Any)}
if that is not already in the documentation, it should be.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10642) Uppercase Default value in conditional documentation a typo?
Title: Message Title
Henrik Lindberg commented on PUP-10642
Re: Uppercase Default value in conditional documentation a typo?
The intention was probably to have this (with a lower case default:
case $facts['os']['name'] {
'Solaris': {
include role::solaris
}
'RedHat', 'CentOS': {
include role::redhat
}
/^(Debian|Ubuntu)$/: {
include role::debian
}
default: {
include role::generic
}
}
Jira (PUP-10664) Puppet 6 should log connection error details when a functional puppet master cannot be located
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-10664 Puppet 6 should log connection error details when a functional puppet master cannot be located Change By: Charlie Sharpsteen Team: Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371698.1599857641000.34825.1599858720029%40Atlassian.JIRA.
Jira (PUP-10664) Puppet 6 should log connection error details when a functional puppet master cannot be located
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-10664
Puppet 6 should log connection error details when a functional puppet master cannot be located
Change By:
Charlie Sharpsteen
At the beginning of each run, the Puppet agent performs a health check to locate a functional Puppet Server to make API calls to. If this health check fails, the run fails with the following message:{noformat}Error: Could not run Puppet configuration client: Could not select a functional puppet master from server_list: 'localhost:8140'{noformat}In order to facilitate troubleshooting, the messages logged at error level should include some detail of what happened to the health check.h2. Reproduction Case - Install Puppet 6 on CentOS 7:{code:bash}yum install -y http://yum.puppetlabs.com/puppet6-release-el-6.noarch.rpmyum install -y puppetserver{ coode code } - Configure the agent to check in locally and bootstrap the Puppet Server CA:{code:bash}source /etc/profile.d/puppet-agent.shpuppet config set server $(hostname -f)puppetserver ca setupsystemctl start puppetserver{code} - Provoke a health check failure by running the Puppet agent with the server url set to {{localhoost}}:{code:bash}puppet agent -t --server_list=localhost:8140{code}h3. OutcomeThe error message is very terse and just states that a healthy server could not be found:{noformat}# puppet --version6.18.0# puppet agent -t --server_list=localhost:8140Error: Could not run Puppet configuration client: Could not select a functional puppet master from server_list: 'localhost:8140'{noformat}h3. Expected OutcomeRaising the log level to DEBUG reveals that the health check failed due to a SSL validation error. These details should be logged at ERROR level so that the root cause of connection failures is visible for post-mortem debugging:{noformat}# puppet agent -t --server_list=localhost:8140 --debug...Debug: Unable to connect to server from server_list setting: Server hostname 'localhost' did not match server certificate; expected one of dull-sanatorium.delivery.puppetlabs.net, DNS:puppet, DNS:dull-sanatorium.delivery.puppetlabs.net...Error: Could not run Puppet configuration client: Could not select a functional puppet master from server_list: 'localhost:8140'{noformat}
Add Comment
Jira (PUP-10664) Puppet 6 should log connection error details when a functional puppet master cannot be located
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-10664 Puppet 6 should log connection error details when a functional puppet master cannot be located Change By: Charlie Sharpsteen Priority: Normal Major Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371698.1599857641000.34815.1599857760088%40Atlassian.JIRA.
Jira (PUP-10664) Puppet 6 should log connection error details when a functional puppet master cannot be located
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-10664 Puppet 6 should log connection error details when a functional puppet master cannot be located Issue Type: Improvement Affects Versions: PUP 6.18.0 Assignee: Unassigned Created: 2020/09/11 1:54 PM Priority: Normal Reporter: Charlie Sharpsteen At the beginning of each run, the Puppet agent performs a health check to locate a functional Puppet Server to make API calls to. If this health check fails, the run fails with the following message: Error: Could not run Puppet configuration client: Could not select a functional puppet master from server_list: 'localhost:8140' In order to facilitate troubleshooting, the messages logged at error level should include some detail of what happened to the health check. Reproduction Case Install Puppet 6 on CentOS 7: yum install -y
Jira (PUP-10608) Option to "prettyprint" /opt/puppetlabs/puppet/cache/client_data/catalog
Title: Message Title Pat Riehecky commented on PUP-10608 Re: Option to "prettyprint" /opt/puppetlabs/puppet/cache/client_data/catalog That makes sense to me, I'd say this can be canceled. 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.367667.1596031358000.34794.1599856140026%40Atlassian.JIRA.
Jira (PUP-10233) environment_classes API endpoint extremely slow
Title: Message Title Charlie Sharpsteen commented on PUP-10233 Re: environment_classes API endpoint extremely slow I'm a bit confused by: This spawns 32 jruby processes hitting: /puppet/v3/environment_classes" How exactly is that activity showing up? As far as I know, that API endpoint is only used by external services like the PE Console. Unless I'm missing something, having 32 request roll in for it seems like bad behavior in some external process. 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.341970.157901085.34750.1599853080085%40Atlassian.JIRA.
Jira (HI-619) Hiera return all keys (or keys matching pattern)
Title: Message Title Pat Riehecky created an issue Hiera / HI-619 Hiera return all keys (or keys matching pattern) Issue Type: New Feature Affects Versions: HI 3.5.0 Assignee: Unassigned Components: CLI Created: 2020/09/11 12:33 PM Priority: Normal Reporter: Pat Riehecky I'd like to have an option for hiera lookups to fetch all keys (or keys matching a pattern). Example use case: I'm looking to change my existing hierarchy by adding/removing a new element. I'd like to validate that some nodes change and that others did not. Dumping the return result and doing diffs from old/new would give me clear insight into the consequences of the change before going live. I'm coming from an ENC (such as foreman) where I'm used to looking at the entire ENC config. As I develop my hiera setup, I'd like to fetch the output for a node in a manner I'm familiar with. A set of nodes is moving from my group to another group. I've given them a list of puppet modules I'm using for these nodes, but I'd also like to provide the values each node is using so they can develop their configuration management.
Jira (PUP-10583) Change default digest algorithm to sha256
Title: Message Title Josh Cooper commented on PUP-10583 Re: Change default digest algorithm to sha256 Follow up merged to main in https://github.com/puppetlabs/puppet/commit/e2a883df7e8bd35238cd274e71dd2d99d6af62ee 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.365680.1594659603000.34728.1599851940023%40Atlassian.JIRA.
Jira (PUP-10660) $module_name is not available up in epp()
Title: Message Title Henrik Lindberg commented on PUP-10660 Re: $module_name is not available up in epp() Ah, yes... the global scope is actually named "" (nothing). Also an ancient design decision. 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.371297.1599469893000.34695.1599850620030%40Atlassian.JIRA.
Jira (PUP-10662) environment_classes API Endpoint takes minutes to return/update
Title: Message Title Josh Cooper commented on PUP-10662 Re: environment_classes API Endpoint takes minutes to return/update Jason Lang thanks for the information, but it'd be good to update the existing ticket with these additional details instead of creating a new ticket. I'm going to mark this as a dup of the other one. 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.371583.159983170.34649.1599848100231%40Atlassian.JIRA.
Jira (PUP-10663) SSL cert agent cannot verify from host.
Title: Message Title Josh Cooper commented on PUP-10663 Re: SSL cert agent cannot verify from host. By default, a new install of puppetserver 6 will create root and intermediate CA certificates, and issue the pupetserver certificate from the intermediate. See https://puppet.com/blog/certificate-improvements-puppet-6/ However, puppet 5 agents do not support CA chains leading to the above error. I suggest following up in #puppet in slack to see how others have handled 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.371573.1599792916000.34636.1599847620031%40Atlassian.JIRA.
Jira (PUP-10663) SSL cert agent cannot verify from host.
Title: Message Title Josh Cooper moved an issue Puppet / PUP-10663 SSL cert agent cannot verify from host. Change By: Josh Cooper Key: PA PUP - 3399 10663 Project: Puppet Agent 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.371573.1599792916000.34611.1599846480038%40Atlassian.JIRA.
Jira (PDB-4891) duplicate key value violates unique constraint
Title: Message Title Zachary Kent commented on PDB-4891 Re: duplicate key value violates unique constraint Hi zoen, could not serialize access due to concurrent update The error above will occur when two transactions tried to update the same row and one wins and the other will then fail and get retried. Some level of these errors is normal and shouldn't be cause for alarm by itself. duplicate key value violates unique constraint "resource_params_cache_pkey" We have also seen the error above in other installs before. That's the db enforcing a unique constraint on the resource_params_cache table. Some level of these errors is normal as well. Both of these errors don't indicate a problem by themselves, if they happen infrequently they're safe to ignore. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10660) $module_name is not available up in epp()
Title: Message Title Magnus Jonsson commented on PUP-10660 Re: $module_name is not available up in epp() For other unknown variables in the epp-file a get a warning that it does not exist but $module_name is just "" without any notifiation. 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.371297.1599469893000.34399.1599833220021%40Atlassian.JIRA.
Jira (PUP-10660) $module_name is not available up in epp()
Title: Message Title Henrik Lindberg commented on PUP-10660 Re: $module_name is not available up in epp() That is also by design (ancient design decision that all variables that does not exist resolve to undef which renders as empty string). You can turn on "strict variables" as that would make it error instead. It is not on by default due to backwards compatibility reasons and if you turn it on you may find that the code you are running needs to be modified. 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.371297.1599469893000.34396.1599832440034%40Atlassian.JIRA.
Jira (PUP-10662) environment_classes API Endpoint takes minutes to return/update
Title: Message Title
Jason Lang created an issue
Puppet / PUP-10662
environment_classes API Endpoint takes minutes to return/update
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/09/11 6:41 AM
Priority:
Normal
Reporter:
Jason Lang
Puppet Version: 5.5.18 (but unrelated to the issue) Puppet Server Version: 5.3.1/5.3.10 OS Name/Version: RHEL 7 This is an extension of PUP-10233 that I've continued to break down and make "less ambiguous" We have a larger environment which makes use of the environment classes cache (Foreman Integrated). When we "update code" we hit the "environment_classes" api endpoint to refresh the environment classes cache. https://puppet.com/docs/puppetserver/5.3/puppet-api/v3/environment_classes.html Specifically - i see this spawn a "process" in the "/status/v1/services/jruby-metrics?level=debug" output on the puppet master. This can take "forever" (400 seconds or more) during which the cache doesn't return as its still "processing/building/whatever". I can check CPU/Memory/Disk IOPS and see "nothing constrained" - borderline idle for this entire time. Example from the jruby-metrics endpoint - specifically under: status -> experimental -> metrics -> borrowed_instances { "time": 1599830351410, "reason": { "request": { "uri": "/puppet/v3/environment_classes", "request-method": "get", "route-id": "puppet-v3-environment_classes-/*/" } }, "duration-millis": 296094 }, "Eventually" - 300-400 seconds after called it will finish. and the environment_classes endpoint will return proper cached data. Desired Behavior: I realize generating a cache isn't instant. But 400 seconds seems obscenely long - particularly when im finding no resource bottleneck. I do have hunddres of modules/thousands of classes across each environment. HOWEVER - even with that - I guess my desired behavior is "60 seconds or less - even in extreme scenarios" I'm not above this potentially being an issue with my config/setup, or even "bad inefficient classes" we have in use on our end contributing here. My problem is knowing where or what to check. This call seems like a "black box" that takes 400 seconds but produces no output/logging/progress. Is there any way to enable some type of
Jira (FACT-2315) Extend Facter 4.x API with warn
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2315 Extend Facter 4.x API with warn 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.344081.1580305957000.34376.1599830220031%40Atlassian.JIRA.
Jira (PUP-10583) Change default digest algorithm to sha256
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-10583 Change default digest algorithm to sha256 Change By: Gabriel Nagy Release Notes: Enhancement Release Notes Summary: Switch to using sha256 as the default digest algorithm for 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.365680.1594659603000.34353.1599822960111%40Atlassian.JIRA.
Jira (PUP-10509) Drop support for ruby < 2.5
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-10509 Drop support for ruby < 2.5 Change By: Gabriel Nagy Release Notes: Enhancement Release Notes Summary: Replace usage of Fixnum and Bignum with Integer as part of dropping support for Rubies older than 2.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.358867.1589476926000.34352.1599822960056%40Atlassian.JIRA.
Jira (PUP-10653) Remove the Dir monkey-patch from Puppet if not used
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-10653 Remove the Dir monkey-patch from Puppet if not used Change By: Gabriel Nagy Release Notes: Enhancement Release Notes Summary: Remove external dependency on the win32/dir gem and replace the usage of CSIDL constants with environment variables 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.370869.1598950845000.34351.1599822840028%40Atlassian.JIRA.
Jira (PUP-6184) Remove win32-dir code usage from Puppet
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-6184 Remove win32-dir code usage from Puppet Change By: Gabriel Nagy Release Notes Summary: Remove dependency on win32 superseded by PUP - dir gem and pull the related missing functionality in Puppet. 10653 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.127175.1461029704000.34350.1599822780076%40Atlassian.JIRA.
Jira (PUP-6184) Remove win32-dir code usage from Puppet
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-6184 Remove win32-dir code usage from Puppet Change By: Gabriel Nagy Release Notes: Enhancement 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.127175.1461029704000.34348.1599822720028%40Atlassian.JIRA.
Jira (PUP-10642) Uppercase Default value in conditional documentation a typo?
Title: Message Title
Claire Cadman commented on PUP-10642
Re: Uppercase Default value in conditional documentation a typo?
Henrik Lindberg, so would you remove the entire case statement example: A case statement evaluates a list of cases against a control _expression_, and executes the first code block where the case value matches the control _expression_. This example declares a role class on a node, but which role class it declares depends on what operating system the node runs: {{}}
case $facts['os']['name'] {
'Solaris': {
include role::solaris
}
'RedHat', 'CentOS': {
include role::redhat
}
/^(Debian|Ubuntu)$/: {
include role::debian
}
Default: {
include role::generic
}
Jira (PDB-4891) duplicate key value violates unique constraint
Title: Message Title
zoen updated an issue
PuppetDB / PDB-4891
duplicate key value violates unique constraint
Change By:
zoen
{noformat}- Ubuntu 18.04.4 LTS \n \l- puppetdb5.2.18-1bionic- postgresql-9.6 9.6.18-1.pgdg18.04+1{noformat}time to time. We got this kind of error on our PostgreSQL. this even after updating(from 5.2.11-1bionic), the errors also are still present. {noformat}2020-09-11 08:03:08 UTC ERROR: duplicate key value violates unique constraint "resource_params_cache_pkey"2020-09-11 08:03:08 UTC DETAIL: Key (resource)=(\xf5061d5d2ebebc3acd3682cf30649ded7de5a58f) already exists.2020-09-11 08:03:08 UTC STATEMENT: INSERT INTO resource_params_cache ( resource, parameters ) VALUES ( $1, $2 )RETURNING *2020-09-11 08:04:14 UTC ERROR: could not serialize access due to concurrent update2020-09-11 08:04:14 UTC STATEMENT: INSERT INTO fact_paths ( path, value_type_id, path_array, name, depth ) VALUES ( $1, $2, $3, $4, $5 ) ON CONFLICT do nothingRETURNING *2020-09-11 08:04:14 UTC ERROR: could not serialize access due to concurrent update2020-09-11 08:04:14 UTC STATEMENT: INSERT INTO fact_paths ( path, value_type_id, path_array, name, depth ) VALUES ( $1, $2, $3, $4, $5 ) ON CONFLICT do nothingRETURNING *2020-09-11 08:04:14 UTC ERROR: could not serialize access due to concurrent update2020-09-11 08:04:14 UTC STATEMENT: INSERT INTO fact_paths ( path, value_type_id, path_array, name, depth ) VALUES ( $1, $2, $3, $4, $5 ) ON CONFLICT do nothingRETURNING *2020-09-11 08:04:14 UTC ERROR: could not serialize access due to concurrent update2020-09-11 08:04:14 UTC STATEMENT: INSERT INTO fact_paths ( path, value_type_id, path_array, name, depth ) VALUES ( $1, $2, $3, $4, $5 ) ON CONFLICT do nothingRETURNING *2020-09-11 08:04:38 UTC ERROR: could not serialize access due to concurrent update2020-09-11 08:04:38 UTC STATEMENT: INSERT INTO fact_paths ( path, value_type_id, path_array, name, depth ) VALUES ( $1, $2, $3, $4, $5 ) ON CONFLICT do nothingRETURNING *2020-09-11 08:04:38 UTC ERROR: could not serialize access due to concurrent update2020-09-11 08:04:38 UTC STATEMENT: INSERT INTO fact_paths ( path, value_type_id, path_array, name, depth ) VALUES ( $1, $2, $3, $4, $5 ) ON CONFLICT do nothingRETURNING *2020-09-11 08:04:38 UTC ERROR: could not serialize access due to concurrent update2020-09-11 08:04:38 UTC STATEMENT: INSERT INTO fact_paths ( path, value_type_id, path_array, name, depth ) VALUES ( $1, $2, $3, $4, $5 ) ON CONFLICT do nothingRETURNING *2020-09-11 08:04:39 UTC ERROR: duplicate key value violates unique constraint "resource_params_cache_pkey"2020-09-11 08:04:39 UTC DETAIL: Key (resource)=(\x68a902bee08b27a7787e6da9f6fff3071d6746f3) already exists.2020-09-11 08:04:39 UTC STATEMENT: INSERT INTO resource_params_cache ( resource, parameters ) VALUES ( $1, $2 )RETURNING *2020-09-11 08:04:43 UTC ERROR: could not serialize access due to concurrent update2020-09-11 08:04:43 UTC
Jira (PDB-4891) duplicate key value violates unique constraint
Title: Message Title zoen created an issue PuppetDB / PDB-4891 duplicate key value violates unique constraint Issue Type: Bug Affects Versions: PDB 5.2.18 Assignee: Unassigned Components: PuppetDB Created: 2020/09/11 2:32 AM Priority: High Reporter: zoen - Ubuntu 18.04.4 LTS \n \l - puppetdb5.2.18-1bionic - postgresql-9.6 9.6.18-1.pgdg18.04+1 time to time. We got this kind of error on our PostgreSQL. this errors also
Jira (FACT-2793) Facter does not support timeout for shell out calls
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2793 Facter does not support timeout for shell out calls 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.371408.1599655845000.34295.1599813000155%40Atlassian.JIRA.
Jira (PUP-10613) Puppet::Util.uri_encode discards '='
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10613 Puppet::Util.uri_encode discards '=' Change By: Josh Cooper Sprint: Coremunity Grooming 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.368658.1596844155000.34290.1599808860027%40Atlassian.JIRA.
Jira (FACT-2389) Fix netkvm_resolver_spec.rb
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2389 Fix netkvm_resolver_spec.rb 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.346692.1582124304000.34286.1599807900026%40Atlassian.JIRA.
Jira (PUP-9309) Remove unused AST class SubLocatedExpression
Title: Message Title Josh Cooper commented on PUP-9309 Re: Remove unused AST class SubLocatedExpression Passed CI in c403763bbb 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.284713.1542018073000.34278.1599806400025%40Atlassian.JIRA.
Jira (PUP-10446) Remove application orchestration language features
Title: Message Title Josh Cooper commented on PUP-10446 Re: Remove application orchestration language features Passed CI in c403763bbb 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.356722.1587765694000.34277.1599806340127%40Atlassian.JIRA.
Jira (PUP-10661) Undefined method uncompress_body can occur for some rest responses
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10661 Undefined method uncompress_body can occur for some rest responses Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371570.1599788088000.34274.1599806220027%40Atlassian.JIRA.
Jira (FACT-2775) partitions..filesystem not working on redhat7
Title: Message Title
Andrei Filipovici updated an issue
Facter / FACT-2775
partitions..filesystem not working on redhat7
Change By:
Andrei Filipovici
Facter 3.x resolves to `xfs` while Facter 4 cannot resolve the fact {code} "partitions./dev/mapper/rhel-root.filesystem" => {: new_value => "nil",: old_value => "\"xfs\""} {code} Also, when the filesystem can't be resolved, the uuid also, isn't resolved. <
/td>
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.370466.1598517881000.34273.1599806040036%40Atlassian.JIRA.
