Jira (PDB-4446) puppet query: certificate verify failed
Title: Message Title
John Florian updated an issue
PuppetDB / PDB-4446
puppet query: certificate verify failed
Change By:
John Florian
Following the installation/configuration instructions at [https://puppet.com/docs/puppetdb/6.3/pdb_client_tools.html], I have been unable to perform a simple test query. These fail like:~~~$ sudo puppet query "nodes [ certname ] { limit 1 } " Traceback (most recent call last): 20: from /usr/local/bin/puppet-query:23:in `' 19: from /usr/local/bin/puppet-query:23:in `load' 18: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/exe/puppet-query:7:in `' 17: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli.rb:13:in `run' 16: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:314:in `run' 15: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:296:in `run' 14: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:360:in `run_this' 13: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli/query.rb:34:in `block (2 levels) in ' 12: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli/utils.rb:41:in `send_query' 11: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:103:in `request' 10: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:103:in `each' 9: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:105:in `block in request' 8: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty.rb:507:in `get' 7: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty.rb:593:in `perform_request' 6: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty/request.rb:145:in `perform' 5: from /usr/share/ruby/net/http.rb:1470:in `request' 4: from /usr/share/ruby/net/http.rb:919:in `start' 3: from /usr/share/ruby/net/http.rb:930:in `do_start' 2: from /usr/share/ruby/net/http.rb:996:in `connect' 1: from /usr/share/ruby/net/protocol.rb:44:in `ssl_socket_connect' /usr/share/ruby/net/protocol.rb:44:in `connect_nonblock': SSL_connect returned=1 errno=0 state=error: certificate verify failed (unspecified certificate verification error) (OpenSSL::SSL::SSLError)~~~My CLI config (/etc/puppetlabs/client-tools/puppetdb.conf) is : {\{{ }} ~~~ \ { { "puppetdb": { }} \{{ "server_urls": "https://puppetdb.doubledog.org:8081", }} \{{ "cacert": "/etc/puppet/ssl/certs/ca.pem", }} \{{ "cert": "/etc/puppet/ssl/certs/zuul.doubledog.org.pem", }} \{{ "key": "/etc/puppet/ssl/private_keys/zuul.doubledog.org.pem" }} {{ } } } {{}}} ~~~ This leaves me with little to debug the connection with. I did an md5sum on the client /etc/puppet/ssl/certs/ca.pem and confirmed it matches both /etc/puppetlabs/puppetdb/ssl/ca.pem and /etc/puppetlabs/puppet/ssl/certs/ca.pem on the Master/DB host. What now? Could this be the CRL checking problem that agents have
Jira (PDB-4446) puppet query: certificate verify failed
Title: Message Title
John Florian updated an issue
PuppetDB / PDB-4446
puppet query: certificate verify failed
Change By:
John Florian
Following the installation/configuration instructions at [https://puppet.com/docs/puppetdb/6.3/pdb_client_tools.html], I have been unable to perform a simple test query. These fail like: {\{ ~~~ $ sudo puppet query "nodes [ certname ] { limit 1 } " Traceback (most recent call last): 20: from /usr/local/bin/puppet-query:23:in `' 19: from /usr/local/bin/puppet-query:23:in `load' 18: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/exe/puppet-query:7:in `' 17: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli.rb:13:in `run' 16: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:314:in `run' 15: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:296:in `run' 14: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:360:in `run_this' 13: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli/query.rb:34:in `block (2 levels) in ' 12: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli/utils.rb:41:in `send_query' 11: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:103:in `request' 10: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:103:in `each' 9: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:105:in `block in request' 8: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty.rb:507:in `get' 7: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty.rb:593:in `perform_request' 6: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty/request.rb:145:in `perform' 5: from /usr/share/ruby/net/http.rb:1470:in `request' 4: from /usr/share/ruby/net/http.rb:919:in `start' 3: from /usr/share/ruby/net/http.rb:930:in `do_start' 2: from /usr/share/ruby/net/http.rb:996:in `connect' 1: from /usr/share/ruby/net/protocol.rb:44:in `ssl_socket_connect' /usr/share/ruby/net/protocol.rb:44:in `connect_nonblock': SSL_connect returned=1 errno=0 state=error: certificate verify failed (unspecified certificate verification error) (OpenSSL::SSL::SSLError) }} ~~~ My CLI config (/etc/puppetlabs/client-tools/puppetdb.conf) is :{\{{ }} \{{ "puppetdb": { }} \{{ "server_urls": "https://puppetdb.doubledog.org:8081", }} \{{ "cacert": "/etc/puppet/ssl/certs/ca.pem", }} \{{ "cert": "/etc/puppet/ssl/certs/zuul.doubledog.org.pem", }} \{{ "key": "/etc/puppet/ssl/private_keys/zuul.doubledog.org.pem" }} {{ }}} {{}}}This leaves me with little to debug the connection with. I did an md5sum on the client /etc/puppet/ssl/certs/ca.pem and confirmed it matches both /etc/puppetlabs/puppetdb/ssl/ca.pem and /etc/puppetlabs/puppet/ssl/certs/ca.pem on the Master/DB host. What now? Could this be the CRL checking problem that agents have with the new(ish) intermediate
Jira (PDB-4446) puppet query: certificate verify failed
Title: Message Title
John Florian updated an issue
PuppetDB / PDB-4446
puppet query: certificate verify failed
Change By:
John Florian
Following the installation/configuration instructions at [https://puppet.com/docs/puppetdb/6.3/pdb_client_tools.html], I have been unable to perform a simple test query. These fail like:{ \ { $ sudo puppet query "nodes [ certname ] \ { limit 1 }" Traceback (most recent call last): 20: from /usr/local/bin/puppet-query:23:in `' 19: from /usr/local/bin/puppet-query:23:in `load' 18: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/exe/puppet-query:7:in `' 17: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli.rb:13:in `run' 16: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:314:in `run' 15: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:296:in `run' 14: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:360:in `run_this' 13: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli/query.rb:34:in `block (2 levels) in ' 12: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli/utils.rb:41:in `send_query' 11: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:103:in `request' 10: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:103:in `each' 9: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:105:in `block in request' 8: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty.rb:507:in `get' 7: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty.rb:593:in `perform_request' 6: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty/request.rb:145:in `perform' 5: from /usr/share/ruby/net/http.rb:1470:in `request' 4: from /usr/share/ruby/net/http.rb:919:in `start' 3: from /usr/share/ruby/net/http.rb:930:in `do_start' 2: from /usr/share/ruby/net/http.rb:996:in `connect' 1: from /usr/share/ruby/net/protocol.rb:44:in `ssl_socket_connect' /usr/share/ruby/net/protocol.rb:44:in `connect_nonblock': SSL_connect returned=1 errno=0 state=error: certificate verify failed (unspecified certificate verification error) (OpenSSL::SSL::SSLError) }}My CLI config (/etc/puppetlabs/client-tools/puppetdb.conf) is :{\{{ }} \{{ "puppetdb": { }} \{{ "server_urls": "https://puppetdb.doubledog.org:8081", }} \{{ "cacert": "/etc/puppet/ssl/certs/ca.pem", }} \{{ "cert": "/etc/puppet/ssl/certs/zuul.doubledog.org.pem", }} \{{ "key": "/etc/puppet/ssl/private_keys/zuul.doubledog.org.pem" }} \ { { } }} {{}}}This leaves me with little to debug the connection with. I did an md5sum on the client /etc/puppet/ssl/certs/ca.pem and confirmed it matches both /etc/puppetlabs/puppetdb/ssl/ca.pem and /etc/puppetlabs/puppet/ssl/certs/ca.pem on the Master/DB host. What now? Could this be the CRL checking problem that agents have with the new(ish) intermediate
Jira (PDB-4446) puppet query: certificate verify failed
Title: Message Title
John Florian updated an issue
PuppetDB / PDB-4446
puppet query: certificate verify failed
Change By:
John Florian
Following the installation/configuration instructions at [https://puppet.com/docs/puppetdb/6.3/pdb_client_tools.html], I have been unable to perform a simple test query. These fail like:{{ $ sudo puppet query "nodes [ certname ]\{ limit 1 }" }} {{ Traceback (most recent call last): }} {{ 20: from /usr/local/bin/puppet-query:23:in `' }} {{ 19: from /usr/local/bin/puppet-query:23:in `load' }} {{ 18: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/exe/puppet-query:7:in `' }} {{ 17: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli.rb:13:in `run' }} {{ 16: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:314:in `run' }} {{ 15: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:296:in `run' }} {{ 14: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:360:in `run_this' }} {{ 13: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli/query.rb:34:in `block (2 levels) in ' }} {{ 12: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli/utils.rb:41:in `send_query' }} {{ 11: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:103:in `request' }} {{ 10: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:103:in `each' }} {{ 9: from /usr/local/share/gems/gems/pl-puppetdb-ruby-2.0.2/lib/puppetdb/client.rb:105:in `block in request' }} {{ 8: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty.rb:507:in `get' }} {{ 7: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty.rb:593:in `perform_request' }} {{ 6: from /usr/local/share/gems/gems/httparty-0.17.0/lib/httparty/request.rb:145:in `perform' }} {{ 5: from /usr/share/ruby/net/http.rb:1470:in `request' }} {{ 4: from /usr/share/ruby/net/http.rb:919:in `start' }} {{ 3: from /usr/share/ruby/net/http.rb:930:in `do_start' }} {{ 2: from /usr/share/ruby/net/http.rb:996:in `connect' }} {{ 1: from /usr/share/ruby/net/protocol.rb:44:in `ssl_socket_connect' }} {{ /usr/share/ruby/net/protocol.rb:44:in `connect_nonblock': SSL_connect returned=1 errno=0 state=error: certificate verify failed (unspecified certificate verification error) (OpenSSL::SSL::SSLError) }}My CLI config (/etc/puppetlabs/client-tools/puppetdb.conf) is :{ \ {{ }} \ {{ "puppetdb": { }} \ {{ "server_urls": "https://puppetdb.doubledog.org:8081", }} \ {{ "cacert": "/etc/puppet/ssl/certs/ca.pem", }} \ {{ "cert": "/etc/puppet/ssl/certs/zuul.doubledog.org.pem", }} \ {{ "key": "/etc/puppet/ssl/private_keys/zuul.doubledog.org.pem" }} \ {{ } }}{{}}}This leaves me with little to debug the connection with. I did an md5sum on the client /etc/puppet/ssl/certs/ca.pem and confirmed it matches both
Jira (PDB-4446) puppet query: certificate verify failed
Title: Message Title
John Florian created an issue
PuppetDB / PDB-4446
puppet query: certificate verify failed
Issue Type:
Bug
Affects Versions:
PDB 6.3.4
Assignee:
Unassigned
Components:
PuppetDB
Created:
2019/06/27 4:31 PM
Environment:
PuppetDB is on CentOS 7 using puppetdb-6.3.4-1.el7.noarch from the puppet6 repo. The CLI is on Fedora 30 using the puppetdb_cli-2.0.0.gem. This same host has puppet-5.5.10-4.fc30.noarch from the regular Fedora repos.
Priority:
Normal
Reporter:
John Florian
Following the installation/configuration instructions at https://puppet.com/docs/puppetdb/6.3/pdb_client_tools.html, I have been unable to perform a simple test query. These fail like: {{$ sudo puppet query "nodes [ certname ]{ limit 1 }" }} {{Traceback (most recent call last): }} {{ 20: from /usr/local/bin/puppet-query:23:in `' }} {{ 19: from /usr/local/bin/puppet-query:23:in `load' }} {{ 18: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/exe/puppet-query:7:in `' }} {{ 17: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli.rb:13:in `run' }} {{ 16: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:314:in `run' }} {{ 15: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:296:in `run' }} {{ 14: from /usr/local/share/gems/gems/cri-2.15.9/lib/cri/command.rb:360:in `run_this' }} {{ 13: from /usr/local/share/gems/gems/puppetdb_cli-2.0.0/lib/puppetdb_cli/query.rb:34:in `block (2 levels) in ' }} {{ 12: from
Jira (BOLT-1406) out::message doesn't work inside without_default_logging
Title: Message Title Michelle Fredette commented on BOLT-1406 Re: out::message doesn't work inside without_default_logging added bug fix to release note 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312979.1560875893000.64537.1561677060218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1399) Task action stub "parameter" method incorrectly merges options and arguments
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-1399 Task action stub "parameter" method incorrectly merges options and arguments Change By: Michelle Fredette 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312824.1560783866000.64528.1561676820415%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1399) Task action stub "parameter" method incorrectly merges options and arguments
Title: Message Title Michelle Fredette commented on BOLT-1399 Re: Task action stub "parameter" method incorrectly merges options and arguments bug fix added. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312824.1560783866000.64531.1561676820568%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1406) out::message doesn't work inside without_default_logging
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-1406 out::message doesn't work inside without_default_logging Change By: Michelle Fredette 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312979.1560875893000.64521.1561676580305%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1399) Task action stub "parameter" method incorrectly merges options and arguments
Title: Message Title Tom Beech updated an issue Puppet Task Runner / BOLT-1399 Task action stub "parameter" method incorrectly merges options and arguments Change By: Tom Beech Release Notes Summary: When a task action stub expectation fails the expected parameters are now properly displayed. Release Notes: Not Needed Bug Fix 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312824.1560783866000.64409.1561674060196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9718) Create a plan_information_service in Puppet and add it to the information_service
Title: Message Title Scott McClellan updated an issue Puppet / PUP-9718 Create a plan_information_service in Puppet and add it to the information_service Change By: Scott McClellan Fix Version/s: PUP 6.y 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309780.1558558495000.64271.1561670520321%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9718) Create a plan_information_service in Puppet and add it to the information_service
Title: Message Title Scott McClellan updated an issue Puppet / PUP-9718 Create a plan_information_service in Puppet and add it to the information_service Change By: Scott McClellan Fix Version/s: PUP 6.y Fix Version/s: PUP 6.6.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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309780.1558558495000.64273.1561670520424%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9718) Create a plan_information_service in Puppet and add it to the information_service
Title: Message Title Scott McClellan updated an issue Puppet / PUP-9718 Create a plan_information_service in Puppet and add it to the information_service Change By: Scott McClellan 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309780.1558558495000.64259.1561669800223%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9811) incoherent Puppet Platform 6.5.0 announcement versus release notes
Title: Message Title James Ralston created an issue Puppet / PUP-9811 incoherent Puppet Platform 6.5.0 announcement versus release notes Issue Type: Task Affects Versions: PUP 6.5.0 Assignee: Unassigned Components: Docs Created: 2019/06/27 1:47 PM Environment: The email announcement for Puppet Platform 6.5.0 consisted of this text: This release contain bug fixes and enhancement, notably: Support added for Fedora 30 (amd64) New v4 catalog endpoint You can see the full list of changes in the release notes https://puppet.com/docs/puppet/6.5/release_notes_puppet.html However, the 6.5.0 release notes make no mention of the new v4 catalog endpoint. I'm guessing that both the release announcement and the release notes went through multiple iterations of reviews/edits, and the final versions were supposed to be coherent, but this discrepancy was accidentally missed. Please update the release notes to include the information about the new v4 catalog endpoint that the release announcement references. Priority: Normal Reporter: James Ralston
Jira (PUP-9811) incoherent Puppet Platform 6.5.0 announcement versus release notes
Title: Message Title
James Ralston updated an issue
Puppet / PUP-9811
incoherent Puppet Platform 6.5.0 announcement versus release notes
Change By:
James Ralston
Environment:
The email announcement for Puppet Platform 6.5.0 consisted of this text:{quote}This release contain bug fixes and enhancement, notably:* Support added for Fedora 30 (amd64)* New v4 catalog endpoint You can see the full list of changes in the release notes https://puppet.com/docs/puppet/6.5/release_notes_puppet.html{quote}However, the 6.5.0 release notes make no mention of the new v4 catalog endpoint.I'm guessing that both the release announcement and the release notes went through multiple iterations of reviews/edits, and the final versions were supposed to be coherent, but this discrepancy was accidentally missed.Please update the release notes to include the information about the new v4 catalog endpoint that the release announcement references.
The email announcement for Puppet Platform 6.5.0 consisted of this text:{quote}This release contain bug fixes and enhancement, notably:* Support added for Fedora 30 (amd64)* New v4 catalog endpoint You can see the full list of changes in the release notes https://puppet.com/docs/puppet/6.5/release_notes_puppet.html{quote}However, the 6.5.0 release notes make no mention of the new v4 catalog endpoint.I'm guessing that both the release announcement and the release notes went through multiple iterations of reviews/edits, and the final versions were supposed to be coherent, but this discrepancy was accidentally missed.Please update the release notes to include the information about the new v4 catalog endpoint that the release announcement references.
Add Comment
Jira (BOLT-1436) Reconcile git commits, JIRA tickets, and versions (Bolt 1.25.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1436 Reconcile git commits, JIRA tickets, and versions (Bolt 1.25.0) Issue Type: Sub-task Assignee: Tom Beech Created: 2019/06/27 1:01 PM Due Date: 2019/06/27 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-27) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-1438) Publish release artifacts (Bolt 1.25.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1438 Publish release artifacts (Bolt 1.25.0) Issue Type: Sub-task Assignee: Tom Beech Created: 2019/06/27 1:01 PM Due Date: 2019/06/27 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-27) Run the Bolt shipping pipeline. Set REF to 1.25.0. If you encounter any issues, ping the on-call person in the #release-new-new Slack channel. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-1442) Send release announcements (Bolt 1.25.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1442 Send release announcements (Bolt 1.25.0) Issue Type: Sub-task Assignee: Michelle Fredette Created: 2019/06/27 1:01 PM Due Date: 2019/06/27 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-27) When docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt now available". In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com In the body, include a summary of the release and links to the release notes and installation instructions. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. (Optional) Set up a canned response in Gmail so that you don't have to recreate this email every time: Subject: Bolt X.Y.Z now available Body: Greetings! We're happy to announce the release of Bolt X.Y.Z. Highlights in this release include: Gerund phrase Gerund phrase For more information, check out
Jira (BOLT-1435) Bolt 1.25.0 2019-06-27 Release
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1435 Bolt 1.25.0 2019-06-27 Release Issue Type: Task Assignee: Tom Beech Created: 2019/06/27 1:01 PM Priority: Normal Reporter: Tom Beech Bolt 1.25.0 2019-06-27 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1440) Update homebrew-puppet (Bolt 1.25.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1440 Update homebrew-puppet (Bolt 1.25.0) Issue Type: Sub-task Assignee: Tom Beech Created: 2019/06/27 1:01 PM Due Date: 2019/06/27 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-27) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Run "rake 'brew:cask[puppet-bolt]'" Verify Casks/puppet-bolt.rb was updated to the correct version Put up a PR to homebrew-puppet and request review Add Comment
Jira (BOLT-1437) Kick off release pipeline (Bolt 1.25.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1437 Kick off release pipeline (Bolt 1.25.0) Issue Type: Sub-task Assignee: Tom Beech Created: 2019/06/27 1:01 PM Due Date: 2019/06/27 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-27) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-1441) Docs for bolt release (Bolt 1.25.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1441 Docs for bolt release (Bolt 1.25.0) Issue Type: Sub-task Assignee: Michelle Fredette Created: 2019/06/27 1:01 PM Due Date: 2019/06/27 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-27) Release notes and docs changes for bolt 1.25.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1439) Update the release spreadsheet (Bolt 1.25.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1439 Update the release spreadsheet (Bolt 1.25.0) Issue Type: Sub-task Assignee: Tom Beech Created: 2019/06/27 1:01 PM Due Date: 2019/06/27 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-27) Update the release google spreadsheet for Bolt 1.25.0. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1168) Add catch_errors and better handling to apply_prep
Title: Message Title Alex Dreyer commented on BOLT-1168 Re: Add catch_errors and better handling to apply_prep I think so. We should verify and perhaps mention that in the apply_prep docs. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.298893.1551982151000.64125.1561665240396%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1305) tasks-hands-on-lab writing tasks page improvements
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1305 tasks-hands-on-lab writing tasks page improvements Change By: Lucy Wyman Labels: DOCS 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308846.1557962891000.64127.1561665240493%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1257) Support Encrypted password in bolt.yaml
Title: Message Title Lucy Wyman commented on BOLT-1257 Re: Support Encrypted password in bolt.yaml We don't support this in the bolt configuration file yet, but you can set this configuration for all nodes in the inventory with the PKCS7 plugin https://github.com/puppetlabs/bolt/blob/master/pre-docs/inventory_version2.md#pkcs7-plugin or by prompting 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305152.115061000.64120.1561665180300%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1168) Add catch_errors and better handling to apply_prep
Title: Message Title Lucy Wyman commented on BOLT-1168 Re: Add catch_errors and better handling to apply_prep Does the catch_errors() function work for this? 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.298893.1551982151000.64109.1561664820335%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1398) I want to see what nodes are in an inventory group
Title: Message Title Tom Beech assigned an issue to Tom Beech Puppet Task Runner / BOLT-1398 I want to see what nodes are in an inventory group Change By: Tom Beech Assignee: Tom Beech 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312528.1560553204000.64075.1561662420300%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-821) System level configuration file for Bolt
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-821 System level configuration file for Bolt Change By: Lucy Wyman Team: Bolt 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.273444.153563933.64009.1561661340971%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-414) Run a task with different parameters per target
Title: Message Title Alex Dreyer commented on BOLT-414 Re: Run a task with different parameters per target Writing a plan that runs multiple tasks in sequence is slow since you have to wait for the task to finish on one target before starting it on the next. This could be solved with concurrency but it also relates to hiera data bindings. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.242960.1522085962000.64002.1561661280204%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-235) Encrypted parameters for tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-235 Encrypted parameters for tasks Change By: Alex Dreyer Summary: Encrypteded Encrypted parameters for tasks 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.223860.1511432259000.63992.1561661041080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-235) Encrypteded parameters for tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-235 Encrypteded parameters for tasks Change By: Alex Dreyer Summary: Create encrypted variables in Encrypteded parameters for tasks 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.223860.1511432259000.63985.1561661040754%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-414) Run a task with different parameters per target
Title: Message Title Lucy Wyman commented on BOLT-414 Re: Run a task with different parameters per target This seems like a case where you would write a plan instead. Is this something we still want to support? 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.242960.1522085962000.63988.1561661040893%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-235) Create encrypted variables in tasks
Title: Message Title Alex Dreyer commented on BOLT-235 Re: Create encrypted variables in tasks I think this is about encrypted parameters to a task rather then connection information to the target. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.223860.1511432259000.63980.1561660980553%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-235) Create encrypted variables in tasks
Title: Message Title Lucy Wyman commented on BOLT-235 Re: Create encrypted variables in tasks Is this fixed with the prompt / pkcs7 work? 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.223860.1511432259000.63972.1561660860680%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1126) Make hands on lab more windows friendly
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1126 Make hands on lab more windows friendly Change By: Lucy Wyman Labels: DOCS 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295951.155000000.63963.1561660622080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9806) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey assigned an issue to James Shen Puppet / PUP-9806 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0) Change By: Kenn Hussey Assignee: Kenn Hussey James Shen 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314022.1561488088000.63925.1561659420230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4443) PuppetDB master branch failing to promote into PE Lovejoy
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4443
PuppetDB master branch failing to promote into PE Lovejoy
Change By:
Austin Blatt
PuppetDB's master branch failing PEZ Integration Smoke Tests on Ubuntu 16.04 https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/job/enterprise_pez_integration-system-pezv2_smoke_2019.2.x/254/The error appears to be artifactory/network related but it is oddly repeatable.{code:java}14:41:55 Could not resolve host: artifactory.delivery.puppetlabs.net14:41:55 Warning: ssh channel on ubuntu1604-64-1 received exception post command execution Net::SSH::Timeout - Timeout, server evilm9s5fp5v3qg.delivery.puppetlabs.net not responding.15:01:55 Warning: Attemped ssh.close, (caught Errno::ETIMEDOUT - Connection timed out - recvfrom(2)).15:02:34 ssh connection to ubuntu1604-64-1 has been terminated15:02:34 15:02:34 evilm9s5fp5v3qg.delivery.puppetlabs.net (ubuntu1604-64-1) executed in 1260.24 seconds15:02:34 Failed: errored in validate15:02:34 #15:02:34 apt-get update15:02:34 Last 10 lines of output were:15:02:34 Err:1 https://artifactory.delivery.puppetlabs.net/artifactory/ubuntu__remote xenial-security InRelease15:02:34Could not resolve host: artifactory.delivery.puppetlabs.net>15:02:34 /tmp/jenkins/workspace/enterprise_pez_integration-system-pezv2_smoke_2019.2.x/LAYOUT/ubuntu1604-64mcd-64compile_master.fa-windows2008r2-64fa/LEGACY_AGENT_VERSION/NONE/UPGRADE_FROM/NONE/label/beaker/vendor/bundler/ruby/2.5.0/gems/beaker-4.9.0/lib/beaker/host.rb:35715:02:34 /tmp/jenkins/workspace/enterprise_pez_integration-system-pezv2_smoke_2019.2.x/LAYOUT/ubuntu1604-64mcd-64compile_master.fa-windows2008r2-64fa/LEGACY_AGENT_VERSION/NONE/UPGRADE_FROM/NONE/label/beaker/vendor/bundler/ruby/2.5.0/gems/beaker-4.9.0/lib/beaker/command_factory.rb:3515:02:34 /tmp/jenkins/workspace/enterprise_pez_integration-system-pezv2_smoke_2019.2.x/LAYOUT/ubuntu1604-64mcd-64compile_master.fa-windows2008r2-64fa/LEGACY_AGENT_VERSION/NONE/UPGRADE_FROM/NONE/label/beaker/vendor/bundler/ruby/2.5.0/gems/beaker-4.9.0/lib/beaker/host/unix/pkg.rb:6815:02:34 /tmp/jenkins/workspace/enterprise_pez_integration-system-pezv2_smoke_2019.2.x/LAYOUT/ubuntu1604-64mcd-64compile_master.fa-windows2008r2-64fa/LEGACY_AGENT_VERSION/NONE/UPGRADE_FROM/NONE/label/beaker/vendor/bundler/ruby/2.5.0/gems/beaker-4.9.0/lib/beaker/host/unix/pkg.rb:9415:02:34 /tmp/jenkins/workspace/enterprise_pez_integration-system-pezv2_smoke_2019.2.x/LAYOUT/ubuntu1604-64mcd-64compile_master.fa-windows2008r2-64fa/LEGACY_AGENT_VERSION/NONE/UPGRADE_FROM/NONE/label/beaker/vendor/bundler/ruby/2.5.0/gems/beaker-4.9.0/lib/beaker/host_prebuilt_steps.rb:15715:02:34 /tmp/jenkins/workspace/enterprise_pez_integration-system-pezv2_smoke_2019.2.x/LAYOUT/ubuntu1604-64mcd-64compile_master.fa-windows2008r2-64fa/LEGACY_AGENT_VERSION/NONE/UPGRADE_FROM/NONE/label/beaker/vendor/bundler/ruby/2.5.0/gems/beaker-4.9.0/lib/beaker/host_prebuilt_steps.rb:15515:02:34
Jira (BOLT-1434) Bolt demo commands should support tab completion
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1434 Bolt demo commands should support tab completion Issue Type: Task Assignee: Unassigned Created: 2019/06/27 10:21 AM Priority: Normal Reporter: Lucy Wyman Now that bolt_demo_env uses a ruby library we can include Bolt bits like the option parser in order to support tab completing bolt commands and loaded modules in the demo. Part of this work should also be addressing how command input validation works - ideally we could use the option parser to raise a 'bolty' error for invalid commands and let the user retry. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1433) get_resources does not work with resource objects.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1433 get_resources does not work with resource objects. Change By: Alex Dreyer Sprint: Bolt Ready for Grooming 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314362.1561649732000.63731.1561655880254%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1433) get_resources does not work with resource objects.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1433
get_resources does not work with resource objects.
Change By:
Alex Dreyer
We document {{get_resources(localhost, Package)}} as an example of how to use get_resources and the function itself is defined to accept Resource objects in addition to strings. However Resource Types are not loaded during a plan so unless you quote the resource name and pass it as a string the plan will error.{{"Evaluation Error: Resource type not found: Package[...]}} Users should be able to use core types like {{Package}} and {{File}} or any custom types available on the module path with {{get_resources}} which may change how these objects behave more generally in the plan language.
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
Jira (FACT-1932) facter does not pick primary network interface properly on FreeBSD or OpenBSD
Title: Message Title Romain Tartière commented on FACT-1932 Re: facter does not pick primary network interface properly on FreeBSD or OpenBSD It looks like a fix was released in 3.14.1 released yesterday: https://github.com/puppetlabs/facter/pull/1788 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314338.1561645641000.63682.1561653420158%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1433) get_resources does not work with resource objects.
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1433 get_resources does not work with resource objects. Issue Type: New Feature Assignee: Unassigned Created: 2019/06/27 8:35 AM Priority: Normal Reporter: Alex Dreyer We document get_resources(localhost, Package) as an example of how to use get_resources and the function itself is defined to accept Resource objects in addition to strings. However Resource Types are not loaded during a plan so unless you quote the resource name and pass it as a string the plan will error. "Evaluation Error: Resource type not found: Package[...] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1423) Bolt actions hang over ssh transport when ProxyCommand is set in openssh config
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1423 Bolt actions hang over ssh transport when ProxyCommand is set in openssh config Change By: Cas Donoghue Assignee: Cas Donoghue 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313738.1561387259000.63451.1561646520715%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1932) facter does not pick primary network interface properly on FreeBSD or OpenBSD
Title: Message Title
Jim Pirzyk created an issue
Facter / FACT-1932
facter does not pick primary network interface properly on FreeBSD or OpenBSD
Issue Type:
Bug
Affects Versions:
FACT 3.14.0
Assignee:
Unassigned
Created:
2019/06/27 7:27 AM
Environment:
44>uname -a FreeBSD $HOST.$DOMAIN 11.2-RELEASE-p10 FreeBSD 11.2-RELEASE-p10 #0: Mon May 13 21:20:50 UTC 2019 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 amd64 amd64 FreeBSD 2>uname -a OpenBSD $HOST.$DOMAIN 6.4 GENERIC.MP#0 amd64
Priority:
Normal
Reporter:
Jim Pirzyk
The default primary interface choice on FreeBSD and OpenBSD is the first non localhost interface alphabetically. This does not really work when a system has more than one interface of differing types. For example: 33>netstat -i {{ Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll}} {{ lo0 16384 lo0 235832 0 0 235832 0 0}} {{ lo0 - localhost localhost 71739 - - 73701 - -}} {{ lo0 - fe80::%lo0/64 fe80::1%lo0 0 - - 0 - -}} {{ lo0 - your-net localhost 162449 - - 162672 - -}} {{ xn0 1500 00:16:3e:64:48:1a 165100162 0 0 35921722 0 0}} {{ xn0 - $IP $HOST 19261337 - - 33901320 - -}} {{ xn0 - fe80::%xn0/64 fe80::216:3eff:fe 0 - - 2 - -}} {{ xn0 - $IPv6 $DOMAIN 2341250 - - 2016716 - -}} {{ tun0 1500 tun0 575848 0 0 505291 0 0}} {{ tun0 - fe80::%tun0/6 fe80::216:3eff:fe 0 - - 1 - -}} {{ tun0 - 192.168.3.0/2 $HOST.vpn.$DOMAIN 575848 - - 505288 - -}} Facter will pick tun0 as the primary interface. facterversion => 3.14.0 ... networking => { ... primary => "tun0" } The logic that is used for picking the primary interface on Solaris works here too, just that the netstat -rn columns are different. on FreeBSD: 34>netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire default $ROUTER UGS xn0 127.0.0.1
Jira (PUP-9805) Prepare release announcement (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey commented on PUP-9805 Re: Prepare release announcement (Puppet Platform 6.6.0) Bill Tang do you have what you need here? It would be great to have this drafted and reviewed before end of the week. Thanks! 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314020.1561488075000.63418.1561643400179%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Ciprian Badescu commented on PUP-2169 Re: Not possible to manage SELinux file contexts via puppet in a sane way I think the performance issue of the fix was caused by calling Selinux.matchpathcon_fini after each file resource change. Instead we could call Selinux.matchpathcon_fini in transaction teardown by defining post_resource_eval on posix file provider. diff --git a/lib/puppet/provider/file/posix.rb b/lib/puppet/provider/file/posix.rb index 3bbe769baf..1754a2cab2 100644 --- a/lib/puppet/provider/file/posix.rb +++ b/lib/puppet/provider/file/posix.rb @@ -1,3 +1,5 @@ +require 'puppet/util/selinux' + Puppet::Type.type(:file).provide :posix do desc "Uses POSIX functionality to manage file ownership and permissions."@@ -133,4 +135,9 @@ Puppet::Type.type(:file).provide :posix do raise error end end
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Ciprian Badescu Assignee: Ciprian Badescu 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.31124.1396878028000.63340.1561640701424%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9647) Pip package provider does not handle pip executable paths with spaces
Title: Message Title Sean Millichamp updated an issue Puppet / PUP-9647 Pip package provider does not handle pip executable paths with spaces Change By: Sean Millichamp Summary: Pip package provider should use execute for Windows compatibility does not handle pip executable paths with spaces 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305257.133562000.63270.1561638780375%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
