date:20161017

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols commented on  PUP-6761 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: [SPIKE] Find a workflow for POT file generation  
 
 
 
 
 
 
 
 
 
 
Larissa Lane, if you have a chance, could you please help us with the question above regarding directory structure for translation (PO and POT) files? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6762) [SPIKE] How and when do we get PO files from Transifex?

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols commented on  PUP-6762 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: [SPIKE] How and when do we get PO files from Transifex?  
 
 
 
 
 
 
 
 
 
 
Larissa Lane, if you have a chance, could you please help us with the questions above regarding the Transifex integration? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6511 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for lookup.conf (version 5)  
 
 
 
 
 
 
 
 
 
 
Agree - too pedantic, not good UX. I can live with having semantics at a higher level (that is, function-kind and function-name can be default, but is overridden by specifying any of the function kinds/name in an entry). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6794 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: acceptance: Sensitive inside Array, Hash, Object  
 
 
 
 
 
 
 
 
 
 
For now I think we need to state that support for Sensitive in the current implementation only works for values directly assigned to an attribute. Later when we do not need the special meta data as the Sensitive values are sent to the agent verbatim in the catalog. (That is the "rich data in catalog" will fix this, but I imagine it will require additional work on the agent side). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6800) Better error messaging around invalid class names

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6800 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Better error messaging around invalid class names  
 
 
 
 
 
 
 
 
 
 
Erik Hansen The name requirement for classes in the documentation is stricter than in the specification and the implementation - so, yes - the documentation should be updated. Documentation should also state that all autoloaded files must be in lower case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6800) Better error messaging around invalid class names

Title: Message Title

Henrik Lindberg commented on PUP-6800

Re: Better error messaging around invalid class names

Puppet does one lookup of a name against the file system using a downcase of the name. So any file with upper case letters will simply not work (unless the file system is case independent like on OSx).
The only search being made is that puppet starts with the most specific name, and then removes name/name-space from the right of the name until all wider name spaces have been loaded - thus subnames of say foo::bar::fee can be defined in foo/bar.pp if there is no foo/bar/fee.pp.
What puppet cannot do is to warn/error on a missing file based on case as a far more exhaustive search would need to be made.
Always use lower case file names. References to classes should be case independent.

Add Comment

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

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6800) Better error messaging around invalid class names

2016-10-17 Thread Nick Walker (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6800 
 
 
 
  Better error messaging around invalid class names  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 

Affects Version/s:
 
 PUP 4.7.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-6825) Missing tty2 package on Ubuntu causing test to fail

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

 
 
 
 
 
 
 
 Puppet /  PUP-6825 
 
 
 
  Missing tty2 package on Ubuntu causing test to fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Assignee:
 
 Maggie Dreyer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6825) Missing tty2 package on Ubuntu causing test to fail

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6825 
 
 
 
  Missing tty2 package on Ubuntu causing test to fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Sprint:
 
 AP 2016-10-19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6825) Missing tty2 package on Ubuntu causing test to fail

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6825 
 
 
 
  Missing tty2 package on Ubuntu causing test to fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6827) test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6827 
 
 
 
  test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  PA 1.8.0 Grooming/  Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6637) New attribute :manage_mountpoint for Mount type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6637 
 
 
 
  New attribute :manage_mountpoint for Mount type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  PA 1.8.0 Grooming/  Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6423) The scheduled_task provider performs incorrect matching on file names

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6423 
 
 
 
  The scheduled_task provider performs incorrect matching on file names  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  PA 1.8.0  Grooming  Top 11-20 /Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6432 
 
 
 
  Puppet::Util::Execution.execute cannot handle Unicode output on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  PA 1.8.0  Grooming  Top 10 /Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6816) Make gettext a hard requirement

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6816 
 
 
 
  Make gettext a hard requirement  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  PA 1.8.0 Grooming/  Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6806 
 
 
 
  Update beaker version to 3.1.0 to allow MacOS Sierra testing Support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Attachment:
 
 el4-beaker3.1.0-test_result.txt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1356) External facts should be able to return structured data

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols commented on  FACT-1356 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: External facts should be able to return structured data  
 
 
 
 
 
 
 
 
 
 


