Jira (PUP-7108) Automatically create pseudo-localized PO file for testing in CI
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7108 Automatically create pseudo-localized PO file for testing in CI Change By: Geoff Nichols Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1720) regression on overidding external facts (shell)
Title: Message Title Branan Riley updated an issue Facter / FACT-1720 regression on overidding external facts (shell) Change By: Branan Riley Sprint: Platform OS 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-1720) regression on overidding external facts (shell)
Title: Message Title Branan Riley updated an issue Facter / FACT-1720 regression on overidding external facts (shell) Change By: Branan Riley Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1724) Facter: error while resolving custom fact "uid_min"
Title: Message Title Branan Riley commented on FACT-1724 Re: Facter: error while resolving custom fact "uid_min" Hi Jo, Without the implementation of your `uid_min` fact, it's hard to tell exactly what's going wrong here. That is not a Facter error, but a Ruby error, indicating that you're not properly handling character encodings correctly in your fact implementation. Given the above, this may be better suited to a question on https://ask.puppet.com. I'm happy to leave this open until we confirm that's the case, though. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1724) Facter: error while resolving custom fact "uid_min"
Title: Message Title Branan Riley assigned an issue to Unassigned Facter / FACT-1724 Facter: error while resolving custom fact "uid_min" Change By: Branan Riley Assignee: Laura Raney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1724) Facter: error while resolving custom fact "uid_min"
Title: Message Title Branan Riley updated an issue Facter / FACT-1724 Facter: error while resolving custom fact "uid_min" Change By: Branan Riley Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3400) change all varchar columns to text
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3400 change all varchar columns to text Change By: Russell Mull Sprint: Hopper Data Platform 2017-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3611) Fact filter from overview page uses nested loops and times out
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3611 Fact filter from overview page uses nested loops and times out Change By: Russell Mull Sprint: Hopper Data Platform 2017-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3195) Investigate "Reset (nothing) on connection"
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3195 Investigate "Reset (nothing) on connection" Change By: Russell Mull Sprint: Hopper Data Platform 2017-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7802) Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Title: Message Title Charlie Sharpsteen commented on PUP-7802 Re: Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer Ah, I guess I should have qualified that as: disable automatic lookups, but keep explicit lookups via the lookup() function working. Seems like setting an empty hierarchy would disable everything. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7768) Heredoc is not accepted by the Puppet TypeParser
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7768 Heredoc is not accepted by the Puppet TypeParser 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-7768) Heredoc is not accepted by the Puppet TypeParser
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-7768 Heredoc is not accepted by the Puppet TypeParser 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-7768) Heredoc is not accepted by the Puppet TypeParser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7768 Heredoc is not accepted by the Puppet TypeParser Change By: Henrik Lindberg Sub-team: Language Team: Data Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Henrik Lindberg commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module Trevor Vaughan It would be per key - yes. APL for defined types has issues if introduced: it means that that every non explicitly set parameter for every resource would need two lookups (one with resource type + title, and one with resource type) this means many thousands of additional lookups which may be a big performance problem parameter binding by APL would win over resource type defaults (probably a good thing though), but resource type defaults are more versatile as they apply per scope, now if APL wins it is not a good thing. To work as a replacement of resource type defaults hiera would need to be aware of scope (more complex, and possibly a performance problem). would need to involve the title of the resource in the key to make it unique, this creates potential issues when authoring the data as titles do not have the same constraints as does parameter names. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (FACT-1674) Add support for systemd-nspawn virtualization detection
Title: Message Title
Casey Williams updated an issue
Facter / FACT-1674
Add support for systemd-nspawn virtualization detection
Change By:
Casey Williams
Facter doesn't currently detect nspawn, but it would be simple to add. Currently, when facter reports whatever comes out of `virt-what` for nspawn containers (since checking ` checks {{ proc/1/cgroup ` as }} to look for docker and lxc, it does not attempt to find nspawn. All that is necessary seems to be adding a check for a string along the lines of {{/machine.slice/machine-name.scope}} alongside these docker or and lxc checks (this is insufficient what comes out of {{/proc/1/cgroup}} for nspawn containers ). But since this doesn't happen, facter falls back to using virt-what, which does not attempt to detect nspawn. If a cgroup check is insufficient for some reason, FACT-1617 also has some very useful information about how to correct this - see systemd's `detect_container` function [here|https://github.com/systemd/systemd/blob/master/src/basic/virt.c#L395]. In short, it seems that we can could also check the ` {{ container ` }} environment variable for the systemd process to get ` {{ systemd-nspawn ` }} .
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this
Jira (PUP-7802) Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Title: Message Title Thomas Hallgren commented on PUP-7802 Re: Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer There is no specific setting that will disable environment lookups but a hierarchy: [] entry in the hiera.yaml file at the environment root will effectively disable all environment lookups. If the file contains a hierarchy that needs to be preserved for later use, then that needs to be commented out. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7802) Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Title: Message Title Charlie Sharpsteen commented on PUP-7802 Re: Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer Is there a way to disable automatic parameter lookup at the environment level? Folks that are currently setting data_binding_terminus = none will likely expect to maintain this behavior when they migrate from Hiera 3 over to Hiera 5. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7800) relationship to aliased Package resources fails
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7800 relationship to aliased Package resources fails Change By: Henrik Lindberg Sub-team: Language Story Points: 1 Release Notes Summary: It did not work to create a relationship to a Package resource using an alias instead of its title (while aliases for other types of resources worked). This is now fixed. Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-7800) relationship to aliased Package resources fails
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7800 relationship to aliased Package resources fails Change By: Henrik Lindberg Priority: Minor 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-7800) relationship to aliased Package resources fails
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7800 relationship to aliased Package resources fails Change By: Henrik Lindberg Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7800) relationship to aliased Package resources fails
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7800 relationship to aliased Package resources fails Change By: Henrik Lindberg Summary: alias parameter fails with package relationship to aliased Package resources fails Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7783) error message when using break() instead of return() is hard to understand
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7783 error message when using break() instead of return() is hard to understand Change By: Henrik Lindberg Assignee: Henrik Lindberg Sub-team: Language Story Points: 1 Release Notes Summary: only improvement of an error message Team: Platform Core Release Notes: Not Needed Fix Version/s: PUP 5.1.0 Component/s: Language Add Comment
Jira (PUP-7783) error message when using break() instead of return() is hard to understand
Title: Message Title Henrik Lindberg commented on PUP-7783 Re: error message when using break() instead of return() is hard to understand Sorry, moving it to "needs information" was a mistake. Thanks for pointing it out. There is now some other ticket that is not in "needs information" as intended Will see what we can do about improving that error message - I think it is terse because it is caught in a context where it is unexpected, I think there are better error messages when break/return that occurs in other contexts where they are not allowed. The error says "StopIteration" which is what break() does, and then there is no iteration in progress that catches that - but yeah, very cryptic. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7802) Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7802
Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Change By:
Henrik Lindberg
Sub-team:
Language
Story Points:
1
Release Notes Summary:
A regression introduced with Hiera 5 caused the setting of {{data_binding_terminus=none}} to turn off the {{hiera_xxx}} functions in addition to the expected disablement of APL (Automatic Parameter Lookup) from the global layer. This is now changed so that the {{hiera_xxx}} calls will continue to work. The {{lookup}} function will continue to return the same result as APL (if the terminus is disabled, then global hiera is also turned off for lookup, while APL and lookup from environment and module layers is still enabled). In the longer run, the {{data_binding_terminus}} setting will be deprecated and removed along with the hiera 3 support. With the speedups and new features in hiera 5, there should be no reason to turn off the {{data_binding_terminus}}.
Sprint:
Platform Core 2017-08-08
Release Notes:
Bug Fix
Add Comment
Jira (PUP-7802) Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7802 Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer Change By: Henrik Lindberg Fix Version/s: PUP 5.0.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-7802) Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7802 Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer Change By: Henrik Lindberg Fix Version/s: PUP 4.10.5 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7802) Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7802 Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer 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 (PDB-3630) Configurable facts blacklist
Title: Message Title Russell Mull commented on PDB-3630 Re: Configurable facts blacklist There's kind of demand; it's a facility we see being useful to work around problems that we just aren't going to be able to solve in PuppetDB any time soon. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3630) Configurable facts blacklist
Title: Message Title Maggie Dreyer commented on PDB-3630 Re: Configurable facts blacklist Ah yeah, there's a ticket for that: https://tickets.puppetlabs.com/browse/FACT-1575. Just hasn't been prioritized, but we might be able to move on it if there's demand. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3630) Configurable facts blacklist
Title: Message Title Wyatt Alt commented on PDB-3630 Re: Configurable facts blacklist Ideally the blacklist could support custom 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 (PUP-7804) Should not fall back to 'server' for requesting file resources when 'server_list' is specified
Title: Message Title Branan Riley assigned an issue to Unassigned Puppet / PUP-7804 Should not fall back to 'server' for requesting file resources when 'server_list' is specified Change By: Branan Riley Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3630) Configurable facts blacklist
Title: Message Title Maggie Dreyer commented on PDB-3630 Re: Configurable facts blacklist I would be more in favor of extending the Facter blocking to address this, or maybe using caching, depending on the use case. Right now, only a small number of facts can be blocked, but we can easily extend this list. We limited it because we didn't want to enable blocking of facts that lots of other facts rely on. So instead we picked a couple known to be problematic, namely "EC2" and "filesystem" facts. Are there other specific cases you'd like to be able to block? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7804) Should not fall back to 'server' for requesting file resources when 'server_list' is specified
Title: Message Title Branan Riley updated an issue Puppet / PUP-7804 Should not fall back to 'server' for requesting file resources when 'server_list' is specified Change By: Branan Riley Team: Platform Core OS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7804) Should not fall back to 'server' for requesting file resources when 'server_list' is specified
Title: Message Title Branan Riley updated an issue Puppet / PUP-7804 Should not fall back to 'server' for requesting file resources when 'server_list' is specified Change By: Branan Riley Sprint: Platform Core Grooming OS 2017-08-09 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7804) Should not fall back to 'server' for requesting file resources when 'server_list' is specified
Title: Message Title Branan Riley updated an issue Puppet / PUP-7804 Should not fall back to 'server' for requesting file resources when 'server_list' is specified Change By: Branan Riley Fix Version/s: PUP 5.0.z Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7804) Should not fall back to 'server' for requesting file resources when 'server_list' is specified
Title: Message Title Branan Riley assigned an issue to Branan Riley Puppet / PUP-7804 Should not fall back to 'server' for requesting file resources when 'server_list' is specified Change By: Branan Riley Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3630) Configurable facts blacklist
Title: Message Title Russell Mull commented on PDB-3630 Re: Configurable facts blacklist Maggie Dreyer iirc you worked on the facter blacklist in some way; but I also seem to remember it having some kind of limitations. do you think it would be worth having such a mechanism in PDB, or would it be actively bad? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7804) Should not fall back to 'server' for requesting file resources when 'server_list' is specified
Title: Message Title Branan Riley moved an issue Puppet / PUP-7804 Should not fall back to 'server' for requesting file resources when 'server_list' is specified Change By: Branan Riley Key: PE PUP - 21709 7804 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3630) Configurable facts blacklist
Title: Message Title Wyatt Alt commented on PDB-3630 Re: Configurable facts blacklist a blacklist went into facter a while ago to address the same issue this addresses. If there's functionality gaps it'd be worth discussing that with the facter team before putting another blacklist here – having two seems confusing to support. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3630) Configurable facts blacklist
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3630 Configurable facts blacklist Change By: Russell Mull Sprint: Data Platform Next Sprint Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3630) Configurable facts blacklist
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3630 Configurable facts blacklist Issue Type: New Feature Assignee: Unassigned Created: 2017/07/26 11:20 AM Priority: Normal Reporter: Russell Mull Add a place in the puppetdb config file to put a set of facts that are blacklisted on ingestion. This will provide an escape hatch for sites that are dealing with poorly behaving facts (large, very dynamic facts) whose value they don't actually care about but which are knocking over the fact storage subsystem. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7790) Downgrading a package with pkgin fails silents
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7790 Downgrading a package with pkgin fails silents Change By: Maggie Dreyer Story Points: 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-7790) Downgrading a package with pkgin fails silents
Title: Message Title Maggie Dreyer assigned an issue to Josh Cooper Puppet / PUP-7790 Downgrading a package with pkgin fails silents Change By: Maggie Dreyer Assignee: Andrew Hill 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 (PDB-3624) Generational fact value GC
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3624 Generational fact value GC Change By: Russell Mull Sprint: Hopper Data Platform Next Sprint Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3625) Use upsert for fact storage
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3625 Use upsert for fact storage Change By: Russell Mull Sprint: Hopper Data Platform 2017-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3623) Minimal query perf test
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3623 Minimal query perf test Change By: Russell Mull Sprint: Hopper Data Platform 2017-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3625) Use upsert for fact storage
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3625 Use upsert for fact storage Change By: Russell Mull Sprint: Data Platform 2017-07-27 Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3626) Minimal storage perf test
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3626 Minimal storage perf test Change By: Russell Mull Sprint: Hopper Data Platform 2017-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1651) facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1651 facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7 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-3629) (maint) Update travis build for Puppet5 release
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3629 (maint) Update travis build for Puppet5 release Issue Type: Bug Assignee: Unassigned Created: 2017/07/26 9:28 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-3628) (maint) Use puppet 4.8.1 for terminus spec tests
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3628 (maint) Use puppet 4.8.1 for terminus spec tests Issue Type: Bug Assignee: Unassigned Created: 2017/07/26 9:24 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (FACT-1723) Create Go bindings
Title: Message Title Jeff Yarnell updated an issue Facter / FACT-1723 Create Go bindings Change By: Jeff Yarnell Sprint: DISC 2017-07-26 , DISC 2017-08-09 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3611) Fact filter from overview page uses nested loops and times out
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-3611
Fact filter from overview page uses nested loops and times out
Change By:
Nick Walker
Attempting to filter the console overview page based on two fact filters causes a timeout in the console.The attempted query was:{noformat}2017-07-03 13:49:03.676 UTC [db:pe-puppetdb,sess:595a3ced.c711,pid:50961,vtid:22/490887,tid:0] LOG: duration: 503820.138 ms execute S_826/C_827: WITH inactive_nodes AS (SELECT certname FROM certnames WHERE (deactivated IS NOT NULL OR expired IS NOT NULL)) SELECT certnames.certname AS certname FROM factsets fs LEFT JOIN environments ON fs.environment_id = environments.id LEFT JOIN producers ON fs.producer_id = producers.id LEFT JOIN certnames ON fs.certname = certnames.certname WHERE (((certnames.certname) in ( (SELECT fs.certname AS certname FROM factsets fs INNER JOIN facts f ON fs.id = f.factset_id INNER JOIN fact_paths fp ON f.fact_path_id = fp.id INNER JOIN value_types vt ON f.value_type_id = vt.id LEFT JOIN environments env ON fs.environment_id = env.id WHERE (vt.id <> 5 AND ((fp.path ~ $1 AND fp.path IS NOT NULL) AND (f.value_string = $2 ) ) AND ((certnames.certname) in ( (SELECT fs.certname AS certname FROM factsets fs INNER JOIN facts f ON fs.id = f.factset_id INNER JOIN fact_paths fp ON f.fact_path_id = fp.id INNER JOIN value_types vt ON f.value_type_id = vt.id LEFT JOIN environments env ON fs.environment_id = env.id WHERE (vt.id <> 5 AND ((fp.path ~ $3 AND fp.path IS NOT NULL) AND (f.value_string = $4 ) )){noformat} Formatted for readability:{noformat}WITH inactive_nodes AS ( SELECT certname FROM certnames WHERE (deactivated IS NOT NULL OR expired IS NOT NULL)) SELECT certnames.certname AS certname FROM factsets fs LEFT JOIN environments ON fs.environment_id = environments.id LEFT JOIN producers ON fs.producer_id = producers.id LEFT JOIN certnames ON fs.certname = certnames.certname WHERE (((certnames.certname) in ( (SELECT fs.certname AS certnameFROM factsets fsINNER JOIN facts f ON fs.id = f.factset_idINNER JOIN fact_paths fp ON f.fact_path_id = fp.idINNER JOIN value_types vt ON f.value_type_id = vt.idLEFT JOIN environments env ON fs.environment_id = env.idWHERE (vt.id <> 5 AND ((fp.path ~ $1 AND fp.path IS NOT NULL) AND (f.value_string = $2 ) ) AND ((certnames.certname) in ( (SELECT fs.certname AS certname FROM factsets fs INNER JOIN facts f ON fs.id = f.factset_id INNER JOIN fact_paths fp ON f.fact_path_id = fp.id INNER JOIN value_types vt ON f.value_type_id = vt.id LEFT JOIN environments env
Jira (PUP-7802) Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Title: Message Title Henrik Lindberg commented on PUP-7802 Re: Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer The PR will make hiera be backwards compatible with hiera 3 as follows: if the terminus is none, the global layer is not used for APL (env and module layers, if present are still used) calls to hiera_xxx will use the global layer even if terminus is none (this is backwards compatible - and what is changed in this ticket) calls to lookup behave as APL; if the terminus is none the global layer is not used. The difference in behavior (lookup/hiera_xxx) is unfortunate as it makes it more difficult for users using the combination of terminus none and hiera_xxx calls to gradually migrate to hiera 5 and calls to lookup. The real solution is to drop the data_binding_terminus setting completely and instead control the result solely via the hiera.yaml (version 5) configuration format. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7802) Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Title: Message Title Thomas Hallgren commented on PUP-7802 Re: Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer Is lookup() affected at all? No. The change only affects the hiera_xxx functions. Is APL still turned on for environment and module layers when terminus is set to 'none'? Yes, the data_binding_terminus setting only affects the global layer. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7802) Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer
Title: Message Title Henrik Lindberg commented on PUP-7802 Re: Disabling automatic class parameter lookup in Hiera 5 also disables the global hierarchy layer Thomas Hallgren thanks for the PR with a fix. Two questions: Is lookup() affected at all? Is APL still turned on for environment and module layers when terminus is set to 'none'? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
