Jira (PUP-4650) cron resources with the same name but for different users can't be purged
Title: Message Title Daniel Parks commented on PUP-4650 Re: cron resources with the same name but for different users can't be purged Just ran into this in production. When you end up with two cron entries with the same name, the resource isn't declared in puppet, and purge is on, then it will remove one entry on the first run, then the second entry on the second run. This could be a bit of a security vulnerability if you're using Puppet for that sort of thing, since it allows an attacker to "hide" cron jobs. 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-5868) yumrepo does not remove repo file
Title: Message Title James Ralston commented on PUP-5868 Re: yumrepo does not remove repo file Leaving the zero-length *.repo files is the correct thing to do, because removing them could create unintended side-effects. For example, say that /etc/yum.repos.d/foo.repo is contributed by the foo-release package. It defines a single repository, foo. You create a yumrepo resource to remove that repository via ensure => absent. This leaves a zero-length foo.repo file, which doesn't perturb yum in the slightest. But if the yumrepo resource were to remove that zero-length foo.repo file, then if the foo-release package is upgraded to a more recent package, the foo.repo file will be recreated, with the foo repository definition that you told Puppet to remove, and will persist until the next Puppet agent run. In contrast, if the yumrepo resource keeps the zero-length foo.repo file, then upgrading the foo-release package won't magically recreate the foo repository definition. (Worst case, you'll get a foo.repo.rpmnew file, which yum will ignore.) Of course, in this example, removing the foo-release package from the system would be a more optimal solution to get rid of the foo repository definition. But yumrepo can't assume that it's always going to be employed in the most optimal way. I suspect yumrepo's behavior of keeping zero-length *.repo files wasn't specifically intentional, but is a side-effect of the fact that the yumrepo resource uses the Ruby inifile gem to do all the reading/writing behind the scenes, and the inifile gem will cheerfully write out a configuration file that has nothing in it if you have removed all of the sections/settings. This is because it cannot assume that you want the configuration file to be removed entirely just because you aren't setting anything in it—in most cases, that assumption would be wrong, and would potentially break things (e.g., a daemon that will run just fine if its configuration file is empty, but will refuse to start if its configuration file is missing entirely). Regardless, whether intentional or not, yumrepo's behavior of leaving zero-length *.repo files is the correct behavior. If those files really task you, then script (via an exec resource that you trigger from your yumrepo resources, a cron job, et. al.) something like this to try to remove them safely: $ find /etc/yum.repos.d -name '*.repo' -type f -size 0 -print | xargs -r rpm -qf | grep 'not owned by any package' |
Jira (FACT-1577) Provide a stable ABI/SONAME
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1577 Provide a stable ABI/SONAME Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1577) Provide a stable ABI/SONAME
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1577 Provide a stable ABI/SONAME Change By: Geoff Nichols Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7296) The eyaml lookup_key function does not evaluate interpolated hash keys
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7296 The eyaml lookup_key function does not evaluate interpolated hash keys 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-7284) hiera-eyaml option 'extension' is ignored
Title: Message Title Thomas Hallgren commented on PUP-7284 Re: hiera-eyaml option 'extension' is ignored I created PUP-7296 to track the missing evaluation of key interpolations. 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-7284) hiera-eyaml option 'extension' is ignored
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7284 hiera-eyaml option 'extension' is ignored 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-7296) The eyaml lookup_key function does not evaluate interpolated hash keys
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7296 The eyaml lookup_key function does not evaluate interpolated hash keys Issue Type: Bug Affects Versions: PUP 4.9.3 Assignee: Thomas Hallgren Created: 2017/03/02 8:51 PM Fix Versions: PUP 4.9.4 Priority: Major Reporter: Thomas Hallgren The eyaml backend, when finding an unencrypted hash, will only evaluate interpolations in the values of that hash. The keys are not evaluated. This is wrong. Both keys and values must be evaluated. Add Comment
Jira (PUP-7273) Hiera 5: error unless data_hash is defined
Title: Message Title Thomas Hallgren commented on PUP-7273 Re: Hiera 5: error unless data_hash is defined I agree, and that brings me back to my original proposal. The knowledge about the parameters is encoded in the dispatcher. So the choice here is to either move that knowledge into the actual function (this is what I oppose, since it defeats the purpose of having a dispatcher), or we add a way for the dispatcher to produce more meaningful error messages. 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-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Thomas Hallgren commented on PUP-7289 Re: PUP 4.9.3 interpolation in hiera.yaml datadir stopped working Alex P, I checked, and the puppet-agent 1.9.2.17.g690aa2c-1jessie package does not include this fix. It contains puppet 4.9.3-2-g0ecc5b9, which was cut to early. 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-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7289 PUP 4.9.3 interpolation in hiera.yaml datadir stopped working 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 (FACT-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1578 Facter incorrectly converts integers causing negative values to be stored in PDB Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1578 Facter incorrectly converts integers causing negative values to be stored in PDB Change By: Geoff Nichols Sprint: AP Grooming On-Deck 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 Jacky Leung commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Andrey Galkin i have this issue in a single puppetserver instance. not sure is https://tickets.puppetlabs.com/browse/PDB-3058 also related as i am currently migrating from puppet3 to puppet4 and i have some issues on storing puppet reports and facts 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 Jacky Leung commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error Wyatt Alt hi thanks. i have no discarded catalog or report but i have lot for discarded facts. it seem i have some encoded data in ec2_user_data and the facter picked it up. is there any way to disable certain facters on the machine? as ec2_user_data only being used when server launch, it never need by puppet itself. i think this issue start happening to us may related to puppet4 deprecated stringify_facts. beside that facts i don't see any binary data anywhere and being discarded 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-7284) hiera-eyaml option 'extension' is ignored
Title: Message Title Thomas Hallgren commented on PUP-7284 Re: hiera-eyaml option 'extension' is ignored The problem is that eyaml lookup_key function doesn't interpolate keys in a Hash. So, yes. Separate ticket. 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-7129) Use systemd service provider for Debian 9 (Strech)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7129 Use systemd service provider for Debian 9 (Strech) Change By: Geoff Nichols Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7129) Use systemd service provider for Debian 9 (Strech)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7129 Use systemd service provider for Debian 9 (Strech) Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7129) Use systemd service provider for Debian 9 (Strech)
Title: Message Title Geoff Nichols commented on PUP-7129 Re: Use systemd service provider for Debian 9 (Strech) PR #5546 was merged to master at https://github.com/puppetlabs/puppet/commit/e5b7926d7e2652da9f5042afe3e0f837fe77f448. 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-7134) Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding for SSL files
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7134 Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding for SSL files Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5782) Re-vendor Win32-Process gem inside of puppet-win32-ruby
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5782 Re-vendor Win32-Process gem inside of puppet-win32-ruby Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7034) Remove dependency on `win32/dir` gem from install.rb
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7034 Remove dependency on `win32/dir` gem from install.rb Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5780) Create minor patch for Win32-Process gem
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5780 Create minor patch for Win32-Process gem Change By: Geoff Nichols Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5780) Create minor patch for Win32-Process gem
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5780 Create minor patch for Win32-Process gem Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5781) Verify new Win32-Process gem includes upstream patch from Puppetlabs
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5781 Verify new Win32-Process gem includes upstream patch from Puppetlabs Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5782) Re-vendor Win32-Process gem inside of puppet-win32-ruby
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5782 Re-vendor Win32-Process gem inside of puppet-win32-ruby Change By: Geoff Nichols Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5758) Remove usage of win32-service gem (if applicable)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5758 Remove usage of win32-service gem (if applicable) Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5781) Verify new Win32-Process gem includes upstream patch from Puppetlabs
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5781 Verify new Win32-Process gem includes upstream patch from Puppetlabs Change By: Geoff Nichols Story Points: 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-5756) Remove usage of win32-eventlog gem
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5756 Remove usage of win32-eventlog gem Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5755) Replace win32-eventlog calls with internal API implementations that are wide-string compatible
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5755 Replace win32-eventlog calls with internal API implementations that are wide-string compatible Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5757) Replace win32-service calls with internal API implementations that are wide-string compatibles
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5757 Replace win32-service calls with internal API implementations that are wide-string compatibles Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title
Adam Bottchen created an issue
Facter / FACT-1578
Facter incorrectly converts integers causing negative values to be stored in PDB
Issue Type:
Bug
Affects Versions:
FACT 3.5.1
Assignee:
Unassigned
Created:
2017/03/02 5:47 PM
Priority:
Normal
Reporter:
Adam Bottchen
PE 2016.5.2 Solaris x86 agent shows correct values in the output of `facter`, but shows negative numbers for large values when `puppet facts` is run. These negative numbers are also submitted to the Puppet server and stored in PDB.
# /opt/puppetlabs/bin/puppet facts
"mountpoints": {
Jira (PUP-7180) Document SSL requirements for `reporturl` option and `http` report processor
Title: Message Title Geoff Nichols assigned an issue to Nicholas Fagerlund Puppet / PUP-7180 Document SSL requirements for `reporturl` option and `http` report processor Change By: Geoff Nichols Assignee: Josh Cooper Nicholas Fagerlund 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-7274) http://links.puppetlabs.com/puppet-kick-deprecation still points to old puppet ticket; never updated
Title: Message Title Geoff Nichols assigned an issue to Nicholas Fagerlund Puppet / PUP-7274 http://links.puppetlabs.com/puppet-kick-deprecation still points to old puppet ticket; never updated Change By: Geoff Nichols Assignee: Geoff Nichols Nicholas Fagerlund 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-7274) http://links.puppetlabs.com/puppet-kick-deprecation still points to old puppet ticket; never updated
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7274 http://links.puppetlabs.com/puppet-kick-deprecation still points to old puppet ticket; never updated Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7252) puppet_mcollective_service_manager acceptance test fails frequently
Title: Message Title
Josh Cooper commented on PUP-7252
Re: puppet_mcollective_service_manager acceptance test fails frequently
This seems easy to reproduce on ubuntu-16.04, just run the following a few times:
root@kifviu8urhamvnv:~# puppet apply -e "service { 'puppet': ensure => 'running' }" && echo "" && puppet apply -e "service { 'puppet': ensure => 'stopped' }"
Notice: Compiled catalog for kifviu8urhamvnv.delivery.puppetlabs.net in environment production in 0.25 seconds
Notice: /Stage[main]/Main/Service[puppet]/ensure: ensure changed 'stopped' to 'running'
Notice: Applied catalog in 0.12 seconds
Notice: Run of Puppet already in progress; skipping (/opt/puppetlabs/puppet/cache/state/agent_catalog_run.lock exists)
I added some debug statements to get a better idea why puppet apply fails to run:
root@kifviu8urhamvnv:~# puppet apply -e "service { 'puppet': ensure => 'running' }" && echo "" && puppet apply -e "service { 'puppet': ensure => 'stopped' }"
Jira (PUP-7252) puppet_mcollective_service_manager acceptance test fails frequently
Title: Message Title Maggie Dreyer assigned an issue to Josh Cooper Puppet / PUP-7252 puppet_mcollective_service_manager acceptance test fails frequently Change By: Maggie Dreyer Assignee: Maggie Dreyer Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7273) Hiera 5: error unless data_hash is defined
Title: Message Title Henrik Lindberg commented on PUP-7273 Re: Hiera 5: error unless data_hash is defined But would it not at least output something before ending in error on that call? But... I realize that it would not be nice as there could be data_hash functions that does not need a path at all (and does not require one in its options). It really needs to be the function that reports the error - it is only there you can know. 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-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7289 PUP 4.9.3 interpolation in hiera.yaml datadir stopped working Change By: Henrik Lindberg 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-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Alex P commented on PUP-7289 Re: PUP 4.9.3 interpolation in hiera.yaml datadir stopped working Eric Sorenson, did install the nightly built as suggested. Unfortunately, CANNOT confirm the fix. If hiera_config isn't set in /etc/puppetlabs/puppet/puppet.conf, i.e. processing goes through /etc/puppetlabs/code/hiera.yaml (v5, configured as per above), then receiving original lookup error: > sudo puppet agent -t Info: Using configured environment 'corporate' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Function lookup() did not find a value for the name 'classes' on node node02.local Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run If I set hiera_config to point to original v3 /etc/puppetlabs/puppet/hiera.yaml, then there is stdlib error:
Jira (PUP-7284) hiera-eyaml option 'extension' is ignored
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7284 hiera-eyaml option 'extension' is ignored Change By: Henrik Lindberg 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-7240) A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists.
Title: Message Title Joshua Partlow commented on PUP-7240 Re: A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists. Thanks Henrik, Thomas. Britt Gresham is working on testing in 2017.2.x pulling in a puppet-agent with the changes, or if we get a promotion of puppet-agent in 2017.2.x before then, we'll check it out, and hopefully be able to close this and then merge the PE module prs associated with PE-18334. 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-7284) hiera-eyaml option 'extension' is ignored
Title: Message Title Henrik Lindberg commented on PUP-7284 Re: hiera-eyaml option 'extension' is ignored Ping Thomas Hallgren it could be that the new eyaml backend does not do interpolation correctly (a separate issue; we will test this against latest and create separate ticket if 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 (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8
Title: Message Title Henrik Lindberg commented on HI-519 Re: Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8 merged (again) to stable at dffeae8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-544) Hiera should error if it finds a v4 hiera.yaml
Title: Message Title Henrik Lindberg commented on HI-544 Re: Hiera should error if it finds a v4 hiera.yaml Has the revert been reversed yet? 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-7284) hiera-eyaml option 'extension' is ignored
Title: Message Title Reinhard Vicinus commented on PUP-7284 Re: hiera-eyaml option 'extension' is ignored I added your commit https://github.com/puppetlabs/puppet/commit/239c2e9f31b3ba20eafbf902f6ff45413df506fc to my puppet 4.9.3 test server and now have the problem, that lookups inside hiera data structures now longer work in all cases. Presumably because the eyaml backend is to greedy looking up data values. Here is an small example: hiera.yaml --- :backends: - eyaml - yaml :hierarchy: - common :yaml: :datadir: "."
Jira (PUP-7295) Puppet is too permissive about skipping SSL verification
Title: Message Title Adrien Thebo commented on PUP-7295 Re: Puppet is too permissive about skipping SSL verification /cc Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7295) Puppet is too permissive about skipping SSL verification
Title: Message Title Adrien Thebo created an issue Puppet / PUP-7295 Puppet is too permissive about skipping SSL verification Issue Type: Bug Assignee: Unassigned Created: 2017/03/02 1:42 PM Labels: ssl Priority: Normal Reporter: Adrien Thebo The majority of SSL connections Puppet makes to Puppet masters (which are mainly done by the indirector) can rely on the CA cert and a signed client certificate being available, which means that we can perform SSL peer verification and can provide a client certificate for client cert based authentication. However the current behavior of the SSL Validator code is able to downgrade to an unauthenticated connection at any point. This introduces unneeded risk when we can clearly identify the small set of code paths that might have a real reason for using a less thorough validator. Instead of having our validators defaulting to no validation, we should reverse this. The default validator should require a CA certificate for peer verification and should have a client certificate available in case client cert based authentication is required. The code paths that need to have reduced validators should specifically use those validators when absolutely necessary and should default to using the cert auth validator in all other cases. The locations that I can think of that can justify reducing or disabling verification are as follows: Fetching the CA certificate when we don't have a local copy of the CA
Jira (PUP-7273) Hiera 5: error unless data_hash is defined
Title: Message Title Thomas Hallgren commented on PUP-7273 Re: Hiera 5: error unless data_hash is defined The only way to do that is if all provider functions always allows an empty options hash and then do the checking inside of the executing function. That defeats the purpose of having a dispatcher that performs the type checking IMO. 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-7224) Replace the Rgen AST model with one generated from a Pcore model
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7224 Replace the Rgen AST model with one generated from a Pcore model Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-7271) performance regression in puppet 4.9
Title: Message Title Henrik Lindberg commented on PUP-7271 Re: performance regression in puppet 4.9 We have a 4.9.3 out now as well. Since there is no concrete information here to act on (cannot reproduce) we have to kick this out from 4.9.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 (PDB-3318) Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days )
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3318 Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days ) Change By: Nick Walker h1. The problemWhen you create and destroy nodes in your puppet infrastructure you build up a lot of deactivated nodes in your PuppetDB database that serve no real purpose but do slow down the performance of the database and cause it to grow. h1. Suggested Solution node-purge-ttl should be enabled by default and set equal to or higher than report-ttl. It should generally be set to an interval longer than report-ttl to avoid needing the node purge process to also delete reports. h1. ConsiderationsIt could be that we need to add a migration step that will delete old nodes during an upgrade so that post-upgrade the service isn't churning through deleting nodes but not processing catalogs or facts. 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-3318) Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days )
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3318 Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days ) Change By: Ryan Senior Labels: maintenance tcse 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-3318) Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days )
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3318 Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days ) Change By: Ryan Senior 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-3318) Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days )
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3318 Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days ) Change By: Ryan Senior 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-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Eric Sorenson commented on PUP-7289 Re: PUP 4.9.3 interpolation in hiera.yaml datadir stopped working Alex P we're looking at a release early next week. is it possible for you to try a nightly build and confirm the fix works for you? The repo config for jessie is here: http://nightlies.puppetlabs.com/puppet-agent-latest/repo_configs/deb/pl-puppet-agent-latest-jessie.list I believe the build there now (1900 GMT on 02-March-2017) includes the fix, so it should be easy to drop in and try. 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-3318) Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days )
Title: Message Title Nick Walker created an issue PuppetDB / PDB-3318 Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days ) Issue Type: Improvement Assignee: Unassigned Created: 2017/03/02 1:00 PM Labels: tcse Priority: Normal Reporter: Nick Walker The problem When you create and destroy nodes in your puppet infrastructure you build up a lot of deactivated nodes in your PuppetDB database that serve no real purpose but do slow down the performance of the database and cause it to grow. Suggested Solution node-purge-ttl should be enabled by default and set equal to or higher than report-ttl. It should generally be set to an interval longer than report-ttl to avoid needing the node purge process to also delete reports. Add Comment
Jira (PUP-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7204 Add support for mapped paths in hiera.yaml version 5 Change By: Thomas Hallgren Assignee: Thomas Hallgren 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 (PDB-2428) Allow Setting The Interval for Each of The Garbage Collection Queries Individually
Title: Message Title Nick Walker commented on PDB-2428 Re: Allow Setting The Interval for Each of The Garbage Collection Queries Individually I've implemented this myself with my puppetdb_gc module. https://github.com/npwalker/puppetdb_gc 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-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Josh Cooper updated an issue Puppet / PUP-893 Deprecate puppet inspect and the audit metaparameter Change By: Josh Cooper Fix Version/s: PUP 4.9.z Fix Version/s: PUP 4.10.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 (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8
Title: Message Title Josh Cooper commented on HI-519 Re: Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8 Ethan Brown, Geoff Nichols, Kenn Hussey It looks like this is the root cause of an issue affecting SERVER-1724. Given the change is low-risk, I'd be in favor of including this in HI 3.3.1 for PA 1.9.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-7271) performance regression in puppet 4.9
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7271 performance regression in puppet 4.9 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-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Ryan Senior commented on PDB-3107 Re: new-command-schema validation prevents PDB/NewRelic integration I would call it a tiny feature. We now support monitoring PDB with New Relic. New Relic reaches inside PDB and alters the ActiveMQ messages that PDB uses internally. We had strict validation on what the headers of those messages can contain (we are the only producers and consumers of those messages). Russell Mull relaxed that validation so that they must contain our headers, but can contain other things as well. 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-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7289 PUP 4.9.3 interpolation in hiera.yaml datadir stopped working 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-7282) Acceptance: Modified test to add tstpool & pointed manifest to available interface
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7282 Acceptance: Modified test to add tstpool & pointed manifest to available interface Change By: Eric Delaney QA Risk Assessment Reason: This is an update to existing acceptance tests 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-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Susan McNerney commented on PDB-3107 Re: new-command-schema validation prevents PDB/NewRelic integration is this just a bug fix, or is it a full blown 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-7252) puppet_mcollective_service_manager acceptance test fails frequently
Title: Message Title Maggie Dreyer commented on PUP-7252 Re: puppet_mcollective_service_manager acceptance test fails frequently The new Ubuntu failure may be related to a deeper Ubuntu/systemd services issue. See PE-19023. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7252) puppet_mcollective_service_manager acceptance test fails frequently
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7252 puppet_mcollective_service_manager acceptance test fails frequently Change By: Maggie Dreyer Affects 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-7252) puppet_mcollective_service_manager acceptance test fails frequently
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7252 puppet_mcollective_service_manager acceptance test fails frequently Change By: Maggie Dreyer Summary: puppet_mcollective_service_manager acceptance test fails frequently on OSX 10.10 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-7210) not english Windows: Puppet agent on windows dont get server from config
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7210
not english Windows: Puppet agent on windows dont get server from config
Change By:
Josh Cooper
UAC enabled {noformat} c:\ProgramData\PuppetLabs\puppet\etc\puppet.conf[main]server=centos7autoflush=trueenvironment=productionc:\Users\All Users\PuppetLabs\puppet\etc\puppet.conf[main]server=centos7autoflush=trueenvironment=productionc:\Users\Все пользователи\PuppetLabs\puppet\etc\puppet.conf[main]server=centos7autoflush=trueenvironment=productionC:\Users\Admin>puppet agent --test --server centos7Info: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Caching catalog for adminInfo: Applying configuration version '1486873839'Notice: Applied catalog in 0.03 seconds {noformat} BUT {noformat} C:\Users\Admin>puppet agent --testWarning: Unable to fetch my node definition, but the agent run will continue:Warning: getaddrinfo: ??.Info: Retrieving pluginfactsError: /File[C:/Users/Admin/.puppetlabs/opt/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': getaddrinfo: ??.Error: /File[C:/Users/Admin/.puppetlabs/opt/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: getaddrinfo: ??.Info: Retrieving pluginError: /File[C:/Users/Admin/.puppetlabs/opt/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': getaddrinfo: ??.Error: /File[C:/Users/Admin/.puppetlabs/opt/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: getaddrinfo: ??.Error: Could not retrieve catalog from remote server: getaddrinfo: ??.Warning: Not using cache on failed catalogError: Could not retrieve catalog; skipping runError: Could not send report: getaddrinfo: ??. {noformat} OR DEBUG WITH TRACE: {noformat} C:\Users\Admin>puppet agent --test --debug --traceDebug: Failed to load library 'syslog' for feature 'syslog'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Applying settings catalog for sections main, agent, sslDebug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Failed to load library 'selinux' for feature 'selinux'Debug: Using settings: adding file resource 'confdir': 'File[C:/Users/Admin/.puppetlabs/etc/puppet]{:path=>"C:/Users/Admin/.puppetlabs/etc/puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'codedir': 'File[C:/Users/Admin/.puppetlabs/etc/code]{:path=>"C:/Users/Admin/.puppetlabs/etc/code", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'vardir': 'File[C:/Users/Admin/.puppetlabs/opt/puppet/cache]{:path=>"C:/Users/Admin/.puppetlabs/opt/puppet/cache",
Jira (PUP-7180) Document SSL requirements for `reporturl` option and `http` report processor
Title: Message Title Max Bowsher commented on PUP-7180 Re: Document SSL requirements for `reporturl` option and `http` report processor Thanks, this seems like a sensible way to divide up the work. 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-7180) Document SSL requirements for `reporturl` option and `http` report processor
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7180 Document SSL requirements for `reporturl` option and `http` report processor Change By: Josh Cooper Component/s: DOCS 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-7294) Diagnose performance problems
Title: Message Title Kevin Paulisse created an issue Puppet / PUP-7294 Diagnose performance problems Issue Type: Task Assignee: Unassigned Created: 2017/03/02 10:49 AM Priority: Normal Reporter: Kevin Paulisse Tracking issue for diagnosing performance problems. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7180) Document SSL requirements for `reporturl` option and `http` report processor
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7180 Document SSL requirements for `reporturl` option and `http` report processor Change By: Josh Cooper Summary: Document SSL requirements for `reporturl` option / built-in and `http` report processing plugin are either wrong or badly documented processor 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-7180) SSL requirements for `reporturl` option / built-in `http` report processing plugin are either wrong or badly documented
Title: Message Title Josh Cooper commented on PUP-7180 Re: SSL requirements for `reporturl` option / built-in `http` report processing plugin are either wrong or badly documented Hi Max Bowsher, currently the `http` report processor can only connect over SSL to a server whose cert is issued by the puppet CA. I agree the docs need to be improved to call this out, so I'll mark this as accepted with a Docs component, and update the title to reflect that. Separately, I agree being able to trust common public CAs would be useful, see my comment in https://tickets.puppetlabs.com/browse/SERVER-1543?focusedCommentId=343467=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-343467. The root issue is that puppet's HTTP client API doesn't allow the caller to specify which certs they want to trust. That work is being tracked in PUP-5069. This would allow `http` report processors to trust the ca-certs bundle that ships in puppet (https://github.com/puppetlabs/puppet-ca-bundle). In parallel, there is on-going work to allow puppet to support multiple root CAs such as those from existing enterprise PKIs, see PUP-6697. /cc Adrien Thebo, Jeremy Barlow, Jayant Sane 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-7180) SSL requirements for `reporturl` option / built-in `http` report processing plugin are either wrong or badly documented
Title: Message Title Geoff Nichols assigned an issue to Josh Cooper Puppet / PUP-7180 SSL requirements for `reporturl` option / built-in `http` report processing plugin are either wrong or badly documented Change By: Geoff Nichols Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7244) Environment variables set in functions leak into subsequent runs
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7244 Environment variables set in functions leak into subsequent runs Change By: Geoff Nichols Sprint: AP Grooming On-Deck 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-7210) not english Windows: Puppet agent on windows dont get server from config
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7210 not english Windows: Puppet agent on windows dont get server from config Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7274) http://links.puppetlabs.com/puppet-kick-deprecation still points to old puppet ticket; never updated
Title: Message Title Josh Cooper commented on PUP-7274 Re: http://links.puppetlabs.com/puppet-kick-deprecation still points to old puppet ticket; never updated Hi otheus, Puppet 3.x is EOL and the kick functionality was removed in 4, so I'm going to close this as won't fix. I'd recommend taking a look at mcollective or orchestration in Puppet Enterprise https://docs.puppet.com/pe/latest/config_orchestration.html. 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-7280) Optimise pacman execution time by running fewer commands
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7280 Optimise pacman execution time by running fewer commands Change By: Geoff Nichols Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7280) Optimise pacman execution time by running fewer commands
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7280 Optimise pacman execution time by running fewer commands Change By: Geoff Nichols Labels: puppethack 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-7280) Optimise pacman execution time by running fewer commands
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7280 Optimise pacman execution time by running fewer commands Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7280) Optimise pacman execution time by running fewer commands
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7280 Optimise pacman execution time by running fewer commands Change By: Geoff Nichols Component/s: Types and Providers 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-7274) http://links.puppetlabs.com/puppet-kick-deprecation still points to old puppet ticket; never updated
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols Puppet / PUP-7274 http://links.puppetlabs.com/puppet-kick-deprecation still points to old puppet ticket; never updated Change By: Geoff Nichols Assignee: Nicholas Fagerlund Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7272) Puppet not using latest facts
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7272 Puppet not using latest facts Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7265) Remove file face
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7265 Remove file face Change By: Geoff Nichols Sprint: AP Triage Accepted Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7284) hiera-eyaml option 'extension' is ignored
Title: Message Title Robert Heinzmann commented on PUP-7284 Re: hiera-eyaml option 'extension' is ignored I can confirm this bug with puppet-agent-1.9.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3317) Unparsed line in puppetdb.conf
Title: Message Title Geoff Nichols updated an issue PuppetDB / PDB-3317 Unparsed line in puppetdb.conf Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7254) Transient: HOCON gem fails to install during puppet spec tests
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7254 Transient: HOCON gem fails to install during puppet spec tests Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3317) Unparsed line in puppetdb.conf
Title: Message Title Geoff Nichols moved an issue PuppetDB / PDB-3317 Unparsed line in puppetdb.conf Change By: Geoff Nichols Affects Version/s: PUP 4.9.2 Component/s: PuppetDB Component/s: Puppet Server Component/s: PuppetDB Key: PUP PDB - 7247 3317 Project: Puppet PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3317) Unparsed line in puppetdb.conf
Title: Message Title Geoff Nichols updated an issue PuppetDB / PDB-3317 Unparsed line in puppetdb.conf Change By: Geoff Nichols Team: Agent & Platform 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-5747) puppet/PuppetBoard 2.7.3 not running with puppetdb 2.3.8
Title: Message Title Josh Cooper commented on PUP-5747 Re: puppet/PuppetBoard 2.7.3 not running with puppetdb 2.3.8 Hi Manoj Kumar, puppetboard is not a Puppet project, so I'm going to close this ticket. I recommend following up at https://github.com/voxpupuli/puppetboard. Might also try slack.puppet.com or IRC for assistance. 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-7224) Replace the Rgen AST model with one generated from a Pcore model
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7224 Replace the Rgen AST model with one generated from a Pcore model Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-7283) Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization
Title: Message Title Adrien Thebo commented on PUP-7283 Re: Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization Karen Van der Veer Heh... my error, thanks for catching this! 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-7283) Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7283 Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization Change By: Adrien Thebo Sprint: PDE SE 2017-03-08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Charlie Sharpsteen commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error Turns out that the nulls are present in discarded commands, they just show up as the unicode escape sequence \u rather than literal null values. 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 Ryan Senior commented on PDB-3107 Re: new-command-schema validation prevents PDB/NewRelic integration Yeah, we just need to board this new feature for the LTS. Eric Sorenson offered to help here. 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 commented on PDB-3107 Re: new-command-schema validation prevents PDB/NewRelic integration Susan McNerney do we need to do any boarding paperwork for this? Ryan Senior may have some comments on scope. 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-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7204 Add support for mapped paths in hiera.yaml version 5 Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-7240) A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists.
Title: Message Title Henrik Lindberg assigned an issue to Joshua Partlow Joshua Partlow We now think you have what you need for meep and the outstanding PR that makes use of lookup. That PR is marked "DO NOT MERGE", so I am assigning this ticket to you to decide on what should happen next. Puppet / PUP-7240 A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists. Change By: Henrik Lindberg Assignee: Joshua Partlow 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.
