Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Moses Mendoza assigned an issue to Ethan Brown Puppet / PUP-7251 gzip decompression mangles utf-8 content in catalog Change By: Moses Mendoza Assignee: Moses Mendoza Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7261) Add/Honor charset parameter in Content-Type header
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7261 Add/Honor charset parameter in Content-Type header Change By: Moses Mendoza Summary: Add /Honor charset parameter to in Content-Type header Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7261) Add charset parameter to Content-Type header
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7261 Add charset parameter to Content-Type header Issue Type: Bug Assignee: Unassigned Created: 2017/02/23 4:29 PM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Moses Mendoza We do not currently honor the charset parameter in Puppet's Network::Http::Compression library, instead defaulting to always encoding as Binary. A more correct solution would be to honor charset in the Content-Type header, ie in Content-Type: text/json; charset=utf-8. Some generic background: https://www.w3.org/International/articles/http-charset/index Add Comment
Jira (PUP-7261) Add charset parameter to Content-Type header
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7261 Add charset parameter to Content-Type header Change By: Moses Mendoza Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Ethan Brown commented on PUP-7251 Re: gzip decompression mangles utf-8 content in catalog FWIW, PSON is binary per https://docs.puppet.com/puppet/latest/http_api/pson.html JSON.parse appears to properly handle a BINARY string in Ruby-land, so I think the strings returned from GZip decompression can still be BINARY strings. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7260) Remove puppet inspect and stop honoring the audit metaparameter
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7260 Remove puppet inspect and stop honoring the audit metaparameter Change By: Moses Mendoza This was added for one customer and is no longer used or supported in PE. We should remove it. *Note** We will not fail catalog compilation given the audit parameter - just ignore it Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7260) Remove puppet inspect and stop honoring the audit metaparameter
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7260 Remove puppet inspect and stop honoring the audit metaparameter Change By: Moses Mendoza Summary: Remove puppet inspect and stop honoring the audit metaparameter Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Ethan Brown commented on PUP-7251 Re: gzip decompression mangles utf-8 content in catalog I have a PR up for some more explicit encoding changes and I had a proposed change, but: My fix was wrong - some details written at https://github.com/puppetlabs/puppet/pull/5636#discussion_r102799207 I think we should fix it with this PR as we have a real issue to point to, rather than speculative remarks about encoding not being specified explicitly Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7260) Remove puppet inspect and the audit metaparameter
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7260 Remove puppet inspect and the audit metaparameter Issue Type: Task Assignee: Unassigned Created: 2017/02/23 3:28 PM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Moses Mendoza This was added for one customer and is no longer used or supported in PE. We should remove it. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-893 Deprecate puppet inspect and the audit metaparameter Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 4.9.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6060) Change node_cache_terminus default to nil
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6060 Change node_cache_terminus default to nil Change By: Moses Mendoza Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6060) Change node_cache_terminus default to nil
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6060 Change node_cache_terminus default to nil Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5756) Remove usage of win32-eventlog gem
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-5756 Remove usage of win32-eventlog gem Change By: Moses Mendoza Fix Version/s: PUP 4.y Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5756) Remove usage of win32-eventlog gem
Title: Message Title Moses Mendoza assigned an issue to Moses Mendoza Puppet / PUP-5756 Remove usage of win32-eventlog gem Change By: Moses Mendoza Assignee: Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5756) Remove usage of win32-eventlog gem
Title: Message Title Moses Mendoza commented on PUP-5756 Re: Remove usage of win32-eventlog gem wip branch: https://github.com/puppetlabs/puppet/pull/5509 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6893) Remove Ruby 1.9.3 support
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6893 Remove Ruby 1.9.3 support Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7259) Ensure JSON is preferred serialization format in various termini
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7259 Ensure JSON is preferred serialization format in various termini Issue Type: Task Assignee: Unassigned Created: 2017/02/23 3:00 PM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Moses Mendoza This is done in various ways, but here's an example: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/transaction/report.rb#L392-L398 JSON needs to be both added as supported format and preferred over other formats. Add Comment
Jira (PUP-7259) Ensure JSON is preferred serialization format in various termini/serializers
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7259 Ensure JSON is preferred serialization format in various termini/serializers Change By: Moses Mendoza Summary: Ensure JSON is preferred serialization format in various termini /serializers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7254) Transient: HOCON gem fails to install during puppet spec tests
Title: Message Title Ethan Brown commented on PUP-7254 Re: Transient: HOCON gem fails to install during puppet spec tests Once QENG-4787 has been merged, I believe this ticket can be closed - we can always reopen if the above theory proves incorrect in any way. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3852) Switch from PSON to JSON as default serialization format
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3852 Switch from PSON to JSON as default serialization format Change By: Moses Mendoza Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3852) Switch from PSON to JSON as default serialization format
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3852 Switch from PSON to JSON as default serialization format Change By: Moses Mendoza Priority: Normal Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7258) Ensure JSON on Agents defaults to native implementation
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7258 Ensure JSON on Agents defaults to native implementation Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7255) SPIKE: Enable newer agents to talk to older masters
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7255 SPIKE: Enable newer agents to talk to older masters Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7258) Ensure JSON on Agents defaults to native implementation
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7258 Ensure JSON on Agents defaults to native implementation Issue Type: Task Assignee: Unassigned Created: 2017/02/23 2:45 PM Priority: Normal Reporter: Moses Mendoza Query JSON::Parser to ensure result is JSON::Ext::Parser not JSON::Pure::Parser Same for Generators Can take the form of a spec test or just a single validation prior to ship Add Comment
Jira (PUP-7257) Don't superfluously CGI encode facts facts_for_uploading
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7257 Don't superfluously CGI encode facts facts_for_uploading Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7256) Ensure console pretty printing maintains pre-JSON formatting
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7256 Ensure console pretty printing maintains pre-JSON formatting Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7254) Transient: HOCON gem fails to install during puppet spec tests
Title: Message Title Ethan Brown commented on PUP-7254 Re: Transient: HOCON gem fails to install during puppet spec tests It looks like the source of this problem is a particular spec node running multiple executors concurrently, and the Ruby environment getting corrupted by Pik as a result. Note that the failing job in this case has requested 2.3.1.1-x64 (based on the matrix), yet the callstack is propagated from bundler on Ruby 1.9.3. 08:28:11 C:\jenkins\workspace\platform_puppet_unit-ruby-win_master\R\ruby-2.3.1.1-x64\S\unit-win2012>call pik use ruby-2.3.1.1-x64 08:28:14 pik 0.3.0.pre on Microsoft Windows [Version 6.3.9600] 08:28:14 by Gordon Thiesfeld (gthiesf...@gmail.com) 08:28:14 08:28:14 08:28:14 ruby: 08:28:14 interpreter: "ruby" 08:28:14 version: "2.3.1" 08:28:14 date: ""
Jira (PUP-3852) Switch from PSON to JSON as default serialization format
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3852 Switch from PSON to JSON as default serialization format Change By: Moses Mendoza Epic Colour: ghx-label-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3852) Switch from PSON to JSON as default serialization format
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3852 Switch from PSON to JSON as default serialization format Change By: Moses Mendoza Epic Name: switch pson Switch from PSON to json JSON as default serialization format Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3852) Switch from PSON to JSON as default serialization format
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3852 Switch from PSON to JSON as default serialization format Change By: Moses Mendoza Summary: Switch from PSON to JSON as default serialization format Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7252) mcollective_service_manager acceptance test fails frequently on OSX 10.10
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7252 mcollective_service_manager acceptance test fails frequently on OSX 10.10 Change By: Maggie Dreyer Sprint: AP 2017-03-08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7252) mcollective_service_manager acceptance test fails frequently on OSX 10.10
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7252 mcollective_service_manager acceptance test fails frequently on OSX 10.10 Change By: Maggie Dreyer Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7252) mcollective_service_manager acceptance test fails frequently on OSX 10.10
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-7252 mcollective_service_manager acceptance test fails frequently on OSX 10.10 Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7257) Don't superfluously CGI encode facts facts_for_uploading
Title: Message Title
Moses Mendoza created an issue
Puppet / PUP-7257
Don't superfluously CGI encode facts facts_for_uploading
Issue Type:
Task
Assignee:
Unassigned
Created:
2017/02/23 2:39 PM
Priority:
Normal
Reporter:
Moses Mendoza
At https://github.com/puppetlabs/puppet/blob/master/lib/puppet/configurer/fact_handler.rb#L35 we "extra" CGI.escape the facts content we are going to include in the body that gets sent to the master.
We do not need to do this. We should just url encode the whole body that gets sent.
Update (or equivalent):
{:facts_format => :pson, :facts => CGI.escape(text)}
to something like:
{:facts_format => :json, :facts => facts.to_json}
Jira (PUP-7256) Ensure console pretty printing maintains pre-JSON formatting
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7256 Ensure console pretty printing maintains pre-JSON formatting Issue Type: Task Assignee: Unassigned Created: 2017/02/23 2:32 PM Priority: Normal Reporter: Moses Mendoza The console is an output format * When "rendering" to console after making JSON the default we have to ensure that we do not change the way this is printed from how it was when PSON was the default Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7255) SPIKE: Enable newer agents to talk to older masters
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7255 SPIKE: Enable newer agents to talk to older masters Issue Type: Task Assignee: Unassigned Created: 2017/02/23 2:30 PM Priority: Blocker Reporter: Moses Mendoza If a newer agent speaks JSON by default and the older master speaks PSON by default when an agent submits its report to the master the first time it may send a JSON report the master cannot understand. Options to consider Some sort of initial protocol negotiation before the report is sent establishing the mutually agreed upon format Leverage preferred_serialization_format setting (or another applicable setting) to switch the agent to speaking an older format by default Add Comment
Jira (PUP-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3551 Sanitize non-UTF-8 data in run reports Change By: Moses Mendoza Summary: Strip Sanitize non-UTF-8 data from in run reports Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3551 Sanitize non-UTF-8 data in run reports Change By: Moses Mendoza One of the consequences of using JSON and the existing serialization of reports is that it won't be able to handle non-UTF-8 showing up. Non-UTF-8 data would not show up from the catalog information (since it also has the same UTF-8 restriction), but it can show up in the output of the commands that puppet runs as part of applying a catalog.Puppet *must* be able to send the report about the run. It can't be stopped by some data that prevents a particular serialization mechanism from working correctly. In order to send the report puppet should strip any non-UTF-8 sequences in the report and replace them with something that can be serialized. *In Scope** Investigate use of replacement characters for invalid UTF-8 byte sequences in report data where applicable* Ensure that report is sent (or at least is not hindered by non-UTF-8 data) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3552 Use application/json Content-Type/Accepts instead of PSON Change By: Moses Mendoza Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3552 Use application/json Content-Type/Accepts instead of PSON Change By: Moses Mendoza Issue Type: Improvement Task Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3552 Use application/json Content-Type/Accepts instead of PSON Change By: Moses Mendoza Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3552 Use application/json Content-Type/Accepts instead of PSON Change By: Moses Mendoza Summary: Use application/json Content-Type/ Accept Accepts instead of PSON Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3540) Remove all uses of PSON and replace with JSON
Title: Message Title Moses Mendoza commented on PUP-3540 Re: Remove all uses of PSON and replace with JSON Note - we're not going to stop using PSON - we're just going to switch to JSON as default in PUP 5 timeframe Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3852) Switch from PSON to JSON
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3852 Switch from PSON to JSON Change By: Moses Mendoza Switch the default serialization format across Puppet, Puppet Server and PuppetDB to JSON. *Requirements* (move to tickets)* Do not break pretty printing to console (see PUP-3706) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4755) Puppet config set --section main foo bar does not set or respect an empty [main] section
Title: Message Title Brian Call commented on PUP-4755 Re: Puppet config set --section main foo bar does not set or respect an empty [main] section FYI, this is how the OS X GUI installer sets the settings in puppet.conf, here: https://github.com/puppetlabs/puppet-agent/blob/master/resources/osx/postinstall-extras#L27 If you're managing puppet.conf with ini_setting resources using puppetlabs-inifile, this results in a new [main] section with the puppet-managed settings in addition to the pkg-placed settings, which are now orphaned without a section. Perhaps seed puppet.conf with a [main] section in the postinstall script before running `puppet config set `? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3852) Switch from PSON to JSON
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3852 Switch from PSON to JSON Change By: Moses Mendoza This is just a placeholder to make sure that this potential work is visible on Switch the default serialization format across Puppet , Puppet Server jira board. Need to find the existing tickets and link them in here PuppetDB to JSON . Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3852) Switch from PSON to JSON
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3852 Switch from PSON to JSON Change By: Moses Mendoza Scrum Team: Puppet Server Epic Status: To Do Epic Name: switch pson to json Status: Ready for Engineering Open Workflow: Scrum Team Engineering Epic Workflow Issue Type: Story Epic Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-3852) Switch from PSON to JSON
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3852 Switch from PSON to JSON Change By: Moses Mendoza Team/s: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3307) Make sure queue depth (and possibly other stats) reflect read errors
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3307 Make sure queue depth (and possibly other stats) reflect read errors Issue Type: Bug Assignee: Unassigned Created: 2017/02/23 2:12 PM Labels: maintenance Priority: Normal Reporter: Rob Browning Everything might be fine, but I had ~60k messages in the queue and then ran this inside the stockpile/q dir "find -type f | xargs rm". pdb recovered just fine, but then I noticed that the jmx global.depth remained up around 60k. This ticket is just one point for investigation, and fix if it's trivial. If not, we'll file a follow up ticket. Add Comment
Jira (PDB-2950) Bump required postgres to 9.6
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2950 Bump required postgres to 9.6 Change By: Karen Van der Veer Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7252) mcollective_service_manager acceptance test fails frequently on OSX 10.10
Title: Message Title Maggie Dreyer commented on PUP-7252 Re: mcollective_service_manager acceptance test fails frequently on OSX 10.10 This appears to be related to https://github.com/puppetlabs/puppet/pull/4584. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3306) Remove the vestigial clojure version of the PuppetDB CLI
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3306 Remove the vestigial clojure version of the PuppetDB CLI Change By: Karen Van der Veer Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7252) mcollective_service_manager acceptance test fails frequently on OSX 10.10
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7252 mcollective_service_manager acceptance test fails frequently on OSX 10.10 Change By: Maggie Dreyer Issue Type: Bug CI Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7254) Transient: HOCON gem fails to install during puppet spec tests
Title: Message Title
Ethan Brown commented on PUP-7254
Re: Transient: HOCON gem fails to install during puppet spec tests
We have seen this happen a few times. The problem involves installation of the gem, which contains a fixture file that has a Unicode name and Unicode contents - https://github.com/puppetlabs/ruby-hocon/blob/master/spec/fixtures/test_utils/resources/%E1%9A%A0%E1%9B%87%E1%9A%BB.conf (note that some web browsers may not display the filename or contents properly)
It's unclear why the gem fails to install / extract the file ᚠᛇᚻ.conf sometimes, but not all times - the Jenkins job output will typically indicate {{a a a ;.conf}} in failure scenarios (as multiple translation layers of different encodings from Ruby, stdout, Jenkins, HTTP, etc) are mangling the name of the file. Previous attempts to look at the workspace / filesystem of the failing host have not proven fruitful as the directory has been missing upon inspection of the actual host.
Some more research will need to take place to figure out what the actual problem is / how to address it.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7233) Puppet configuration for storage(Netapp cluster mode)
Title: Message Title Geoff Nichols commented on PUP-7233 Re: Puppet configuration for storage(Netapp cluster mode) Hi hrushikesh, we don't know the answer to your question, but would like to help connect you to the information you need. Would you mind posing your question on ask.puppet.com? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Moses Mendoza commented on PUP-7251 Re: gzip decompression mangles utf-8 content in catalog Note - while BINARY is the right thing for text/pson, and it likely is the right thing for text/json, when we switch default serialization to json we may want to revisit and do something like checking the content type and switching to UTF-8 if its JSON. cc Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7254) Transient: HOCON gem fails to install during puppet spec tests
Title: Message Title Maggie Dreyer commented on PUP-7254 Re: Transient: HOCON gem fails to install during puppet spec tests Example of failed job: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent%20components/view/puppet/job/platform_puppet_unit-ruby-win_master/183/R=ruby-2.3.1.1-x64,S=unit-win2012/console Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7254) Transient: HOCON gem fails to install during puppet spec tests
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-7254 Transient: HOCON gem fails to install during puppet spec tests Issue Type: Bug Assignee: Unassigned Created: 2017/02/23 11:44 AM Priority: Normal Reporter: Maggie Dreyer Sometimes the setup for the Puppet spec tests in the component pipeline will fail when trying to install the hocon gem with the following error: Bundler::InstallError: Errno::EINVAL: Invalid argument - C:/8161-183-0/gems/gems/hocon-1.2.4/spec/fixtures/test_utils/resources/a a a ;.conf This is a file with a Unicode name, which has been rendered incorrectly. The two times this has appeared, it has gone away on a rerun of the job. Add
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7251 gzip decompression mangles utf-8 content in catalog Change By: Moses Mendoza Sprint: AP Grooming 2017-03-08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7251 gzip decompression mangles utf-8 content in catalog Change By: Moses Mendoza Fix Version/s: PUP 4.9.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7251 gzip decompression mangles utf-8 content in catalog Change By: Moses Mendoza Labels: utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7251 gzip decompression mangles utf-8 content in catalog Change By: Moses Mendoza Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7251 gzip decompression mangles utf-8 content in catalog Change By: Moses Mendoza Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-7251
gzip decompression mangles utf-8 content in catalog
Change By:
Moses Mendoza
It appears a regression in UTF-8 handling by Puppet was introduced when gzip compression was fixed in trapperkeeper / puppet server via https://tickets.puppetlabs.com/browse/TK-429This was discovered in investigating a local failure of the agent 1.9 series against https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/file/ticket_6448_file_with_utf8_source.rb against puppet server 2.7.2.master-0.1SNAPSHOT.2017.02.22T1106. We are not seeing this failure in CI presumably because CI is pinned to a released version of puppet server without this change.The catalog returned by the server in this test contains a UTF-8 named file resource,{code}"\u9759\u7864"{code}Prior to the change, the catalog received by the agent was uncompressed and contained:{code}[5] pry(#)> response.body=> "{\"tags\":[\"settings\"],\"name\":\"cpq55y0vuphp44u.delivery.puppetlabs.net\",\"version\":1487871618,\"code_id\":null,\"catalog_uuid\":\"cf89d5fd-ebdf-426a-832b-68812066c165\",\"catalog_format\":1,\"environment\":\"ticket_6448_file_with_utf8_source_j9w3rhmk\",\"resources\":[{\"type\":\"Stage\",\"title\":\"main\",\"tags\":[\"stage\"],\"exported\":false,\"parameters\":{\"name\":\"main\"}},{\"type\":\"Class\",\"title\":\"Settings\",\"tags\":[\"class\",\"settings\"],\"exported\":false},{\"type\":\"Class\",\"title\":\"main\",\"tags\":[\"class\"],\"exported\":false,\"parameters\":{\"name\":\"main\"}},{\"type\":\"File\",\"title\":\"/tmp/ticket_6448_file_with_utf8_source_j9w3rhmk.7EeVuV/\xEF\xBD\xB2\xEF\xBD\xA7\xE3\x83\x95\xE3\x83\xAB\",\"tags\":[\"file\",\"class\"],\"file\":\"/etc/puppetlabs/code/environments/ticket_6448_file_with_utf8_source_j9w3rhmk/manifests/site.pp\",\"line\":2,\"exported\":false,\"parameters\":{\"ensure\":\"present\",\"source\":\"puppet:///modules/utf8_file_module/\xE9\x9D\x99\xE7\x9A\x84\"}}],\"edges\":[{\"source\":\"Stage[main]\",\"target\":\"Class[Settings]\"},{\"source\":\"Stage[main]\",\"target\":\"Class[main]\"},{\"source\":\"Class[main]\",\"target\":\"File[/tmp/ticket_6448_file_with_utf8_source_j9w3rhmk.7EeVuV/\xEF\xBD\xB2\xEF\xBD\xA7\xE3\x83\x95\xE3\x83\xAB]\"}],\"classes\":[\"settings\"]}"{code}It thus did not go through gzip decompression, here:https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/http/compression.rb#L23After the change, the catalog requires decompression - and the decompressed result is mangled UTF-8:{code}[4] pry(#)> Zlib::GzipReader.new(StringIO.new(response.body)).read=>
Jira (PUP-7253) tests/resource/service/puppet_mcollective_service_management.rb test failing on OSX 1010 on puppet#master
Title: Message Title John Duarte created an issue Puppet / PUP-7253 tests/resource/service/puppet_mcollective_service_management.rb test failing on OSX 1010 on puppet#master Issue Type: CI Blocker Assignee: Unassigned Attachments: 20170223-puppet-agent-daily-puppet-master-osx1010-64a.log Created: 2017/02/23 11:26 AM Environment: OS X 10.10 Priority: Normal Reporter: John Duarte The tests/resource/service/puppet_mcollective_service_management.rb acceptance test fails on OS X 10.10 using puppet-agent at SHA e44a9529aa970fa8c682103c8ccdd1271772316e containing puppet at SHA ad6df55a248a9fdf19afdce42a00eea7adeeae45. Error * Stopping the puppet service while it is stopped: it should be stopped
Jira (PUP-7245) fix configuration_interpolation test
Title: Message Title John Duarte commented on PUP-7245 Re: fix configuration_interpolation test This has passed the puppet-agent#stable puppet CI run Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-7251
gzip decompression mangles utf-8 content in catalog
Change By:
Moses Mendoza
It appears a regression in UTF-8 handling by Puppet was introduced by when compression was fixed in https:// github tickets . puppetlabs. com/ puppetlabs browse / puppetserver/commit/b7d8ff4ab2603ef94f2f09ebcf42e535b69033a3. TK-429 This was discovered in investigating a local failure of the agent 1.9 series against https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/file/ticket_6448_file_with_utf8_source.rb against puppet server 2.7.2.master-0.1SNAPSHOT.2017.02.22T1106. We are not seeing this failure in CI presumably because CI is pinned to a released version of puppet server without this change.The catalog returned by the server in this test contains a UTF-8 named file resource,{code}"\u9759\u7864"{code}Prior to the change, the catalog received by the agent was uncompressed and contained:{code}[5] pry(#)> response.body=> "{\"tags\":[\"settings\"],\"name\":\"cpq55y0vuphp44u.delivery.puppetlabs.net\",\"version\":1487871618,\"code_id\":null,\"catalog_uuid\":\"cf89d5fd-ebdf-426a-832b-68812066c165\",\"catalog_format\":1,\"environment\":\"ticket_6448_file_with_utf8_source_j9w3rhmk\",\"resources\":[{\"type\":\"Stage\",\"title\":\"main\",\"tags\":[\"stage\"],\"exported\":false,\"parameters\":{\"name\":\"main\"}},{\"type\":\"Class\",\"title\":\"Settings\",\"tags\":[\"class\",\"settings\"],\"exported\":false},{\"type\":\"Class\",\"title\":\"main\",\"tags\":[\"class\"],\"exported\":false,\"parameters\":{\"name\":\"main\"}},{\"type\":\"File\",\"title\":\"/tmp/ticket_6448_file_with_utf8_source_j9w3rhmk.7EeVuV/\xEF\xBD\xB2\xEF\xBD\xA7\xE3\x83\x95\xE3\x83\xAB\",\"tags\":[\"file\",\"class\"],\"file\":\"/etc/puppetlabs/code/environments/ticket_6448_file_with_utf8_source_j9w3rhmk/manifests/site.pp\",\"line\":2,\"exported\":false,\"parameters\":{\"ensure\":\"present\",\"source\":\"puppet:///modules/utf8_file_module/\xE9\x9D\x99\xE7\x9A\x84\"}}],\"edges\":[{\"source\":\"Stage[main]\",\"target\":\"Class[Settings]\"},{\"source\":\"Stage[main]\",\"target\":\"Class[main]\"},{\"source\":\"Class[main]\",\"target\":\"File[/tmp/ticket_6448_file_with_utf8_source_j9w3rhmk.7EeVuV/\xEF\xBD\xB2\xEF\xBD\xA7\xE3\x83\x95\xE3\x83\xAB]\"}],\"classes\":[\"settings\"]}"{code}It thus did not go through gzip decompression, here:https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/http/compression.rb#L23After the change, the catalog requires decompression - and the decompressed result is mangled UTF-8:{code}[4] pry(#)> Zlib::GzipReader.new(StringIO.new(response.body)).read=>
Jira (PUP-7251) gzip decompression mangles utf-8 content in catalog
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7251 gzip decompression mangles utf-8 content in catalog Change By: Moses Mendoza Summary: gzip decompression manges mangles utf-8 content in catalog Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7238) Yum package provider should support reinstall
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7238 Yum package provider should support reinstall Change By: Geoff Nichols Sprint: Puppet Triage AP Accepted Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7233) Puppet configuration for storage(Netapp cluster mode)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7233 Puppet configuration for storage(Netapp cluster mode) Change By: Geoff Nichols Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7233) Puppet configuration for storage(Netapp cluster mode)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7233 Puppet configuration for storage(Netapp cluster mode) Change By: Geoff Nichols Sprint: Puppet Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7252) mcollective_service_manager acceptance test fails frequently on OSX 10.10
Title: Message Title Maggie Dreyer commented on PUP-7252 Re: mcollective_service_manager acceptance test fails frequently on OSX 10.10 Failed job link: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/master/view/puppet-agent/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-master/15/SLAVE_LABEL=beaker,TEST_TARGET=sles12-64a/testReport/junit/(root)/tests_resource_service/puppet_mcollective_service_management_rb/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7233) Puppet configuration for storage(Netapp cluster mode)
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols Puppet / PUP-7233 Puppet configuration for storage(Netapp cluster mode) Change By: Geoff Nichols Assignee: Nicholas Fagerlund Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7252) mcollective_service_manager acceptance test fails frequently on OSX 10.10
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-7252 mcollective_service_manager acceptance test fails frequently on OSX 10.10 Issue Type: Bug Assignee: Unassigned Created: 2017/02/23 10:52 AM Priority: Normal Reporter: Maggie Dreyer The puppet_mcollective_service_management test has been failing transiently but recently quite frequently on OSX 10.10. It also failed in the same way at least once on sles12. Error output: * Stopping the puppet service while it is running: it should be stopped * Establishing precondition: puppet: ensure => running
Jira (PUP-7231) Facts always one run behind when using storeconfigs and PuppetDB
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7231 Facts always one run behind when using storeconfigs and PuppetDB Change By: Geoff Nichols Sprint: Puppet Triage AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7211) puppet ssh_authorized_key not purged as expected
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7211 puppet ssh_authorized_key not purged as expected Change By: Geoff Nichols Sprint: Puppet Triage AP Accepted Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7211) puppet ssh_authorized_key not purged as expected
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7211 puppet ssh_authorized_key not purged as expected Change By: Geoff Nichols Labels: needs_epic Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7198 Puppet Server uses facts from the previous run (n-1) after agent switches masters Change By: Geoff Nichols Sprint: Puppet Triage AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression manges utf-8 content in catalog
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7251 gzip decompression manges utf-8 content in catalog Change By: Geoff Nichols Sprint: Puppet Triage AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression manges utf-8 content in catalog
Title: Message Title Geoff Nichols assigned an issue to Moses Mendoza Puppet / PUP-7251 gzip decompression manges utf-8 content in catalog Change By: Geoff Nichols Assignee: Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression manges utf-8 content in catalog
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7251 gzip decompression manges utf-8 content in catalog Change By: Geoff Nichols Sprint: Puppet Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7251) gzip decompression manges utf-8 content in catalog
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7251 gzip decompression manges utf-8 content in catalog Issue Type: Bug Assignee: Unassigned Created: 2017/02/23 10:29 AM Priority: Normal Reporter: Moses Mendoza It appears a regression in UTF-8 handling by Puppet was introduced by https://github.com/puppetlabs/puppetserver/commit/b7d8ff4ab2603ef94f2f09ebcf42e535b69033a3. This was discovered in investigating a local failure of the agent 1.9 series against https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/file/ticket_6448_file_with_utf8_source.rb against puppet server 2.7.2.master-0.1SNAPSHOT.2017.02.22T1106. We are not seeing this failure in CI presumably because CI is pinned to a released version of puppet server without this change. The catalog returned by the server in this test contains a UTF-8 named file resource, "\u9759\u7864" Prior to the change, the catalog received by the agent was uncompressed and contained:
Jira (HI-555) Hiera v5 configuration format is not documented
Title: Message Title Jean Bond commented on HI-555 Re: Hiera v5 configuration format is not documented Pretty sure Nicholas Fagerlund is on this, but I don't know which ticket offhand. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1576) Acceptance: Switch to new SPARC hardware
Title: Message Title Eric Delaney updated an issue Facter / FACT-1576 Acceptance: Switch to new SPARC hardware Change By: Eric Delaney QA Risk Assessment Reason: We are changing solaris hardware used by CI QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (HI-556) Acceptance: Switch to new SPARC hardware
Title: Message Title Eric Delaney updated an issue Hiera / HI-556 Acceptance: Switch to new SPARC hardware Change By: Eric Delaney QA Risk Assessment Reason: We are changing solaris hardware used by CI QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1378) EC2 metadata fact is not parsed properly
Title: Message Title Greg Hardy commented on FACT-1378 Re: EC2 metadata fact is not parsed properly I'll check. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7250) Acceptance: Switch to new SPARC hardware
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7250 Acceptance: Switch to new SPARC hardware Change By: Eric Delaney QA Risk Assessment Reason: We are changing solaris hardware QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7247) Unparsed line in puppetdb.conf
Title: Message Title Jeremy Barlow commented on PUP-7247 Re: Unparsed line in puppetdb.conf I can reproduce a very similar error if I insert an extra character between the "[main]" and "server_urls" lines in the puppetdb.conf file. In my case, the error occurs if I have a carriage return (ASCII 0xd) and line feed (ASCII 0xa) between the two lines whereas the error does not occur if I only have a line feed character between the two lines. I still wonder if there's some sort of formatting issue in the content of the puppetdb.conf file which is causing this error. Could you upload as an attachment the actual puppetdb.conf file you are using so we can see if there's anything odd about the content within it? What version of Puppet Server are you using? Also, could you capture the stack backtrace from the /var/log/puppetlabs/puppetserver/puppetserver.log file for this error? For example, it looked like the following for the case in which I was able to recreate it: 2017-02-23 08:11:09,361 DEBUG [qtp1123454304-38] [c.p.p.LoggingPuppetProfiler] [http POST /puppet/v3/catalog/localhost] (133 ms) Processed request POST /puppet/v3/catalog/localhost 2017-02-23 08:11:09,361 ERROR [qtp1123454304-38] [puppetserver] Puppet Server Error: Unparseable line '[main] ' in PuppetDB config /Users/jbarlow/puppet-scratch/master/conf-puppetdb/puppetdb.conf:1 .../puppet/lib/puppet/util/puppetdb/config.rb:52:in `load' org/jruby/RubyString.java:7213:in `lines' org/jruby/RubyEnumerator.java:274:in `each' org/jruby/RubyEnumerator.java:412:in `each_with_index'
Jira (PUP-7247) Unparsed line in puppetdb.conf
Title: Message Title Gábor Vereb updated an issue Puppet / PUP-7247 Unparsed line in puppetdb.conf Change By: Gábor Vereb Attachment: puppet.conf Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7247) Unparsed line in puppetdb.conf
Title: Message Title Gábor Vereb commented on PUP-7247 Re: Unparsed line in puppetdb.conf My puppet.conf file content is: [master] vardir = /opt/puppetlabs/server/data/puppetserver logdir = /var/log/puppetlabs/puppetserver rundir = /var/run/puppetlabs/puppetserver pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid codedir = /etc/puppetlabs/code storeconfigs = true storeconfigs_backend = puppetdb dns_alt_names = puppet FQDN: puppetmaster4.home.lan It's interesting, because PuppetDB and Puppet-Server location in same server (see FQDN). What's trying to solv this issue ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7247) Unparsed line in puppetdb.conf
Title: Message Title Ryan Senior commented on PUP-7247 Re: Unparsed line in puppetdb.conf What does your puppet.conf look like? I've seen issues in the past in Puppet where something fails locally (in this case an issue collecting facts) and so it tries to get them from PuppetDB instead. It doesn't look like it's even reading in your puppetdb.conf. You have a different hostname in the error than you do in your config. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7249) Automatic coercion of String to SemVer/SemVerRange
Title: Message Title Henrik Lindberg commented on PUP-7249 Re: Automatic coercion of String to SemVer/SemVerRange As humans we are very good at finding special cases - the type system does not have the same kind of powers. Replace all types in the above with X, Y, T, etc. and start to describe the rules as abstract type algebra - not fun, riddled with ambiguities and requires rules for how to resolve. That is truly a very slippery slope and I am not sure we would end up with a sane result. (Again see _javascript_ for the hilarity of what that can look like). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7240) A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists.
Title: Message Title Henrik Lindberg commented on PUP-7240 Re: A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists. Ping Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7249) Automatic coercion of String to SemVer/SemVerRange
Title: Message Title Rune Juhl Jacobsen commented on PUP-7249 Re: Automatic coercion of String to SemVer/SemVerRange Gotcha – thank you for explaining. I'm not sure I agree on the slippery slope though, wouldn't that only happen if the type was e.g. Variant[Data,Boolean,String]? In the case of Variant[SemVer,Enum['latest'],Boolean] there's no possibility of overlap. For untyped parameters I agree completely; trying to match with a type is near impossible. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7130) Fix problems with Puppet running on Ruby 2.4
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7130 Fix problems with Puppet running on Ruby 2.4 Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7249) Automatic coercion of String to SemVer/SemVerRange
Title: Message Title
Henrik Lindberg commented on PUP-7249
Re: Automatic coercion of String to SemVer/SemVerRange
When you actually want to differentiate - for example accept a version or the string "latest". This would be a general mechanism so you end up on a slippery slope - did the user actual mean one or the other? And we end up in the number vs. string, boolean value vs. boolean string etc. (Just go through the fun and games that happen if you start dealing with Booleans in String form and auto conversion). We would quickly be back at the wonky 3.x rules for type conversion (also see the classic WAT presentation regarding _javascript_).
I can imagine adding automatic conversion when explicitly requested, but doing it everywhere for all values will create more problems than it solves. Part of me does not want to add this as it makes argument passing and parameter matching even more complicated - instead we should make it easier to deliver data of the correct type (i.e. it is a hiera/data issue, and not an issue of automatic type conversion). The Initializer[T] variant would provide automatic checking, but would not instantiate - thus the logic can rely on it being done and simply do something like:
class myclass(Variant[SemVer, Initializer[SemVer]] $ver) {
$actual_ver = SemVer($ver) # would always work as automatic type checking makes sure of that
}
Add Comment
Jira (PUP-7249) Automatic coercion of String to SemVer/SemVerRange
Title: Message Title
Rune Juhl Jacobsen commented on PUP-7249
Re: Automatic coercion of String to SemVer/SemVerRange
Hi Henrik Lindberg,
Could you elaborate on your thoughts when you say it's a curse too? Maybe I'm being dense, but as long as the parameters are typed I can't see the downsides of automatic conversion. If you want to allow an untyped parameters (and hence uninstantiated) as well, using {{ Variant[SemVer,Data] }} and trying conversion from left to right could maybe be an option?
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7249) Automatic coercion of String to SemVer/SemVerRange
Title: Message Title
Henrik Lindberg commented on PUP-7249
Re: Automatic coercion of String to SemVer/SemVerRange
One option (that requires a language change) is to introduce some kind of operator for defining that a type cast should be performed. For example here are some examples of what has been considered:
# Use () after type
class mything (SemVer() $ver) {
}
# Spell out .new
class mything (SemVer.new $ver) {
}
# argument to Initializer type (somewhat strange though)
class mything (Initializer[SemVer, true] $ver) {
Jira (PUP-7249) Automatic coercion of String to SemVer/SemVerRange
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7249 Automatic coercion of String to SemVer/SemVerRange Change By: Henrik Lindberg Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7249) Automatic coercion of String to SemVer/SemVerRange
Title: Message Title Henrik Lindberg commented on PUP-7249 Re: Automatic coercion of String to SemVer/SemVerRange Automatic type conversions are both a blessing and a curse. We are considering adding a type that describes that a value is of the type that allows it to be use as arguments to a constructor of a given type - for example Initializer[SemVer] would accept a string that can be fed to SemVer.new. That is still just one step in the right direction and we have yet to define you you can specify that it should automatically instantiate the type. Clearly, you would want to be able to just get the argument without initialization in some cases, whereas in others you want the initialization to take place. Another option being explored is to have a transform/filter in hiera 5 that allows the string to be transformed via logic before being assigned to the parameter. This would enable looking up a SemVer instance as opposed to an initializer. This can already be done with hiera 5 (add a function to hiera.yaml that returns that instance for the given key), but you cannot then also bind it to that key in a yaml file. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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. For more options, visit https://groups.google.com/d/optout.
