Jira (FACT-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title Josh Cooper commented on FACT-1578 Re: Facter incorrectly converts integers causing negative values to be stored in PDB Valid CI failures on several hardware platforms: https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet-agent-cve_intn-van-sys_suite-hardware-facter-CVE-2017-2292-1.10.x/2/ The new functionality passes when using facter root@hz2k70n7l5najbp:~# /opt/puppetlabs/puppet/bin/facter mountpoints | grep used_bytes used_bytes => 4278557696 used_bytes => 0 used_bytes => 0 used_bytes => 0 used_bytes => 0 used_bytes => 0 used_bytes => 32768 used_bytes => 31744 used_bytes => 4278557696
Jira (PUP-7267) rewrite Puppet::Util::Execution
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7267 rewrite Puppet::Util::Execution Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.y 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-7455) cpp-pcp-client builds are failing on AIX 6.1 and 7.1
Title: Message Title Josh Cooper created an issue Puppet / PUP-7455 cpp-pcp-client builds are failing on AIX 6.1 and 7.1 Issue Type: CI Blocker Assignee: Unassigned Created: 2017/04/18 4:31 PM Priority: Normal Reporter: Josh Cooper https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet-agent_pkg-van-ship_daily-hardware-master/24/BUILD_TARGET=aix-6.1-ppc,SLAVE_LABEL=beaker/console https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet-agent_pkg-van-ship_daily-hardware-master/24/BUILD_TARGET=aix-7.1-ppc,SLAVE_LABEL=beaker/ 16:00:54 The branch at address 0x1cfdc is not followed by a recognized no-op 16:00:54 or TOC-reload instruction. The unrecognized instruction is 0x907F000C. 16:00:54 ld: 0711-768 WARNING: Object CMakeFiles/libcpp-pcp-client.dir/src/connector/v1/connector.cc.o, section 1, function .boost::re_detail::basic_regex_formatter
Jira (PUP-7427) Change rich data in Catalog so that it becomes backward compatible
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7427 Change rich data in Catalog so that it becomes backward compatible Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action 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-7427) Change rich data in Catalog so that it becomes backward compatible
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7427 Change rich data in Catalog so that it becomes backward compatible Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests; experimental 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-7427) Change rich data in Catalog so that it becomes backward compatible
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7427 Change rich data in Catalog so that it becomes backward compatible Change By: Eric Thompson 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-7427) Change rich data in Catalog so that it becomes backward compatible
Title: Message Title Eric Thompson commented on PUP-7427 Re: Change rich data in Catalog so that it becomes backward compatible ah. looks like Sensitive parameters are handled separately and differently? https://github.com/thallgren/puppet/blob/6abd752f3a964aa0e1b0b74c0adf3f6ba33d0e1c/lib/puppet/pops/serialization/serializer.rb#L81 https://github.com/thallgren/puppet/blob/6abd752f3a964aa0e1b0b74c0adf3f6ba33d0e1c/lib/puppet/resource.rb#L149 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-7268) SPIKE: Puppet::Util::Execution rewrite
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7268 SPIKE: Puppet::Util::Execution rewrite Change By: Geoff Nichols Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.y 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 Jeremy Barlow updated an issue Puppet / PUP-7198 Puppet Server uses facts from the previous run (n-1) after agent switches masters Change By: Jeremy Barlow 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: Geoff Nichols 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-6660) cached catalogs setting not respected when --test is specified
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6660 cached catalogs setting not respected when --test is specified Change By: Geoff Nichols 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-7157) Remove 'semantic' shim in Puppet 6
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7157 Remove 'semantic' shim in Puppet 6 Change By: Geoff Nichols Summary: Remove 'semantic' shim in Puppet 5 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-7157) Remove 'semantic' shim in Puppet 5
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7157 Remove 'semantic' shim in Puppet 5 Change By: Geoff Nichols Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 6.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-7454) The schedule metaparameter should allow for suppressing skip events
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-7454
The schedule metaparameter should allow for suppressing skip events
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2017/04/18 3:31 PM
Priority:
Normal
Reporter:
Erik Hansen
The following code snippet generates 48 event messages every day (per node) with the default run interval. 47 of the events are a "skipped" event and one being a success:
schedule { 'allowed_hours':
period => daily,
range => "5:00 - 17:00",
repeat => 1,
Jira (PUP-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Geoff Nichols Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.y 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-7063) Handle incompatible encodings in Puppet::Util::Log when rendering to console
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7063 Handle incompatible encodings in Puppet::Util::Log when rendering to console Change By: Geoff Nichols Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.y 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-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6432 Puppet::Util::Execution.execute cannot handle Unicode output on Windows Change By: Geoff Nichols Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.y 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-6035) Puppet Throws Exception when Running Under Unicode Windows User
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6035 Puppet Throws Exception when Running Under Unicode Windows User Change By: Geoff Nichols Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.y 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-1595) Add TestRail numbers split files with multiple tests and code style for config file tests
Title: Message Title Josh Cooper updated an issue Facter / FACT-1595 Add TestRail numbers split files with multiple tests and code style for config file tests Change By: Josh Cooper 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 (FACT-1600) Update the last of the options tests for facter with TestRail numbers, risk tags, code style
Title: Message Title Josh Cooper updated an issue Facter / FACT-1600 Update the last of the options tests for facter with TestRail numbers, risk tags, code style Change By: Josh Cooper 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 (FACT-1599) Add --color and --no-color acceptance tests
Title: Message Title Josh Cooper updated an issue Facter / FACT-1599 Add --color and --no-color acceptance tests Change By: Josh Cooper 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 (FACT-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title Josh Cooper commented on FACT-1578 Re: Facter incorrectly converts integers causing negative values to be stored in PDB This has passed per-commit CI, but still waiting on suite pipelines. 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-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title Josh Cooper updated an issue Facter / FACT-1578 Facter incorrectly converts integers causing negative values to be stored in PDB Change By: Josh Cooper Release Notes Summary: Previously, facter had an integer overflow when reporting on large numeric fact values, eg disk sizes, so the values were reported as negative numbers. This bug fix ensures facter uses 64-bit longs to correctly report on the data. 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-3901) Host type has unexpected behavior and is not idempotent
Title: Message Title Paul Whitehead commented on PUP-3901 Re: Host type has unexpected behavior and is not idempotent I hit an edge case where idempotence related to the host resource became an issue. Steps to reproduce Stand up a vagrant box using vagrant up puppetlabs/ubuntu-16.04-64-puppet Install the forge hosts module puppet module install ghoneycutt-hosts --version 2.5.0 Run puppet puppet apply -e "include hosts" The first run changes /etc/hosts The second run is not idempotent, and modifies /etc/hosts further The third run is idempotent Initial /etc/hosts file
Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Russell Mull commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error Isaac Eldridge the fixversion field is accurate 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-3322) PuppetDB fails to update catalogs when sensitive parameters are added
Title: Message Title Isaac Eldridge updated an issue PuppetDB / PDB-3322 PuppetDB fails to update catalogs when sensitive parameters are added Change By: Isaac Eldridge Labels: davis-triage docs_reviewed 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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Isaac Eldridge updated an issue PuppetDB / PDB-3058 Report not being stored in PuppetDB due to Unicode Error Change By: Isaac Eldridge Labels: docs_reviewed maintenance 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-3432) Backport elapsed command processing logging to LTS
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3432 Backport elapsed command processing logging to LTS Change By: Russell Mull Release Notes: 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 (PDB-3432) Backport elapsed command processing logging to LTS
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3432 Backport elapsed command processing logging to LTS Change By: Russell Mull Release Notes Summary: PuppetDB now logs the time spent processing each command, making it easier to trace performance problems to associated nodes. 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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Isaac Eldridge commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error Which PE versions will is this fixed in? 2016.4.4 and Glisan? 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-3322) PuppetDB fails to update catalogs when sensitive parameters are added
Title: Message Title Isaac Eldridge commented on PDB-3322 Re: PuppetDB fails to update catalogs when sensitive parameters are added Which PE versions will is this fixed in? 2016.4.4 and Glisan? 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-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3107 new-command-schema validation prevents PDB/NewRelic integration Change By: Russell Mull Release Notes Summary: PuppetDB can now run in conjunction with the New Relic 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 (PDB-2939) Don't try to store the same report twice
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2939 Don't try to store the same report twice Change By: Russell Mull Release Notes Summary: PuppetDB now checks to see if a report is already present before storing it. This eliminates a class of common (but harmless) log noise. 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-2939) Don't try to store the same report twice
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2939 Don't try to store the same report twice Change By: Russell Mull Release Notes Summary: PuppetDB now checks to see if a report is already present before storing it. This eliminates a class of common (but harmless) log noise and greatly reduces the number of spurious messages sent to the DLO . 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-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3107 new-command-schema validation prevents PDB/NewRelic integration Change By: Russell Mull Release Notes: 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 (PDB-3322) PuppetDB fails to update catalogs when sensitive parameters are added
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3322 PuppetDB fails to update catalogs when sensitive parameters are added Change By: Russell Mull Release Notes Summary: Sensitive parameters, which are created in puppet code using Sensitive.new, are now redacted before being sent to PuppetDB. 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-2939) Don't try to store the same report twice
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2939 Don't try to store the same report twice Change By: Russell Mull Release Notes: 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 (PDB-3322) PuppetDB fails to update catalogs when sensitive parameters are added
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3322 PuppetDB fails to update catalogs when sensitive parameters are added Change By: Russell Mull Release Notes: 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 (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3058 Report not being stored in PuppetDB due to Unicode Error Change By: Russell Mull Release Notes Summary: PuppetDB now filters null bytes in Resource Events fields; this fixes a problem when dealing with certain entries in the Windows registry which contain the value '\0' by default. 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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3058 Report not being stored in PuppetDB due to Unicode Error Change By: Russell Mull 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-7427) Change rich data in Catalog so that it becomes backward compatible
Title: Message Title Eric Thompson commented on PUP-7427 Re: Change rich data in Catalog so that it becomes backward compatible Russell Mull, Thomas Hallgren, Henrik Lindberg what happens when Sensitive types are in the catalog in this solution? is the value en clair in the catalog? in puppetdb? did we decide the latter would be covered by warnings in the docs for now? 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-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3467 possible memory leak in reports querying (maybe querying in general) Change By: Russell Mull Sprint: PuppetDB 2017-04-19 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-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title Russell Mull assigned an issue to Rob Browning PuppetDB / PDB-3467 possible memory leak in reports querying (maybe querying in general) Change By: Russell Mull Assignee: Rob Browning 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-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3467 possible memory leak in reports querying (maybe querying in general) Change By: Russell Mull 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 (PDB-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3467 possible memory leak in reports querying (maybe querying in general) Change By: Russell Mull Story Points: 3 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-3469) Streaming queries are being retained in memory
Title: Message Title Russell Mull assigned an issue to Rob Browning PuppetDB / PDB-3469 Streaming queries are being retained in memory Change By: Russell Mull Assignee: Rob Browning 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-3469) Streaming queries are being retained in memory
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3469 Streaming queries are being retained in memory Issue Type: Bug Assignee: Unassigned Created: 2017/04/18 1:54 PM Priority: Normal Reporter: Russell Mull That is, they aren't being fully streamed. Something is holding onto the head of the seq, which can cause us to OOM in some situations. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3469) Streaming queries are being retained in memory
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3469 Streaming queries are being retained in memory Change By: Russell Mull Story Points: 3 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-3469) Streaming queries are being retained in memory
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3469 Streaming queries are being retained in memory Change By: Russell Mull Affects Version/s: PDB 4.4.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-5853) 5.x TechDebt - to be resolved in Puppet 5.x
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5853 5.x TechDebt - to be resolved in Puppet 5.x Change By: Geoff Nichols Fix Version/s: PUP 5.y 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-3469) Streaming queries are being retained in memory
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3469 Streaming queries are being retained in memory Change By: Russell Mull Sprint: PuppetDB 2017-04-19 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-3469) Streaming queries are being retained in memory
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3469 Streaming queries are being retained in memory Change By: Russell Mull 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-5853) 5.x TechDebt - to be resolved in Puppet 5.x
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5853 5.x TechDebt - to be resolved in Puppet 5.x Change By: Geoff Nichols Team/s: Agent,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 (PDB-3468) (maint) Dynamically allocate puppetserver port in integration test
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3468 (maint) Dynamically allocate puppetserver port in integration test Change By: Russell Mull 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 (PDB-3468) (maint) Dynamically allocate puppetserver port in integration test
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3468 (maint) Dynamically allocate puppetserver port in integration test Change By: Russell Mull Fix Version/s: PDB 5.0.0 Fix Version/s: PDB 4.4.1 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-7333) make it possible to control partial ordering of layers
Title: Message Title Eric Sorenson commented on PUP-7333 Re: make it possible to control partial ordering of layers Is this truly necessary? It seems like it adds a great deal of complexity and I can't tell whether anyone has actually asked 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 (FACT-1607) split and update external fact test root_users_default_external_fact_dir
Title: Message Title Eric Delaney created an issue Facter / FACT-1607 split and update external fact test root_users_default_external_fact_dir Issue Type: Task Assignee: Eric Delaney Created: 2017/04/18 11:33 AM Priority: Normal Reporter: Eric Delaney We should split this test into: test the default directory (with a comment to the extra directory test for Unix) --external-dir overrides the same fact in the default directory Add Comment
Jira (PUP-7453) utf8 test failures after upgrading puppet pin
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-7453 utf8 test failures after upgrading puppet pin Issue Type: CI Blocker Assignee: Unassigned Created: 2017/04/18 11:22 AM Priority: Normal Reporter: Jeremy Barlow After upgrading puppetserver's puppet pins to 8e8866b, we started experiencing failures for three Ruby Puppet acceptance tests: language.binary_data_type.rb utf8.utf8-in-catalog.rb file.ticket_6448_file_with_utf8_source.rb See this CI job link. In each case, it seems that the agent is somehow having issues handling UTF-8 bytes returned from the server. For example, the following error appears in the agent output for the utf8-in-catalog.rb test: RuntimeError: PuppetAcceptance::DSL::Helpers.with_puppet_running_on failed (check backtrace for location) because: Host 'b1nf7ehap0olkfb.delivery.puppetlabs.net' exited with 1 running:
Jira (PDB-3468) (maint) Dynamically allocate puppetserver port in integration test
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3468 (maint) Dynamically allocate puppetserver port in integration test Change By: Russell Mull 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 (PDB-3468) (maint) Dynamically allocate puppetserver port in integration test
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3468 (maint) Dynamically allocate puppetserver port in integration test Change By: Russell Mull Sprint: PuppetDB 2017-04-19 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-3468) (maint) Dynamically allocate puppetserver port in integration test
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3468 (maint) Dynamically allocate puppetserver port in integration test Issue Type: Bug Assignee: Unassigned Created: 2017/04/18 10:54 AM Priority: Normal Reporter: gepetto-bot Using port 8140 everywhere makes things start failing when multiple tests are run on the same machine. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7438) Lookup knockout prefix behaviour affected by seemingly unrelated changes in hierarchy
Title: Message Title Jarkko Oranen commented on PUP-7438 Re: Lookup knockout prefix behaviour affected by seemingly unrelated changes in hierarchy So if I understand that correctly, essentially the weird behaviour is because using multiple paths in a hierarchy element causes a merge when values have been collected from all paths, and the knockout information is lost, whereas if there is only a single path per hierarchy element, the merge occurs only after the values have been collected from all elements. That sort of makes sense. but it might be a good idea to document this behaviour more explicitly, as it's not exactly intuitive. I certainly found it very surprising that the number of paths affects the merging behaviour. Filters sound interesting. For now, I have implemented a workaround that performs knockout explicitly via a puppet function, so I can get the behaviour I want. 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-3421) Send vector to db-do-commands from jdbc do-commands
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3421 Send vector to db-do-commands from jdbc do-commands Change By: Russell Mull 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 (PDB-3458) Change the puppetserver-version to a plain snapshot
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3458 Change the puppetserver-version to a plain snapshot Change By: Russell Mull 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 (PDB-3458) Change the puppetserver-version to a plain snapshot
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3458 Change the puppetserver-version to a plain snapshot Change By: Russell Mull Fix Version/s: PDB 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Jesse Scott commented on PUP-7431 Re: Upgrade vendored version of SemanticPuppet I can add them, I just need to know if they have accounts on Rubygems.org already and if so, what the associated email addresses are. 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Jesse Scott commented on PUP-7431 Re: Upgrade vendored version of SemanticPuppet Ummm, I think I have released it in the past but I'm not sure the responsibility falls clearly on anyone. Probably would make sense to add Thomas/Henrik to the owners on Rubygems so they could release 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-2614) update module docs to reflect lack of support for HSQL
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2614 update module docs to reflect lack of support for HSQL Change By: Russell Mull Fix Version/s: PDB module-5.2.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-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Moses Mendoza Team: 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-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Moses Mendoza Sprint: Agent 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-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Moses Mendoza commented on PUP-7451 Re: Puppet HTTP client should respect Retry-After headers thanks for filing Charlie Sharpsteen 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-7452) puppet certificate is missing a real destroy
Title: Message Title Moses Mendoza commented on PUP-7452 Re: puppet certificate is missing a real destroy thanks for filing Fabrice Bacchella. There's a related epic where we're tracking input to a remote management API/interface Puppet Server's CA, https://tickets.puppetlabs.com/browse/SERVER-1747. I'm going to link this to that effort. 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-1606) split the external_facts/fact_precedence tests into multiple files
Title: Message Title Eric Delaney updated an issue Facter / FACT-1606 split the external_facts/fact_precedence tests into multiple files Change By: Eric Delaney QA Risk Assessment Reason: This ticket is updating acceptance tests QA Risk Assessment: Automate 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-3374) Collapse / shrink integration tests
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3374 Collapse / shrink integration tests Change By: Russell Mull Fix Version/s: PDB 5.0.0 Fix Version/s: PDB 4.4.1 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-2614) update module docs to reflect lack of support for HSQL
Title: Message Title Russell Mull commented on PDB-2614 Re: update module docs to reflect lack of support for HSQL https://github.com/puppetlabs/puppetlabs-puppetdb/pull/252 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-7436) regression: epp parameter with default expression = undef does not take
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7436 regression: epp parameter with default _expression_ = undef does not take 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 (PDB-3466) (maint) Run integration tests against puppetserver master branch
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3466 (maint) Run integration tests against puppetserver master branch Change By: Russell Mull 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 (PDB-3466) (maint) Run integration tests against puppetserver master branch
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3466 (maint) Run integration tests against puppetserver master branch Change By: Russell Mull Sprint: PuppetDB 2017-04-19 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-3466) (maint) Run integration tests against puppetserver master branch
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3466 (maint) Run integration tests against puppetserver master branch Change By: Russell Mull Fix Version/s: PDB 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-7098) Acceptance: utf-8 characters in catalog
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7098 Acceptance: utf-8 characters in catalog Change By: Kenn Hussey Team: 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 (PDB-3387) Work with Spencer to complete the move to vmPooler
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3387 Work with Spencer to complete the move to vmPooler Change By: Russell Mull Fix Version/s: PDB 5.0.0 Fix Version/s: PDB 4.4.1 Fix Version/s: PDB 4.2.3.3 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-7119) Acceptance: utf-8 characters in module describe block (puppet describe)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7119 Acceptance: utf-8 characters in module describe block (puppet describe) Change By: Kenn Hussey Team: 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-7117) Acceptance: utf-8 characters in file resource
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7117 Acceptance: utf-8 characters in file resource Change By: Kenn Hussey Team: 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 (FACT-1606) split the external_facts/fact_precedence tests into multiple files
Title: Message Title John Duarte updated an issue Facter / FACT-1606 split the external_facts/fact_precedence tests into multiple files Change By: John Duarte QA Risk Assessment: Needs Assessment Automate 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-7447) Need prescriptive method for combining 'lookup' with ENCs and the Roles/Profiles pattern (aka, lookup should look up the entire stack)
Title: Message Title Trevor Vaughan commented on PUP-7447 Re: Need prescriptive method for combining 'lookup' with ENCs and the Roles/Profiles pattern (aka, lookup should look up the entire stack) Thomas Hallgren Thanks for the response. You are correct that we want Global on down, which is what you would expect if you were referencing something as a class parameter and is the way most users end up thinking about variable lookups in Puppet since the advent of automatic parameter lookups. It's rare that I see direct calls to lookup in code and, when I do, I can tell that they expect things to work with PE out of the box (but it won't). Unfortunately, that will require a modification to the Hiera configuration for all of our users which is what we were trying to avoid by requesting that this capability be added to lookup as a switch. If there's no hope of this happening, we'll post the Hiera configuration and I would suggest that you update the lookup documentation to include a working example and/or a 'supported' Hiera backend module for doing this so that users can have assurance that it will continue to function and you can test it against upcoming changes in Puppet. Interestingly, we ran into this just the other day which I completely understand is order dependent and we need to watch out for this, but the scenario was that we had a defined type that needed a value from the top level class. For this example, we'll call the foo::def and foo::var. So, foo::def::bar needed to default to the value of foo::var and there are a couple of ways to do this. The first, is to use the pick function but this is annoying because I can't just use pick, I have to use pick with getvar so that the compiler doesn't complain at me. Also, this gets a bit confusing for users because pick + getvar is not very widely used. And, unfortunately, in this case it doesn't actually matter if the top scope parameter isn't defined. We just need a consistent method for changing it globally that works with class resource declarations. Now, lookup can almost do this, but unfortunately, as implemented currently, it can't because it doesn't hit gobal scope. But, it would be great to use lookup since, at this point, pretty much everyone understands what lookup does and they would not need to update their Hiera configuration and add a new backend if it just had the option to keep looking. Anyway, I have a feeling that I'm not going to see this so we'll move towards the Hiera backend. I do hope that we see a supported Hiera backend that we can use to do this though! Add Comment
Jira (FACT-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title Kenn Hussey commented on FACT-1578 Re: Facter incorrectly converts integers causing negative values to be stored in PDB Josh Cooper please provide release notes for 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-7427) Change rich data in Catalog so that it becomes backward compatible
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7427 Change rich data in Catalog so that it becomes backward compatible 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-5908) Implement a PCore MsgPack Serializer
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5908 Implement a PCore MsgPack Serializer Change By: Kenn Hussey Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.y 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-1916) puppet cert clean cannot remove signing requests
Title: Message Title Nick Howes commented on PUP-1916 Re: puppet cert clean cannot remove signing requests `puppet ca` has recently been deprecated, so that option is going away and soon there'll be no way to do this without manually managing the files. 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-7452) puppet certificate is missing a real destroy
Title: Message Title Fabrice Bacchella created an issue Puppet / PUP-7452 puppet certificate is missing a real destroy Issue Type: Improvement Affects Versions: PUP 4.10.0 Assignee: Unassigned Created: 2017/04/18 6:13 AM Priority: Normal Reporter: Fabrice Bacchella Puppet provides a 'certificate' command to allows remote CA management. But the option 'destroy' only operate on the local CA. It break one of the main purpose of that command, to allows remote administration of puppet CA. Wihout a remote destroy, generate and sign are not very useful, as they can only works on brand new hosts, not re-installed one. Add Comment
Jira (PUP-7447) Need prescriptive method for combining 'lookup' with ENCs and the Roles/Profiles pattern (aka, lookup should look up the entire stack)
Title: Message Title Thomas Hallgren commented on PUP-7447 Re: Need prescriptive method for combining 'lookup' with ENCs and the Roles/Profiles pattern (aka, lookup should look up the entire stack) I don't understand this hierachy: Hiera -> Class Declarations (Profiles) -> normal lookup() stuff Hiera IS the normal lookup stuff. They are not two separate things. Perhaps you mean: Global layer -> Class Declarations (Profiles) -> Environment layer -> Module layer ? If so, then it should be easy enough to achieve by just adding a lookup_key function, either at the end of the global hierarchy or at the start of the environment hierarchy, that essentially performs the same task as the simplib::lookup but calls context#not_found unless it finds the global value. By doing that, you gain the following advantages: You get the desired hierarchy. You get explain support. Values can be merged. Instead of calling closure_scope, I'd recommend injecting it into a parameter. Like this: Puppet::Functions.create_function(:'my::scope_lookup', Puppet::Functions::InternalFunction) do dispatch :scope_lookup do scope_param param 'String[1]', :key param 'Hash[String[1],Any]', :options
Jira (HI-424) Hiera github page links to redmine
Title: Message Title Geoff Nichols commented on HI-424 Re: Hiera github page links to redmine Changed the github page link from http://projects.puppetlabs.com/projects/hiera/ to https://docs.puppet.com/hiera/, 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-7438) Lookup knockout prefix behaviour affected by seemingly unrelated changes in hierarchy
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7438 Lookup knockout prefix behaviour affected by seemingly unrelated changes in hierarchy Change By: Thomas Hallgren Issue Type: Bug Improvement 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-7438) Lookup knockout prefix behaviour affected by seemingly unrelated changes in hierarchy
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7438 Lookup knockout prefix behaviour affected by seemingly unrelated changes in hierarchy Change By: Thomas Hallgren Priority: Major Normal 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-7438) Lookup knockout prefix behaviour affected by seemingly unrelated changes in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7438 Re: Lookup knockout prefix behaviour affected by seemingly unrelated changes in hierarchy While I fully agree that the behavior is far from optimal, it's not new to Hiera 5. What you expericence is actually expected when using --knockout_prefix and you will get the exact same behavior from a classic Hiera 3 (albeit, there you'll need to use a hash at the top since "deeper" merge doesn't merge arrays unless they reside in a hash). The deep merge gem that performs the knockout is designed so that any entries found in the merged source that matches the prefix will be removed from the source along with a matching entry in the target. That means that once a merge has been performed, all entries that match the prefix in the source of the merge will be gone, possibly eliminating some entries in the target. The behavior you're asking for would require unmatched entries to remain in the source during all merges performed in the same hierarchy. While that might be considered an improvement, it would also be a breaking change. Our current plans are to add a new concept where it will be possible to inject filters into the hierarchy. A filter will be a function (puppet or ruby) that can perform various manipulations on found values but the design for that is not yet complete. 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.
