Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Chris Cowell Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.312869.1560800327000.70134.1566532200187%40Atlassian.JIRA.
Jira (PDB-4490) Combine release_notes_x.y.markdown into release_notes.x.markdown
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4490 Combine release_notes_x.y.markdown into release_notes.x.markdown Change By: Austin Blatt Going forward we'll only maintain doc branches for maintained streams of PuppetDB (currently that's 5.2.x, 6.0.x and 6.3.x). The docs page will also feature a "latest" version, which is the most recent y release. As a result of currently separating release notes via y release, some release notes (such as those for 6.1.0 and 6.2.0) would not be visible on the docs page. Combining these to x version will solve that issue. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9962) stdlib : When ensure_resource() is used, it should correctly report duplicate resource declaration issues with more correct file and line numbers
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-9962 stdlib : When ensure_resource() is used, it should correctly report duplicate resource declaration issues with more correct file and line numbers Change By: Adam Bottchen CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.319159.1564655694000.69939.1566517560471%40Atlassian.JIRA.
Jira (PDB-4490) Combine release_notes_x.y.markdown into release_notes.x.markdown
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4490 Combine release_notes_x.y.markdown into release_notes.x.markdown Issue Type: Improvement Assignee: Austin Blatt Created: 2019/08/22 4:44 PM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9970) Regression in Docker Images - puppetdb.conf permission denied
Title: Message Title Ethan Brown commented on PUP-9970 Re: Regression in Docker Images - puppetdb.conf permission denied Merged in https://github.com/puppetlabs/puppetserver/commit/725e903dfba6059f794fd65d22c17df3d7d7fd37 Pending automated release to DockerHub which should happen in the next few minutes! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321545.1566315167000.69842.1566515700425%40Atlassian.JIRA.
Jira (PUP-9930) Do not necessarily load OpenSSL in JRuby
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9930 Do not necessarily load OpenSSL in JRuby Change By: Maggie Dreyer Fix Version/s: PUP 6.9.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.318889.1564525009000.69775.1566514380442%40Atlassian.JIRA.
Jira (PUP-9930) Do not necessarily load OpenSSL in JRuby
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9930 Do not necessarily load OpenSSL in JRuby Change By: Maggie Dreyer Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.318889.1564525009000.69777.1566514380454%40Atlassian.JIRA.
Jira (PUP-3262) By default, the cadir should be separated from the ssldir
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3262 By default, the cadir should be separated from the ssldir Change By: Charlie Sharpsteen Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.51395.141089306.69712.1566513180976%40Atlassian.JIRA.
Jira (PUP-9973) Can't create users using useradd provider when specifying uid since 6.8.0
Title: Message Title
Tim Bishop updated an issue
Puppet / PUP-9973
Can't create users using useradd provider when specifying uid since 6.8.0
Change By:
Tim Bishop
*Puppet Version: 6.8.0* *Puppet Server Version: 6.4.0* *OS Name/Version: Ubuntu 18.04*Creating a user specifying the UID (uses useradd provider automatically) : {{ user }} { {{ 'test': ... uid => 123,}}} *Desired Behavior:* Creating a user specifying the UID: User is created with uid 123. *Actual Behavior:* Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. {{Error: Could not create user test1: Execution of '[redacted]' returned 1: Error: Could not execute posix command: no implicit conversion of Integer into String}} Examples Debugging showed the command as : Run puppet agent with --test --trace --debug Relevant sections of {{ [" / var usr / log sbin / puppetlabs useradd", "-c", "Test1", "-g", "users", "-d", " / puppetserver home / puppetserver.log test1", "-p", "removed", "-s", "/bin/tcsh", "-u", 123, "-m", "test1"] }} 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 So I ' s logback m assuming the 123 argument there should be quoted . xml Relevant sections of configurations files (puppet.conf Suspect this is to do with this change , hiera.conf, Server but can ' s conf.d, defaults/sysconfig) t see why: For memory issues with server heap dumps are also helpful [https://github . com/puppetlabs/puppet/commit/70d20329012fc986c3d130f5769cc644f248c1b0#diff-f5b9cc80dd02278d845d220721ac0217]
Add Comment
Jira (PUP-9973) Can't create users using useradd provider when specifying uid since 6.8.0
Title: Message Title
Tim Bishop created an issue
Puppet / PUP-9973
Can't create users using useradd provider when specifying uid since 6.8.0
Issue Type:
Bug
Affects Versions:
PUP 6.8.0
Assignee:
Unassigned
Components:
Types and Providers
Created:
2019/08/22 2:35 PM
Priority:
Major
Reporter:
Tim Bishop
Puppet Version: 6.8.0 Puppet Server Version: 6.4.0 OS Name/Version: Ubuntu 18.04 Creating a user specifying the UID: user { 'test': Desired Behavior: Creating a user specifying the UID: 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 --debug Relevant 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.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.
Jira (PUP-9732) Client should cache successful host address for at least the length of a Puppet run
Title: Message Title Josh Cooper commented on PUP-9732 Re: Client should cache successful host address for at least the length of a Puppet run We only resolve server_list once at the beginning and use that for the duration of the run. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.311676.1559921066000.69458.1566507960397%40Atlassian.JIRA.
Jira (PUP-5109) Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5109 Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems Change By: Josh Cooper Fix Version/s: PUP 6.9.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.95553.144084808.69391.1566505620339%40Atlassian.JIRA.
Jira (PDB-4489) SPIKE - investigate feasibility of fact/param projection
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4489 SPIKE - investigate feasibility of fact/param projection Issue Type: Task Assignee: Austin Blatt Created: 2019/08/22 12:35 PM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Craig Watson commented on PDB-4487 Re: PuppetDB Terminus with Masterless Fails on SSL Errors Thanks Austin Blatt and Josh Cooper - I’ve had a dive upstream into the SSL code, and it does seem like the change to `ssl_context` is the cause, pulling this data in invokes `Puppet::SSL::Verifier` which attempts a full validation of the local certificate and CA. The wider implication here is that its directly incompatible with masterless deployments that lack these certificates. As it’s not technically caused by PuppetDB, I’m happy for this ticket to be closed/migrated around as necessary. If there’s anything I can do to help with diagnosis, feel free to reach out Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321961.1566490124000.69242.1566500700551%40Atlassian.JIRA.
Jira (PDB-4488) PuppetDB module uses deprecated http_instance method
Title: Message Title Vadym Chepkov commented on PDB-4488 Re: PuppetDB module uses deprecated http_instance method Thanks, it's not a production, just thought to brings attention to the right people. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321972.1566497006000.69233.1566500640322%40Atlassian.JIRA.
Jira (PDB-4488) PuppetDB module uses deprecated http_instance method
Title: Message Title
Vadym Chepkov updated an issue
PuppetDB / PDB-4488
PuppetDB module uses deprecated http_instance method
Change By:
Vadym Chepkov
puppetdb termini PuppetDB module uses deprecated in puppet 6.8.0 function, causing a warning:{noformat}Warning: Puppet::SSL::Host is deprecated and will be removed in a future release of Puppet. (location: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/host.rb:235:in `initialize'){noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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.321972.1566497006000.69227.1566500520586%40Atlassian.JIRA.
Jira (PDB-4488) PuppetDB module uses deprecated http_instance method
Title: Message Title Austin Blatt commented on PDB-4488 Re: PuppetDB module uses deprecated http_instance method This should stay in the PDB project, we manage that module. In the meantime, Vadym Chepkov, if you would like to avoid this deprecation warning you can turn off the strict_validation parameter in the PuppetDB module. It should be noted, that this will allow you to apply changes that break Puppet/PuppetDB communication, but if your settings are applying and working, but emitting a deprecation warning it is fairly low-risk. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321972.1566497006000.69030.1566498780670%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Kris Bosland updated an issue Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Change By: Kris Bosland Sprint: Coremunity Hopper Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.295251.154953565.69009.1566498601344%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Change By: Kris Bosland Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.295251.154953565.68998.1566498601130%40Atlassian.JIRA.
Jira (PDB-4488) PuppetDB module uses deprecated http_instance method
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4488 PuppetDB module uses deprecated http_instance method Change By: Austin Blatt Summary: puppetdb termini PuppetDB module uses deprecated in puppet 6.8.0 function http_instance method Assignee: Austin Blatt Affects Version/s: PDB 6.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321972.1566497006000.68986.1566498420430%40Atlassian.JIRA.
Jira (PUP-9732) Client should cache successful host address for at least the length of a Puppet run
Title: Message Title Kris Bosland commented on PUP-9732 Re: Client should cache successful host address for at least the length of a Puppet run Does server_list get tried multiple times during a puppet run? That might be worth caching too. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.311676.1559921066000.68978.1566498300173%40Atlassian.JIRA.
Jira (PDB-4488) puppetdb termini uses deprecated in puppet 6.8.0 function
Title: Message Title Josh Cooper commented on PDB-4488 Re: puppetdb termini uses deprecated in puppet 6.8.0 function Thanks Vadym Chepkov. It's coming from https://github.com/puppetlabs/puppetlabs-puppetdb/blob/8329c6c7152655112d3c996ce95434e219718ea3/lib/puppet/util/puppetdb_validator.rb#L28. This is an issue in the puppetdb module used to configure puppetdb. Austin Blatt should this be moved to MODULES or stay in PDB? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321972.1566497006000.68958.1566497940411%40Atlassian.JIRA.
Jira (PDB-4488) puppetdb termini uses deprecated in puppet 6.8.0 function
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4488 puppetdb termini uses deprecated in puppet 6.8.0 function Change By: Austin Blatt Affects Version/s: PDB 6.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321972.1566497006000.68952.1566497880843%40Atlassian.JIRA.
Jira (PDB-4488) puppetdb termini uses deprecated in puppet 6.8.0 function
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4488 puppetdb termini uses deprecated in puppet 6.8.0 function Change By: Austin Blatt Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321972.1566497006000.68948.1566497880821%40Atlassian.JIRA.
Jira (PUP-9513) Deprecate SSL host, validators, indirected types and termini
Title: Message Title Vadym Chepkov commented on PUP-9513 Re: Deprecate SSL host, validators, indirected types and termini Done, PDB-4488 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.297867.1551401113000.68898.1566497102385%40Atlassian.JIRA.
Jira (PDB-4488) puppetdb termini uses deprecated in puppet 6.8.0 function
Title: Message Title Vadym Chepkov created an issue PuppetDB / PDB-4488 puppetdb termini uses deprecated in puppet 6.8.0 function Issue Type: Improvement Assignee: Unassigned Attachments: trace.txt Created: 2019/08/22 11:03 AM Priority: Normal Reporter: Vadym Chepkov puppetdb termini uses deprecated in puppet 6.8.0 function, causing a warning: Warning: Puppet::SSL::Host is deprecated and will be removed in a future release of Puppet. (location: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/host.rb:235:in `initialize')
Jira (PUP-9513) Deprecate SSL host, validators, indirected types and termini
Title: Message Title Vadym Chepkov commented on PUP-9513 Re: Deprecate SSL host, validators, indirected types and termini Sure, under puppetdb project? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.297867.1551401113000.68886.1566496817257%40Atlassian.JIRA.
Jira (PUP-9513) Deprecate SSL host, validators, indirected types and termini
Title: Message Title Josh Cooper commented on PUP-9513 Re: Deprecate SSL host, validators, indirected types and termini Vadym Chepkov thanks for the trace! It looks like the puppetdb termini changes missed this usage of HttpPool.http_instance. Can you file a new ticket since 6.8 has already been released? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.297867.1551401113000.68858.1566496500372%40Atlassian.JIRA.
Jira (PUP-9513) Deprecate SSL host, validators, indirected types and termini
Title: Message Title Vadym Chepkov updated an issue Puppet / PUP-9513 Deprecate SSL host, validators, indirected types and termini Change By: Vadym Chepkov Attachment: trace.txt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.297867.1551401113000.68740.1566494760522%40Atlassian.JIRA.
Jira (PUP-9513) Deprecate SSL host, validators, indirected types and termini
Title: Message Title Vadym Chepkov commented on PUP-9513 Re: Deprecate SSL host, validators, indirected types and termini It seems one of the Puppetlabs components is still using it, since after installing 6.8.0 I started get warnings: Warning: Puppet::SSL::Host is deprecated and will be removed in a future release of Puppet. (location: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/host.rb:235:in `initialize') # rpm -qa|grep puppet|sort puppet6-release-6.0.0-5.el7.noarch puppet-agent-6.8.0-1.el7.x86_64 puppetdb-6.5.0-1.el7.noarch puppetdb-termini-6.5.0-1.el7.noarch puppetserver-6.5.0-1.el7.noarch
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Austin Blatt commented on PDB-4487 Re: PuppetDB Terminus with Masterless Fails on SSL Errors From Craig Watson in Slack, "last confirmed working versions were 6.5.0 for the agent and (IIRC) 6.4.0 for the terminus" Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321961.1566490124000.68651.1566493560214%40Atlassian.JIRA.
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4487 PuppetDB Terminus with Masterless Fails on SSL Errors Change By: Austin Blatt Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321961.1566490124000.68646.1566493500564%40Atlassian.JIRA.
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Austin Blatt commented on PDB-4487 Re: PuppetDB Terminus with Masterless Fails on SSL Errors Assuming this isn't a configuration error, and it only affects the 6.5.0 terminus, I have a feeling this was caused by switching to the non-deprecated HTTP Pool method connection. We now explicitly look up an ssl_context from Puppet. This likely needs to be guarded with a config option, either existing or new. https://github.com/puppetlabs/puppetdb/commit/8714ba9288da588e9fd197902332dd7c04635f10#diff-768747907b90c39ab6f16fcb3320897a Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321961.1566490124000.68629.1566492300218%40Atlassian.JIRA.
Jira (PUP-9959) Add puppet plugin to help output
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9959 Add puppet plugin to help output Change By: Josh Cooper Fix Version/s: PUP 6.9.0 Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 6.0.11 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.317346.1563668147000.68614.1566492180226%40Atlassian.JIRA.
Jira (PUP-9959) Add puppet plugin to help output
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9959 Add puppet plugin to help output Change By: Josh Cooper Summary: Plugin sync to get latest fact set when running Add puppet facts upload plugin to help output Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.317346.1563668147000.68610.1566492120771%40Atlassian.JIRA.
Jira (PUP-9959) Plugin sync to get latest fact set when running puppet facts upload
Title: Message Title Josh Cooper commented on PUP-9959 Re: Plugin sync to get latest fact set when running puppet facts upload Merged to 6.0.x in https://github.com/puppetlabs/puppet/commit/5b115d4bb8146463df0e88b7267e640594971fa4 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.317346.1563668147000.68604.1566492120741%40Atlassian.JIRA.
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Josh Cooper commented on PDB-4487 Re: PuppetDB Terminus with Masterless Fails on SSL Errors Craig Watson was this working when using puppet 6.5.0, and is now broken after upgrading the test node to 6.8.0? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.321961.1566490124000.68595.1566491760399%40Atlassian.JIRA.
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title
Craig Watson updated an issue
PuppetDB / PDB-4487
PuppetDB Terminus with Masterless Fails on SSL Errors
Change By:
Craig Watson
We are running Puppet masterless, connecting to a standalone PuppetDB cluster (6.5.0) with a shared PostgreSQL backend. SSL termination is handed by the load balancer, which is using a managed SSL certificate (from Google, signed by LetsEncrypt).routes.yaml: {code}---apply: catalog: terminus: compiler cache: puppetdb resource: terminus: ral cache: puppetdb facts: terminus: facter cache: puppetdb_apply{code}puppetdb.conf:{code}[main]server_urls = https://puppetdb.[redacted]:443soft_write_failure = true{code}puppet.conf:{code}[main] storeconfigs = false report = true reports = puppetdb{code}We have upgraded a test node to Puppet 6.8.0 and also upgraded the PuppetDB Termini to 6.5.0:{code}$ yum list puppet-agent puppetdb-terminiInstalled Packagespuppet-agent.x86_64 6.8.0-1.el7 @puppet6puppetdb-termini.noarch 6.5.0-1.el7 @puppet{code}We now have issues where the PuppetDB terminus is complaining about a lack of TLS-related files (CRL, CA, certificate, key) which would normally exist on a mastered Puppet installation, but don't on ours as they're not used.So far, I have added:{code}localcacert = /etc/pki/tls/certs/ca-bundle.crtcertificate_revocation = false{code}To try and work around and stub out the SSL, but I am now left with the following for each interaction with PuppetDB (facts, catalog, report):{code}Error: Failed to initialize SSL: The private key is missing from '/etc/puppetlabs/puppet/ssl/private_keys/[fqdn].pem'Error: Run `puppet agent -t`Error: The private key is missing from '/etc/puppetlabs/puppet/ssl/private_keys/[fqdn].pem'{code}I have tried rolling a temporary/throwaway local CA with no success.The Puppet run itself succeeds, but nothing is sent at all to PuppetDB
Add Comment
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title
Craig Watson updated an issue
PuppetDB / PDB-4487
PuppetDB Terminus with Masterless Fails on SSL Errors
Change By:
Craig Watson
We are running Puppet masterless, connecting to a standalone PuppetDB cluster (6.5.0) with a shared PostgreSQL backend. SSL termination is handed by the load balancer, which is using a managed SSL certificate (from Google, signed by LetsEncrypt).routes.yaml: {code :java }---apply: catalog: terminus: compiler cache: puppetdb resource: terminus: ral cache: puppetdb facts: terminus: facter cache: puppetdb_apply{code}puppetdb.conf:{code :java }[main]server_urls = https://puppetdb.[redacted]:443soft_write_failure = true{code}puppet.conf:{code :java }[main] storeconfigs = false report = true reports = puppetdb{code}We have upgraded a test node to Puppet 6.8.0 and also upgraded the PuppetDB Termini to 6.5.0:{code :java }$ yum list puppet-agent puppetdb-terminiInstalled Packagespuppet-agent.x86_64 6.8.0-1.el7 @puppet6puppetdb-termini.noarch 6.5.0-1.el7 @puppet{code}We now have issues where the PuppetDB terminus is complaining about a lack of TLS-related files (CRL, CA, certificate, key) which would normally exist on a mastered Puppet installation, but don't on ours as they're not used.So far, I have added:{code}localcacert = /etc/pki/tls/certs/ca-bundle.crtcertificate_revocation = false{code}To try and work around and stub out the SSL, but I am now left with the following for each interaction with PuppetDB (facts, catalog, report) :{code :java }Error: Failed to initialize SSL: The private key is missing from '/etc/puppetlabs/puppet/ssl/private_keys/[fqdn].pem'Error: Run `puppet agent -t`Error: The private key is missing from '/etc/puppetlabs/puppet/ssl/private_keys/[fqdn].pem'{code}I have tried rolling a temporary/throwaway local CA with no success. The Puppet run itself succeeds, but nothing is sent at all to PuppetDB
Add Comment
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title
Craig Watson updated an issue
PuppetDB / PDB-4487
PuppetDB Terminus with Masterless Fails on SSL Errors
Change By:
Craig Watson
We are running Puppet masterless, connecting to a standalone PuppetDB cluster (6.5.0) with a shared PostgreSQL backend. SSL termination is handed by the load balancer, which is using a managed SSL certificate (from Google, signed by LetsEncrypt).routes.yaml: {code:java} ---apply: catalog: terminus: compiler cache: puppetdb resource: terminus: ral cache: puppetdb facts: terminus: facter cache: puppetdb_apply{code}puppetdb.conf: {code:java} [main]server_urls = https://puppetdb.[redacted]:443soft_write_failure = true{code}puppet.conf: {code:java} [main] storeconfigs = false report = true reports = puppetdb{code} We have upgraded a test node to Puppet 6.8.0 and also upgraded the PuppetDB Termini to 6.5.0: {code:java} $ yum list puppet-agent puppetdb-terminiInstalled Packagespuppet-agent.x86_64 6.8.0-1.el7 @puppet6puppetdb-termini.noarch 6.5.0-1.el7 @puppet{code}We now have issues where the PuppetDB terminus is complaining about a lack of TLS-related files (CRL, CA, certificate, key) which would normally exist on a mastered Puppet installation, but don't on ours as they're not used. {{ So far, I have added: }} {code :java } localcacert = /etc/pki/tls/certs/ca-bundle.crtcertificate_revocation = false{code}To try and work around and stub out the SSL, but I am now left with:{code:java} Error: Failed to initialize SSL: The private key is missing from '/etc/puppetlabs/puppet/ssl/private_keys/[fqdn].pem'Error: Run `puppet agent -t`Error: The private key is missing from '/etc/puppetlabs/puppet/ssl/private_keys/[fqdn].pem'{code}I have tried rolling a temporary/throwaway local CA with no success.
Add Comment
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Craig Watson created an issue PuppetDB / PDB-4487 PuppetDB Terminus with Masterless Fails on SSL Errors Issue Type: Task Affects Versions: PDB 6.5.0 Assignee: Unassigned Components: PuppetDB Created: 2019/08/22 9:08 AM Priority: Blocker Reporter: Craig Watson We are running Puppet masterless, connecting to a standalone PuppetDB cluster (6.5.0) with a shared PostgreSQL backend. SSL termination is handed by the load balancer, which is using a managed SSL certificate (from Google, signed by LetsEncrypt). routes.yaml: --- apply: catalog: terminus: compiler cache: puppetdb
Jira (FACT-1853) facter networking is very slow on OpenStack compute node
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-1853 facter networking is very slow on OpenStack compute node Change By: Ciprian Badescu Team: Platform OS Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.251436.1526644654000.68334.1566485760192%40Atlassian.JIRA.
Jira (FACT-1904) facter (leatherman) is slow if nofile ulimit is bigger than default
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-1904 facter (leatherman) is slow if nofile ulimit is bigger than default Change By: Ciprian Badescu Team: Platform OS Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.292241.1547658928000.68332.1566485640162%40Atlassian.JIRA.
Jira (FACT-1997) Collect statistics on multiple platforms using Beaker
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-1997 Collect statistics on multiple platforms using Beaker Issue Type: Task Assignee: Oana Tanasoiu Created: 2019/08/22 1:40 AM Priority: Normal Reporter: Oana Tanasoiu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1996) Invalidate resolver cache once Facter run in over
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1996 Invalidate resolver cache once Facter run in over Issue Type: Task Assignee: Unassigned Created: 2019/08/22 12:27 AM Priority: Normal Reporter: Bogdan Irimie This is important for the gem as it can be used in a long running process and we need to invalidate cached data between multiple runs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