LTH-114
 is resolved, so moving this to "Ready for Engineering". 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6637) New attribute :manage_mountpoint for Mount type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6637 
 
 
 
  New attribute :manage_mountpoint for Mount type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6432 
 
 
 
  Puppet::Util::Execution.execute cannot handle Unicode output on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP Grooming Top 10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6687) lest and then functions not well referenced in the documentation

2016-10-17 Thread Michelle Fredette (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6687 
 
 
 
  lest and then functions not well referenced in the documentation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Labels:
 
 docs_reviewed maintenance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6637) New attribute :manage_mountpoint for Mount type

2016-10-17 Thread Kylo Ginsberg (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6637 
 
 
 
  New attribute :manage_mountpoint for Mount type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support

2016-10-17 Thread Sean McDonald (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6806 
 
 
 
  Update beaker version to 3.1.0 to allow MacOS Sierra testing Support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean McDonald 
 
 
 

Attachment:
 
 windows.log 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6800) Better error messaging around invalid class names

2016-10-17 Thread Nick Walker (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker commented on  PUP-6800 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Better error messaging around invalid class names  
 
 
 
 
 
 
 
 
 
 
So, I think we have a bug around how the puppet master searches for the file on disk that holds a class. Allow me to demonstrate with some examples.  
I see three factors:  1. The name of the .pp file we put the class in 2. The name of the class 3. The name of the class when we try to include it 
Lower case, everything works  
 
 
 
 
 
 
[root@master201640-centos modules]# pwd 
 
 
 
 
/etc/puppetlabs/code/environments/production/modules 
 
 
 
 
[root@master201640-centos modules]# tree 
 
 
 
 
. 
 
 
 
 
└── role 
 
 
 
 
└── manifests 
 
 
 
 
└── appserver 
 
 
 
 
└── windows_2012r2.pp 
 
 
 
 
  
 
 
 
 
3 directories, 1

Jira (FACT-1356) External facts should be able to return structured data

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1356 
 
 
 
  External facts should be able to return structured data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP 2016-09-21, AP 2016-11-02  Holding 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6800) Better error messaging around invalid class names

2016-10-17 Thread Erik Hansen (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Hansen commented on  PUP-6800 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Better error messaging around invalid class names  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg The documentation says that class names must match the regex: \A[a-z][a-z0-9_]*\Z 
Or, for multiple namespaces: \A([a-z][a-z0-9_])?(::[a-z][a-z0-9_])*\Z 
Do we need to change this so that uppercase characters are included? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6637) New attribute :manage_mountpoint for Mount type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6637 
 
 
 
  New attribute :manage_mountpoint for Mount type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Fix Version/s:
 
 PUP 4.y 
 
 
 

Fix Version/s:
 
 PUP 4.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-6830) Support CA certificate and CRL bundles

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6830 
 
 
 
  Support CA certificate and CRL bundles  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/10/17 3:10 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Adrien Thebo 
 
 
 
 
 
 
 
 
 
 
The Puppet agent technically supports multiple CAs, though this isn't documented or really supported. As part of our long term CA rotation plan we need to formally support multiple CAs, and by extension multiple CRLs. 
Both CA cert and CRL bundles need to be updated on some interval. This can either be at the beginning of every Puppet run as part of the health check, or it can be on a slower interval based on the timestamp of the CA cert/CRL bundle. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This

Jira (PUP-6637) New attribute :manage_mountpoint for Mount type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6637 
 
 
 
  New attribute :manage_mountpoint for Mount type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Fix Version/s:
 
 PUP 4.8.0 
 
 
 

Fix Version/s:
 
 PUP 4.y 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6829) Improve agent mutex on Windows

