Jira (FACT-2751) Facter reports wrong Windows build
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2751 Facter reports wrong Windows build Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-09-01 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.369870.1597934847000.20973.1597989120036%40Atlassian.JIRA.
Jira (PUP-8014) Create an environment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Josh Cooper commented on PUP-8014 Re: Create an environment_ttl setting to clear short-lived puppet environments from memory I think the easiest approach would be to define an environment_ttl setting in puppet and a new type of cache entry (https://github.com/puppetlabs/puppet/blob/ec8bcbd5287ccdd67ff06618bb2d0d568a3f2328/lib/puppet/environments.rb#L437-L447) that keeps track of when the environment was last accessed. In order to eagerly evict environments, we could use Concurrent::TimerTask to evict expired environments. We'd also need to remove the environment_timeout setting at the same time. I think it would be difficult to implement this in puppetserver, because we still need to support the "never cache" vs "cache if unused after" use cases, where "never cache" would still be the default. 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.20950.1597971420024%40Atlassian.JIRA.
Jira (PUP-10446) Remove application orchestration language features
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10446 Remove application orchestration language features 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.356722.1587765694000.20943.1597970820029%40Atlassian.JIRA.
Jira (PUP-10446) Remove application orchestration language features
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10446 Remove application orchestration language features Change By: Josh Cooper Assignee: Josh Cooper 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.20942.1597970760084%40Atlassian.JIRA.
Jira (PUP-10509) Drop support for ruby < 2.5
Title: Message Title
Josh Cooper commented on PUP-10509
Re: Drop support for ruby < 2.5
I think all of these monkey patches can be deleted: https://github.com/puppetlabs/puppet/blob/main/lib/puppet/util/monkey_patches.rb#L85-L150 There's also some conditional spec logic in:
spec/unit/functions/camelcase_spec.rb: it 'performs capitalize of international UTF-8 characters', :if => RUBY_VERSION >= "2.4" do
spec/unit/functions/capitalize_spec.rb: it 'performs capitalize of international UTF-8 characters', :if => RUBY_VERSION >= "2.4" do
spec/unit/functions/downcase_spec.rb: it 'performs capitalize of international UTF-8 characters', :if => RUBY_VERSION >= "2.4" do
spec/unit/functions/upcase_spec.rb: it 'performs capitalize of international UTF-8 characters', :if => RUBY_VERSION >= "2.4" do
spec/unit/http/factory_spec.rb: it "disables ruby's max retry on 2.5 and up", if: RUBY_VERSION.to_f >= 2.5 do
spec/unit/util/run_mode_spec.rb:@gte_ruby_2_4 ||= SemanticPuppet::Version.parse(RUBY_VERSION) >= SemanticPuppet::Version.parse('2.4.0')
spec/unit/util_spec.rb:@gte_ruby_2_4 ||= SemanticPuppet::Version.parse(RUBY_VERSION) >= SemanticPuppet::Version.parse('2.4.0')
Jira (PUP-10509) Drop support for ruby < 2.5
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10509 Drop support for ruby < 2.5 Change By: Josh Cooper Team: Coremunity 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.358867.1589476926000.20939.1597970100143%40Atlassian.JIRA.
Jira (PUP-9426) Remove future_features logic
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9426 Remove future_features logic Change By: Josh Cooper Assignee: Josh Cooper 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.291460.1547160478000.20937.1597970100054%40Atlassian.JIRA.
Jira (PUP-9426) Remove future_features logic
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9426 Remove future_features logic 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.291460.1547160478000.20938.1597970100099%40Atlassian.JIRA.
Jira (PDB-4847) DOCS: Incorrect command in connect_puppet_master
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4847 DOCS: Incorrect command in connect_puppet_master Change By: Austin Blatt Epic Link: PDB-4759 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.367967.1596387686000.20773.1597961280322%40Atlassian.JIRA.
Jira (PDB-4700) Support all the normal report operations for plan generated reports
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4700 Support all the normal report operations for plan generated reports Change By: Rob Browning Epic Status: To Do Done 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.356884.158800944.20723.1597959840027%40Atlassian.JIRA.
Jira (PDB-4602) Guard PuppetDB migrations against simultaneous writers
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4602 Guard PuppetDB migrations against simultaneous writers Change By: Rob Browning Epic Status: To Do Done 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.339273.1576193168000.20721.1597959780039%40Atlassian.JIRA.
Jira (PDB-4659) Create acceptance tests that simulate PDB command broadcast
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4659 Create acceptance tests that simulate PDB command broadcast Change By: Zachary Kent 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.347259.1582314337000.20722.1597959780095%40Atlassian.JIRA.
Jira (PDB-4863) Address pdb tech debt
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4863 Address pdb tech debt Issue Type: Epic Assignee: Unassigned Created: 2020/08/20 2:39 PM 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-10386) Remove status application
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10386 Remove status application Change By: Josh Cooper Team: Coremunity 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.350960.1585070005000.20629.1597954020024%40Atlassian.JIRA.
Jira (PUP-10475) Remove Puppet::Util::Yaml.load_file
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10475 Remove Puppet::Util::Yaml.load_file Change By: Josh Cooper Team: Coremunity 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.356948.1588032733000.20628.1597953960166%40Atlassian.JIRA.
Jira (PUP-10598) Change default value of ignore_plugin_errors to false
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10598 Change default value of ignore_plugin_errors to false Change By: Josh Cooper Summary: Remove setting Change default value of ignore_plugin_errors to ignore pluginsync errors false 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.366911.1595431337000.20623.1597953900055%40Atlassian.JIRA.
Jira (PUP-10598) Change default value of ignore_plugin_errors to false
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10598 Change default value of ignore_plugin_errors to false Change By: Josh Cooper PUP-1763 added a setting to allow the agent to stop the run if pluginsync fails. In puppet 7, the setting should be removed changed so the agent should always fail the run if pluginsync fails. 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.366911.1595431337000.20624.1597953900099%40Atlassian.JIRA.
Jira (PUP-10598) Remove setting to ignore pluginsync errors
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10598 Remove setting to ignore pluginsync errors Change By: Josh Cooper Team: Coremunity 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.366911.1595431337000.20621.1597953780085%40Atlassian.JIRA.
Jira (PUP-10610) Change disable_i18n to true by default
Title: Message Title Josh Cooper commented on PUP-10610 Re: Change disable_i18n to true by default Changing the name of the setting creates upgrade issues. If you've set `disable_i18n=false` explicitly, and then upgrade to 7, then puppet won't recognize the old setting, and the behavior of "I really want i18n to be enabled" will be lost. 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.368587.1596752428000.20610.1597952160026%40Atlassian.JIRA.
Jira (PUP-10628) Performance regression with large hashes using lookup
Title: Message Title Henrik Lindberg commented on PUP-10628 Re: Performance regression with large hashes using lookup An optimization that was done in other places were that instead of inferring the type of the value and then matching the inferred against the desired you ask if it is an instance of the desired type - not sure if there is something like that going on here, or if also asking if it is an instance requires a deep recursion. 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.369684.1597848926000.20605.1597951620156%40Atlassian.JIRA.
Jira (PUP-10628) Performance regression with large hashes using lookup
Title: Message Title Henrik Lindberg commented on PUP-10628 Re: Performance regression with large hashes using lookup RichData as a format allows for types to be embedded in the serialization of data - that way, a serialization can be self describing. In serialization it is optional to use this, or to simply include types as reference via their name (i.e. "hoping" that the other side has the same definition of the type). Early on in the implementation of rich-data support in the catalog we did include the serialized types - but this proved to be too bulky. There is currently no other data type (alias) defined for RichData without the Type and Type set types, but one could be created. Don't see it is of much practical use to support Type/TypeSet in hiera data, you would get the same if types were returned as strings and then turned into types dynamically - rather than a hiera backend returning an instance of Type/TypeSet. Not sure if dropping them from RichData would cause problems - probably not that difficult to test. Speeding up the inference is still of value - there may be some obvious things that can be done to make it faster to discriminate if a hash could possibly represent a type or typeset. 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-10628) Performance regression with large hashes using lookup
Title: Message Title Josh Cooper commented on PUP-10628 Re: Performance regression with large hashes using lookup Excluding TypeSet from the list of possible data provider values types is about 300x faster: diff --git a/lib/puppet/pops/loader/static_loader.rb b/lib/puppet/pops/loader/static_loader.rb index 3e6b78ce4c..8faca4e84f 100644 --- a/lib/puppet/pops/loader/static_loader.rb +++ b/lib/puppet/pops/loader/static_loader.rb @@ -29,6 +29,7 @@ class StaticLoader < Loader 'Data' => 'Variant[ScalarData,Undef,Hash[String,Data],Array[Data]]', 'RichDataKey' => 'Variant[String,Numeric]', 'RichData' => 'Variant[Scalar,SemVerRange,Binary,Sensitive,Type,TypeSet,URI,Object,Undef,Default,Hash[RichDataKey,RichData],Array[RichData]]', +'LookupDataValue' => 'Variant[Scalar,SemVerRange,Binary,Sensitive,Type,URI,Object,Undef,Default,Hash[RichDataKey,LookupDataValue],Array[LookupDataValue]]', # Backward compatible aliases. 'Puppet::LookupKey' => 'RichDataKey',
Jira (PUP-10628) Performance regression with large hashes using lookup
Title: Message Title
Josh Cooper commented on PUP-10628
Re: Performance regression with large hashes using lookup
This can be reproduced using:
require 'puppet'
require 'puppet/pops'
Puppet.initialize_settings
Puppet::Util::Log.newdestination(:console)
values = 0.upto(2000).inject({}) do |memo, i|
memo["key#{i}"] = "value#{i}"
memo
end
hash = { 'hash2' => { 'hash3' => values } }
Puppet::Util.benchmark(:notice, "Inferred hash is an instance of #{Puppet::Pops::Lookup::DataProvider.value_type.name} in %{seconds}") do
Jira (PDB-4850) Attempt to improve automation of the perf A/B testing process
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4850 Attempt to improve automation of the perf A/B testing process 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.368976.1597254958000.20555.1597948620083%40Atlassian.JIRA.
Jira (PDB-4833) Check/add support for Ubuntu 20.04
Title: Message Title Rob Browning assigned an issue to Austin Blatt PuppetDB / PDB-4833 Check/add support for Ubuntu 20.04 Change By: Rob Browning Assignee: Austin Blatt 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.367700.1596042828000.20526.1597948020172%40Atlassian.JIRA.
Jira (PUP-10598) Remove setting to ignore pluginsync errors
Title: Message Title Josh Cooper commented on PUP-10598 Re: Remove setting to ignore pluginsync errors We might want to keep the setting, but change the default to false? 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.366911.1595431337000.20490.1597947120035%40Atlassian.JIRA.
Jira (PUP-10617) Request to status endpoint not using extra_headers setting
Title: Message Title Josh Cooper commented on PUP-10617 Re: Request to status endpoint not using extra_headers setting The compiler service should expose a method for querying the simple status endpoint, and the server_list resolver should call that instead of making a "raw" HTTPS request. 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.368953.1597240842000.20477.1597946940022%40Atlassian.JIRA.
Jira (PUP-10603) File Resource HTTP GET - Misuse of URL encoding
Title: Message Title Josh Cooper commented on PUP-10603 Re: File Resource HTTP GET - Misuse of URL encoding Passed CI in 3443d72083 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.367500.1595969611000.20474.1597946820415%40Atlassian.JIRA.
Jira (PUP-10600) Allow running puppet commands via AWS Session Manager on Windows Server 2019
Title: Message Title Josh Cooper commented on PUP-10600 Re: Allow running puppet commands via AWS Session Manager on Windows Server 2019 Yep, it's resolved in 6.18.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.367242.1595613997000.20458.1597946520031%40Atlassian.JIRA.
Jira (PUP-10586) Regression: Puppet::Util.default_env method removed in 5.5.21 and 6.17.0
Title: Message Title Josh Cooper commented on PUP-10586 Re: Regression: Puppet::Util.default_env method removed in 5.5.21 and 6.17.0 Yep both 5.5.22 and 6.18.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.366100.1594833328000.20457.1597946460221%40Atlassian.JIRA.
Jira (PUP-10639) renew cached Puppet CA on Puppet client
Title: Message Title Josh Cooper commented on PUP-10639 Re: renew cached Puppet CA on Puppet client Updating the local CA file when the file doesn't exist yet (new agent) is a weak link in puppet's security model, because it's the only time that puppet agents don't authenticate the server (VERIFY_NONE). To avoid MTIM attacks, puppet has a ca_fingerprint command line argument which can be used to verify the contents of the CA file over an untrusted channel. The argument accepts the SHA256 digest of the CA file, which can be computed on the CA server as: # openssl dgst -sha256 -r /etc/puppetlabs/puppet/ssl/certs/ca.pem | cut -f1 -d' ' 6e09bc3e6778d6b497d233a49f9906b95adc212468d9d3e260398f093badaf03 Then on the agent, pass the CA fingerprint when bootstrapping the agent (or running puppet agent -t. Puppet will reject the file if the digests don't match: # puppet ssl bootstrap --ca_fingerprint Error: CA bundle with digest (SHA256) 6E:09:BC:3E:67:78:D6:B4:97:D2:33:A4:9F:99:06:B9:5A:DC:21:24:68:D9:D3:E2:60:39:8F:09:3B:AD:AF:03 did not match expected digest FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF So if we allow agents to refresh an expired CA certificate, then we have two problems: 1. If ca_fingerprint is not set (the default), then it expands the window of opportunity when an agent could be vulnerable to MITM. 2. If ca_fingerprint is set, then won't match the new CA file. The first issue could be handled by ignoring the expiration date of the CA certificate for the TLS connection that downloads the new CA certificate. All other errors (like bad signature would continue to fail the connection). This could be done by passing a custom Puppet::SSL::Verifier. The second issue could be handled by only applying the ca_fingerprint to the very first CA file download. Once we have a trust anchor, then we can use that CA to download the next once (ignoring the expiration date issue above), preserving the chain of trust.
Jira (PUP-10626) puppet node deactivate and external CA - cert revocation can't be disabled
Title: Message Title Josh Cooper commented on PUP-10626 Re: puppet node deactivate and external CA - cert revocation can't be disabled Steve Traylen could you run with --trace and include the backtrace? Also can you include the puppet.conf on the node where you're running puppet node? I'm guessing this is related to http client changes in puppet, but the deactivate action comes from the puppetdb repo, so it could be a combination of things. /cc Austin Blatt 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.369661.1597828121000.20375.1597943940088%40Atlassian.JIRA.
Jira (PDB-4788) Enable ubuntu-20.04-amd64 test pipeline for puppetdb
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4788 Enable ubuntu-20.04-amd64 test pipeline for puppetdb Change By: Austin Blatt Assignee: Austin Blatt 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.364327.1593451099000.20362.1597943700088%40Atlassian.JIRA.
Jira (PUP-10585) Puppet::Util::Yaml safe_load not loading "Time" class which leads to compilation error for time serial data
Title: Message Title Josh Cooper commented on PUP-10585 Re: Puppet::Util::Yaml safe_load not loading "Time" class which leads to compilation error for time serial data Thanks Vadym Chepkov, could you file a new ticket and run the agent with --trace? 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.366012.1594784795000.20357.1597943580095%40Atlassian.JIRA.
Jira (PDB-4787) Enable ubuntu-20.04-amd64 builds for puppetdb
Title: Message Title Austin Blatt commented on PDB-4787 Re: Enable ubuntu-20.04-amd64 builds for puppetdb Simon Lauger We've started building PuppetDB packages for focal, so it'll be available in the next release. 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.364326.1593451097000.20358.1597943580139%40Atlassian.JIRA.
Jira (PDB-4787) Enable ubuntu-20.04-amd64 builds for puppetdb
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4787 Enable ubuntu-20.04-amd64 builds for puppetdb Change By: Austin Blatt Assignee: Austin Blatt 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.364326.1593451097000.20356.1597943580051%40Atlassian.JIRA.
Jira (PDB-4855) Dashboard doesn't load due to error response from /pdb/dashboard/data
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4855 Dashboard doesn't load due to error response from /pdb/dashboard/data Change By: Austin Blatt Release Notes: Bug Fix Release Notes Summary: Fixed an issue with the catalog duplication percent metric. This resulted in an error that prevented the dashboard from loading. 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.369694.1597852778000.20349.1597943280026%40Atlassian.JIRA.
Jira (PDB-4855) Dashboard doesn't load due to error response from /pdb/dashboard/data
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4855 Dashboard doesn't load due to error response from /pdb/dashboard/data Change By: Austin Blatt Fix Version/s: PDB 6.12.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.369694.1597852778000.20348.1597943100107%40Atlassian.JIRA.
Jira (PDB-4855) Dashboard doesn't load due to error response from /pdb/dashboard/data
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4855 Dashboard doesn't load due to error response from /pdb/dashboard/data Change By: Austin Blatt Summary: Dashboard doesn't load due to error response from /pdb/dashboard/data : java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number 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.369694.1597852778000.20347.1597943100063%40Atlassian.JIRA.
Jira (PUP-10585) Puppet::Util::Yaml safe_load not loading "Time" class which leads to compilation error for time serial data
Title: Message Title
Vadym Chepkov commented on PUP-10585
Re: Puppet::Util::Yaml safe_load not loading "Time" class which leads to compilation error for time serial data
Josh Cooper, not sure if I need to open another ticket, but seems some edge cases still exists for audit metaparameter, For instance, on Windows platform, this code also produces one-time errors
file { $pkg_source:
audit => 'owner',
}
err:[/Stage[main]/Splunk::Install/File[E:/Apps/staging/splunk/splunkforwarder-7.3.7-9d9aa3f78593-x64-release.msi]]: Could not evaluate: undefined method `+' for :absent:Symbol
Add Comment
Jira (FACT-2645) Remove Facter for JRuby on ubuntu-16.04-amd64
Title: Message Title Maggie Dreyer commented on FACT-2645 Re: Remove Facter for JRuby on ubuntu-16.04-amd64 Yes, we were not planning to remove those platforms immediately. Is it problematic to keep this around? 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.360412.1590701406000.20239.1597938900024%40Atlassian.JIRA.
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10627 write public information to puppet_dir/public Change By: Luchian Nemes [TODO]Add description Puppet needs a new folder called `public` which should be accessible by everyone (public user class) and have the public puppet files such as reports (without sensitive data in them) stored there. Default location proposed is `/opt/puppetlabs/puppet/public` on Linux and `C:\ProgramData\PuppetLabs\puppet\public` on Microsoft Windows. Both the folder and containing files should have `0755` (rwxr-xr-x) permissions set. Installation/upgrade of puppet-agent should ensure the existence of this folder.Custom path for this folder should be possible through custom settings in `puppet.conf` or using the `puppet config set publicdir ` cli command. Current implementation should only include the `last_run_summary.yaml` file in said folder (which is currently located in `/opt/puppetlabs/puppet/cache/state` on Linux and `C:\ProgramData\PuppetLabs\puppet\cache\state` on Microsoft Windows).Changes needed in Puppet Agent (regarding the new cli parameter setting and folder packaging) should be covered in PA-3253. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2751) Facter reports wrong Windows build
Title: Message Title Mihai Buzgau created an issue Facter / FACT-2751 Facter reports wrong Windows build Issue Type: Bug Assignee: Unassigned Created: 2020/08/20 7:47 AM Priority: Normal Reporter: Mihai Buzgau Facter 3 load ntoskrnl.exe and calls RtlGetVersion to get the build number. It seems like build 1909 of Windows has a bug that retrieves 18362 instead of 18363 as the build number. Loading Ntdll.dll exposes the same method as ntoskrnl.exe and it seems to return the correct build number. We need to update Facter 3 to use Ntdll.dll instead of ntoskrnl.exe Ref: https://docs.microsoft.com/en-us/windows/win32/devnotes/rtlgetversion Add Comment This message was sent by Atlassian Jira
Jira (FACT-2642) fact value for aggregates is printed twice on facter 3 and once on facter 4
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2642 fact value for aggregates is printed twice on facter 3 and once on facter 4 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.360286.1590664261000.20124.1597933020028%40Atlassian.JIRA.
Jira (PUP-10639) renew cached Puppet CA on Puppet client
Title: Message Title Andreas Paul updated an issue Puppet / PUP-10639 renew cached Puppet CA on Puppet client Change By: Andreas Paul *Puppet Version:* all *Puppet Server Version:* irrelevant *OS Name/Version:* irrelevantCurrently the Puppet agent/client does cache the Puppet CA file it first received forever. When this CA expires and get renewed on the configured `ca_server` or Puppetserver the cache still does not get updated with the new CA. #puppet slack channel discussion: [https://puppetcommunity.slack.com/messages/C0W298S9G/p1597402361432800] *Desired Behavior:* * add sane defaults that would recheck if the cached local CA does differ from the one used by the configured `ca_server` (e.g. 1 week or 2 weeks before CA expiration date) * add Puppet client config settings to specify intervals for this CA check * if the local cached CA file is expired check if the configured `ca_server` uses a different one and replace the local cached CA file*Actual Behavior:*Currently the client does use the cached CA file forever even when the CA file has expired or the used CA file of the configured `ca_server` or Puppetserver was renewed.This results in completely failed Puppet runs, which will never recover without external/manual intervention (removing the expired locally cached CA file) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10640) Move Puppet PR testing to Github Actions
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10640 Move Puppet PR testing to Github Actions Issue Type: Task Assignee: Unassigned Created: 2020/08/20 5:00 AM Priority: Normal Reporter: Mihai Buzgau On Puppet we currently use Travis for Linux unit testing and appvayor for Windows unit testing. Having two different providers is causing additional maintainability cost. Also as noted in this PR: https://github.com/puppetlabs/puppet/pull/8282 updating some of their dependencies causes the tests to take longer. We've implemented github actions on facter and they seem to provide a stable, multi-OS platform and performant platform for running unit tests. We should update the Puppet PR testing to Github Actions. Add Comment
Jira (PUP-10639) renew cached Puppet CA on Puppet client
Title: Message Title Andreas Paul updated an issue Puppet / PUP-10639 renew cached Puppet CA on Puppet client Change By: Andreas Paul *Puppet Version:* all *Puppet Server Version:* irrelevant *OS Name/Version:* irrelevantCurrently the Puppet agent/client does cache the Puppet CA file it first received forever. When this CA expires and get renewed on the configured `ca_server` or Puppetserver the cache still does not get updated with the new CA.*Desired Behavior:* * add sane defaults that would recheck if the cached local CA does differ from the one used by the configured `ca_server` (e.g. 1 week or 2 weeks before CA expiration date) * add Puppet client config settings to specify intervals for this CA check * if the local cached CA file is expired check if the configured `ca_server` uses a different one and replace the local cached CA file*Actual Behavior:*Currently the client does use the cached CA file forever even when the CA file has expired or the used CA file of the configured `ca_server` or Puppetserver was renewed.This results in completely failed Puppet runs, which will never recover without external/manual intervention (removing the expired localy locally cached CA file) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10639) renew cached Puppet CA on Puppet client
Title: Message Title Andreas Paul updated an issue Puppet / PUP-10639 renew cached Puppet CA on Puppet client Change By: Andreas Paul *Puppet Version: all * all *Puppet Server Version: irrelevant * irrelevant *OS Name/Version:* * irrelevant *** Currently the Puppet agent/client does cache the Puppet CA file it first received forever. When this CA expires and get renewed on the configured `ca_server` or Puppetserver the cache still does not get updated with the new CA. *Desired Behavior:* * add sane defaults that would recheck if the cached local CA does differ from the one used by the configured `ca_server` (e.g. 1 week or 2 weeks before CA expiration date) * add Puppet client config settings to specify intervals for this CA check * if the local cached CA file is expired check if the configured `ca_server` uses a different one and replace the local cached CA file*Actual Behavior:* Currently the client does use the cached CA file forever even when the CA file has expired or the used CA file of the configured `ca_server` or Puppetserver was renewed.This results in completely failed Puppet runs, which will never recover without external/manual intervention (removing the expired localy cached CA file) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10639) renew cached Puppet CA on Puppet client
Title: Message Title Andreas Paul created an issue Puppet / PUP-10639 renew cached Puppet CA on Puppet client Issue Type: New Feature Assignee: Unassigned Created: 2020/08/20 4:40 AM Priority: Normal Reporter: Andreas Paul Puppet Version: all Puppet Server Version: irrelevant OS Name/Version: irrelevant** Currently the Puppet agent/client does cache the Puppet CA file it first received forever. When this CA expires and get renewed on the configured `ca_server` or Puppetserver the cache still does not get updated with the new CA. Desired Behavior: add sane defaults that would recheck if the cached local CA does differ from the one used by the configured `ca_server` (e.g. 1 week or 2 weeks before CA expiration date) add Puppet client config settings to specify intervals for this CA check if the local cached CA file is expired check if the configured `ca_server` uses a different one and replace the local cached CA file Actual Behavior: Currently the client does use the cached CA file forever even when the CA file has expired or the used CA file of the configured `ca_server` or Puppetserver was renewed. This results in completely failed Puppet runs, which will never recover without external/manual intervention (removing the expired localy cached CA file)
Jira (PUP-10624) Puppet::Agent::Locker#running? deprecation warning
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Puppet / PUP-10624 Puppet::Agent::Locker#running? deprecation warning 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.369496.1597738847000.20032.1597923240037%40Atlassian.JIRA.
Jira (FACT-2454) Free Memory calculation on Debian
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2454 Free Memory calculation on Debian Change By: Andrei Filipovici In Facter 3.x 4 calculates the free system used memory is calculated by adding subtracting the free , buffered and cached memory from the total memory . In Facter 4.x only The 'free' system call calculates the used memory by subtracting the free memory is displayed , buffers, cached and SReclaimable memory from the total memory . 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.349296.1583917175000.20031.159790076%40Atlassian.JIRA.
Jira (PUP-10610) Change disable_i18n to true by default
Title: Message Title
Ciprian Badescu commented on PUP-10610
Re: Change disable_i18n to true by default
instead of having disable_i18n default on true, could we replace option with enable{{_i18n with default false?}}
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.368587.1596752428000.20028.1597922040085%40Atlassian.JIRA.
Jira (PUP-10584) puppet_gem provider does not use vendored PKG_CONFIG_PATH when installing native extensions
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10584 puppet_gem provider does not use vendored PKG_CONFIG_PATH when installing native extensions Change By: Mihai Buzgau Release Notes Summary: set Allows installing of gems with native extensions that require PKG_CONFIG_PATH to /opt/puppetlabs/puppet/lib/pkgconfig while when using puppet_gem provider (needed for some native gems , like for example the rugged ) gem 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.365792.1594733596000.20021.1597921020028%40Atlassian.JIRA.
Jira (FACT-2644) Remove Facter for JRuby on el-6-x86_64
Title: Message Title Ciprian Badescu commented on FACT-2644 Re: Remove Facter for JRuby on el-6-x86_64 We may need to keep jruby support as long as FOSS puppetserver supports it, waiting updates on: https://tickets.puppetlabs.com/browse/FACT-2645 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.360374.1590701217000.20017.1597917540028%40Atlassian.JIRA.
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Claire Cadman updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Claire Cadman Labels: doc_reviewed redmine 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.35962.1400279607000.19979.1597914420025%40Atlassian.JIRA.
Jira (PUP-6631) Apt package provider does not mark managed packages as manual
Title: Message Title Claire Cadman updated an issue Puppet / PUP-6631 Apt package provider does not mark managed packages as manual Change By: Claire Cadman Labels: debian doc_reviewed linux package type_and_provider ubuntu 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.147758.1471514773000.19978.1597914360025%40Atlassian.JIRA.
Jira (PUP-10547) Manage user rights on Windows
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10547 Manage user rights on Windows Change By: Claire Cadman Labels: doc_reviewed 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.363693.1592980666000.19977.1597914300032%40Atlassian.JIRA.
Jira (PUP-10584) puppet_gem provider does not use vendored PKG_CONFIG_PATH when installing native extensions
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10584 puppet_gem provider does not use vendored PKG_CONFIG_PATH when installing native extensions Change By: Claire Cadman Labels: doc_reviewed 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.365792.1594733596000.19975.1597914240027%40Atlassian.JIRA.
Jira (PUP-10599) Puppet lookup on remote nodes should skip loading local external facts
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10599 Puppet lookup on remote nodes should skip loading local external facts Change By: Claire Cadman Labels: docs-reviewed 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.367118.1595504611000.19974.1597914180049%40Atlassian.JIRA.
Jira (PUP-10600) Allow running puppet commands via AWS Session Manager on Windows Server 2019
Title: Message Title Claire Cadman commented on PUP-10600 Re: Allow running puppet commands via AWS Session Manager on Windows Server 2019 Josh Cooper to confirm, is this still a known issue in 6.18 or is it resolved? 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.367242.1595613997000.19970.1597914060024%40Atlassian.JIRA.
Jira (PUP-10603) File Resource HTTP GET - Misuse of URL encoding
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10603 File Resource HTTP GET - Misuse of URL encoding Change By: Claire Cadman Labels: docs-reviewed 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.367500.1595969611000.19965.1597913940028%40Atlassian.JIRA.
Jira (PUP-10615) Add facts and vars back to PAL ScriptCompiler scope
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10615 Add facts and vars back to PAL ScriptCompiler scope Change By: Claire Cadman Labels: docs-reviewed 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.368742.1597093035000.19961.1597913820063%40Atlassian.JIRA.
Jira (PUP-10632) Prepare documentation updates and release notes (Puppet Platform 6.18.0)
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10632 Prepare documentation updates and release notes (Puppet Platform 6.18.0) Change By: Claire Cadman (Initial planned release date: 2020-08-25)Please post a link to the docs PR in the 'Publish Docs' ticket.For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Draft: [https://docs.google.com/document/d/1jttwqo-uQwIt3yFQYsa7hs_SwFp-SZls_tSATgD9AvM/edit] 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.369805.1597883901000.19958.1597913520035%40Atlassian.JIRA.
Jira (PUP-10489) Remove deprecated method from DirectoryService
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Puppet / PUP-10489 Remove deprecated method from DirectoryService 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.357608.1588683093000.19937.1597911300034%40Atlassian.JIRA.
Jira (PUP-10488) Remove deprecated method from Puppet::Provider::NameService
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Puppet / PUP-10488 Remove deprecated method from Puppet::Provider::NameService 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.357606.1588681832000.19934.1597910340028%40Atlassian.JIRA.
Jira (PUP-7667) puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set
Title: Message Title Florian Klink commented on PUP-7667 Re: puppet agent doesn't create certificate with FQDN if /etc/hostname contains FQDN, but search domain is not set I don't use puppet anymore, so can't check again, sorry. If you can't reproduce it anymore, feel free to close this issue. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.196080.1497521296000.19928.1597908600031%40Atlassian.JIRA.
Jira (PUP-10628) Performance regression with large hashes using lookup
Title: Message Title
Oleksandr Shtepa commented on PUP-10628
Re: Performance regression with large hashes using lookup
Looks like same problem exists for facter code. On some node I have 270 IP addresses. --profile shows:
[puppetserver] Puppet functions -> net::ipaddresses4_list: 6.164248 s (5 calls)
On a node with 3 IPs:
[puppetserver] Puppet functions -> net::ipaddresses4_list: 0.075847 s (5 calls)
net::ipaddresses4_list only works with fact $::networking:
function net::ipaddresses4_list() >>Array[String] {
$::networking['interfaces'].filter|$v|{ 'bindings' in $v[1] }.reduce([])|$memo, $v|{ $memo + $v[1]['bindings'].map()|$i|{ $i['address']} }
}
Add Comment
