Jira (PUP-7878) Change in Puppet type management breaks defined class checks

[Justin Couch (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Couch updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7878 
 
 
 
  Change in Puppet type management breaks defined class checks  
 
 
 
 
 
 
 
 
 

Change By:
 
 Justin Couch 
 
 
 
 
 
 
 
 
 
 After upgrading the puppet version on a puppet server from 5.0.1 to 5.1.0 puppet runs on all nodes referencing that master now fail with the same type of error.  It appears heavily  Downgrading the server's puppet version back to 5.0.1 results in no errors again. The bug appear to be  related to PUP-7670.   {{  [root@puppet ~]# puppet agent -tInfo: Using configured environment 'infrastructure'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsError: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, uninitialized constant Puppet::Pops::Types::PClassType at /etc/puppetlabs/code/environments/infrastructure/modules/puppetdb/manifests/master/config.pp:4:34 on node puppet.mydomain}}When looking at the code referenced, it appears that it is choking on a very common template{{class puppetdb::master::config (  $puppetdb_server = $::fqdn,  $puppetdb_port   = defined(Class['puppetdb']) ? {}}ie - the {{defined(Class['foo']) }} is what causes the problem. On playing on other nodes, not the puppet master, I see the same error in various different modules, depending on what the node requires.  For example, on a webserver node using Apache the line that trips this up is:{{[root@mezabaan1 ~]# puppet agent -tInfo: Using configured environment 'application'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsError: 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, uninitialized constant Puppet::Pops::Types::PClassType at /etc/puppetlabs/code/environments/application/modules/apache/manifests/service.pp:27:8 at /etc/puppetlabs/code/environments/application/modules/webserver/manifests/static.pp:77 on node mezabaan1.mydomain}}{{if ! defined(Class['apache::params']) }}I can replicate the exact same error in my own modules using the same code pattern. {{Info: Loading factsError: 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, uninitialized constant Puppet::Pops::Types::PClassType at /etc/puppetlabs/code/environments/application/modules/ntpd/manifests/config.pp:5:8 on node mezabaan1.mydomain}}{{ define ntpd::config (  Array[String] $local_servers = [],) { if ! defined( Class['ntpd::master']) }}etc etc. 
 
 
 
 
 
 
 
 
 
 
 
 

 

Jira (PUP-7878) Change in Puppet type management breaks defined class checks

[Justin Couch (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Couch updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7878 
 
 
 
  Change in Puppet type management breaks defined class checks  
 
 
 
 
 
 
 
 
 

Change By:
 
 Justin Couch 
 
 
 

Environment:
 
 Puppet Agent (open source) on Centos 7, Installed using both Yum and puppetlabs/puppet_agent modules.System managed using r10k and PuppetDB with puppet master server ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux] on the server 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (FACT-1475) facter returns wrong ipv6 information when IPV6 stack is disabled

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1475 
 
 
 
  facter returns wrong ipv6 information when IPV6 stack is disabled   
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Meier 
 
 
 

Labels:
 
 help_wanted  regression 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1475) facter returns wrong ipv6 information when IPV6 stack is disabled

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-1475 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter returns wrong ipv6 information when IPV6 stack is disabled   
 
 
 
 
 
 
 
 
 
 
We could at least validate the info we get from `ip` like whether the supposed ipv6 address contains a : (colon) otherwise drop it. 
This is what people are left to do now if they have hosts with ipv6 disabled, but are slowly enabling it and hence try to figure out, if the host has an ipv6 address. 
IMHO this is a pretty severe bug that is opened way too long, as it is reporting false facts, that people can't rely on, which makes the purpose of facts completely meaningless. Especially this wasn't the case in Facter versions < 3, so people have code that is with the newer facter version completely unreliable. So at least it is also a regression.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1475) facter returns wrong ipv6 information when IPV6 stack is disabled

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1475 
 
 
 
  facter returns wrong ipv6 information when IPV6 stack is disabled   
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Meier 
 
 
 

Affects Version/s:
 
 FACT 3.8.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-7878) Change in Puppet type management breaks defined class checks