2016-10-17 Thread James Stocks (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Stocks created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6829 
 
 
 
  Improve agent mutex on Windows  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PUP 4.7.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Windows 
 
 
 

Created:
 

 2016/10/17 2:27 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 James Stocks 
 
 
 
 
 
 
 
 
 
 
Current behaviour: 
 

puppet agent on Windows starts ruby.exe, that takes some time to launch, then ruby checks for an existing agent PID file and exits if puppet agent is already running
 
 
Suggestion: 
 

Improve this so that puppet agent exits immediately. The time to launch ruby can be significant (~12 seconds on our Windows 2008 vmpooler VMs) and may cause complications with newer PE features that run puppet on demand.

Jira (PUP-6188) Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza assigned an issue to Moses Mendoza 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6188 
 
 
 
  Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Assignee:
 
 Moses Mendoza 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6188) Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6188 
 
 
 
  Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Sprint:
 
 AP 2016- 11 10 - 02 19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support

Title: Message Title

Maggie Dreyer commented on PUP-6806

Re: Update beaker version to 3.1.0 to allow MacOS Sierra testing Support

That is unfortunately only one of 4 or 5 associated PRs that resulted from the fact that there are many many places where the Ruby version needed to be bumped.
The others are: https://github.com/puppetlabs/ci-job-configs/pull/1879 https://github.com/puppetlabs/ci-job-configs/pull/1881 https://github.com/puppetlabs/ci-job-configs/pull/1882 https://github.com/puppetlabs/ci-job-configs/pull/1883 https://github.com/puppetlabs/ci-job-configs/pull/1884
If we weren't throwing out the current ci-job-configs as part of CI.next, it would almost certainly be worth it to centralize this kind of change. Ideally we would be able to change one number, and all of those would be updated.

Add Comment

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

Jira (PUP-6474) Incorporate gettext_setup gem into puppet

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6474 
 
 
 
  Incorporate gettext_setup gem into puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Assignee:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  PUP-6806 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update beaker version to 3.1.0 to allow MacOS Sierra testing Support  
 
 
 
 
 
 
 
 
 
 
Yes, we are now on Ruby 2.3.1 on all the beaker masters. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-6806 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update beaker version to 3.1.0 to allow MacOS Sierra testing Support  
 
 
 
 
 
 
 
 
 
 
Ah yes. found it: https://github.com/puppetlabs/ci-job-configs/pull/1886/files. Adding as a link to this ticket  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-6806 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update beaker version to 3.1.0 to allow MacOS Sierra testing Support  
 
 
 
 
 
 
 
 
 
 
Has the ci-job-configs change to ruby 2.2.5 or later been merged?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza assigned an issue to Moses Mendoza 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6806 
 
 
 
  Update beaker version to 3.1.0 to allow MacOS Sierra testing Support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Assignee:
 
 Moses Mendoza 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6827) test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016

