Jira (PUP-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Thomas Hallgren commented on PUP-7671
Re: Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
We have a unit test that tests the loader. I'd like for us to have something that tests the full shebang. With and without puppet generate types and preferable with the ability to use a master and an agent.
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 Jo Rhett commented on PUP-7260 Re: Remove puppet inspect and stop honoring the audit metaparameter Ditto on what Vadym Chepkov said about tracking changes to files that Puppet doesn't manage. This is used by many sites for PCI and other compliance. Regarding inspect, there is the need to be able to pull or send specialized reports to specific people. The two most common cases I've seen are special reviews of configuration changes for application developers (without all the other Puppet meat) and compliance reports for security auditors. They want these weekly or monthly not every 30 minutes. In the back of my head I'm sure that this data would be much easier to pull from Puppet DB, however I haven't had a chance to figure this out yet and there's no linkage in the documentation. I grok that you're desperate to retire inspect. I don't have technical bits tied to inspect, I just have customers receiving value from its functionality. If you can direct us to get the same or better functionality from PuppetDB, we can likely let inspect pass away. 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-7665) Puppet 5 fails when facter facts contain ampersands
Title: Message Title Moses Mendoza assigned an issue to Ethan Brown Puppet / PUP-7665 Puppet 5 fails when facter facts contain ampersands 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-7665) Puppet 5 fails when facter facts contain ampersands
Title: Message Title Moses Mendoza commented on PUP-7665 Re: Puppet 5 fails when facter facts contain ampersands Initial PR only updated URI encoding for PSON facts. Second PR raised to master to address JSON facts: https://github.com/puppetlabs/puppet/pull/5996 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-7665) Puppet 5 fails when facter facts contain ampersands
Title: Message Title Moses Mendoza commented on PUP-7665 Re: Puppet 5 fails when facter facts contain ampersands merged up to master at 3e66932aa2d2d822626e35a46f04ce9922c086cf Note that unit test file fact_handler_spec.rb had conflicts and was corrected for master. 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-7665) Puppet 5 fails when facter facts contain ampersands
Title: Message Title Moses Mendoza commented on PUP-7665 Re: Puppet 5 fails when facter facts contain ampersands merged to stable at https://github.com/puppetlabs/puppet/commit/5e7e50feecb370a97718a663e3c4c08070669502 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-6828) Simplify agent SSL initialization
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6828 Simplify agent SSL initialization Change By: Karen Van der Veer Epic Colour: ghx-label-6 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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Eric Delaney commented on PUP-7671
Re: Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Thomas Hallgren Can we test this in unit tests or do we need an acceptance level test for 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 (PDB-3565) PuppetDB module needs updated for Puppet 5 platform (requires PostgreSQL 9.6)
Title: Message Title
Doug Rosser created an issue
PuppetDB / PDB-3565
PuppetDB module needs updated for Puppet 5 platform (requires PostgreSQL 9.6)
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/06/16 2:25 PM
Priority:
Normal
Reporter:
Doug Rosser
Out of the box, a user attempting to use the PuppetDB module from the forge (https://forge.puppet.com/puppetlabs/puppetdb) will hit an error applying the catalog stating, "PostgreSQL 9.6 is required".
Workaround is to add the Postgres yum repository at https://yum.postgresql.org/repopackages.php (so Postgres96 can be found) and add the following to their manifest/module:
class { 'puppetdb':
postgres_version => '9.6'
}
Jira (PUP-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Thomas Hallgren commented on PUP-7671
Re: Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Eric Delaney, will this reproducer be added to an acceptance test? It would be great to have that to catch future regressions in this area.
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Eric Delaney commented on PUP-7671
Re: Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Reproduced problem on 4.10.3, then recreated the files necessary files on 4.10.4 system, SHA=ce1ed0943284a5c6ef21ae2da7b21439533c1846 SUITE_VERSION=1.10.3.8.gce1ed09, and the error no longer occurred.
manifests/init.pp
class saltnetwork {
each([ "icmp"
, "ssh"
]) |$service_chain| {
$service_chain_dashes = regsubst($service_chain, '_', '-', 'G')
Resource["saltnetwork::iptables::service_chain::${service_chain}"] { "allow_${service_chain}":
rule_set_name => 'common'
, rule_target => 'rule'
}
Jira (PUP-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Verne Lindner commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run Henrik Lindberg In reference to PUP-5934, do you have an idea of when that ticket might be groomed? I noticed it going into Triage a while back. For PE Console reporting, this issue impacts accuracy. 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-3558) Update puppetdb-termini 5 package to dep on puppet-agent >= 5
Title: Message Title Jeremy Barlow commented on PDB-3558 Re: Update puppetdb-termini 5 package to dep on puppet-agent >= 5 >= 4.99.0 or greater appears to work fine for each of the OSes we package for puppetserver. I put up a puppetserver PR here: https://github.com/puppetlabs/puppetserver/pull/1431. 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-3564) Create stubbed graphql endpoint
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3564 Create stubbed graphql endpoint Change By: Zachary Kent Assignee: Zachary Kent 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-3564) Create stubbed graphql endpoint
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3564 Create stubbed graphql endpoint Change By: Russell Mull Sprint: Hopper 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-3564) Create stubbed graphql endpoint
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3564 Create stubbed graphql endpoint Issue Type: New Feature Assignee: Unassigned Created: 2017/06/16 11:01 AM Priority: Normal Reporter: Russell Mull 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
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6739 Error running puppet with non-existent and non-default environment Change By: Kenn Hussey Flagged: Impediment 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Kenn Hussey Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.1.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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Kenn Hussey Flagged: Impediment 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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Eric Thompson
QA Risk Assessment Reason:
can be covered by unit tests. qa to confirm. validation would be good as this regressed
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Eric Thompson
QA Risk Assessment:
Needs Assessment Manual
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-3561) store report statuses in the reports table
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3561 store report statuses in the reports table Change By: Russell Mull Fix Version/s: PDB 5.1.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-7665) Puppet 5 fails when facter facts contain ampersands
Title: Message Title Geoff Nichols assigned an issue to Moses Mendoza Puppet / PUP-7665 Puppet 5 fails when facter facts contain ampersands Change By: Geoff Nichols Assignee: Ethan Brown 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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Geoff Nichols assigned an issue to Moses Mendoza
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Geoff Nichols
Assignee:
Thomas Hallgren 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 (PDB-3558) Update puppetdb-termini 5 package to dep on puppet-agent >= 5
Title: Message Title Jeremy Barlow commented on PDB-3558 Re: Update puppetdb-termini 5 package to dep on puppet-agent >= 5 Geoff Nichols, I'm doing some testing with that right now with puppetserver packages. I can confirm that our CI would blow up if we tried to pin puppetserver's dependency on puppet-agent to >= 5.0.0, as Moses Mendoza had suspected. >= 4.9.9 might work fine with current packages, though. I'll do a little more testing with that as a sanity check. If it works, I'll get a PR up for that today. 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-7669) Tag puppet 4.10.3 for agent 1.10.3 release
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7669 Tag puppet 4.10.3 for agent 1.10.3 release Change By: Eric Delaney 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 (PDB-3550) Upgrade to puppet5-nightly : puppetdb doens't start
Title: Message Title Russell Mull commented on PDB-3550 Re: Upgrade to puppet5-nightly : puppetdb doens't start Rob Braden Any idea how the puppetdb package got into the trusty repo? It seems like it shouldn't be there. 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-7650) "Attempt to redefine entity" caused by upper/lower case name confusion in Loader
Title: Message Title John Duarte commented on PUP-7650 Re: "Attempt to redefine entity" caused by upper/lower case name confusion in Loader Kenn Hussey, yes this successfully passed CI for puppet-agent#master at SHA f1de0f233b931db8d19c3fa1c7131b4fcda0e1f7 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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Kenn Hussey updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Kenn Hussey
Flagged:
Impediment
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Kenn Hussey updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Kenn Hussey
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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: John Duarte Status: Ready for CI Test Assignee: Ethan Brown qa 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-7660) Metaparameters are validated on unrealized resources
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-7660 Metaparameters are validated on unrealized resources Change By: John Duarte Status: Ready for CI Test Assignee: qa 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-7650) "Attempt to redefine entity" caused by upper/lower case name confusion in Loader
Title: Message Title Kenn Hussey commented on PUP-7650 Re: "Attempt to redefine entity" caused by upper/lower case name confusion in Loader John Duarte can you verify whether this made it through CI for 5.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-7510) FIPS-Enabled Puppet
Title: Message Title Trevor Vaughan commented on PUP-7510 Re: FIPS-Enabled Puppet Jayant Sane I didn't see the Sun one on the list, but I did see the IBM Java libs http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp2715.pdf. There are definite pros and cons to using native vs Bouncy Castle. The pro to not using it is that you don't have to change any code. The con is that you need to wait for the next version of Java to be certified before you can actually upgrade. If you disconnect the crypto libs, then you should be able to upgrade asynchronously (I think). 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-7673) puppet-agent 1.10.4
Title: Message Title Kenn Hussey created an issue Puppet / PUP-7673 puppet-agent 1.10.4 Issue Type: Bug Assignee: Kenn Hussey Components: Platform Created: 2017/06/16 7:02 AM Due Date: 2017/08/01 Priority: Normal Reporter: Kenn Hussey Release ticket for puppet-agent 1.10.4 release. Issues in this release can be found using the following query: https://tickets.puppetlabs.com/issues/?filter=27118 Add Comment
Jira (PUP-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3551 Sanitize non-UTF-8 data in run reports Change By: Kenn Hussey Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.1.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-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3551 Sanitize non-UTF-8 data in run reports Change By: Kenn Hussey Flagged: Impediment 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-7602) If the catalog contains binary content, the server should downgrade to pson
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7602 If the catalog contains binary content, the server should downgrade to pson Change By: Kenn Hussey Flagged: Impediment 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-7672) The ZFS zoned property is not portable
Title: Message Title Joris Dedieu created an issue Puppet / PUP-7672 The ZFS zoned property is not portable Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Components: Types and Providers Created: 2017/06/16 5:16 AM Environment: FreeBSD Priority: Normal Reporter: Joris Dedieu On Solaris ZFS has a 'zoned' property. On Linux it's a noop, on FreeBSD it is called 'jailed'. Exemple : bundle exec puppet resource zfs Error: Could not run: Execution of '/sbin/zfs get -H -o value zoned SSD' returned 2: bad property list: invalid property 'zoned' /sbin/zfs get -H -o value zoned SSD should be /sbin/zfs get -H -o value jailed SSD on FreeBSD
Jira (PUP-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Henrik Lindberg
Labels:
regression
Release Notes Summary:
Puppet 4.10.3 contained a regression where resources created using the syntax {{Resource\[xx::yy]}} would cause an error as Puppet would not find an existing 'xx::yy' user defined resource type. This was caused by fixing another problem with inconsistent use of upper/lower case in references.
Release Notes:
Bug Fix
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Henrik Lindberg
Fix Version/s:
PUP 4.10.4
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Thomas Hallgren commented on PUP-7671
Re: Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
The regression was introduced by PUP-7650.
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Thomas Hallgren
Sub-team:
Language
Story Points:
1
Team:
Agent
Sprint:
Agent 2017-06-28
Method Found:
Needs Assessment Customer Feedback
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
Jira (PUP-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Thomas Hallgren assigned an issue to Thomas Hallgren
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Change By:
Thomas Hallgren
Assignee:
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-7597) Add hiera5 default config file to puppet
Title: Message Title
John O'Connor updated an issue
Puppet / PUP-7597
Add hiera5 default config file to puppet
Change By:
John O'Connor
Release Notes Summary:
Drop new hiera 5 compliant default files in {{confdir}} and {{env-directory}}Note Upgrade Handling:For Puppet 4.10.x - No changes for now. (We can backport changes from 5.x later if there is customer demand.)For Puppet 5.0.0:a. New installs: Lay down the appropriate v5 hiera.yaml in $confdir and $environment:b. On upgrade:If we detect a hiera.yaml in either $confdir or $environment, don’t install a new file in either location.Don’t remove $hieradata.This is also the summary for related PA issues PA-1169 & PA-1139
Release Notes:
Not Needed New Feature
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Thomas Hallgren commented on PUP-7671
Re: Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
I managed to create a simple reproducer for this. Investigating.
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-5635) accessing facts via another scope
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5635 accessing facts via another scope Change By: Henrik Lindberg Release Notes Summary: Instead of an error/undef when referencing a non existing variable, Puppet could end up resolving the last part of a qualified name against top scope such that a request for $::somemodule::x would be satisfied by the existence of a topscope $::x variable. This baffling problem is now fixed. Release Notes: Bug Fix 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-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-523 Make it possible to declare classes, defines and functions (and more) as private to a module Change By: Henrik Lindberg 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-7597) Add hiera5 default config file to puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7597 Add hiera5 default config file to puppet Change By: Henrik Lindberg Release Notes: Not Needed 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-5459) Remove deprecated methods in puppet/data_providers.rb
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5459 Remove deprecated methods in puppet/data_providers.rb Change By: Henrik Lindberg Release Notes Summary: internal concern Release Notes: Not Needed 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-5912) Implement a human friendly PCore serialization format
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5912 Implement a human friendly PCore serialization format Change By: Henrik Lindberg Release Notes Summary: Part of experimental - not yet publically released feature. Release Notes: Not Needed 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-5917) Puppet 5.0.0 Removals
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5917 Puppet 5.0.0 Removals Change By: Henrik Lindberg Release Notes Summary: not needed at epic level 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-6264) Semantic::VersionRange considers '1.0.0-alpha' part of range '>=1.0.0'
Title: Message Title Henrik Lindberg commented on PUP-6264 Re: Semantic::VersionRange considers '1.0.0-alpha' part of range '>=1.0.0' Thomas Hallgren Can you add a release note? 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-6368) Semantic::VersionRange creates incorrect range for <= version
Title: Message Title Henrik Lindberg commented on PUP-6368 Re: Semantic::VersionRange creates incorrect range for <= version Thomas Hallgren Can you add a release note? 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-7016) 5.0.0 Lookup features
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7016 5.0.0 Lookup features Change By: Henrik Lindberg Release Notes Summary: Nothing at the epic level to release note. See individual tickets. Release Notes: Not Needed 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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Matthias Hörmann commented on PUP-7671
Re: Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
It seems possible to work around the problem by replacing it with create_resources(). it would still be good if the issue could be fixed though, as the original syntax is a lot cleaner than create_resources().
Where I write 'on multiple nodes' above, I mean on all nodes using the code.
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-7671) Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Title: Message Title
Matthias Hörmann created an issue
Puppet / PUP-7671
Resource definition via Resource["string"] { "title": ... } fails in Puppet 4.10.3
Issue Type:
Bug
Affects Versions:
PUP 4.10.3
Assignee:
Unassigned
Created:
2017/06/16 1:29 AM
Environment:
Puppetserver 2.72 on Debian jessie Puppet Agent 4.10.3 on both Master and Node strict=error strict_variables=true
Priority:
Blocker
Reporter:
Matthias Hörmann
We have been using the following snippet to generate a number of resources dynamically in an each loop for a while now without problems. After the upgrade to 4.10.3 this morning (including a restart of the Puppetserver) we get this error on multiple nodes
Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Unknown resource type: 'Saltnetwork::Iptables::Service_chain::Icmp' at
Jira (PUP-7670) Rename PType and PHostClassType to follow naming convention
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7670 Rename PType and PHostClassType to follow naming convention Issue Type: Improvement Assignee: Unassigned Created: 2017/06/16 1:23 AM Priority: Minor Reporter: Thomas Hallgren Almost all Pcore type classes are named using the convention: PType. There are two exceptions, the PType and PHostClassType. They should be renamed to PTypeType and PClassType and the code in place to cater for the exceptions should be removed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7431 Upgrade vendored version of SemanticPuppet Change By: Thomas Hallgren Release Notes Summary: The vendored semantic_puppet gem was upgraded to version 1.0.0 which contains bug fixes described in tickets PUP-6242, PUP-6264, and PUP-6373. Release Notes: Bug Fix 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-7625) puppet-master logcheck rule needs adjustment
Title: Message Title Josh Cooper commented on PUP-7625 Re: puppet-master logcheck rule needs adjustment There's no CI for this, so moving it to resolved. 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-7321) Update API schema docs
Title: Message Title Josh Cooper assigned an issue to Moses Mendoza Puppet / PUP-7321 Update API schema docs Change By: Josh Cooper Assignee: Josh Cooper 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-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Josh Cooper commented on PUP-3551 Re: Sanitize non-UTF-8 data in run reports Now that we're sanitizing log entries, I agree that it's unlikely for binary data to get into a report. One remaining issue is whether the previous_value or desired_value event fields can contain binary data? In the case of the file type, it always emits md5 checksums for previous/desired, so that isn't an issue. The only other place I think of is if a custom type/provider happens to manage a property whose value is binary data, such as a kerberos keytab file or java keystore. Using the host resource's comment property, I was able to demonstrate the problem, though I had to delete the property's validate method: Error: Could not convert change 'comment' to string: invalid byte sequence in UTF-8 /Users/josh/work/puppet/lib/puppet/pops/types/string_converter.rb:842:in `each_codepoint' /Users/josh/work/puppet/lib/puppet/pops/types/string_converter.rb:842:in `puppet_quote' /Users/josh/work/puppet/lib/puppet/pops/types/string_converter.rb:802:in `string_PStringType' /Users/josh/work/puppet/lib/puppet/pops/visitor.rb:110:in `visit_this_3' /Users/josh/work/puppet/lib/puppet/pops/types/string_converter.rb:516:in `_convert' /Users/josh/work/puppet/lib/puppet/pops/types/string_converter.rb:503:in `convert'