[Justin Couch (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Couch updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7878 
 
 
 
  Change in Puppet type management breaks defined class checks  
 
 
 
 
 
 
 
 
 

Change By:
 
 Justin Couch 
 
 
 
 
 
 
 
 
 
 After upgrading the puppet version on a puppet server from 5.0.1 to 5.1.0 puppet runs on all nodes referencing that master now fail with the same type of error. It appears heavily related to PUP-7670.   {{  [root@puppet ~]# puppet agent -tInfo: Using configured environment 'infrastructure'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsError: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, uninitialized constant Puppet::Pops::Types::PClassType at /etc/puppetlabs/code/environments/infrastructure/modules/puppetdb/manifests/master/config.pp:4:34 on node puppet.mydomain}}When looking at the code referenced, it appears that it is choking on a very common template{{class puppetdb::master::config (  $puppetdb_server = $::fqdn,  $puppetdb_port   = defined(Class['puppetdb']) ? {}}ie - the {{defined(Class['foo']) }} is what causes the problem. On playing on other nodes, not the puppet master, I see the same error in various different modules, depending on what the node requires.  For example, on a webserver node using Apache the line that trips this up is:{{[root@mezabaan1 ~]# puppet agent -tInfo: Using configured environment 'application'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsError: 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, uninitialized constant Puppet::Pops::Types::PClassType at /etc/puppetlabs/code/environments/application/modules/apache/manifests/service.pp:27:8 at /etc/puppetlabs/code/environments/application/modules/webserver/manifests/static.pp:77 on node mezabaan1.mydomain}}{{if ! defined(Class['apache::params']) }}I can replicate the exact same error in my own modules using the same code pattern. {{Info: Loading factsError: 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, uninitialized constant Puppet::Pops::Types::PClassType at /etc/puppetlabs/code/environments/application/modules/ntpd/manifests/config.pp:5:8 on node mezabaan1.mydomain}}{{ define ntpd::config (  Array[String] $local_servers = [],) { if ! defined( Class['ntpd::master']) }}etc etc. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
  

Jira (PUP-7878) Change in Puppet type management breaks defined class checks

[Justin Couch (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Couch created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7878 
 
 
 
  Change in Puppet type management breaks defined class checks  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 5.1.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Breaking Change, Type System 
 
 
 

Created:
 

 2017/08/24 6:37 PM 
 
 
 

Environment:
 
 
Puppet Agent (open source) on Centos 7, Installed using both Yum and puppetlabs/puppet_agent modules. 
System managed using r10k and PuppetDB with puppet master server 
 
 
 

Labels:
 

 puppet-agent 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Justin Couch 
 
 
 
 
 
 
 
 
 
 
After upgrading the puppet version on a puppet server from 5.0.1 to 5.1.0 puppet runs on all nodes referencing that master now fail with the 

Jira (PUP-5934) Updated fact values should be submitted after each Puppet run

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-5934 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Updated fact values should be submitted after each Puppet run  
 
 
 
 
 
 
 
 
 
 
Submitting facts as part of the report seems like intuitive behavior to me. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John O'Connor (JIRA)]

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

 
 
 
 
 
 
 
  Re: Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 
 
I run the acceptance test suite on jenkins-imaging to test all the packet built platforms.  So far the suite has run ok on Japanese Windows, except for this run. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error

[Charlie Sharpsteen (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Charlie Sharpsteen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3058 
 
 
 
  Report not being stored in PuppetDB due to Unicode Error  
 
 
 
 
 
 
 
 
 

Change By:
 
 Charlie Sharpsteen 
 
 
 

Fix Version/s:
 
 PDB 4.4.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-7630) "Successful" puppet agent reports hide provider errors

[Owen Rodabaugh (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7630 
 
 
 
  "Successful" puppet agent reports hide provider errors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Priority:
 
 Needs Priority Major 
 
 
 

CS Impact:
 
 This has been a long standing issue. The console should not show a node as "unchanged" when there is an error in the report.Some customers never look into node reports unless it shows as an error on the front page of the console and due to this they probably won't notice these errors. False negatives are not good. 
 
 
 

CS Severity:
 
 3 - Serious 
 
 
 

CS Business Value:
 
 4 - $ 
 
 
 

CS Frequency:
 
 4 - 50-90% of Customers 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[Eric Delaney (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney commented on  PUP-7876 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 
 
I haven't seen this, but to date I haven't run the acceptance tests on a Japanese configured machine or anything like that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  PUP-7876 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 
 
The test is: https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/reports/cached_catalog_status_in_report.rb 
I am able to reproduce the failure consistently outside of the context of the test on a Japanese Windows 2012r2 VM. The cached catalog is not applied and a report is not submitted to the master. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-3283) Resource type ssh_authorized key, 'name' attribute accepts a blank string

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3283 
 
 
 
  Resource type ssh_authorized key, 'name' attribute accepts a blank string  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Assignee:
 
 Joe Pinsonault 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-1739 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ipaddress6 returns ipv4 address  
 
 
 
 
 
 
 
 
 
 
I thought we had an older bug that this is a duplicate of, but I can't find it. 
The issue is that the `ip` command itself spits out ipv4 data when v6 is disabled (try `ip -6 addr eth0` on your host). 
We need to detect this case in Facter and not report on ipv6 data when it's bogus. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error

[Andreas Lambrecht (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Lambrecht commented on  PDB-3058 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Report not being stored in PuppetDB due to Unicode Error  
 
 
 
 
 
 
 
 
 
 
I've experience the same issue on PE2017.2.1 today, with a profile which includes the following: 
registry_value  { 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\LegalNoticeText': type => string, data ="" 'This Legal Notice Text is Managed By Puppet', } 
 registry_value  { KEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\LegalNoticeCaption': type => string, data ="" 'This Legal Notice Caption is Managed By Puppet', } 
  
According to "Fixed version" this should be fixed in PE2017.2.2+. However I have updated my PE2017.2.1 -> PE2017.2.3 and still have the same issue.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4212) Create a Splay "Start Time" Setting

[Owen Rodabaugh (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4212 
 
 
 
  Create a Splay "Start Time" Setting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Priority:
 
 Major Normal 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4212) Create a Splay "Start Time" Setting

[Owen Rodabaugh (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4212 
 
 
 
  Create a Splay "Start Time" Setting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Impact:
 
 The pseudo-randomness of splay can still result in thundering herds and this would help reduce the randomness leading to this. Would prefer to see PUP-7451 land instead of this so we are dropping CS Priority down 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[Maggie Dreyer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  PUP-7876 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 
 
I haven't seen this before... Does this just run the acceptace tests from the Puppet repo? If not, where is the test suite? I'd like to look at the test. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7876 
 
 
 
  Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  PUP-7876 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 
 
Maggie Dreyer or Eric Delaney is this something you have bumped into with i18n testing? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7876 
 
 
 
  Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Priority:
 
 Normal Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2189) The CRL can get corrupted if two workers revoke certs at same time

[Charlie Sharpsteen (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Charlie Sharpsteen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2189 
 
 
 
  The CRL can get corrupted if two workers revoke certs at same time  
 
 
 
 
 
 
 
 
 

Change By:
 
 Charlie Sharpsteen 
 
 
 

CS Priority:
 
 Needs Priority 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7876 
 
 
 
  Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 

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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7876 
 
 
 
  Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

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 (PUP-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7876 
 
 
 
  Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Affects 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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7876 
 
 
 
  Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Method Found:
 
 Needs Assessment Automated Test 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7854) Handle Default type in Puppet Serialization

[Thomas Kishel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Kishel commented on  PUP-7854 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Handle Default type in Puppet Serialization  
 
 
 
 
 
 
 
 
 
 
Enabling rich_data (and restarting the puppetserver service) on the master and the agent: 
 
 
 
 
 
 
[root@pe-201723-master ~]# cat /etc/puppetlabs/puppet/puppet.conf  
 
 
 
 
[main] 
 
 
 
 
certname = pe-201723-master.puppetdebug.vlan 
 
 
 
 
server = pe-201723-master.puppetdebug.vlan 
 
 
 
 
user = pe-puppet 
 
 
 
 
group = pe-puppet 
 
 
 
 
environment_timeout = 0 
 
 
 
 
app_management = true 
 
 
 
 
module_groups = base+pe_only 
 
 
 
 
rich_data = true 
 
 
 
 
 

Jira (PUP-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  PUP-7876 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 
 
This appears to be a failure in puppet that is preventing it from failing over to the cached catalog. The node can correctly apply a cached catalog and submit the report to the master when using the --used_cached_catalog flag. However, the node cannot fail over to using a cached catalog when the server is unreachable. 
The critical line in the error below is 
 
 
 
 
 
 
Error: カタログ適用に失敗しました: incompatible character encodings: UTF-8 and ASCII-8BIT
 
 
 
 
 
 
 
 
 
 
 
 
 
Debug: Starting connection for https://noexist:8140 
 
 
 
 
Warning: ノード定義を取得できませんが、agent実行を続行します: 
 
 
 
 
Warning: Failed to open TCP connection to noexist:8140 (getaddrinfo: そのようなホストは不明です。 ) 
 
 
 
 
Info: pluginfactsを取得しています。 
 
 
 
 
Debug: Evicting cache entry for environment 'production' 
 
 
 
 
Debug: Caching environment 'production' (ttl = 0 sec) 
 
 
 
 
Debug: Evicting cache entry for environment 'production' 
   

Jira (PUP-7854) Handle Default type in Puppet Serialization

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7854 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Handle Default type in Puppet Serialization  
 
 
 
 
 
 
 
 
 
 
rich data must be enabled on both master and agent for that experimental feature to work - then there is PUP-7855 which indicates it may not work with the --rich_data flag either. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7854) Handle Default type in Puppet Serialization

[Thomas Kishel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Kishel commented on  PUP-7854 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Handle Default type in Puppet Serialization  
 
 
 
 
 
 
 
 
 
 
Am I missing something regarding enabling rich_data ? 
 
 
 
 
 
 
[root@pe-201723-agent ~]# cat /etc/puppetlabs/puppet/puppet.conf  
 
 
 
 
server = pe-201723-master.puppetdebug.vlan 
 
 
 
 
certname = pe-201723-agent.puppetdebug.vlan 
 
 
 
 
rich_data = true 
 
 
 
 
  
 
 
 
 
[root@pe-201723-agent ~]# puppet agent -t
 
 
 
 
 
 
 
Results in the same warning: 
 
 
 
 
 
 
[root@pe-201723-master production]# tail -f /var/log/puppetlabs/puppetserver/puppetserver.log  
 
 
 
 
2017-08-24 17:38:32,584 WARN  [qtp790472544-65] [puppetserver] Puppet Resource 'Class[Test]' contains a Symbol value. It will be converted to the String 'default'
 
 
 
 
 
 
  

Jira (PUP-7877) Future Work for Intermediate CA Improvements

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7877 
 
 
 
  Future Work for Intermediate CA Improvements  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Epic 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/24 11:06 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Moses Mendoza 
 
 
 
 
 
 
 
 
 
 
Epic for Intermediate CA improvements that did not make the cut for initial iteration. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-3788) Puppet Agent does not support Chained CRLs

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3788 
 
 
 
  Puppet Agent does not support Chained CRLs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Sprint:
 
 Server 2017-07-25, Platform Core 2017-08-08, Platform Core 2017-08-22 , Platform Core 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 (PUP-3788) Puppet Agent does not support Chained CRLs

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3788 
 
 
 
  Puppet Agent does not support Chained CRLs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Assignee:
 
 Adrien Thebo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3788) Puppet Agent does not support Chained CRLs

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-3788 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Agent does not support Chained CRLs  
 
 
 
 
 
 
 
 
 
 
Per discussion on team it was determined that the total effort to support chained CRLs through the system exceeds our short term capacity. Decision was that PUP-7845 (leaf CRL checking) moves us closer to the goal and is sufficient for short term requirements, so that is what we are proceeding with. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7845) Support leaf certificate CRL checking

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7845 
 
 
 
  Support leaf certificate CRL checking  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Sprint:
 
 Platform Core 2017- 09 08 - 05 22 , Platform Core  2017-08-22  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 (PUP-3788) Puppet Agent does not support Chained CRLs

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3788 
 
 
 
  Puppet Agent does not support Chained CRLs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 Platform Core 2017-09-05,  Server 2017-07-25, Platform Core 2017-08-08, Platform Core 2017-08-22 , Platform Core 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 (PUP-7668) ResourceExpression has incorrect offset when inside of an else block

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7668 
 
 
 
  ResourceExpression has incorrect offset when inside of an else block  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Sprint:
 
 Platform Core 2017- 09 08 - 05 22 , Platform Core  2017-08-22  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 (PUP-7102) Insufficient logging when encountering 'permission denied' on environmentpath

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7102 
 
 
 
  Insufficient logging when encountering 'permission denied' on environmentpath  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Sprint:
 
 PDE 2017-02-08, PDE 2017-02-22, PDE 2017-03-08, PDE 2017-03-22, PDE 2017-04-05, PDE 2017-04-19,  Platform Core 2017-09-05,  Agent 2017-06-28, Agent 2017-07-12, Platform Core 2017-08-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7845) Support leaf certificate CRL checking

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7845 
 
 
 
  Support leaf certificate CRL checking  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 Platform Core 2017- 09-05, Platform Core 2017- 08-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7858) `puppet help` output contains untranslated subcommand summaries

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7858 
 
 
 
  `puppet help` output contains untranslated subcommand summaries  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 Platform Core 2017- 09-05, Platform Core 2017- 08-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3788) Puppet Agent does not support Chained CRLs

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3788 
 
 
 
  Puppet Agent does not support Chained CRLs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 Platform Core 2017-09-05, Server 2017-07-25, Platform Core 2017-08-08, Platform Core 2017-08-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7618 
 
 
 
  PSON -> JSON Testing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 Platform Core 2017-09-05, Agent 2017-06-28, Platform Core 2017-08-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7102) Insufficient logging when encountering 'permission denied' on environmentpath

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7102 
 
 
 
  Insufficient logging when encountering 'permission denied' on environmentpath  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 PDE 2017-02-08, PDE 2017-02-22, PDE 2017-03-08, PDE 2017-03-22, PDE 2017-04-05, PDE 2017-04-19,  Platform Core 2017-09-05,  Agent 2017-06-28, Agent 2017-07-12, Platform Core 2017-08-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7668) ResourceExpression has incorrect offset when inside of an else block

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7668 
 
 
 
  ResourceExpression has incorrect offset when inside of an else block  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 Platform Core 2017- 09-05, Platform Core 2017- 08-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1648) Execute manual test: Facter content in various locales

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1648 
 
 
 
  Execute manual test: Facter content in various locales  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 Platform Core 2017- 09-05, Platform Core 2017- 08-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7645) Ensure that translations are available in released puppet gems

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7645 
 
 
 
  Ensure that translations are available in released puppet gems  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 Platform Core 2017- 09-05, Platform Core 2017- 08-08, Platform Core 2017-08-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7820) error string needs update for I18N support

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7820 
 
 
 
  error string needs update for I18N support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 Platform Core 2017- 09-05, Platform Core 2017- 08-08, Platform Core 2017-08-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7729) acceptance: add preferred serialization format test

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer commented on  PUP-7729 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: acceptance: add preferred serialization format test  
 
 
 
 
 
 
 
 
 
 
Eric Delaney This one too, 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 (PUP-7820) error string needs update for I18N support

[Maggie Dreyer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7820 
 
 
 
  error string needs update for I18N support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Fix Version/s:
 
 PUP 5.1.z 
 
 
 

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 (HI-578) Symbolized facts causes "ignore bad definition" error in hierarchy

[Dan Dunckel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Dunckel commented on  HI-578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Symbolized facts causes "ignore bad definition" error in hierarchy  
 
 
 
 
 
 
 
 
 
 
Pull request created: https://github.com/puppetlabs/hiera/pull/402 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (HI-578) Symbolized facts causes "ignore bad definition" error in hierarchy

[Dan Dunckel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Dunckel commented on  HI-578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Symbolized facts causes "ignore bad definition" error in hierarchy  
 
 
 
 
 
 
 
 
 
 
Stepping thru the code brought me to here: https://github.com/puppetlabs/hiera/blob/3.4.0/lib/hiera/backend.rb#L332 
where Hiera checks if fqdn is a key of the facts hash via value.include?(segment) 
 

value is the facts hash
 

segment is the variable to be interpolated, in this case: fqdn
 
 
Because the hash has fqdn as a Symbol and not a String, the check fails, resulting in the Ignoring bad definition in :hierarchy: 'fqdn/' error. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (HI-578) Symbolized facts causes "ignore bad definition" error in hierarchy

[Dan Dunckel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Dunckel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-578 
 
 
 
  Symbolized facts causes "ignore bad definition" error in hierarchy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Dunckel 
 
 
 
 
 
 
 
 
 
 h1. SummaryWhen I try to perform a *hiera.lookup* request in a spec, the hierarchy doesn't find the *kernel* fact.  Because of that, Hiera shows this message:{code}Ignoring bad definition in :hierarchy: 'kernel/'{code}And as a result, the data I need is not found.h2. spec/spec_helper.rb{code}require "puppetlabs_spec_helper/module_spec_helper"require "rspec-puppet-facts"include RspecPuppetFacts# needed to perform lookups inside specsrequire "hiera"RSpec.configure do |c|  c.default_facts = {"hostname"  => `hostname -f`.strip,"ipaddress" => `hostname -i`.strip,"puppetversion" => "4.6.1",  }  c.fail_fast = true if ENV['FAIL_FAST'] == "true"  # needed to evaluate hiera lookups in the puppet code  c.hiera_config = "spec/fixtures/hiera/hiera.yaml"  if ENV['COVERAGE'] == "true"c.after(:suite) do  RSpec::Puppet::Coverage.report!end  endend# Default to "no" as our specs fail on default facts (i.e. "$::networking")ENV['STRICT_VARIABLES'] = "no" unless ENV['STRICT_VARIABLES']{code}h2. spec/fixtures/hiera/hiera.yaml{code}:backends:  - yaml:yaml:  :datadir: spec/fixtures/hiera:hierarchy:  - "fqdn/%{fqdn}"  - "environment/%{environment}"  - "hostgroup/%{hostgroup}"  - "os/%{operatingsystem}/%{operatingsystemrelease}"  - "os/%{operatingsystem}"  - "kernel/%{kernel}"  - "common"{code}h2. spec/fixtures/hiera/os/Ubuntu.yaml{code}cron_service: 'cron'{code}h2. spec/fixtures/hiera/kernel/Linux.yaml{code}cron_service: 'crond'{code}h2. manifests/linux.pp{code}class ta_base::linux() {  $cron_service = hiera('cron_service')  service { $cron_service:enable => true,ensure => true,hasrestart => true,hasstatus  => true,  }}{code}h2. spec/classes/linux_spec.rb{code}require "spec_helper"hiera = Hiera.new(:config => "spec/fixtures/hiera/hiera.yaml")describe "ta_base::linux" do  on_supported_os.each do |os, facts|context "on #{os}" do  let(:facts) { facts }  cron_service = hiera.lookup("cron_service", nil, facts)  it { is_expected.to compile.with_all_deps }  it { is_expected.to contain_service(cron_service).with(  "enable"  => true,  "ensure"  => true)  }end  endend{code}h2. Example run{code}$ SPEC=spec/classes/linux_spec.rb FAIL_FAST=true rake spec_standalone/home/dunk/.rvm/rubies/ruby-2.3.1/bin/ruby -I/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-core-3.6.0/lib:/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-support-3.6.0/lib/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-core-3.6.0/exe/rspec spec/classes/linux_spec.rb --colorDEBUG: 2017-08-23 17:38:05 -0600: Hiera YAML backend startingDEBUG: 2017-08-23 17:38:05 -0600: Looking up cron_service in YAML backendDEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'fqdn/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'environment/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'hostgroup/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'os//'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'os/'DEBUG: 2017-08-23 

Jira (HI-578) Symbolized facts causes "ignore bad definition" error in hierarchy

[Dan Dunckel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Dunckel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-578 
 
 
 
  Symbolized facts causes "ignore bad definition" error in hierarchy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Dunckel 
 
 
 
 
 
 
 
 
 
 h1. SummaryWhen I try to perform a { code noformat }hiera.lookup{ code noformat } request in a spec, the hierarchy doesn't find the `kernel` fact.  Because of that, Hiera shows this message:Ignoring bad definition in :hierarchy: 'kernel/'And as a result, the data I need is not found.h2. spec/spec_helper.rb{code}require "puppetlabs_spec_helper/module_spec_helper"require "rspec-puppet-facts"include RspecPuppetFacts# needed to perform lookups inside specsrequire "hiera"RSpec.configure do |c|  c.default_facts = {"hostname"  => `hostname -f`.strip,"ipaddress" => `hostname -i`.strip,"puppetversion" => "4.6.1",  }  c.fail_fast = true if ENV['FAIL_FAST'] == "true"  # needed to evaluate hiera lookups in the puppet code  c.hiera_config = "spec/fixtures/hiera/hiera.yaml"  if ENV['COVERAGE'] == "true"c.after(:suite) do  RSpec::Puppet::Coverage.report!end  endend# Default to "no" as our specs fail on default facts (i.e. "$::networking")ENV['STRICT_VARIABLES'] = "no" unless ENV['STRICT_VARIABLES']{code}h2. spec/fixtures/hiera/hiera.yaml{code}:backends:  - yaml:yaml:  :datadir: spec/fixtures/hiera:hierarchy:  - "fqdn/%{fqdn}"  - "environment/%{environment}"  - "hostgroup/%{hostgroup}"  - "os/%{operatingsystem}/%{operatingsystemrelease}"  - "os/%{operatingsystem}"  - "kernel/%{kernel}"  - "common"{code}h2. spec/fixtures/hiera/os/Ubuntu.yaml{code}cron_service: 'cron'{code}h2. spec/fixtures/hiera/kernel/Linux.yaml{code}cron_service: 'crond'{code}h2. manifests/linux.pp{code}class ta_base::linux() {  $cron_service = hiera('cron_service')  service { $cron_service:enable => true,ensure => true,hasrestart => true,hasstatus  => true,  }}{code}h2. spec/classes/linux_spec.rb{code}require "spec_helper"hiera = Hiera.new(:config => "spec/fixtures/hiera/hiera.yaml")describe "ta_base::linux" do  on_supported_os.each do |os, facts|context "on #{os}" do  let(:facts) { facts }  cron_service = hiera.lookup("cron_service", nil, facts)  it { is_expected.to compile.with_all_deps }  it { is_expected.to contain_service(cron_service).with(  "enable"  => true,  "ensure"  => true)  }end  endend{code}h2. Example run{code}$ SPEC=spec/classes/linux_spec.rb FAIL_FAST=true rake spec_standalone/home/dunk/.rvm/rubies/ruby-2.3.1/bin/ruby -I/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-core-3.6.0/lib:/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-support-3.6.0/lib/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-core-3.6.0/exe/rspec spec/classes/linux_spec.rb --colorDEBUG: 2017-08-23 17:38:05 -0600: Hiera YAML backend startingDEBUG: 2017-08-23 17:38:05 -0600: Looking up cron_service in YAML backendDEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'fqdn/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'environment/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'hostgroup/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'os//'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 

Jira (HI-578) Symbolized facts causes "ignore bad definition" error in hierarchy

[Dan Dunckel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Dunckel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-578 
 
 
 
  Symbolized facts causes "ignore bad definition" error in hierarchy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Dunckel 
 
 
 
 
 
 
 
 
 
 h1. SummaryWhen I try to perform a  {noformat}  * hiera.lookup {noformat} *  request in a spec, the hierarchy doesn't find the  `  * kernel ` *  fact.  Because of that, Hiera shows this message: {code} Ignoring bad definition in :hierarchy: 'kernel/' {code} And as a result, the data I need is not found.h2. spec/spec_helper.rb{code}require "puppetlabs_spec_helper/module_spec_helper"require "rspec-puppet-facts"include RspecPuppetFacts# needed to perform lookups inside specsrequire "hiera"RSpec.configure do |c|  c.default_facts = {"hostname"  => `hostname -f`.strip,"ipaddress" => `hostname -i`.strip,"puppetversion" => "4.6.1",  }  c.fail_fast = true if ENV['FAIL_FAST'] == "true"  # needed to evaluate hiera lookups in the puppet code  c.hiera_config = "spec/fixtures/hiera/hiera.yaml"  if ENV['COVERAGE'] == "true"c.after(:suite) do  RSpec::Puppet::Coverage.report!end  endend# Default to "no" as our specs fail on default facts (i.e. "$::networking")ENV['STRICT_VARIABLES'] = "no" unless ENV['STRICT_VARIABLES']{code}h2. spec/fixtures/hiera/hiera.yaml{code}:backends:  - yaml:yaml:  :datadir: spec/fixtures/hiera:hierarchy:  - "fqdn/%{fqdn}"  - "environment/%{environment}"  - "hostgroup/%{hostgroup}"  - "os/%{operatingsystem}/%{operatingsystemrelease}"  - "os/%{operatingsystem}"  - "kernel/%{kernel}"  - "common"{code}h2. spec/fixtures/hiera/os/Ubuntu.yaml{code}cron_service: 'cron'{code}h2. spec/fixtures/hiera/kernel/Linux.yaml{code}cron_service: 'crond'{code}h2. manifests/linux.pp{code}class ta_base::linux() {  $cron_service = hiera('cron_service')  service { $cron_service:enable => true,ensure => true,hasrestart => true,hasstatus  => true,  }}{code}h2. spec/classes/linux_spec.rb{code}require "spec_helper"hiera = Hiera.new(:config => "spec/fixtures/hiera/hiera.yaml")describe "ta_base::linux" do  on_supported_os.each do |os, facts|context "on #{os}" do  let(:facts) { facts }  cron_service = hiera.lookup("cron_service", nil, facts)  it { is_expected.to compile.with_all_deps }  it { is_expected.to contain_service(cron_service).with(  "enable"  => true,  "ensure"  => true)  }end  endend{code}h2. Example run{code}$ SPEC=spec/classes/linux_spec.rb FAIL_FAST=true rake spec_standalone/home/dunk/.rvm/rubies/ruby-2.3.1/bin/ruby -I/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-core-3.6.0/lib:/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-support-3.6.0/lib/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-core-3.6.0/exe/rspec spec/classes/linux_spec.rb --colorDEBUG: 2017-08-23 17:38:05 -0600: Hiera YAML backend startingDEBUG: 2017-08-23 17:38:05 -0600: Looking up cron_service in YAML backendDEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'fqdn/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'environment/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'hostgroup/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'os//'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition 

Jira (HI-578) Symbolized facts causes "ignore bad definition" error in hierarchy

[Dan Dunckel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Dunckel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-578 
 
 
 
  Symbolized facts causes "ignore bad definition" error in hierarchy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Dunckel 
 
 
 
 
 
 
 
 
 
 h1. SummaryWhen I try to perform a  `  {code} hiera.lookup ` {code}  request in a spec, the hierarchy doesn't find the `kernel` fact.  Because of that, Hiera shows this message:Ignoring bad definition in :hierarchy: 'kernel/'And as a result, the data I need is not found.h2. spec/spec_helper.rb{code}require "puppetlabs_spec_helper/module_spec_helper"require "rspec-puppet-facts"include RspecPuppetFacts# needed to perform lookups inside specsrequire "hiera"RSpec.configure do |c|  c.default_facts = {"hostname"  => `hostname -f`.strip,"ipaddress" => `hostname -i`.strip,"puppetversion" => "4.6.1",  }  c.fail_fast = true if ENV['FAIL_FAST'] == "true"  # needed to evaluate hiera lookups in the puppet code  c.hiera_config = "spec/fixtures/hiera/hiera.yaml"  if ENV['COVERAGE'] == "true"c.after(:suite) do  RSpec::Puppet::Coverage.report!end  endend# Default to "no" as our specs fail on default facts (i.e. "$::networking")ENV['STRICT_VARIABLES'] = "no" unless ENV['STRICT_VARIABLES']{code}h2. spec/fixtures/hiera/hiera.yaml{code}:backends:  - yaml:yaml:  :datadir: spec/fixtures/hiera:hierarchy:  - "fqdn/%{fqdn}"  - "environment/%{environment}"  - "hostgroup/%{hostgroup}"  - "os/%{operatingsystem}/%{operatingsystemrelease}"  - "os/%{operatingsystem}"  - "kernel/%{kernel}"  - "common"{code}h2. spec/fixtures/hiera/os/Ubuntu.yaml{code}cron_service: 'cron'{code}h2. spec/fixtures/hiera/kernel/Linux.yaml{code}cron_service: 'crond'{code}h2. manifests/linux.pp{code}class ta_base::linux() {  $cron_service = hiera('cron_service')  service { $cron_service:enable => true,ensure => true,hasrestart => true,hasstatus  => true,  }}{code}h2. spec/classes/linux_spec.rb{code}require "spec_helper"hiera = Hiera.new(:config => "spec/fixtures/hiera/hiera.yaml")describe "ta_base::linux" do  on_supported_os.each do |os, facts|context "on #{os}" do  let(:facts) { facts }  cron_service = hiera.lookup("cron_service", nil, facts)  it { is_expected.to compile.with_all_deps }  it { is_expected.to contain_service(cron_service).with(  "enable"  => true,  "ensure"  => true)  }end  endend{code}h2. Example run{code}$ SPEC=spec/classes/linux_spec.rb FAIL_FAST=true rake spec_standalone/home/dunk/.rvm/rubies/ruby-2.3.1/bin/ruby -I/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-core-3.6.0/lib:/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-support-3.6.0/lib/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-core-3.6.0/exe/rspec spec/classes/linux_spec.rb --colorDEBUG: 2017-08-23 17:38:05 -0600: Hiera YAML backend startingDEBUG: 2017-08-23 17:38:05 -0600: Looking up cron_service in YAML backendDEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'fqdn/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'environment/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'hostgroup/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'os//'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'os/'DEBUG: 

Jira (HI-578) Symbolized facts causes "ignore bad definition" error in hierarchy

[Dan Dunckel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Dunckel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-578 
 
 
 
  Symbolized facts causes "ignore bad definition" error in hierarchy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Dunckel 
 
 
 
 
 
 
 
 
 
 # h1.  SummaryWhen I try to perform a `hiera.lookup` request in a spec, the hierarchy doesn't find the `kernel` fact.  Because of that, Hiera shows this message:Ignoring bad definition in :hierarchy: 'kernel/'And as a result, the data I need is not found. ## h2.  spec/spec_helper.rb ``` {code} require "puppetlabs_spec_helper/module_spec_helper"require "rspec-puppet-facts"include RspecPuppetFacts# needed to perform lookups inside specsrequire "hiera"RSpec.configure do |c|  c.default_facts = {"hostname"  => `hostname -f`.strip,"ipaddress" => `hostname -i`.strip,"puppetversion" => "4.6.1",  }  c.fail_fast = true if ENV['FAIL_FAST'] == "true"  # needed to evaluate hiera lookups in the puppet code  c.hiera_config = "spec/fixtures/hiera/hiera.yaml"  if ENV['COVERAGE'] == "true"c.after(:suite) do  RSpec::Puppet::Coverage.report!end  endend# Default to "no" as our specs fail on default facts (i.e. "$::networking")ENV['STRICT_VARIABLES'] = "no" unless ENV['STRICT_VARIABLES'] ``` {code}  ## h2.  spec/fixtures/hiera/hiera.yaml ``` {code} :backends:  - yaml:yaml:  :datadir: spec/fixtures/hiera:hierarchy:  - "fqdn/%{fqdn}"  - "environment/%{environment}"  - "hostgroup/%{hostgroup}"  - "os/%{operatingsystem}/%{operatingsystemrelease}"  - "os/%{operatingsystem}"  - "kernel/%{kernel}"  - "common" ``` {code}  ## h2.  spec/fixtures/hiera/os/Ubuntu.yaml ``` {code} cron_service: 'cron' ``` {code}  ## h2.  spec/fixtures/hiera/kernel/Linux.yaml ``` {code} cron_service: 'crond' ``` {code}  ## h2.  manifests/linux.pp ``` {code} class ta_base::linux() {  $cron_service = hiera('cron_service')  service { $cron_service:enable => true,ensure => true,hasrestart => true,hasstatus  => true,  }} ``` {code}  ## h2.  spec/classes/linux_spec.rb ``` {code} require "spec_helper"hiera = Hiera.new(:config => "spec/fixtures/hiera/hiera.yaml")describe "ta_base::linux" do  on_supported_os.each do |os, facts|context "on #{os}" do  let(:facts) { facts }  cron_service = hiera.lookup("cron_service", nil, facts)  it { is_expected.to compile.with_all_deps }  it { is_expected.to contain_service(cron_service).with(  "enable"  => true,  "ensure"  => true)  }end  endend ``` {code}  ## h2.  Example run ``` {code} $ SPEC=spec/classes/linux_spec.rb FAIL_FAST=true rake spec_standalone/home/dunk/.rvm/rubies/ruby-2.3.1/bin/ruby -I/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-core-3.6.0/lib:/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-support-3.6.0/lib/home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing/gems/rspec-core-3.6.0/exe/rspec spec/classes/linux_spec.rb --colorDEBUG: 2017-08-23 17:38:05 -0600: Hiera YAML backend startingDEBUG: 2017-08-23 17:38:05 -0600: Looking up cron_service in YAML backendDEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'fqdn/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'environment/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 'hostgroup/'DEBUG: 2017-08-23 17:38:05 -0600: Ignoring bad definition in :hierarchy: 

Jira (HI-578) Symbolized facts causes "ignore bad definition" error in hierarchy

[Dan Dunckel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Dunckel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-578 
 
 
 
  Symbolized facts causes "ignore bad definition" error in hierarchy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Dunckel 
 
 
 

Environment:
 
 ## Environment```Bundler   1.14.6Rubygems  2.5.1Ruby  2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]GEM_HOME  /home/dunk/.rvm/gems/ruby-2.3.1@puppet-testingGEM_PATH  /home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing:/home/dunk/.rvm/gems/ruby-2.3.1@globalRVM   1.29.1 (latest)Git   1.9.1Platform  x86_64-linuxrubygems-bundler (1.4.4)```### Gemfile```rubysource "https://rubygems.org"gem 'puppet', '4.7.0'group :test do  gem 'puppet-lint', '2.3.0'  gem 'puppetlabs_spec_helper', '2.2.0'  gem 'rspec-puppet', '2.6.8'  gem 'parallel_tests', '2.14.2'  gem 'rspec-puppet-facts', '1.8.0', :require => false  gem 'metadata-json-lint', '2.0.2'  gem 'semantic_puppet', '1.0.1' # this gem is needed (for metadata-json-lint) until we move to Puppet 4.9.xendgroup :development, :test do  gem 'beaker-rspec', '6.1.0', :require => false  gem 'pry', '0.10.4'end```### Gemfile.lock```GEM  remote: https://rubygems.org/  specs:CFPropertyList (2.3.5)addressable (2.5.1)  public_suffix (~> 2.0, >= 2.0.2)aws-sdk-v1 (1.67.0)  json (~> 1.4)  nokogiri (~> 1)beaker (3.20.0)  aws-sdk-v1 (~> 1.57)  beaker-hiera (~> 0.0)  beaker-hostgenerator  beaker-puppet (~> 0.0)  beaker-vmpooler (~> 0.1)  docker-api  fission (~> 0.4)  fog (~> 1.38)  google-api-client (~> 0.9)  hocon (~> 1.0) See environment section   in -parallel (~> 0.1)  inifile (~> 3.0)  minitar (~> 0.5.4)  minitest (~> 5.4)  net-scp (~> 1.2)  net-ssh (~> 4.0)  open_uri_redirections (~> 0.2.1)  rsync (~> 1.0.9)  stringify-hash (~> 0.0)  thor (~> 0.19)  unf (~> 0.1)beaker-hiera (0.1.1)  stringify-hash (~> 0.0.0)beaker-hostgenerator (0.10.1)  deep_merge (~> 1.0)  stringify-hash (~> 0.0.0)beaker-puppet (0.3.0)  in-parallel (~> 0.1)  stringify-hash (~> 0.0.0)beaker-rspec (6.1.0)  beaker (~> 3.0)  rspec (~> 3.0)  serverspec (~> 2)  specinfra (~> 2)beaker-vmpooler (0.1.0)  rbvmomi (~> 1.9)  stringify-hash (~> 0.0.0)builder (3.2.3)coderay (1.1.1)declarative (0.0.9)declarative-option (0.1.0)deep_merge (1.1.1)diff-lcs (1.3)docker-api (1.33.6)  excon (>= 0.38.0)  jsonexcon (0.57.1)facter (2.4.6)facterdb (0.3.11)  facter  jgrepfaraday (0.12.1)  multipart-post (>= 1.2, < 3)fast_gettext (1.1.0)fission (0.5.0)  CFPropertyList (~> 2.2)fog (1.40.0)  fog-aliyun (>= 0.1.0)  fog-atmos  fog-aws (>= 0.6.0)  fog-brightbox (~> 0.4)  fog-cloudatcost (~> 0.1.0)  fog-core (~> 1.43)  fog-digitalocean (>= 0.3.0)  fog-dnsimple (~> 1.0)  fog-dynect (~> 0.0.2)  fog-ecloud (~> 0.1)  fog-google (<= 0.1.0)  fog-json  fog-local  fog-openstack  fog-powerdns (>= 0.1.1)  fog-profitbricks  fog-rackspace  fog-radosgw (>= 0.0.2)  fog-riakcs  fog-sakuracloud (>= 0.0.4)  fog-serverlove  fog-softlayer  fog-storm_on_demand  fog-terremark  fog-vmfusion  fog-voxel  fog-vsphere (>= 0.4.0)  fog-xenserver  fog-xml (~> 0.1.1)  ipaddress (~> 0.5)  json (>= 1.8, < 2.0)fog-aliyun 

Jira (HI-578) Symbolized facts causes "ignore bad definition" error in hierarchy

[Dan Dunckel (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Dunckel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-578 
 
 
 
  Symbolized facts causes "ignore bad definition" error in hierarchy  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 HI 3.4.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/24 9:28 AM 
 
 
 

Environment:
 
 
 
 
 

Environment
 
 
 
 
``` Bundler 1.14.6 Rubygems 2.5.1 Ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux] GEM_HOME /home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing GEM_PATH /home/dunk/.rvm/gems/ruby-2.3.1@puppet-testing:/home/dunk/.rvm/gems/ruby-2.3.1@global RVM 1.29.1 (latest) Git 1.9.1 Platform x86_64-linux rubygems-bundler (1.4.4) ``` 
 
 
 
 
 

Gemfile
 
 
 
 
 
 
```ruby source "https://rubygems.org" 
gem 'puppet', '4.7.0' 
group :test do gem 'puppet-lint', '2.3.0' gem 'puppetlabs_spec_helper', '2.2.0' gem 'rspec-puppet', '2.6.8' gem 'parallel_tests', '2.14.2' gem 'rspec-puppet-facts', '1.8.0', :require => false gem 'metadata-json-lint', '2.0.2' gem 'semantic_puppet', '1.0.1' # this gem is needed (for metadata-json-lint) until we move to Puppet 

Jira (PUP-7850) Add plan to puppet language

[Henrik Lindberg (JIRA)]

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

 
 
 
 
 
 
 
 Puppet /  PUP-7850 
 
 
 
  Add plan to puppet language  
 
 
 
 
 
 
 
 
 

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-1739) ipaddress6 returns ipv4 address

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1739 
 
 
 
  ipaddress6 returns ipv4 address  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 3.8.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/24 9:11 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Peter Meier 
 
 
 
 
 
 
 
 
 
 
A host with ipv6 disabled: 
 
 
 
 
 
 
$ ip addr show eth0 
 
 
 
 
2: eth0:  mtu 1500 qdisc pfifo_fast state UP qlen 1000 
 
 
 
 
link/ether 52:54:00:48:4e:21 brd ff:ff:ff:ff:ff:ff 
 
 
 
 
 

Jira (PUP-7863) The Default type is not considered RichData

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7863 
 
 
 
  The Default type is not considered RichData  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

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-7862) Optional types are not assignable to Data and RichData

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7862 
 
 
 
  Optional types are not assignable to Data and RichData  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7876 
 
 
 
  Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

[John O'Connor (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John O'Connor created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7876 
 
 
 
  Puppet Acceptance Suite Fails for Win-2012r2 Japanese  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/24 8:43 AM 
 
 
 

Labels:
 

 windows 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 John O'Connor 
 
 
 
 
 
 
 
 
 
 
This was noticed when running the imaging acceptance test suites for latest Puppet-Agent () against the Packer Built Windows Images. 
The win-2012r2-ja-x86_64 fails with test: tests/reports/cached_catalog_status_in_report.rb failing. 
There is also a log of "strange" output in the build log - see the log after elapsed time 01:33:17.686 
The build log is available at: https://jenkins-imaging.delivery.puppetlabs.net/view/Win-Acpt/job/imaging_windows-2012r2-ja_x86_64_vmware_vsphere.cygwin_acceptance_packer/17/consoleFull 
Unsure where this issue should be logged, so starting with PUP and will check with Larissa Lane 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 

Jira (PUP-7865) error 500 on server file metadata with space in name

[Eric V. Bahmer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric V. Bahmer commented on  PUP-7865 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: error 500 on server file metadata with space in name  
 
 
 
 
 
 
 
 
 
 
2017-08-19 10:12:11,717 WARN [qtp1330508248-60] [o.e.j.s.HttpChannel] /puppet/v3/file_metadata/products/product_puppetserver/common/etc/puppetlabs/code/hieradata/osfamily/windows/2008%20R2.yaml javax.servlet.ServletException: java.net.URISyntaxException: Illegal character in path at index 122: file:puppet/v3/file_metadata/products/product_puppetserver/common/etc/puppetlabs/code/hieradata/osfamily/windows/2008 R2.yaml at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146) at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:521) at org.eclipse.jetty.server.handler.RequestLogHandler.handle(RequestLogHandler.java:56) at org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:169) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:564) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:317) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110) at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:278) at org.eclipse.jetty.io.ssl.SslConnection$3.succeeded(SslConnection.java:148) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124) at org.eclipse.jetty.util.thread.Invocable.invokePreferred(Invocable.java:128) at org.eclipse.jetty.util.thread.Invocable$InvocableExecutor.invoke(Invocable.java:222) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:294) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:199) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:672) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:590) at java.lang.Thread.run(Thread.java:745) Caused by: java.net.URISyntaxException: Illegal character in path at index 122: file:puppet/v3/file_metadata/products/product_puppetserver/common/etc/puppetlabs/code/hieradata/osfamily/windows/2008 R2.yaml at java.net.URI$Parser.fail(URI.java:2848) at java.net.URI$Parser.checkChars(URI.java:3021) at java.net.URI$Parser.parseHierarchical(URI.java:3105) at java.net.URI$Parser.parse(URI.java:3053) at java.net.URI.(URI.java:588) at bidi.bidi$just_path.invokeStatic(bidi.cljc:191) at bidi.bidi$just_path.invoke(bidi.cljc:187) at clojure.core$update.invokeStatic(core.clj:5960) at clojure.core$update.invoke(core.clj:5952) at bidi.bidi$match_pair.invokeStatic(bidi.cljc:200) at bidi.bidi$match_pair.invoke(bidi.cljc:195) at bidi.bidi$match_route_STAR_.invokeStatic(bidi.cljc:382) at bidi.bidi$match_route_STAR_.invoke(bidi.cljc:380) at bidi.bidi$match_route.invokeStatic(bidi.cljc:389) at bidi.bidi$match_route.doInvoke(bidi.cljc:385) at clojure.lang.RestFn.applyTo(RestFn.java:142) at clojure.core$apply.invokeStatic(core.clj:650) at clojure.core$apply.invoke(core.clj:641) at puppetlabs.comidi$eval23402$wrap_with_route_metadata_23407$fn23408$fn_23410.invoke(comidi.clj:334) at puppetlabs.trapperkeeper.services.webserver.jetty9_core$ring_handler$fn__32969.invoke(jetty9_core.clj:422) at puppetlabs.trapperkeeper.services.webserver.jetty9_core.proxy$org.eclipse.jetty.server.handler.AbstractHandler$ff19274a.handle(Unknown Source) at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at 

Jira (PUP-7730) acceptance: add test ensuring v5 sends report as json when catalog cached

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer commented on  PUP-7730 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: acceptance: add test ensuring v5 sends report as json when catalog cached  
 
 
 
 
 
 
 
 
 
 
Maggie DreyerEric Delaney Would either of you be able to review John's 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-7850) Add plan to puppet language

[Thomas Hallgren (JIRA)]

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

 
 
 
 
 
 
 
 Puppet /  PUP-7850 
 
 
 
  Add plan to puppet language  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-7875) Add a run_task function

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7875 
 
 
 
  Add a run_task function  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 Add a function {{run_task(Task $t, Array[String] $hosts = [])}} that runs the referenced instance of {{Task}} on the given set of hosts. Such that* if $hosts is not given, then it will run on the local hostAs an intermediate step, a mocking version of this function will instead accept any Object as a simulation of a real Task. The function will initially do a notice of the type for feedback, and return a 'result' attribute if an 'exit' attribute is non existing or '0', and the exit code otherwise. This allows mocking up  examples with fake tasks (before they can be loaded). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[Henrik Lindberg (JIRA)]

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

 
 
 
 
 
 
 
 Puppet /  PUP-7875 
 
 
 
  Add a run_task function  
 
 
 
 
 
 
 
 
 

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-7853) Add short form type definition

[Kenn Hussey (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-7853 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add short form type definition  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg did this make it through CI yet? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-7852) Simplify definition and override of constants in Object

[Kenn Hussey (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-7852 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Simplify definition and override of constants in Object  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg did this make it through CI yet? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-7875) Add a run_task function

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7875 
 
 
 
  Add a run_task function  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Tasks  ETP  Kanban 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7875 
 
 
 
  Add a run_task function  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Key:
 
 TASKS PUP - 34 7875 
 
 
 

Project:
 
 Puppet  Tasks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3589) PQL: easier querying for nodes that have a class applied

[Russell Mull (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull commented on  PDB-3589 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PQL: easier querying for nodes that have a class applied  
 
 
 
 
 
 
 
 
 
 
'inventory  { class = "Webserver" } 
or something like that 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7850 
 
 
 
  Add plan to puppet language  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 placeholder The puppet language should support the notion of a "plan" such that:* a plan created in the language with the syntax (example){code}plan mymodule::my_plan(String $msg) {  # doing lots of things with tasks}{code}* a plan is either defined in the "main manifest" or is autoloaded:** from a module with the name of the first part of a plan's fully qualified name** from the environment** with autoloading taking place from /plans* can be invoked by calling the function {{run_plan(String $plan_name, Hash\[String, Any] $args = \{})}} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[Henrik Lindberg (JIRA)]

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

 
 
 
 
 
 
 
 Puppet /  PUP-7850 
 
 
 
  Add plan to puppet language  
 
 
 
 
 
 
 
 
 

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-7541) Explore removing export / collect / virtual / realize syntax

[Craig Dunn (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Dunn commented on  PUP-7541 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Explore removing export / collect / virtual / realize syntax  
 
 
 
 
 
 
 
 
 
 
I think generally speaking the use of export/collect and virtualize/realize are in decline in the wild - there are certainly very few Forge modules that use the pattern and I think there are sufficient replacement patterns now that achieve the desired result, so I'm not against moving to deprecate that specific functionality - however, resource collectors also are used to set dependencies with chaining and this is something that would break a lot of stuff. 
I think PUP-6712 should be linked into this issue - as that would enable the retention of chaining functionality whilst also deprecating the collector syntax. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7865) error 500 on server file metadata with space in name

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7865 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: error 500 on server file metadata with space in name  
 
 
 
 
 
 
 
 
 
 
Eric V. Bahmer A stacktrace from the server logs would be very helpful. Just the part for the error in question is enough. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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