2016-10-17 Thread Sean McDonald (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6827 
 
 
 
  test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/10/17 1:34 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Sean McDonald 
 
 
 
 
 
 
 
 
 
 
When running the puppet aio test suite: 
 
 
 
 
 
 
Test Case tests/ticket_6857_password-disclosure-when-changing-a-users-password.rb reported: # 
 
 
 
 
  Test line: tests/ticket_6857_password-disclosure-when-changing-a-users-password.rb:45:in `block (2 levels) in run_test' 
 
 
 
 
Test Case tests/ticket_13948_lib_dir_hook_should_be_called_on_initialization.rb reported: # 
 
 
 
 
   cmd.exe /c puppet help

Jira (PUP-6828) Agent PKI initialization is too complicated

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6828 
 
 
 
  Agent PKI initialization is too complicated  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Adrien Thebo 
 
 
 

Created:
 

 2016/10/17 1:41 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Adrien Thebo 
 
 
 
 
 
 
 
 
 
 
The Puppet X.509 PKI initialization logic is currently confusing, inconsistent, and buggy, due to the ad hoc nature of its implementation. The Puppet::SSL::Host class is responsible, either directly or indirectly, for fetching the CA certificate, CRL, RSA key pair, CSR, and certificate. This initialization is scattered across a number of functions and files, and is largely triggered by lazy methods. This structure makes it very hard to reason about or improve the PKI initialization process. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA

Jira (PUP-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support

2016-10-17 Thread Sean McDonald (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald commented on  PUP-6806 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update beaker version to 3.1.0 to allow MacOS Sierra testing Support  
 
 
 
 
 
 
 
 
 
 
So, everything relating to 2012r2 has been identified as transient. The 2016 error is legitimate, but should not block this work as 2016 is not in the pipelines 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-6825) Missing tty2 package on Ubuntu causing test to fail

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-6825 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing tty2 package on Ubuntu causing test to fail  
 
 
 
 
 
 
 
 
 
 
I believe daemontools-run may be a sufficient replacement? 
 
 
 
 
 
 
root@l5g73au1ypxm4io:/etc/init# apt-cache show daemontools-run 
 
 
 
 
Package: daemontools-run 
 
 
 
 
Priority: optional 
 
 
 
 
Section: universe/admin 
 
 
 
 
Installed-Size: 104 
 
 
 
 
Maintainer: Ubuntu Developers  
 
 
 
 
Original-Maintainer: Gerrit Pape  
 
 
 
 
Architecture: all 
 
 
 
 
Source: daemontools 
 
 
 
 
Version: 1:0.76-3ubuntu3

Jira (PUP-6826) Agents should renew their certificate when their current cert is expiring

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6826 
 
 
 
  Agents should renew their certificate when their current cert is expiring  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/10/17 12:39 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Adrien Thebo 
 
 
 
 
 
 
 
 
 
 
Currently, the Puppet agent can only request a certificate once and does not understand certificate expiration/renewal. Moreover when the client certificate expires the node is disconnected from the master, so certificate expiration is pretty catastrophic. Puppet agents should be able to detect when their certificate is expiring, submit a CSR, and attempt to retrieve a new certificate once the CSR has been signed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA

Jira (PUP-6825) Missing tty2 package on Ubuntu causing test to fail

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6825 
 
 
 
  Missing tty2 package on Ubuntu causing test to fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Issue Type:
 
 Bug CI Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6825) Missing tty2 package on Ubuntu causing test to fail

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6825 
 
 
 
  Missing tty2 package on Ubuntu causing test to fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 
 
 
 
 
 
 
 This test  -->  https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/service/ticket_14297_handle_upstart.rb  <--  recently started failing with this error:{code}v8pd6i6xevzbg63.delivery.puppetlabs.net (ubuntu1004-64-1) 19:07:36$ puppet resource package tty2 ensure=present Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install tty2' returned 100: Reading package lists... Building dependency tree... Reading state information... E: Couldn't find package tty2 Error: /Package[tty2]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install tty2' returned 100: Reading package lists... Building dependency tree... Reading state information... E: Couldn't find package tty2 package { 'tty2':   ensure => 'purged', }{code}The tty2 package does not appear to be in apt repos anymore. In the test, we were using tty2 as an example of a package that uses "upstart with no linked init script". We may need to find an alternative example that is still distributed for Ubuntu. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to

Jira (PUP-6825) Missing tty2 package on Ubuntu causing test to fail

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6825 
 
 
 
  Missing tty2 package on Ubuntu causing test to fail  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/10/17 11:53 AM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Maggie Dreyer 
 
 
 
 
 
 
 
 
 
 
This test -

> https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/service/ticket_14297_handle_upstart.rb <
- recently started failing with this error: 
 
 
 
 
 
 
v8pd6i6xevzbg63.delivery.puppetlabs.net (ubuntu1004-64-1) 19:07:36$ puppet resource package tty2 ensure=present 
 
 
 
 
 Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install tty2' returned 100: Reading package lists... 
 
 
 
 
 Building dependency tree...

Jira (PUP-6824) Use UUIDs for certificate serial numbers

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6824 
 
 
 
  Use UUIDs for certificate serial numbers  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Adrien Thebo 
 
 
 

Created:
 

 2016/10/17 11:06 AM 
 
 
 

Labels:
 

 ca 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Adrien Thebo 
 
 
 
 
 
 
 
 
 
 
Puppet has historically used a monotonically increasing serial number when signing certificates, which is the default behavior for the underlying library, OpenSSL. However RFC 5280 4.1.2.2 indicates that serial numbers need only be 20 byte non-negative integers. We should switch to using 16 byte v4 UUIDs to reduce the likelihood of serial number collisions and make it easier to sign CSRs on multiple masters with the same CA certificate and key pair. 
See also redmine #6725. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-1271) puppet ca list --all fails with "Error: The certificate retrieved from the master does not match the agent's private key."

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1271 
 
 
 
  puppet ca list --all fails with "Error: The certificate retrieved from the master does not match the agent's private key."  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrien Thebo 
 
 
 

Labels:
 
 ca redmine 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2931 
 
 
 
  Puppet CA sometimes resets certificate serial counter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrien Thebo 
 
 
 

Labels:
 
 ca 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo commented on  PUP-6794 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: acceptance: Sensitive inside Array, Hash, Object  
 
 
 
 
 
 
 
 
 
 
Oof. This is a case that I didn't expect. I that Array[Variant[Sensitive, String]] should be converted to Sensitive[Array[String]], and in general combining any type with Sensitive should wrap the resulting object in Sensitive. However implementing that sort of thing seems hard. 
I'm starting to wonder if it was a mistake to implement Sensitive as a datatype when it's really just metadata - being able to recursively apply metadata to all of a data structure might be easier than having to transform data structures based on the type of a contained value. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1384) Remove deprecated APIs necessitated by Server 2003 compat

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1384 
 
 
 
  Remove deprecated APIs necessitated by Server 2003 compat  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Fix Version/s:
 
 FACT 3.y 
 
 
 

Fix Version/s:
 
 FACT 3.5.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (FACT-1516) Update facter tests to include check for Sierra Kernel version

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  FACT-1516 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update facter tests to include check for Sierra Kernel version  
 
 
 
 
 
 
 
 
 
 
PR to add the beaker version bump back in is here: https://github.com/puppetlabs/facter/pull/1447 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

2016-10-17 Thread gepetto-bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3100 
 
 
 
  (MAINT) Bump beaker to 2.50.0  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/10/17 8:47 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Previously, PuppetDB's Gemfile was picking up beaker version 2.43.0. This was transitively picking up hocon version 0.9.5. puppetserver recently added some variable interpolation to the puppetserver.conf file. Some fixes in hocon 1.0 and later are needed in order for the interpolation to be handled correctly. 
This commit bumps the beaker dependency in the Gemfile to ~> 2.50.0, which transitively will cause test jobs to pick up a newer hocon gem dependency, >= 1.0. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This

Jira (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc

2016-10-17 Thread Branan Riley (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-1441 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add "virtualization" fact that identifies AWS, Azure, etc  
 
 
 
 
 
 
 
 
 
 
Scott McClellan I'd duplicate the virtual fact, yeah. And also the EC2 metadata when it's running in that environment. We may also want to look at the virtual fact and ensure that it's really reporting hypervisors, and not cloud systems - I think it kinda-sorta does both in some cases. Now that we have separate fields we should fix that up if needed for the hypervisor fact (while maintaining the old idea of the "virtual" fact) 
I think the "right way" to do this is to move the virtual and ec2 fact data into the new virtualization fact, and from there make the require legacy bits (the virtual fact and the ec2_metadata) available at the top level. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

2016-10-17 Thread Rob Browning (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Rob Browning 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3098 
 
 
 
  Remove ActiveMQ/KahaDB related docs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Assignee:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6823) Puppet filebucket command does not pick up proper server address from server_list config property

2016-10-17 Thread Mateusz Gozdek (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mateusz Gozdek commented on  PUP-6823 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet filebucket command does not pick up proper server address from server_list config property  
 
 
 
 
 
 
 
 
 
 
As far as i see in filebucket.rb, it's using 
 
 
 
 
 
 
Puppet[:server]
 
 
 
 
 
 
 
which is puppet by default. Maybe that would be good to make it default to first server from server_list, if server_list IS defined and server is not in the config. 
Other solution would be to patch filebucket to be able to use mutliple servers. IE. if sending to first server fails, try to send it to next server. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6823) Puppet filebucket command does not pick up proper server address from server_list config property

2016-10-17 Thread Mateusz Gozdek (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mateusz Gozdek created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6823 
 
 
 
  Puppet filebucket command does not pick up proper server address from server_list config property  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.7.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 filebucket 
 
 
 

Created:
 

 2016/10/17 5:32 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Mateusz Gozdek 
 
 
 
 
 
 
 
 
 
 
I have following problem. When I changed `server` config option to `server_list` to increase redundancy, I met following problem (useless stuff omitted): 
 
 
 
 
 
 
root@localhost: puppet filebucket backup foo 
 
 
 
 
Debug: Runtime environment: puppet_version=4.7.0, ruby_version=2.1.9, run_mode=user, default_encoding=UTF-8

Jira (PUP-6823) Puppet filebucket command does not pick up proper server address from server_list config property

2016-10-17 Thread Mateusz Gozdek (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mateusz Gozdek updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6823 
 
 
 
  Puppet filebucket command does not pick up proper server address from server_list config property  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mateusz Gozdek 
 
 
 
 
 
 
 
 
 
 I have following problem. When I changed  `  * server ` *  config option to  `  * server_list ` *  to increase redundancy, I met following problem (useless stuff omitted):{noformat}root@localhost: puppet filebucket backup fooDebug: Runtime environment: puppet_version=4.7.0, ruby_version=2.1.9, run_mode=user, default_encoding=UTF-8Info: Computing checksum on file fooDebug: Dynamically-bound server lookup failed; using first entryDebug: Dynamically-bound port lookup failed; using first entryDebug: Applying settings catalog for sections main, sslDebug: /User[puppet]: Provider useradd does not support features libuser; not managing attribute forcelocalDebug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not existDebug: Puppet::Type::Group::ProviderPw: file pw does not existDebug: Puppet::Type::Group::ProviderLdap: feature ldap is missingDebug: /Group[puppet]: Provider groupadd does not support features libuser; not managing attribute forcelocalDebug: Finishing transaction 29004960Debug: Creating new connection for https://puppet:8140Error: Could not back up foo: getaddrinfo: Name or service not knownError: Could not run: Could not back up foo: getaddrinfo: Name or service not known{noformat} ` * puppet.conf ` *  file:{noformat}[main]server_list=foo:8140,bar:8140,baz:8140factpath=$vardir/lib/facterca_server=foopreferred_serialization_format=msgpack{noformat}When I specify both  `  * server ` *  and  `  * server_list ` *  in puppet.conf file it's working, but I'm getting this warning:{noformat}Warning: Attempted to set both server and server_list. Server setting will not be used.   (at /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/defaults.rb:1411:in `block in '){noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-6511) Add support for lookup.conf (version 5)

2016-10-17 Thread Thomas Hallgren (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6511 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for lookup.conf (version 5)  
 
 
 
 
 
 
 
 
 
 
Agree about that oddity. It also makes the definition of the actual type (the Struct) for the hierarchy entry a bit difficult since we don't currently allow an entry to be a Variant. I can live with that though. The alternative is ugly. It would be something like: 
 
 
 
 
 
 
hierarchy: 
 
 
 
 
  - name: Common 
 
 
 
 
function: 
 
 
 
 
  type: data_hash 
 
 
 
 
  name: yaml_data 
 
 
 
 
location: 
 
 
 
 
  type: path 
 
 
 
 
  value: common.yaml

Jira (PUP-6511) Add support for lookup.conf (version 5)