Jira (PUP-10030) Update Public-facing Puppet docs to include CentOS 8 (amd64)
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10030 Update Public-facing Puppet docs to include CentOS 8 (amd64) Issue Type: Task Assignee: Unassigned Created: 2019/09/24 1:43 AM Priority: Normal Reporter: Mihai Buzgau Update Public-facing Puppet docs to include this platform Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-2968) Make it possible to namespace ruby-defined custom types
Title: Message Title David Schmitt assigned an issue to Unassigned Puppet / PUP-2968 Make it possible to namespace ruby-defined custom types Change By: David Schmitt Team: Network Automation Coremunity Assignee: David Schmitt 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.43382.1406157609000.110932.1569320460303%40Atlassian.JIRA.
Jira (PUP-10032) puppetserver foreground fails when started as non-root user without sudo permissions
Title: Message Title Yury Bushmelev created an issue Puppet / PUP-10032 puppetserver foreground fails when started as non-root user without sudo permissions Issue Type: Bug Assignee: Unassigned Created: 2019/09/24 3:30 AM Priority: Minor Reporter: Yury Bushmelev Puppet Version: 6.9.0 Puppet Server Version: 6.6.0 OS Name/Version: Ubuntu 16.04 LTS Today I found running puppetserver in container (I have dedicated CA there) is preventing puppetserver to run on host because of the way systemd unit is operating (forking + killmode I guess). So I decided to create 'proper' systemd unit with Type=simple and ExecStart using 'foreground' mode (note User=puppet there): [Unit] Description=puppetserver Service After=syslog.target network.target nss-lookup.target [Service]
Jira (PUP-10031) Update Public-facing Puppet docs to include Fedora 31 (amd64)
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10031 Update Public-facing Puppet docs to include Fedora 31 (amd64) Issue Type: Task Assignee: Unassigned Created: 2019/09/24 1:51 AM Priority: Normal Reporter: Mihai Buzgau Update Public-facing Puppet docs to include this platform Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-291) Build reference doc for transport schemas
Title: Message Title
David Schmitt updated an issue
Puppet Strings / PDOC-291
Build reference doc for transport schemas
Change By:
David Schmitt
To make use of the new Resource API transport schema information, puppet-strings should read and render the information from {{ register_transport }} to the REFERENCE.md.The existing code for parsing {{ register_type }} can be used as a template.
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.296968.1550757016000.110953.1569321840110%40Atlassian.JIRA.
Jira (PDOC-291) Build reference doc for transport schemas
Title: Message Title David Schmitt moved an issue Puppet Strings / PDOC-291 Build reference doc for transport schemas Change By: David Schmitt Key: FM PDOC - 7816 291 Project: Modules [Internal] Puppet Strings 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.296968.1550757016000.110952.1569321780136%40Atlassian.JIRA.
Jira (FACT-2016) Add the scope of found ipv6 addresses (global/linklocal/...) as a fact
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Facter / FACT-2016 Add the scope of found ipv6 addresses (global/linklocal/...) as a fact 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324361.1568209514000.14.1569336480254%40Atlassian.JIRA.
Jira (FACT-2039) Os.family for Soalaris
Title: Message Title Alexandru Popa created an issue Facter / FACT-2039 Os.family for Soalaris Issue Type: Task Assignee: Unassigned Created: 2019/09/24 6:31 AM Priority: Normal Reporter: Alexandru Popa Create os.family for Solaris Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-2040) Memory fact for Solaris
Title: Message Title Alexandru Popa created an issue Facter / FACT-2040 Memory fact for Solaris Issue Type: Task Assignee: Unassigned Created: 2019/09/24 6:32 AM Priority: Normal Reporter: Alexandru Popa 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-2029) Release os fact for Solaris
Title: Message Title Alexandru Popa updated an issue Facter / FACT-2029 Release os fact for Solaris Change By: Alexandru Popa Summary: Full Release os fact for Solaris 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.325375.1568891051000.111030.1569331740615%40Atlassian.JIRA.
Jira (FACT-2037) Os.architecture for Solaris
Title: Message Title Alexandru Popa created an issue Facter / FACT-2037 Os.architecture for Solaris Issue Type: Task Assignee: Unassigned Created: 2019/09/24 6:30 AM Priority: Normal Reporter: Alexandru Popa Create os.architecture for Solaris Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-2038) Os.hardware for Solaris
Title: Message Title Alexandru Popa created an issue Facter / FACT-2038 Os.hardware for Solaris Issue Type: Task Assignee: Unassigned Created: 2019/09/24 6:30 AM Priority: Normal Reporter: Alexandru Popa Create os.hardware for Solaris Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title Thomas Hallgren commented on PUP-10029 Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow The code doesn't understand that Puppet::Datatypes::Error is a known type. Does the same thing happen if you precede this with require 'puppet/datatypes' (that's where the type registration happens)? 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.325693.1569277631000.110990.1569328140298%40Atlassian.JIRA.
Jira (PDB-4512) See if we can drop joins that a query doesn't need in some cases
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4512 See if we can drop joins that a query doesn't need in some cases Change By: Rob Browning Assignee: Rob Browning 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.325806.1569343323000.111451.1569343381242%40Atlassian.JIRA.
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title
Joshua Partlow commented on PUP-10029
Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Hmm, that's interesting, that does work:
[root@wuh7cxdfusfnult ~]# cat test.rb
require 'puppet'
Puppet.initialize_settings
env = Puppet.lookup(:environments).get(Puppet[:environment])
Puppet.override(:current_environment => env, :loaders => Puppet::Pops::Loaders.new(env)) do
require 'puppet/datatypes/error'
e = Puppet::DataTypes::Error.new('foo')
puts e.to_s
end
[root@wuh7cxdfusfnult ~]# /opt/puppetlabs/puppet/bin/ruby test.rb
Error({'msg' => 'foo'})
So the issue I'm seeing appears to be a case of Bolt handling an error instance outside of a context with loaders available, here. Unless you consider the Puppet::DataTypes::Error.to_s requiring loaders a bug in and of itself?
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title Joshua Partlow commented on PUP-10029 Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow Hi Thomas Hallgren, yeah, I was originally trying to require 'puppet/datatypes/error', but that has some add behavior, see below: [root@wuh7cxdfusfnult ~]# /opt/puppetlabs/puppet/bin/irb irb(main):001:0> require 'puppet' => true irb(main):002:0> require 'puppet/datatypes' => false irb(main):003:0> require 'puppet/datatypes/error' Traceback (most recent call last): 7: from /opt/puppetlabs/puppet/bin/irb:11:in `' 6: from (irb):3 5: from /opt/puppetlabs/puppet/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 4: from /opt/puppetlabs/puppet/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 3: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/datatypes/error.rb:1:in `'
Jira (PDB-4512) See if we can drop joins that a query doesn't need in some cases
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4512 See if we can drop joins that a query doesn't need in some cases Issue Type: Improvement Assignee: Unassigned Created: 2019/09/24 9:42 AM Priority: Normal Reporter: Rob Browning It looks like this may dramatically speed up some queries (and correspondingly decrease the load on pg), but there are plenty of questions. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title
Henrik Lindberg commented on PUP-10029
Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Joshua Partlow That means there are no loaders bound in the puppet context. The logic you are executing ends up in this method to get the implementation registry - and since there are no loaders in the context you end up with the nil loaders.
def self.implementation_registry
loaders = Puppet.lookup(:loaders) { nil }
loaders.nil? ? nil : loaders.implementation_registry
end
You can probably initialize it like apply does - like this:
env = Puppet.lookup(:environments).get(Puppet[:environment])
Puppet.override(:current_environment => env, :loaders => Puppet::Pops::Loaders.new(env)) do
# Do your stuff here
end
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title Josh Cooper commented on PUP-10029 Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow I'd expect puppet to fail more gracefully if there isn't a current environment. 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.325693.1569277631000.112030.1569350340314%40Atlassian.JIRA.
Jira (PUP-10028) yumrepo misses support for minrate
Title: Message Title Rob Braden updated an issue Puppet / PUP-10028 yumrepo misses support for minrate Change By: Rob Braden Sprint: Coremunity Grooming 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.325379.1568897737000.112051.1569350881479%40Atlassian.JIRA.
Jira (PUP-10028) yumrepo misses support for minrate
Title: Message Title Rob Braden assigned an issue to Jorie Tappa Puppet / PUP-10028 yumrepo misses support for minrate Change By: Rob Braden Assignee: Jorie Tappa 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.325379.1568897737000.112046.1569350881446%40Atlassian.JIRA.
Jira (PUP-9732) Client should cache successful host address for at least the length of a Puppet run
Title: Message Title Rob Braden updated an issue Puppet / PUP-9732 Client should cache successful host address for at least the length of a Puppet run Change By: Rob Braden Sprint: Coremunity Hopper 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.112059.1569350881542%40Atlassian.JIRA.
Jira (PUP-10028) yumrepo misses support for minrate
Title: Message Title Rob Braden updated an issue Puppet / PUP-10028 yumrepo misses support for minrate Change By: Rob Braden Sprint: Coremunity Grooming 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.325379.1568897737000.112055.1569350881516%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Rob Braden updated an issue Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Change By: Rob Braden Sprint: Coremunity Hopper 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.112066.1569350881576%40Atlassian.JIRA.
Jira (PUP-9933) Make indirector settings thread-local
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9933 Make indirector settings thread-local Change By: Maggie Dreyer Fix Version/s: SERVER 6.6.1 Fix Version/s: PUP 6.10.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.306744.1556579701000.111796.1569347040721%40Atlassian.JIRA.
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title Joshua Partlow commented on PUP-10029 Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow I opened https://github.com/puppetlabs/bolt/issues/1242 to discuss how to handle this issue in 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325693.1569277631000.111723.1569346321016%40Atlassian.JIRA.
Jira (PUP-1537) Dpkg package provider misbehaving for held package with specific version
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1537 Dpkg package provider misbehaving for held package with specific version Change By: Josh Cooper 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.24894.1391021944000.112713.1569362940420%40Atlassian.JIRA.
Jira (PUP-10037) Add CA HTTP service
Title: Message Title Josh Cooper created an issue Puppet / PUP-10037 Add CA HTTP service Issue Type: Improvement Assignee: Unassigned Created: 2019/09/24 4:13 PM Priority: Normal Reporter: Josh Cooper 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-10033) Implement basic HTTP client
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10033
Implement basic HTTP client
Change By:
Josh Cooper
Implement an httpclient abstraction over Net::HTTP for making GET requests. It should:* Return puppet response objects, not Net::HTTP* Raise puppet exceptions, not Net::HTTP exceptions* Use persistent HTTP connections* Stream response body* Observe connection and read timeouts* Observe proxy settings or env variables* Send {{User-Agent}} and {{X-Puppet-Version}} HTTP headers* Support gzip and inflate de/compression* Support server basic authentication* Escape query parameters and request paths* Uses the default puppet ssl context, which contains the verification mode, CA certs, CRLs, etc
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
Jira (PUP-10040) Convert ssl state machine to using http client
Title: Message Title Josh Cooper created an issue Puppet / PUP-10040 Convert ssl state machine to using http client Issue Type: Improvement Assignee: Unassigned Created: 2019/09/24 4:43 PM Priority: Normal Reporter: Josh Cooper Change ssl state machine to use http client instead of Puppet::Rest Deprecate the latter. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10040) Convert ssl state machine and application to using http client
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10040
Convert ssl state machine and application to using http client
Change By:
Josh Cooper
Change ssl state machine to use http client instead of {{Puppet::Rest}} Change {{puppet ssl}} to use http client instead of {{Puppet::Rest}} Deprecate the latter. {{Puppet::Rest}}
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.326145.1569368598000.112969.1569368761060%40Atlassian.JIRA.
Jira (PUP-10040) Convert ssl state machine and application to using http client
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10040 Convert ssl state machine and application to using http client Change By: Josh Cooper Summary: Convert ssl state machine and application to using http client 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.326145.1569368598000.112966.1569368700251%40Atlassian.JIRA.
Jira (PUP-8146) consider combined merge strategies for lookup_option with patterns
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8146 consider combined merge strategies for lookup_option with patterns Change By: Maggie Dreyer Component/s: 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.221398.1510332362000.112977.1569368761097%40Atlassian.JIRA.
Jira (PUP-9346) Change default value of hostcsr setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9346 Change default value of hostcsr setting Change By: Josh Cooper Fix Version/s: PUP 7.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.287916.1544223816000.112262.1569355920565%40Atlassian.JIRA.
Jira (PUP-9566) Allow to send extra headers when requesting a catalog compilation
Title: Message Title Josh Cooper commented on PUP-9566 Re: Allow to send extra headers when requesting a catalog compilation We are working on improvements to the agent's HTTP code, and it will be fairly straightforward to add additional HTTP headers when the agent is talking to the puppetserver service. 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.300606.1552923936000.113003.1569369240664%40Atlassian.JIRA.
Jira (PUP-10037) Add CA HTTP service
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10037
Add CA HTTP service
Change By:
Josh Cooper
Implement a CA service with support for the following:{noformat}GET certificateGET certificate_revocation_listPUT certificate_request{noformat}* All bodies are de/serialized as UTF-8 and {{Content-Type: text/plain}}* CRL download allows an optional {{If-Modified-Since}} header* Uses {{puppet-ca/v1}} prefix
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.326128.156936681.112930.1569367080222%40Atlassian.JIRA.
Jira (PUP-10038) Add Report HTTP service
Title: Message Title Josh Cooper created an issue Puppet / PUP-10038 Add Report HTTP service Issue Type: Improvement Assignee: Unassigned Created: 2019/09/24 4:26 PM Priority: Normal Reporter: Josh Cooper Implement a report service with support for the following: PUT report Include the report's environment as a query parameter Serialize request body as JSON with Content-Type: application/json Use puppet/v3 prefix Accept response content as application/json, application/x-msgpack, text/pson If we fail to send the report, the server version is < 5 and the current serialization format is not pson, then emit an error that preferred_serialization_format should be set to pson.
Jira (PUP-10033) Implement basic HTTP client
Title: Message Title Josh Cooper created an issue Puppet / PUP-10033 Implement basic HTTP client Issue Type: Improvement Assignee: Unassigned Created: 2019/09/24 3:51 PM Priority: Normal Reporter: Josh Cooper Implement an httpclient abstraction over Net::HTTP for making GET requests. It should: Return puppet response objects, not Net::HTTP Raise puppet exceptions, not Net::HTTP exceptions Use persistent HTTP connections Observe connection and read timeouts Observe proxy settings or env variables Send User-Agent and X-Puppet-Version HTTP headers Support gzip and inflate de/compression Support server basic authentication Escape query parameters and request paths Uses the default puppet ssl context, which contains the verification mode, CA certs, CRLs, etc
Jira (PUP-10036) Implement HTTP retry after
Title: Message Title Josh Cooper created an issue Puppet / PUP-10036 Implement HTTP retry after Issue Type: Improvement Assignee: Unassigned Created: 2019/09/24 4:10 PM Priority: Normal Reporter: Josh Cooper Add support for retry-after using the existing connection code. It supports: Handles HTTP responses 429, 503 Parse the Retry-After header as seconds or an RFC 2822 date If missing, stop retry loop Don't wait more than the agent's runinterval to retry Retry 0 means to not wait, and retry immediately. Add Comment
Jira (PUP-10039) Add settings network resolver
Title: Message Title Josh Cooper created an issue Puppet / PUP-10039 Add settings network resolver Issue Type: Improvement Assignee: Unassigned Created: 2019/09/24 4:31 PM Priority: Normal Reporter: Josh Cooper Resolve the host and port for a service based on its name and the current Puppet settings. The CA service should resolve to Puppet[:ca_server] and Puppet[:ca_port], which default to the Puppet[:server] and Puppet[:masterport]. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9990) no_proxy config setting is overridden by http_proxy environment variable
Title: Message Title Josh Cooper commented on PUP-9990 Re: no_proxy config setting is overridden by http_proxy environment variable Dhumala can you open a new ticket and provide more detail about why the issue is not solved, including the result of running puppet agent -t --http_debug? 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.322755.1567086003000.112724.1569363180220%40Atlassian.JIRA.
Jira (PUP-10034) Implement DELETE, HEAD, PUT, POST
Title: Message Title Josh Cooper created an issue Puppet / PUP-10034 Implement DELETE, HEAD, PUT, POST Issue Type: Improvement Assignee: Unassigned Created: 2019/09/24 3:52 PM Priority: Normal Reporter: Josh Cooper Add support for DELETE, HEAD, PUT, POST requests. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10039) Add network resolvers
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10039 Add network resolvers Change By: Josh Cooper Summary: Add settings network resolver resolvers 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.326143.1569367897000.112958.1569368040294%40Atlassian.JIRA.
Jira (PUP-10041) Switch PMT to use puppet's http client
Title: Message Title Josh Cooper created an issue Puppet / PUP-10041 Switch PMT to use puppet's http client Issue Type: Improvement Assignee: Unassigned Created: 2019/09/24 4:47 PM Priority: Normal Reporter: Josh Cooper Switch the PMT to using puppet's HTTP client instead of creating its own Net::HTTP objects. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8246) Consolidate http client connection implementations
Title: Message Title Josh Cooper commented on PUP-8246 Re: Consolidate http client connection implementations The work required to do this has been split into different tickets in this epic, so this ticket can be closed. 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.226489.1513193082000.112985.1569368880595%40Atlassian.JIRA.
Jira (PUP-8146) consider combined merge strategies for lookup_option with patterns
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8146 consider combined merge strategies for lookup_option with patterns Change By: Maggie Dreyer Labels: 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.221398.1510332362000.112979.1569368820212%40Atlassian.JIRA.
Jira (PUP-10035) Follow HTTP redirects
Title: Message Title Josh Cooper created an issue Puppet / PUP-10035 Follow HTTP redirects Issue Type: Improvement Assignee: Unassigned Created: 2019/09/24 4:04 PM Priority: Normal Reporter: Josh Cooper Implement HTTP redirection based on puppet's current behavior: If the HTTP response code is 301, 302, 307, then follow the redirect using the Location response header. Codes 300, 303, 304, 305, and 308 are treated as errors Follow redirects for all HTTP methods, even unsafe ones like PUT Always preserve the HTTP method, for example, never switch from POST to GET Preserve all headers, except Host. Preserve all query parameters Raise an exception if we redirect more than the limit, which defaults to 10 Redirection loops are handled by the redirect limit Additionally responses 301, 302, and 307 may have a response body. The response body must be fully read/drained when using persistent connections, otherwise, the next request will read the body from the redirected request.
Jira (PUP-10039) Add network resolvers
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10039
Add network resolvers
Change By:
Josh Cooper
Resolve Each resolver should resolve the host and port for a service based on its name and the current Puppet settings offer multiple candidates . * The settings resolve should use the corresponding Puppet settings. For example, the CA service should resolve to {{Puppet[:ca_server]}} and {{Puppet[:ca_port]}}, which default to the {{Puppet[:server]}} and {{Puppet[:masterport]}}. * The server_list resolver should use {{Puppet[:server_list]}}* The SRV resolver should use the service name and SRV domain
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-4513) puppetserver fails to connect to puppetdb 6.6.0
Title: Message Title Vadym Chepkov created an issue PuppetDB / PDB-4513 puppetserver fails to connect to puppetdb 6.6.0 Issue Type: Bug Affects Versions: PDB 6.6.0 Assignee: Unassigned Components: PuppetDB Created: 2019/09/24 5:15 PM Priority: Normal Reporter: Vadym Chepkov Fresh install with the following components puppet-agent-6.9.0-1.el7.x86_64 puppetserver-6.6.0-1.el7.noarch puppetdb-6.6.0-1.el7.noarch puppetdb-termini-6.6.0-1.el7.noarch puppet server fails to connect to puppetdb and compile a catalog ``` puppet agent -t Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 500 on SERVER: Server Error: Could not retrieve facts for master.localdomain: Failed to find facts from PuppetDB at master.localdomain:8140: Failed to execute '/pdb/query/v4/nodes/master.localdomain/facts' on at least 1 of the following 'server_urls': https://master.localdomain:8081 Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Loading facts Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Failed to execute '/pdb/cmd/v1?checksum=cff02e6fb7cbf363fd52eac951b5c42e09a0718a=5=master.localdomain=replace_facts=2019-09-25T00:14:42.328Z' on at least 1 of the following 'server_urls': https://master.localdomain:8081 Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run ```
Jira (PDB-4513) puppetserver fails to connect to puppetdb 6.6.0
Title: Message Title Vadym Chepkov updated an issue PuppetDB / PDB-4513 puppetserver fails to connect to puppetdb 6.6.0 Change By: Vadym Chepkov Attachment: puppetserver.log 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.326149.1569370509000.113070.1569370680241%40Atlassian.JIRA.
