Jira (PUP-10391) URI.escape is obsolete in Ruby 2.7
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-10391 URI.escape is obsolete in Ruby 2.7 Change By: Melissa Stone Assignee: Melissa Stone 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.351394.1585310712000.69046.1590188280076%40Atlassian.JIRA.
Jira (PUP-10391) URI.escape is obsolete in Ruby 2.7
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10391 URI.escape is obsolete in Ruby 2.7 Change By: Melissa Stone Sprint: Coremunity Hopper 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.351394.1585310712000.69044.1590188220128%40Atlassian.JIRA.
Jira (PUP-5349) only the ca server is veryfing puppet client certificates
Title: Message Title Josh Cooper commented on PUP-5349 Re: only the ca server is veryfing puppet client certificates The CA writes to /etc/puppetlabs/puppet/ssl/ca/ca_crl.pem when revoking a cert. Puppetserver watches for changes to that file and copies it to /etc/puppetlabs/puppet/ssl/crl.pem which is what puppetserver and the local puppet agent read from. Did you disable the CA service for the puppetservers that are not the CA, see https://puppet.com/docs/puppetserver/5.3/external_ca_configuration.html#disabling-the-internal-puppet-ca-service 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.101226.127929000.68952.1590181200091%40Atlassian.JIRA.
Jira (PUP-5349) only the ca server is veryfing puppet client certificates
Title: Message Title Leif M commented on PUP-5349 Re: only the ca server is veryfing puppet client certificates I can provide the CRL/serial number if necessary, but I don't think there is a problem with the CRL, because the CA server is rejecting agents appropriately when agents with revoked certificates try to run against the CA. SSL termination is on the puppet servers, not the LB. As I mentioned, agent runs work against the LB and against the servers directly, and for that reason I've just been testing directly against one of the individual puppet servers. As I mentioned, I found the CRL in two different locations under /etc/puppetlabs on the CA, so I went ahead & tried to copy it to those same two locations on the puppet server that I am using to test, but it didn't have any effect. Those locations are: /etc/puppetlabs/puppet/ssl/ca/ca_crl.pem /etc/puppetlabs/puppet/ssl/crl.pem It could just be that the CRL needs to be dropped somewhere else on the other puppet servers. I know that the puppetserver service isn't supposed to need a restart to pick up CRL updates, but at this point it seemed like a reasonable thing to try. Thanks for looking at 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
Jira (PUP-2301) puppet module list --tree output shows dependencies incorrectly
Title: Message Title Greg commented on PUP-2301 Re: puppet module list --tree output shows dependencies incorrectly If you're up for dirty hacks, in lib/puppet/face/module/list.rb it's the line next if @seen[(mod.forge_name or mod.name)] in list_build_tree. Comment it out and you'll get a full tree (with lots of 'repeats') that more accurately reflects reality. 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.27587.1393543664000.68896.1590179100086%40Atlassian.JIRA.
Jira (PUP-5349) only the ca server is veryfing puppet client certificates
Title: Message Title Josh Cooper commented on PUP-5349 Re: only the ca server is veryfing puppet client certificates Does the load-balancer terminate the SSL connection? If yes, then the CA's CRL needs to be copied to where ever the LB looks for the file, and possibly reloaded. If no, then it can't check the validity of the client's certificate since all the load-balancer sees is encrypted traffic. So then each puppetserver terminates the SSL connection, and the CRL from the CA needs to be copied to each puppetserver. Older versions of puppetserver need to be explicitly HUP'ed or restarted, but newer versions don't require that: https://puppet.com/docs/puppetserver/latest/crl_refresh.html Can you provide the CRLs from a puppetserver that accepts connections from the client and a CRL from the CA that rejects connections? 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.101226.127929000.68837.1590177600339%40Atlassian.JIRA.
Jira (PUP-10526) pip3 package provider fails manage multiple environments
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10526 pip3 package provider fails manage multiple environments Change By: Josh Cooper 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.359538.1590075231000.68823.1590176700053%40Atlassian.JIRA.
Jira (PUP-10122) Only collect checksum metadata for links pointing to files
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10122 Only collect checksum metadata for links pointing to files Change By: Josh Cooper Epic Link: PUP-10533 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.333946.1573148555000.68816.1590176340051%40Atlassian.JIRA.
Jira (PUP-9390) Static catalogs match multiple environment paths incorrectly
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9390 Static catalogs match multiple environment paths incorrectly Change By: Josh Cooper Epic Link: PUP-10533 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.290064.1546442552000.68810.1590176280151%40Atlassian.JIRA.
Jira (PUP-7051) Static catalog compiler uses Puppet master hostname for %H in fileserver config
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7051 Static catalog compiler uses Puppet master hostname for %H in fileserver config Change By: Josh Cooper Epic Link: PUP-10533 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.168126.1483013694000.68811.1590176280195%40Atlassian.JIRA.
Jira (PUP-10058) Allow static catalogs to inline metadata for deeper modulepaths
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10058 Allow static catalogs to inline metadata for deeper modulepaths Change By: Josh Cooper Epic Link: PUP-10533 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.290273.1546538287000.68809.1590176280106%40Atlassian.JIRA.
Jira (PUP-10533) Static Catalog Metadata
Title: Message Title Josh Cooper created an issue Puppet / PUP-10533 Static Catalog Metadata Issue Type: Epic Assignee: Unassigned Created: 2020/05/22 12:36 PM Priority: Normal Reporter: Josh Cooper Static catalogs are meant to reduce load on the compiler since agents don't need to request file metadata N different times for one catalog. However, there are some issues that cause the compiler to do more work than it should, reducing the overall benefit. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10532) Puppet fetches metadata for files with "ensure => absent"
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10532 Puppet fetches metadata for files with "ensure => absent" Change By: Josh Cooper Epic Link: PUP-10533 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.359734.1590173269000.68806.1590176220203%40Atlassian.JIRA.
Jira (PUP-10533) Static Catalog Metadata Optimizations
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10533 Static Catalog Metadata Optimizations Change By: Josh Cooper Summary: Static Catalog Metadata Optimizations 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.359742.1590176164000.68805.1590176220159%40Atlassian.JIRA.
Jira (PUP-10123) Static catalogs should check whether a directory is inlineable before collecting metadata for its children
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10123 Static catalogs should check whether a directory is inlineable before collecting metadata for its children Change By: Josh Cooper Epic Link: PUP-10533 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.333947.1573149067000.68807.1590176220247%40Atlassian.JIRA.
Jira (PDB-4748) Check pinned deps for 6.11 release
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4748 Check pinned deps for 6.11 release 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.359737.159017369.68748.1590173700376%40Atlassian.JIRA.
Jira (PDB-4748) Check pinned deps for 6.11 release
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4748 Check pinned deps for 6.11 release Issue Type: Task Assignee: Unassigned Created: 2020/05/22 11:54 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
Jira (PUP-10532) Puppet fetches metadata for files with "ensure => absent"
Title: Message Title
Nate McCurdy updated an issue
Puppet / PUP-10532
Puppet fetches metadata for files with "ensure => absent"
Change By:
Nate McCurdy
# h1. Problem *Puppet Version:* 6.15.0*Puppet Server Version:* 6.11.1*OS Name/Version:* CentOS 7Puppet makes a HTTP request for {{/file_metadata/}} for files that are set to "{{ensure => absent}}" and have {{source => 'puppet:///modules/...}}.This defeats the purpose of using static catalogs when your intent is to reduce the amount of file_metadata HTTP traffic. It causes unnecessary traffic and overheard on the Puppet server. # h1. Reproduction Given this Puppet code:{code}node 'agent1.vagrant' { file { '/root/one':ensure => file,owner => 0,group => 0,mode => '0644',source => 'puppet:///modules/test/one', } file { '/root/two':ensure => absent,owner => 0,group => 0,mode => '0644',source => 'puppet:///modules/test/two', }}{code}Running {{puppet agent -t}} from {{agent1.vagrant}} causes these messages in Puppetserver's logs: {noformat}==> /var/log/puppetlabs/puppetserver/puppetserver.log <==2020-05-22T18:44:27.159Z INFO [qtp9036388-38] [puppetserver] Puppet Inlined resource metadata into static catalog for agent1.vagrant in environment production in 0.01 seconds2020-05-22T18:44:27.160Z INFO [qtp9036388-38] [puppetserver] Puppet Compiled static catalog for agent1.vagrant in environment production in 0.12 seconds==> /var/log/puppetlabs/puppetserver/puppetserver-access.log <==10.20.1.6 - - [22/May/2020:18:44:26 +] "GET /puppet/v3/node/agent1.vagrant?environment=production_environment=production_uuid=ee221fd5-13a0-4fdd-9413-1b57a98cd690 HTTP/1.1" 200 12572 "-" "Puppet/6.15.0 Ruby/2.5.8-p224 (x86_64-linux)" 33 - 3010.20.1.6 - - [22/May/2020:18:44:26 +] "GET /puppet/v3/file_metadatas/pluginfacts?recurse=true=.svn=CVS=.git=.hg=follow_type=md5_permissions=use=production HTTP/1.1" 200 240 "-" "Puppet/6.15.0 Ruby/2.5.8-p224 (x86_64-linux)" 17 - 1210.20.1.6 - - [22/May/2020:18:44:26 +] "GET /puppet/v3/file_metadatas/plugins?recurse=true=.svn=CVS=.git=.hg=follow_type=md5_permissions=ignore=production HTTP/1.1" 200 244 "-" "Puppet/6.15.0 Ruby/2.5.8-p224 (x86_64-linux)" 19 - 1410.20.1.6 - - [22/May/2020:18:44:26 +] "GET /puppet/v3/file_metadatas/locales?recurse=true=.svn=CVS=.git=.hg=%2A.pot=config.yaml=follow_type=md5_permissions=ignore=production HTTP/1.1" 200 244 "-" "Puppet/6.15.0 Ruby/2.5.8-p224 (x86_64-linux)" 76 - 7210.20.1.6 - - [22/May/2020:18:44:27 +] "POST /puppet/v3/catalog/agent1.vagrant?environment=production HTTP/1.1" 200 1864 "-" "Puppet/6.15.0 Ruby/2.5.8-p224 (x86_64-linux)" 272 25743 26810.20.1.6 - - [22/May/2020:18:44:27 +] "GET /puppet/v3/file_metadata/modules/test/two?links=manage_type=md5_permissions=ignore=production HTTP/1.1" 200 258 "-" "Puppet/6.15.0 Ruby/2.5.8-p224 (x86_64-linux)" 17 - 1310.20.1.6 - - [22/May/2020:18:44:27 +] "PUT /puppet/v3/report/agent1.vagrant?environment=production HTTP/1.1" 200 9 "-" "Puppet/6.15.0 Ruby/2.5.8-p224
Jira (PUP-10532) Puppet fetches metadata for files with "ensure => absent"
Title: Message Title
Nate McCurdy created an issue
Puppet / PUP-10532
Puppet fetches metadata for files with "ensure => absent"
Issue Type:
Bug
Affects Versions:
PUP 6.15.0, PUP 5.5.14
Assignee:
Unassigned
Created:
2020/05/22 11:47 AM
Priority:
Normal
Reporter:
Nate McCurdy
Problem Puppet Version: 6.15.0 Puppet Server Version: 6.11.1 OS Name/Version: CentOS 7
Puppet makes a HTTP request for /file_metadata/ for files that are set to "ensure => absent" and have source => 'puppet:///modules/ This defeats the purpose of using static catalogs when your intent is to reduce the amount of file_metadata HTTP traffic. It causes unnecessary traffic and overheard on the Puppet server.
Reproduction Given this Puppet code:
node 'agent1.vagrant' {
file { '/root/one':
Jira (PUP-10530) FromDataConverter attempts to access deserialized object when deserializing local references
Title: Message Title
Tom Beech updated an issue
Puppet / PUP-10530
FromDataConverter attempts to access deserialized object when deserializing local references
Change By:
Tom Beech
*Puppet Version:* 6.15.0 *Puppet Server Version:* – *OS Name/Version:* macOS 10.15*Describe your issue in as much detail as possible…*When applying manifest blocks, Bolt uses ToDataConverter to serialize plan variables, which can include Target objects. Bolt sets local_reference:true for ToDataConverter, as Target objects have references to objects that in turn have references to the Target object, causing endless recursion.[https://github.com/puppetlabs/bolt/blob/master/lib/bolt/applicator.rb#L182-L186] Later in execution, the serialized data is passed to FromDataConverter, which begins to deserialize the plan variables, including the Target objects.[https://github.com/puppetlabs/bolt/blob/master/lib/bolt/catalog.rb#L75] During deserialization, any targets that share identical config and are set as plan variables will cause Puppet to raise an error due to an attempt to access a deserialized Target object's config via the bracket [] operator. For example, given the following inventory where targets share identical configuration: {code:java}targets: - name: targetAconfig: ssh:run-as: roothost-key-check: falsetty: true - name: targetBconfig: ssh:run-as: roothost-key-check: falsetty: true{code} ToDataConverter will serialize these targets such that target B will have a local reference to target A's configuration: {code:java}..."targetA"=> [{"__ptype"=>"Target", "name"=>"targetA", "config"=> { "transport"=>"ssh", "ssh"=> { "run-as" => "root", "host-key-check" => false, "tty" => true } } }],"targetB"=> [{"__ptype"=>"Target", "name"=>"targetB", "config"=>{ "transport"=>"ssh", "ssh"=>{"__ptype"=>"LocalRef","__pvalue"=>"$['targetA'][0]['config']['ssh']" }} }],...{code} However, during deserialization, the data hash for targetA will be replaced with the deserialized Bolt::ApplyTarget object. When targetB is deserialized, the local reference for the configuration will then be resolved such that $['targetA'][0] returns the Bolt::ApplyTarget object, and then attempts to access the configuration with ['config']['ssh']. This raises an exception, as the Bolt::ApplyTarget object does not define the [] method. *Describe steps to reproduce…*Create an inventory with multiple targets that share identical configuration: {code:java}# Boltdir/inventory.yamltargets:- uri: name: targetAconfig: transport: ssh ssh:host-key-check: falseconnect-timeout: 100 - uri: name: targetBconfig: transport: ssh ssh:host-key-check: falseconnect-timeout: 100{code} Create a plan that sets these targets as plan variables and then has an apply block:{code:java}plan bolt ( TargetSpec $targets) { $targetA = get_targets('targetA')
Jira (PUP-10306) Environments should track their version
Title: Message Title Nick Walker updated an issue Puppet / PUP-10306 Environments should track their version Change By: Nick Walker Epic Link: PE CODEMGMT - 26632 1270 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.347141.1582240386000.68596.1590170520027%40Atlassian.JIRA.
Jira (PUP-10266) Environment cache should store previous versions of environments
Title: Message Title Nick Walker updated an issue Puppet / PUP-10266 Environment cache should store previous versions of environments Change By: Nick Walker Epic Link: PE CODEMGMT - 26632 1270 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.344927.1580776369000.68595.1590170460250%40Atlassian.JIRA.
Jira (PUP-10312) The agent should ensure it uses the same version of its environment thoughout a run
Title: Message Title Nick Walker updated an issue Puppet / PUP-10312 The agent should ensure it uses the same version of its environment thoughout a run Change By: Nick Walker Epic Link: PE CODEMGMT - 26632 1270 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.347421.1582585759000.68588.1590170280185%40Atlassian.JIRA.
Jira (PUP-10530) FromDataConverter attempts to access deserialized object when deserializing local references
Title: Message Title
Tom Beech updated an issue
Puppet / PUP-10530
FromDataConverter attempts to access deserialized object when deserializing local references
Change By:
Tom Beech
*Puppet Version:* 6.15.0 *Puppet Server Version:* -- – *OS Name/Version:* macOS 10.15*Describe your issue in as much detail as possible…*When applying manifest blocks, Bolt uses ToDataConverter to serialize plan variables, which can include Target objects. Bolt sets local_reference:true for ToDataConverter, as Target objects have references to objects that in turn have references to the Target object, causing endless recursion.[https://github.com/puppetlabs/bolt/blob/master/lib/bolt/applicator.rb#L182-L186] Later in execution, the serialized data is passed to FromDataConverter, which begins to deserialize the plan variables, including the Target objects.[https://github.com/puppetlabs/bolt/blob/master/lib/bolt/catalog.rb#L75] During deserialization, any targets that share identical config and are set as plan variables will cause Puppet to raise an error due to an attempt to access a deserialized Target object's config via the bracket [] operator. For example, given the following inventory where targets share identical configuration: {code:java} targets: - name: targetAconfig: ssh:run-as: roothost-key-check: falsetty: true - name: targetBconfig: ssh:run-as: roothost-key-check: falsetty: true{code} ToDataConverter will serialize these targets such that target B will have a local reference to target A's configuration: {code:java} ..."targetA"=> [{"__ptype"=>"Target", "name"=>"targetA", "config"=> { "transport"=>"ssh", "ssh"=> { "run-as" => "root", "host-key-check" => false, "tty" => true } } }],"targetB"=> [{"__ptype"=>"Target", "name"=>"targetB", "config"=>{ "transport"=>"ssh", "ssh"=>{"__ptype"=>"LocalRef","__pvalue"=>"$['targetA'][0]['config']['ssh']" }} }],...{code} However, during deserialization, the data hash for targetA will be replaced with the deserialized Bolt::ApplyTarget object. When targetB is deserialized, the local reference for the configuration will then be resolved such that $['targetA'][0] returns the Bolt::ApplyTarget object, and then attempts to access the configuration with ['config']['ssh']. This raises an exception, as the Bolt::ApplyTarget object does not define the [] method. *Describe steps to reproduce…* ** Create an inventory with multiple targets that share identical configuration: {code:java} # Boltdir/inventory.yamltargets:- uri: name: targetAconfig: transport: ssh ssh:host-key-check: falseconnect-timeout: 100 - uri: name: targetBconfig: transport: ssh ssh:host-key-check: falseconnect-timeout: 100{code} Create a plan that sets these targets as plan variables and then has an apply block:{code:java} plan bolt ( TargetSpec $targets) {
Jira (PUP-8014) Create an environment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Nick Walker updated an issue Puppet / PUP-8014 Create an environment_ttl setting to clear short-lived puppet environments from memory Change By: Nick Walker Labels: ondeck1 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.214193.1506980344000.68553.1590169260085%40Atlassian.JIRA.
Jira (PUP-10531) Document report metrics
Title: Message Title Josh Cooper commented on PUP-10531 Re: Document report metrics Claire Cadman I filed this as a PUP ticket since there will be puppet code changes and also we need to research/document how the metrics nest. 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.359728.1590168995000.68545.1590169080124%40Atlassian.JIRA.
Jira (PUP-10530) FromDataConverter attempts to access deserialized object when deserializing local references
Title: Message Title Tom Beech created an issue Puppet / PUP-10530 FromDataConverter attempts to access deserialized object when deserializing local references Issue Type: Bug Assignee: Unassigned Attachments: repo.json Created: 2020/05/22 10:36 AM Priority: Normal Reporter: Tom Beech Puppet Version: 6.15.0 Puppet Server Version: – OS Name/Version: macOS 10.15 Describe your issue in as much detail as possible… When applying manifest blocks, Bolt uses ToDataConverter to serialize plan variables, which can include Target objects. Bolt sets local_reference:true for ToDataConverter, as Target objects have references to objects that in turn have references to the Target object, causing endless recursion. https://github.com/puppetlabs/bolt/blob/master/lib/bolt/applicator.rb#L182-L186 Later in execution, the serialized data is passed to FromDataConverter, which begins to deserialize the plan variables, including the Target objects. https://github.com/puppetlabs/bolt/blob/master/lib/bolt/catalog.rb#L75 During deserialization, any targets that share identical config and are set as plan variables will cause Puppet to raise an error due to an attempt to access a deserialized Target object's config via the bracket [] operator. For example, given the following inventory where targets share identical configuration: targets: - name: targetA
Jira (PUP-10531) Document report metrics
Title: Message Title Josh Cooper created an issue Puppet / PUP-10531 Document report metrics Issue Type: Task Assignee: Unassigned Components: Docs Created: 2020/05/22 10:36 AM Priority: Normal Reporter: Josh Cooper The agent calculates 3 types of metrics and submits them in the report. One of types is "Time" and it captures how long different parts of the agent run take, for example, how long pluginsync took, how long each resource type took to apply, etc. This can be seen using puppet agent -t --summarize: Time: Schedule: 0.00 Notify: 0.00 File: 0.01 Config retrieval: 0.32
Jira (PDB-4635) puppetdb_avg_mem larger than baseline values
Title: Message Title John Duarte commented on PDB-4635 Re: puppetdb_avg_mem larger than baseline values For the performance comparison run of week 2020-05-18, this tolerance failed when testing recent PE master build (2019.8.0-rc1-17-gf233795) to the LTS baseline (but not STS). 2019.8.0-rc1-17-gf233795 2018.1.15 comparison: Result 'process_puppetdb_avg_mem' is outside tolerances: baseline: 720443; result: 863682; variance: 19.88% 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.343321.1579814655000.68489.1590167040026%40Atlassian.JIRA.
Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch
Title: Message Title Josh Cooper commented on PUP-9570 Re: Catalog failure on first run due to pluginsync and environment switch The configurer changes landed, I should be able to get this done for 6.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.300842.1553021716000.68365.1590160560038%40Atlassian.JIRA.
Jira (PUP-10527) Add beaker test to ensure puppet-agent service executes in the background
Title: Message Title Josh Cooper commented on PUP-10527 Re: Add beaker test to ensure puppet-agent service executes in the background That should have caught the issue which makes me wonder why it didn’t? Does the test not run nightly? I also agree that it’d be better to test this in PA pipeline. 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.359553.159008498.68364.1590159960028%40Atlassian.JIRA.
Jira (PUP-10524) Puppet tests fail with facter 4
Title: Message Title Bogdan Irimie commented on PUP-10524 Re: Puppet tests fail with facter 4 Josh Cooper Melissa Stone we just released Facter [4.0.23|https://rubygems.org/gems/facter/versions/4.0.23] today and with the fixes from https://github.com/puppetlabs/puppet/pull/8165 puppet tests should pass. 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.359341.1589935505000.68343.1590151680029%40Atlassian.JIRA.
Jira (FACT-2633) Relax rubocop dependancy and fix new cops offenses
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2633 Relax rubocop dependancy and fix new cops offenses 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.359677.1590144536000.68305.1590144600075%40Atlassian.JIRA.
Jira (FACT-2633) Relax rubocop dependancy and fix new cops offenses
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2633 Relax rubocop dependancy and fix new cops offenses Issue Type: Task Assignee: Unassigned Created: 2020/05/22 3:48 AM Priority: Normal Reporter: 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
Jira (PDB-4746) Docs: man command error on PuppetDB CLI page
Title: Message Title Claire Cadman updated an issue PuppetDB / PDB-4746 Docs: man command error on PuppetDB CLI page Change By: Claire Cadman Labels: feedback-form-docs-site 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 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.359653.1590134909000.68300.1590144180028%40Atlassian.JIRA.
Jira (PDB-4747) Docs: Broken link in Install from packages
Title: Message Title Claire Cadman created an issue PuppetDB / PDB-4747 Docs: Broken link in Install from packages Issue Type: Bug Assignee: Unassigned Created: 2020/05/22 3:41 AM Labels: puppetdb feedback-form-docs-site Priority: Normal Reporter: Claire Cadman I'd have made a PR for this fix but I'm not sure what the link should be? Url: https://puppet.com/docs/puppetdb/latest/install_from_packages.html Comment: Step 2 lead to an broken link Add Comment This message was sent by Atlassian Jira
Jira (PDB-4746) Docs: man command error on PuppetDB CLI page
Title: Message Title Claire Cadman created an issue PuppetDB / PDB-4746 Docs: man command error on PuppetDB CLI page Issue Type: Bug Assignee: Unassigned Created: 2020/05/22 1:08 AM Priority: Normal Reporter: Claire Cadman Puppet Version: 5.5 PuppetDB Version: 5.2 We had the following feedback on the PuppetDB CLI docs page. I'm not sure if it's actionable, but I'll let you decide. Url: https://puppet.com/docs/puppetdb/5.2/pdb_client_tools.html Comment: Im not even sure where to find the configuration file in pe-tools. i have prob implemented it somewhere, but this is a complex toolset, so a reminder of the path would help, and whats the relation to pe-tools, that would help. "man" isnt working, i did add to path and exited relogged in. Its not clear if you have to do this on the puppet master, but i do see mention of that. I tried to gem install, but on the puppet controller i got ```ERROR: Error installing puppetdb_cli: cri requires Ruby version ~> 2.3. ``` i did see https://tickets.puppetlabs.com/browse/SERVER-1544. for help on that. I also got an Exception when trying to check `$ puppetserver gem -v` ``Exception in thread "main" java.io.FileNotFoundException: Configuration path '/etc/puppetlabs/puppetserver/conf.d' must exist and must be readable.``` I ended logging into the puppet master, and wasnt able to install it as user, had to install it as root. Thats not mentioned here. Still, i cant seem to scrape enough info form this document to get a single query working yet. Email: bl...@vtmgroup.com
Jira (FACT-2632) Log error when we cannot load custom fact from file
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2632
Log error when we cannot load custom fact from file
Change By:
Bogdan Irimie
Facter 4 is failing when there is an exception in the file with a custom fact. The failure should be outside `Facter.add(...)`Custom fact example:{code}# frozen_string_literal: truenil.sizeFacter.add(:my_custom_fact) do has_weight(10_000) setcode do'my_custom_fact' endend{code} Facter 3 on the other hand, logs an error message for the files with exceptions, but still resolves all other facts. We should implement the same behaviour in Facter 4. The error message should be{code}ERROR Facter - error while resolving custom facts in /my_custom_fact.rb undefined method `size' for nil:NilClass {code}
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
Jira (FACT-2632) Log error when we cannot load custom fact from file
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2632
Log error when we cannot load custom fact from file
Change By:
Bogdan Irimie
Facter 4 is failing when there is an exception in the file with a custom fact. The failure should be outside `Facter.add(...)`Custom fact example:{code}# frozen_string_literal: truenil.sizeFacter.add(:my_custom_fact) do has_weight(10_000) setcode do'my_custom_fact' endend{code}Facter 3 on the other hand, logs an error message for the files with exceptions , but still resolves all the other facts that is able to . We should implement the same behaviour in Facter 4.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit
Jira (FACT-2632) Log error when we cannot load custom fact from file
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2632
Log error when we cannot load custom fact from file
Change By:
Bogdan Irimie
Facter 4 is failing when there is an exception in the file with a custom fact. The failure should be outside `Facter.add(...)`Custom fact example:{code}# frozen_string_literal: truenil.sizeFacter.add(:my_custom_fact) do has_weight(10_000) setcode do'my_custom_fact' endend{code}Facter 3 on the other hand, logs an error message, but still resolves all the facts that is able to. We should implement the same behaviour in Facter 4.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit
Jira (FACT-2631) Trace is not working as expected
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2631 Trace is not working as expected Change By: Bogdan Irimie Log level was set incorrectly to `trace` when calling the `trace` API method. The `trace` API method should enable backtrace. 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.359512.1590061804000.68205.1590130080291%40Atlassian.JIRA.
Jira (FACT-2631) Trace is not working as expected
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2631
Trace is not working as expected
Change By:
Bogdan Irimie
*Puppet Version:* *Puppet Server Version:* *OS Name/Version:*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:**Actual Behavior:*Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.Examples: Run puppet agent with --test --trace --debugRelevant sections of {{/var/log/puppetlabs/puppetserver/puppetserver.log}} or any applicable logs from the same directory.For more detailed information turn up the server logs by upping the log level in the server's logback.xmlRelevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig)For memory issues with server heap dumps are also helpful.
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
