Jira (PUP-4867) Puppets modulepath setting should be made into separate settings for distmoduledir / sitemoduledir

[Matthew Patton (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Patton commented on  PUP-4867 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppets modulepath setting should be made into separate settings for distmoduledir / sitemoduledir  
 
 
 
 
 
 
 
 
 
 
Might as well add the missing 'local_module_dir'. Really these vars should be formatted with hyphens. If ModulePath is expressly defined than these 3 helpers are ignored. Otherwise they get glued together with BaseModulePath. 
Why not take a page out of Perl's book and make the directory names a bit more explicit? (if the word '-modules' is excessive, then shorten). 
'/usr/share/puppet/site-modules' = sysadmin provided often 3rd party (Forge) that are frequently shared across hosts via common filesystem mount.  
 

'/opt/puppetlabs/puppet/vendor-modules' = ONLY modules that are shipped with distribution packages. A purist would insist all 3rd party (eg. Forge) modules do NOT go under /opt/puppetlabs even if inside a 'site-module' subdirectory (same applies to Facts), but the installed base may be too wed to using the /opt/puppetlabs path instead of /usr/local/share. Or may consider Forge to be official enough to merit inclusion.
 
 
 

'/etc/puppet[labs/code/]modules' = modules specific to a host. But this really should be deprecated and steered (symlink?) to '/usr/local/share/puppet/modules'. /etc is properly reserved for system-wide or environment-based configuration data (Facts, Hiera, Node) only. It is improper to store potentially sizable code or executables here.
 
 
I don't see why a hard-line stance can't be taken. It's not so difficult to move things to where they should have been all along. If some users don't like the new defaults, they can always add directives to puppet.conf 
ref: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
 

Jira (PUP-4923) Exec resource can use facts comparison for onlyif and unless attributes

[Matthew Patton (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Patton commented on  PUP-4923 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Exec resource can use facts comparison for onlyif and unless attributes  
 
 
 
 
 
 
 
 
 
 
Puppet Apply could benefit from this right now and requires no extra features.  
If still using Server-side evaluation, then the only way forward would be to wrap the Exec() declaration inside an IF which is very ugly and likely to have unpredictable results. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDOC-171) generate the hiera keynames to use for parameterised classes

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PDOC-171 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: generate the hiera keynames to use for parameterised classes  
 
 
 
 
 
 
 
 
 
 
so you mean extend this ticket to cover if someone was using in-module hiera data to set defaults then pick up those and document what they resolve to? That would be even better and really useful. perhaps there could even be some _javascript_ magic so that you could see what defaults eg for different OS's 
On 3 Aug. 2017 21:25, "Henrik Lindberg (JIRA)" < issue-updates+henriklindb...@puppet.com> wrote: 
Henrik Lindberg  commented on [image: New Feature] PDOC-171  
Re: generate the hiera keynames to use for parameterised classes  
When considering adding support for hiera bindings it is also of value to make it possible to document default data bindings and lookup options. A module could for example come with lookup options configured for deep merge etc for some parameters, and could have defaults bound in hiera (as opposed to defaults in manifests). The most elegant would be if PDOC could pick up the information directly from hiera, but this gets complicated because information can come from any kind of backend. It is therefore best if this is documented in the puppet logic. If doing that, then there needs to be a structured way to mark up a parameter with such information. [image: Add Comment]  Add Comment  
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) [image: Atlassian logo] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 

Jira (FACT-1642) facter should understand cpu model on Power for the processors.model fact

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1642 
 
 
 
  facter should understand cpu model on Power for the processors.model fact  
 
 
 
 
 
 
 
 
 

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-1725) Migrate os-specific acceptance tests from 3.6.x into the fact-specific tests in 3.7.x

[Scott Garman (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott Garman created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1725 
 
 
 
  Migrate os-specific acceptance tests from 3.6.x into the fact-specific tests in 3.7.x  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/03 1:29 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Scott Garman 
 
 
 
 
 
 
 
 
 
 
In the facter 3.7.x branch, we stopped using using os-specific test files in favor of fact-specific ones. During a merge-up it was noted that in 3.6.x we have two os-specific files, el.rb and ubuntu.rb, which may need to be refactored into the fact-specific tests used in 3.7.x. 
https://github.com/puppetlabs/facter/blob/3.6.x/acceptance/tests/facts/el.rb 
https://github.com/puppetlabs/facter/blob/3.6.x/acceptance/tests/facts/ubuntu.rb 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
   

Jira (FACT-1714) Use posix::operating_system_resolver for bsd, freebsd and openbsd

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1714 
 
 
 
  Use posix::operating_system_resolver for bsd, freebsd and openbsd  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7797) Report format 6 logs do not indicate corrective changes

[Hunter (Hunner) Haugen (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hunter (Hunner) Haugen commented on  PUP-7797 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Report format 6 logs do not indicate corrective changes  
 
 
 
 
 
 
 
 
 
 
That's acceptable, and kind of expected. Thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1714) Use posix::operating_system_resolver for bsd, freebsd and openbsd

[Maggie Dreyer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1714 
 
 
 
  Use posix::operating_system_resolver for bsd, freebsd and openbsd  
 
 
 
 
 
 
 
 
 

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-6966) Tidy and File cannot remove fifo or socket files

[Maggie Dreyer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer assigned an issue to Maggie Dreyer 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6966 
 
 
 
  Tidy and File cannot remove fifo or socket files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Assignee:
 
 Maggie Dreyer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (FACT-1354) Facter ec2_userdata handles binary data incorrectly

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  FACT-1354 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter ec2_userdata handles binary data incorrectly  
 
 
 
 
 
 
 
 
 
 
This is an issue when trying to use JSON serialization, see https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/dpLyduMbCrE/RuBFnC8MAAAJ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-4669) Varargs support for "args by name" calls to user defined resource types and EPP templates

[David Schmitt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Schmitt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4669 
 
 
 
  Varargs support for "args by name" calls to user defined resource types and EPP templates  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Schmitt 
 
 
 

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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2297) Remove the defined function

[David Schmitt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Schmitt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2297 
 
 
 
  Remove the defined function  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Schmitt 
 
 
 

Team:
 
 Puppet Developer Experience 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-3995) Prevent node resource names from potentially overlapping with other resources

[David Schmitt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Schmitt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3995 
 
 
 
  Prevent node resource names from potentially overlapping with other resources  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Schmitt 
 
 
 

Team:
 
 Puppet Developer Experience 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-4669) Varargs support for "args by name" calls to user defined resource types and EPP templates

[David Schmitt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Schmitt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4669 
 
 
 
  Varargs support for "args by name" calls to user defined resource types and EPP templates  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Schmitt 
 
 
 

Team:
 
 Puppet Developer Experience 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (NPUP-22) Ensure settings and top-level variables match (to a logical extent) those set by the Ruby implementation

[David Schmitt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Schmitt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-22 
 
 
 
  Ensure settings and top-level variables match (to a logical extent) those set by the Ruby implementation  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Schmitt 
 
 
 

Team:
 
 Puppet Developer Experience 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows

[Thomas Kishel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Kishel commented on  PUP-6134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows  
 
 
 
 
 
 
 
 
 
 
This bug prevents Package Inspection from being able to inspect system gems, making Package Inspection inaccurate. 
I wrote a module to workaround this bug: 
https://forge.puppet.com/tkishel/system_gem 
It's basically the PR. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7807) AIX mount resource remounts without options

[Owen Rodabaugh (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7807 
 
 
 
  AIX mount resource remounts without options  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Priority:
 
 Major Normal 
 
 
 

CS Severity:
 
 3 - Serious 
 
 
 

CS Business Value:
 
 4 - $ 
 
 
 

CS Frequency:
 
 2 - 5-25% of Customers 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1597) WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug.

[Owen Rodabaugh (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1597 
 
 
 
  WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Priority:
 
 Major Normal 
 
 
 

CS Business Value:
 
 4 - $ 
 
 
 

CS Frequency:
 
 2 - 5-25% of Customers 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows

[Owen Rodabaugh (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6134 
 
 
 
  Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Priority:
 
 Reviewed Minor 
 
 
 

CS Impact:
 
 This can be worked around via an exec. It's another tick against supporting windows as a first class citizen in our ecosystem. 
 
 
 

CS Severity:
 
 2 - Annoyance 
 
 
 

CS Business Value:
 
 3 -  
 
 
 

CS Frequency:
 
 1 - 1-5% of Customers 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 

Jira (PUP-7521) Puppet Acceptance Test Failure in Imaging Acceptance Tests

[John O'Connor (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John O'Connor commented on  PUP-7521 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Acceptance Test Failure in Imaging Acceptance Tests  
 
 
 
 
 
 
 
 
 
 
A new PR (https://github.com/puppetlabs/ci-job-configs/pull/3182) has just been merged up to fix the issue with tests/catalog_with_binary_data.rb Just need to wait until the merge is promoted to master to see the results in the imaging acceptance tests. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7678) Add functions 'all' and 'any'

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7678 
 
 
 
  Add functions 'all' and 'any'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 The functions {{any}} and {{all}} have been added to puppet. They iterate over something iterable and tests if there is at least one element for which a lambda returns  true  a truthy value  ({{any}}) or if the lambda returns  {{true}}  a truthy value  for all elements ({{all}}). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7678) Add functions 'all' and 'any'

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7678 
 
 
 
  Add functions 'all' and 'any'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 5.y 
 
 
 

Fix Version/s:
 
 PUP 5.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7678) Add functions 'all' and 'any'

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7678 
 
 
 
  Add functions 'all' and 'any'  
 
 
 
 
 
 
 
 
 

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 (FACT-1720) regression on overidding external facts (shell)

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1720 
 
 
 
  regression on overidding external facts (shell)  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Needs Assessment Automate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7792) argument type mismatch message could be clearer

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7792 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: argument type mismatch message could be clearer  
 
 
 
 
 
 
 
 
 
 
This error is "you provided the wrong arguments in a call to the lookup function", but it is presented in a generic way that makes it harder to understand that. Maybe just tweaking the words leading up to the part where the non matching alternatives is enough. 
A really cool feature would be to send less to an agent and instead provide an id/URL that can be used to retrieve the full message from the server. This would help a lot when users are asked for things like a stack trace (which is available server side). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1675) virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1675 
 
 
 
  virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Needs Assessment No Action 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (FACT-1714) Use posix::operating_system_resolver for bsd, freebsd and openbsd

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1714 
 
 
 
  Use posix::operating_system_resolver for bsd, freebsd and openbsd  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Needs Assessment No Action 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7811) puppet-agent 5.0.x build failed for aix-6.1-ppc

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7811 
 
 
 
  puppet-agent 5.0.x build failed for aix-6.1-ppc  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Needs Assessment No Action 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7792) argument type mismatch message could be clearer

[Eric Sorenson (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  PUP-7792 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: argument type mismatch message could be clearer  
 
 
 
 
 
 
 
 
 
 
I don't think it requires a ton of UX research, though some validation with users such as Adam Buxton would help to make sure we're moving in the right direction. 
But if we look at the message, even in the context of Puppet's historically bad track record at producing helpful errors (whitespace added for readabilty): 
 
 
 
 
 
 
  
 
 
 
 
 
 
Error: Could not retrieve catalog from remote server:  Error 500 on SERVER:  Server Error:  Evaluation Error: Error while evaluating a Resource Statement,  Evaluation Error: Error while evaluating a Function Call, 'lookup' expects one of: (NameType = Variant[String, Array[String]] name,  ValueType = Type value_type?,  MergeType = Variant[String[1, default],  Hash[String, Scalar]] merge?) rejected: expects between 1 and 3 arguments, got 4 
 
Adam is an expert Puppet user and I am ... somewhat less than that, but not a newbie, but I have no idea what that message is telling us to do. 
IMO it'd be way better to simply conceal everything except the manifest line number and position and say "something went wrong with the type system", and maybe log the full error server-side, rather than expose the guts of it without a path to action. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
   

Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available

[Anthony Chevalet (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anthony Chevalet commented on  PUP-7813 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum package provider: ensure => latest fails when packages update available  
 
 
 
 
 
 
 
 
 
 
Hi Josh Cooper, here it is: 
 
 
 
 
 
 
p-infra-katello.ks.net 12:11:46 ~ # puppet --version 
 
 
 
 
4.10.5 
 
 
 
 
p-infra-katello.ks.net 12:11:48 ~ # puppet resource package kernel  
 
 
 
 
package { 'kernel': 
 
 
 
 
  ensure => '3.10.0-514.21.2.el7', 
 
 
 
 
} 
 
 
 
 
p-infra-katello.ks.net 12:11:55 ~ # puppet resource package kernel ensure=latest --trace 
 
 
 
 
Error: Could not get latest version: undefined method `[]' for nil:NilClass 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/yum.rb:112:in `update_to_hash' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/yum.rb:95:in `block in parse_updates' 
  

Jira (PUP-7792) argument type mismatch message could be clearer

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7792 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: argument type mismatch message could be clearer  
 
 
 
 
 
 
 
 
 
 
Thinking about this again. In order to improve the readability of type mismatch messages we would need to do a quite comprehensive UX study and reevaluate both the wording used and the implemented heuristics. (I think it is decent as it is, but there is room for improvement).  
However, tweaking per observed error will have the risk that some other case gets worse, so to do something this becomes a bigger thing. Not sure how to prioritize that. Ping Eric Sorenson. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7806) puppet epp render fails to find variables with ::

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7806 
 
 
 
  puppet epp render fails to find variables with ::  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 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-7806) puppet epp render fails to find variables with ::

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7806 
 
 
 
  puppet epp render fails to find variables with ::  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 

Release Notes Summary:
 
 It was not possible to set arbitrary name spaced variable values when testing epp templates with {{epp render}} and giving values with a values_file. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7806) puppet epp render fails to find variables with ::

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7806 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet epp render fails to find variables with ::  
 
 
 
 
 
 
 
 
 
 
It is indeed a limitation of what the given values_file can contain - it currently only sets unqualified (local) variables. There is no reason why it would not be allowed to set any namespaced variable value as this is for testing / mocking. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7815) Modules can find and list all their tasks

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7815 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Modules can find and list all their tasks  
 
 
 
 
 
 
 
 
 
 
I think tasks should be represented by puppet data types. We then have all the loading, reflection, serialization, etc. already implemented. It also makes it possible to directly and without ambiguity refer to a task via its name. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDOC-171) generate the hiera keynames to use for parameterised classes

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PDOC-171 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: generate the hiera keynames to use for parameterised classes  
 
 
 
 
 
 
 
 
 
 
When considering adding support for hiera bindings it is also of value to make it possible to document default data bindings and lookup options. A module could for example come with lookup options configured for deep merge etc for some parameters, and could have defaults bound in hiera (as opposed to defaults in manifests). The most elegant would be if PDOC could pick up the information directly from hiera, but this gets complicated because information can come from any kind of backend. It is therefore best if this is documented in the puppet logic. If doing that, then there needs to be a structured way to mark up a parameter with such information. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7810) augeas don't parse the ssh/sshd config option HostKeyAlgorithms/KexAlgorithms as an array

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-7810 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: augeas don't parse the ssh/sshd config option HostKeyAlgorithms/KexAlgorithms as an array  
 
 
 
 
 
 
 
 
 
 
Ah, sorry about that, I misunderstood. It looks like the ssh.aug lens that we ship in puppet-agent needs updating: 
 
 
 
 
 
 
let key_re = /[A-Za-z0-9]+/ 
 
 
 
 
   - /SendEnv|Host|ProxyCommand|RemoteForward|LocalForward|MACs|Ciphers/i
 
 
 
 
 
 
 
I'm going to move this ticket to the PA project. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7810) augeas don't parse the ssh/sshd config option HostKeyAlgorithms/KexAlgorithms as an array

[Frank (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank commented on  PUP-7810 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: augeas don't parse the ssh/sshd config option HostKeyAlgorithms/KexAlgorithms as an array  
 
 
 
 
 
 
 
 
 
 
I don't use an external module for it. Only the puppet augeas function is used. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7810) augeas don't parse the ssh/sshd config option HostKeyAlgorithms/KexAlgorithms as an array

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7810 
 
 
 
  augeas don't parse the ssh/sshd config option HostKeyAlgorithms/KexAlgorithms as an array  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Assignee:
 
 Alex Dreyer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7810) augeas don't parse the ssh/sshd config option HostKeyAlgorithms/KexAlgorithms as an array

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper assigned an issue to Alex Dreyer 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7810 
 
 
 
  augeas don't parse the ssh/sshd config option HostKeyAlgorithms/KexAlgorithms as an array  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Assignee:
 
 Josh Cooper Alex Dreyer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7810) augeas don't parse the ssh/sshd config option HostKeyAlgorithms/KexAlgorithms as an array

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-7810 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: augeas don't parse the ssh/sshd config option HostKeyAlgorithms/KexAlgorithms as an array  
 
 
 
 
 
 
 
 
 
 
I think you're running into an issue with an external module which looks to be fixed in https://github.com/hercules-team/augeasproviders_ssh/commit/bc3afed1a24f20ea6c44f9d5d1d132f2592a41fe. Try out the latest version: https://forge.puppet.com/herculesteam/augeasproviders_ssh/changelog#253 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3866) File checksum should not be triggered when 'replace => false'

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-3866 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File checksum should not be triggered when 'replace => false'  
 
 
 
 
 
 
 
 
 
 
When replace is false and checksum is mtime, then puppet will open and read big_file_01 3 times, once for each copy operation to 02, 03, 04. It appears puppet is reading the entire file contents into memory. This is due to the file serving code 
 
 
 
 
 
 
[root@pnfo90tpwvcp5v9 ~]# cat manifest.pp 
 
 
 
 
  exec { '/usr/bin/dd if=/dev/urandom of=/tmp/big_file_01 bs=1MB count=100': 
 
 
 
 
creates => '/tmp/big_file_01', 
 
 
 
 
  } -> 
 
 
 
 
  
 
 
 
 
  file { [ '/tmp/big_file_02', 
 
 
 
 
   '/tmp/big_file_03', 
 
 
 
 
   '/tmp/big_file_04' ]: 
 
 
 
 
ensure   => file, 
 
 
 
 
replace  => false, 
 
  

Jira (PUP-3866) File checksum should not be triggered when 'replace => false'

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3866 
 
 
 
  File checksum should not be triggered when 'replace => false'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (FACT-1597) WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug.

[Stefan Pijnappels (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Pijnappels updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1597 
 
 
 
  WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stefan Pijnappels 
 
 
 

CS Priority:
 
 Major 
 
 
 

CS Impact:
 
 Seen on multiple customer systems, in multiple theatres.APJ has many banking customers heavily dependent on AIX, and this has hit some but is likely to hit more. 
 
 
 

CS Severity:
 
 3 - Serious 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3251) Man page for puppet is useless

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3251 
 
 
 
  Man page for puppet is useless  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-7814 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: HTTPS file sources with non-puppet-trusted certs can't be used  
 
 
 
 
 
 
 
 
 
 
Our HTTP connection factory doesn't expose the ability for a client to request which trust anchors to use. The idea Jeremy Barlow and I had discussed previously was to allow the client to request a connection that 1) only trusts the puppet CA or 2) in addition trusts the certs in the puppet-agent cacerts bundle. If it's the latter, then the connection factory can call X509Store.set_default_paths to initialize the cert store. Marking this ticket as blocked on PUP-5069. 
Also, there's a similar issue when the puppetmaster/server's report processor tries to make an HTTPS connection (see PUP-7737). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7814) HTTPS file sources with non-puppet-trusted certs can't be used

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7814 
 
 
 
  HTTPS file sources with non-puppet-trusted certs can't be used  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available

[Josh Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-7813 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum package provider: ensure => latest fails when packages update available  
 
 
 
 
 
 
 
 
 
 
Hi Anthony Chevalet, I can't reproduce the issue: 
 
 
 
 
 
 
[root@pnfo90tpwvcp5v9 ~]# puppet resource package puppet-agent 
 
 
 
 
package { 'puppet-agent': 
 
 
 
 
  ensure => '1.10.5-1.el7', 
 
 
 
 
} 
 
 
 
 
[root@pnfo90tpwvcp5v9 ~]# puppet --version 
 
 
 
 
4.10.5 
 
 
 
 
[root@pnfo90tpwvcp5v9 ~]# puppet resource package kernel 
 
 
 
 
package { 'kernel': 
 
 
 
 
  ensure => '3.10.0-327.el7', 
 
 
 
 
}