Jira (PUP-4742) Bring semantic_puppet library into Puppet

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4742 
 
 
 
  Bring semantic_puppet library into Puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2106-06-01 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4514 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Improve external syntax checking of heredoc  
 
 
 
 
 
 
 
 
 
 
This should move to NPUP to be dealt with in some future... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4764 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the ability to compile catalogs and get code coverage  
 
 
 
 
 
 
 
 
 
 
I don't think this will ever be done in the Ruby implementation - closing this epic and related tickets. (Can always be reopened). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5764 
 
 
 
  Support a single _ to mean ignored parameter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5764 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support a single _ to mean ignored parameter  
 
 
 
 
 
 
 
 
 
 
An alternative is to accept that a parameter that only has a type is the same as entering _ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-5816) Allow puppet type system types to be used in ruby case expressions by supporting === to mean instance?

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5816 
 
 
 
  Allow puppet type system types to be used in ruby case expressions by supporting === to mean instance?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-5816) Allow puppet type system types to be used in ruby case expressions by supporting === to mean instance?

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5816 
 
 
 
  Allow puppet type system types to be used in ruby case expressions by supporting === to mean instance?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Summary:
 
 Allow puppet type system types to be used in  ruby  case expressions by supporting === to mean instance? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-5816) Allow puppet type system types to be used in ruby case expressions by supporting === to mean instance?

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5816 
 
 
 
  Allow puppet type system types to be used in ruby case expressions by supporting === to mean instance?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5871 
 
 
 
  Add Timestamp and Timespan to Puppet type system  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6310 
 
 
 
  Specify the PCore Serialization formats  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2106-06-01 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6312) Load XPP instead of .pp if present and feature flag is on

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6312 
 
 
 
  Load XPP instead of .pp if present and feature flag is on  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2106-06-01 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6311) Define where XPP files should be written, and how resolution works

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6311 
 
 
 
  Define where XPP files should be written, and how resolution works  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2106-06-01 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-5723) Poor error reporting when metadata.json is incorrect or incomplete

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5723 
 
 
 
  Poor error reporting when metadata.json is incorrect or incomplete  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 2 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6304 
 
 
 
  Add string formatting rules to String.new  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language  2106-06-01  Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6135 
 
 
 
  change type mismatch errors in past tense to present tense  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language  Triage, Language  2016-05-04 , Language 2106-06-01 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Larissa Lane (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Larissa Lane updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2547 
 
 
 
  Add in new clj-i18n scaffolding to PuppetDB  
 
 
 
 
 
 
 
 
 

Change By:
 
 Larissa Lane 
 
 
 

Labels:
 
 i18n 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2802) add slot support for packages in portage.rb

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2802 
 
 
 
  add slot support for packages in portage.rb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Acceptance Criteria:
 
 Verify behavior in a Gentoo environment. I've setup a Vagrant environment based on{code}config.vm.box = "cmiles/gentoo-amd64-minimal"config.vm.provider "virtualbox" do |vb|  vb.memory = "3072"  vb.cpus = 3end{code}and tried {{puppet apply}} with{code}package { "dev-lang/python:2.7":ensure => latest;}package { "dev-lang/python:3.4":ensure => latest;}package { "dev-lang/python:3.3":ensure => absent;}{code} 
 
 
 

Story Points:
 
 3 2 
 
 
 

Sprint:
 
 Client Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-2802) add slot support for packages in portage.rb

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2802 
 
 
 
  add slot support for packages in portage.rb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Hailee Kenney (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney commented on  FACT-1408 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter productname issue on Solaris  
 
 
 
 
 
 
 
 
 
 
Boyd Adamson, thank you! All that information is incredibly helpful. I think our plan, especially with the info you've provided, is to revert back to using prtdiag and go from there. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald assigned an issue to Sean McDonald 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-515 
 
 
 
  Add option to omit batch files from installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean McDonald 
 
 
 

Assignee:
 
 Sean McDonald 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-515 
 
 
 
  Add option to omit batch files from installation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/17 2:13 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Sean McDonald 
 
 
 
 
 
 
 
 
 
 
There are instances (such as the compilation of the puppet-agent project) where we do not want the installation of facter to create batch files. There needs to be an option to omit batch files 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 

Jira (HI-515) Add option to omit batch files from installation

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-515 
 
 
 
  Add option to omit batch files from installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean McDonald 
 
 
 

Sprint:
 
 RE 2016-05-18 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald assigned an issue to Sean McDonald 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6318 
 
 
 
  Add option to omit batch files from installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean McDonald 
 
 
 

Assignee:
 
 Sean McDonald 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald assigned an issue to Sean McDonald 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1421 
 
 
 
  Add option to omit batch files from installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean McDonald 
 
 
 

Assignee:
 
 Sean McDonald 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6318 
 
 
 
  Add option to omit batch files from installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean McDonald 
 
 
 

Scrum Team:
 
 Release Engineering 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1421 
 
 
 
  Add option to omit batch files from installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean McDonald 
 
 
 

Scrum Team:
 
 Release Engineering 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6318 
 
 
 
  Add option to omit batch files from installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean McDonald 
 
 
 

Sprint:
 
 RE 2016-05-18 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6318 
 
 
 
  Add option to omit batch files from installation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Sean McDonald 
 
 
 

Created:
 

 2016/05/17 2:10 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Sean McDonald 
 
 
 
 
 
 
 
 
 
 
There are instances (such as the compilation of the puppet-agent project) where we do not want the installation of facter to create batch files. There needs to be an option to omit batch files 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
  

Jira (FACT-1421) Add option to omit batch files from installation

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1421 
 
 
 
  Add option to omit batch files from installation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Sean McDonald 
 
 
 

Created:
 

 2016/05/17 2:02 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Sean McDonald 
 
 
 
 
 
 
 
 
 
 
There are instances (such as the compilation of the puppet-agent project) where we do not want the installation of facter to create batch files. There needs to be an option to omit batch files 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 

Jira (PUP-6317) Puppet apt repository broken for jessie

[Simon Hoenscheid (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Simon Hoenscheid created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6317 
 
 
 
  Puppet apt repository broken for jessie  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/17 1:58 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Simon Hoenscheid 
 
 
 
 
 
 
 
 
 
 
It seems to be the classical apt repository pool jessie is empty, which is the one, the puppet jessie package is writing to the sources list. stable is working instead. 
please fix the repo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
   

Jira (FACT-1419) Add a 'privileged' element to the identity fact

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1419 
 
 
 
  Add a 'privileged' element to the identity fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Fix Version/s:
 
 FACT 3.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Kylo Ginsberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6099 
 
 
 
  Additional file and mount autorequire  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Scope Change Reason:
 
 Community PR was ready to merge. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Kylo Ginsberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6099 
 
 
 
  Additional file and mount autorequire  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1416) Facter solaris_zones fact does not include non-running zones

[William Hopper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1416 
 
 
 
  Facter solaris_zones fact does not include non-running zones  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Release Notes Summary:
 
 Previously, the `solaris_zones` fact was only displaying information about zones which were running. This was fixed, and that fact now includes information about all zones on the system, whether they are running or not. 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1416) Facter solaris_zones fact does not include non-running zones

[William Hopper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1416 
 
 
 
  Facter solaris_zones fact does not include non-running zones  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Scope Change Reason:
 
 Support escalation - brought in to provide hotfix. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2707 
 
 
 
  puppetdb 4.1.0 2016-05-19 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Sprint:
 
 Hopper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2707 
 
 
 
  puppetdb 4.1.0 2016-05-19 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2720 
 
 
 
  Send out announcements (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Beth Cornils 
 
 
 

Created:
 

 2016/05/17 12:39 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
 

Morgan Rhodes: update the release google spreadsheet.
 

Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014)
 

Send the drafted release notes email.
 

If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev).
 

If this release has security implications, also send the release announcement to puppet-security-announce
 

Make a PSA on IRC letting those kiddos know about the new release.
 

Something along the lines of "PSA: facter 1.7.3 now available"
 
 

Jira (PDB-2721) Update dujour to notify users to use 4.1.0 (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2721 
 
 
 
  Update dujour to notify users to use 4.1.0 (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 

Created:
 

 2016/05/17 12:39 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
Update dujour to notify users to use 4.1.0. 
Dependencies: 
 

Packages pushed
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
   

Jira (PDB-2722) Close all resolved tickets in Jira (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2722 
 
 
 
  Close all resolved tickets in Jira (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 

Created:
 

 2016/05/17 12:39 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
Close any tickets that have been resolved for the release. 
https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%224.1.0%22%20AND%20status%20%3D%20Resolved 
There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: 
 

Select Bulk Change - All # issues
 

Step 1 - choose all relevant issues (likely all of them)
 

Step 2 - Select "Transition Issues"
 

Step 3 - Select "Closed"
 

Step 4 - Select "Fixed" in Change Resolution.
 

View what is about to change and confirm it. Then commit the change.
 
 
Dependencies: 
 

Jira (PDB-2719) Docs pushed (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2719 
 
 
 
  Docs pushed (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Nicholas Fagerlund 
 
 
 

Created:
 

 2016/05/17 12:39 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
Push the documentation updates to docs.puppetlabs.com. 
Dependencies: 
 

Go / No Go meeting (Status - Ship it!)
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
   

Jira (PDB-2718) Packages pushed (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2718 
 
 
 
  Packages pushed (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Morgan Rhodes 
 
 
 

Created:
 

 2016/05/17 12:39 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
Push packages 
 

run `rake pl:jenkins:uber_ship`
 

You will need the keys to the castle (aka the passphrase) for this to work.
 

Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms.
 

Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay.
 

If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file.
 

If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed.
 
 
   

Jira (PDB-2709) Reconcile git commits and JIRA tickets (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2709 
 
 
 
  Reconcile git commits and JIRA tickets (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. 
 

cd ~/work
 

git clone https://github.com/puppetlabs/ticketmatch
 

cd ~/work/puppet # or whatever the repo is you're releasing from
 

ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0
 
 
The output may contain the following headers: 
COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) 
Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into an earlier 

Jira (PDB-2710) Update version number in source (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2710 
 
 
 
  Update version number in source (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
Bump VERSION in lib/PDB/version.rb or project.clj to correct version. 
 

Commit the updated version file.
 

e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3".
 

If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask).
 

Once this is done, hand the SHA to be built to RelEng to be tagged.
 
 
Dependencies: 
 

Is the code ready for release?
 

Reconcile git commits and JIRA tickets
 
 
 
 
 
 
 
 

Jira (PDB-2712) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2712 
 
 
 
  Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
This happens on Jira - we need to clean up the current release and prepare for the next release. 
 

Mark the version that's going out as "Released" in the Project Admin -> Versions panel.
 

Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future)
 

Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket):
 
 
 

'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone
 

'project = XX AND fixVersion = 

Jira (PDB-2713) Prepare long form release notes and short form release story (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2713 
 
 
 
  Prepare long form release notes and short form release story (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Nicholas Fagerlund 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
Collaborating with product for release story 
Dependencies: 
 

Reconcile git commits and JIRA tickets
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian 

Jira (PDB-2714) Tag the release and create packages (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2714 
 
 
 
  Tag the release and create packages (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Morgan Rhodes 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
Tag and create packages 
 

Developer provides the SHA - Wyatt Alt - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
 

checkout the sha
 

Make sure you are about to tag the correct thing
 

Create the tag e.g.) git tag -s -u {GPG key} 
 -m "1.7.3" 1.7.3
 

You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
 

DO NOT push the tag to the repo, keep it local only
 

`git describe` will show you the tag. Make sure you're building what you think you're building.
 
   

Jira (PDB-2715) Smoke test packages (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2715 
 
 
 
  Smoke test packages (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
Procedure may vary by project and point in the release cycle. Ask around. 
In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). 
For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. 
Lighter testing of Z releases is acceptable. 
 

Add a link to the Packages repository that you receive from the "Tag and create packages" subtask
 

Ping folks on your team for help with different platforms.
 

When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.
 
   

Jira (PDB-2716) Go/no-go meeting (before noon PST) (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2716 
 
 
 
  Go/no-go meeting (before noon PST) (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. 
Get a yes/no for the release from dev, docs, product, qa, releng. 
This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. 
Dependencies: 
 

Smoke testing
 
 
Participants: 
 

Wyatt Alt
 

Nicholas Fagerlund
 

Beth Cornils
 

Kurt Wall
 

Morgan Rhodes
  

Jira (PDB-2708) Is the code ready for release? (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2708 
 
 
 
  Is the code ready for release? (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. 
All tests (spec, acceptance) should be passing on all platforms for both stable & master. 
 

If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc.
 

If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests
 

Move all items that should be moved from Ready for CI to Ready for Review
 
 
Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. 
https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%224.1.0%22 
 
 
 
   

Jira (PDB-2711) Merge master into stable (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2711 
 
 
 
  Merge master into stable (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
For some releases, the code base will need to be merged down to stable. 
NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. 
Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: 
 
 
 
 
 
 
git fetch upstream 
 
 
 
 
git rebase upstream/master 
 
 
 
 
  
 
 
 
 
git 

Jira (PDB-2717) Push tag (PDB 4.1.0)

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2717 
 
 
 
  Push tag (PDB 4.1.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Morgan Rhodes 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
(Initial planned release date: 2016-05-19) 
The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. 
Dependencies: 
 

Go / No Go meeting (except where it's required to push the tag to build packages - MSIs)
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
  

Jira (PDB-2707) puppetdb 4.1.0 2016-05-19 Release

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2707 
 
 
 
  puppetdb 4.1.0 2016-05-19 Release  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 

Created:
 

 2016/05/17 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
puppetdb 4.1.0 2016-05-19 Release 
When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. 
 

The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them.
 

Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward.
 

When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
 
 
 
 
 
 
 
 
 
 
 
 
  

Jira (PDB-2706) investigate convergence test failure 5/17/16

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2706 
 
 
 
  investigate convergence test failure 5/17/16  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PDB 4.1.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/17 12:26 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
See 
https://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_pe-puppetdb-extensions_unit-clj-puppetdb_master/591/JDK=oraclejdk8,PUPPETDB_DBTYPE=postgres,label=integration/console 
or https://gist.github.com/wkalt/464f4f0a741cdc55a8565dd15d053459 for plaintext output. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 

Jira (FACT-1419) Add a 'privileged' element to the identity fact

[Michal Ruzicka (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Ruzicka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1419 
 
 
 
  Add a 'privileged' element to the identity fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michal Ruzicka 
 
 
 

Release Notes Summary:
 
 The `identity` structured fact has been enhanced with the ` superuser privileged ` element - a boolean flag which is set to true if facter is running  with the superuser privileges  as a privileged process  or false if not. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2524) Display replication status in the built-in PDB dashboard

[Russell Mull (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2524 
 
 
 
  Display replication status in the built-in PDB dashboard  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Sprint:
 
 HA 2016-06-15 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2526) Query pdb metrics / replication status from the PDB cli

[Russell Mull (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2526 
 
 
 
  Query pdb metrics / replication status from the PDB cli  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Sprint:
 
 HA 2016-07-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Sean Griffin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6159 
 
 
 
  OSX Passwords not setting under Puppet 4.4.1  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Sean Griffin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6301 
 
 
 
  Acceptance: AIX_service_provider test failing during setup  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-5926) launchd service provider doesn't implement status override.

[Sean Griffin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5926 
 
 
 
  launchd service provider doesn't implement status override.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-4617) puppet cert list should display long names for extensions

[Sean Griffin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4617 
 
 
 
  puppet cert list should display long names for extensions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1416) Facter solaris_zones fact does not include non-running zones

[Sean Griffin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1416 
 
 
 
  Facter solaris_zones fact does not include non-running zones  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Michal Ruzicka (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Ruzicka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1419 
 
 
 
  Add a 'privileged' element to the identity fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michal Ruzicka 
 
 
 

Summary:
 
 Add a ' superuser privileged ' element to the identity fact 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Michal Ruzicka (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Ruzicka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1419 
 
 
 
  Add a 'privileged' element to the identity fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michal Ruzicka 
 
 
 
 
 
 
 
 
 
 Enhance the {{identity}} fact with the {{ superuser privileged }} element - a boolean flag which is set to {{true}} if the facter process runs with UID of 0 on *NIX systems or with the privileges of the local Administrators group on Windows. Under any other circumstances the flag is set to {{false}}. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Michal Ruzicka (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Ruzicka assigned an issue to Michal Ruzicka 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1419 
 
 
 
  Add a 'superuser' element to the identity fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michal Ruzicka 
 
 
 

Assignee:
 
 Michal Ruzicka 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6316) Write up notes on Puppet Settings spike w/Kylo

[Erik Dasher (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6316 
 
 
 
  Write up notes on Puppet Settings spike w/Kylo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 

QA Risk Assessment Reason:
 
 QA RA=N/A; No functional code change associated with this ticket. 
 
 
 

QA Status:
 
 Reviewed 
 
 
 

QA Contact:
 
 Erik Dasher 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Matt Schuchard (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Schuchard commented on  PUP-4412 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow automatic parameter lookups to collect metaparameters  
 
 
 
 
 
 
 
 
 
 
Thanks for all the ideas and algorithms, These were very helpful. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-514 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Better error reporting for hiera type mismatch  
 
 
 
 
 
 
 
 
 
 
Which Puppet version are you using? (The error handling and reporting of line numbers etc. is done on the puppet side, not inside of hiera). If you are on a newer puppet, you can use the lookup function and the functionality that is offered by the lookup CLI which among other things have an --explain option. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Henrik Lindberg (JIRA)]

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

 
 
 
 
 
 
 
 Hiera /  HI-514 
 
 
 
  Better error reporting for hiera type mismatch  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Andrew Wasilczuk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2690) (maint) .gitignore: constrain; add Emacs entries

[Kenneth Barber (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2690 
 
 
 
  (maint) .gitignore: constrain; add Emacs entries  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 4.0.3 
 
 
 

Issue Type:
 
 Bug Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-2655 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create storage refactor design doc  
 
 
 
 
 
 
 
 
 
 
working document is here: https://docs.google.com/document/d/1tkzN4MAjTjySxe1yNLZ6QiOKOdHkZ7kmdBvVpJ5SYeY/edit#heading=h.9zm962jul7jn 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6305) R spike w/Kylo on simplifying Puppet's settings logic

[Chris Price (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6305 
 
 
 
  R spike w/Kylo on simplifying Puppet's settings logic  
 
 
 
 
 
 
 
 
 

Change By:
 
 Chris Price 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6305) R spike w/Kylo on simplifying Puppet's settings logic

[Chris Price (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6305 
 
 
 
  R spike w/Kylo on simplifying Puppet's settings logic  
 
 
 
 
 
 
 
 
 

Change By:
 
 Chris Price 
 
 
 

Scope Change Reason:
 
 prep for arch meetings 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6316) Write up notes on Puppet Settings spike w/Kylo

[Chris Price (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6316 
 
 
 
  Write up notes on Puppet Settings spike w/Kylo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Chris Price 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6316) Write up notes on Puppet Settings spike w/Kylo

[Chris Price (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6316 
 
 
 
  Write up notes on Puppet Settings spike w/Kylo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Chris Price 
 
 
 

Scope Change Reason:
 
 prep for arch meetings 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6316) Write up notes on Puppet Settings spike w/Kylo

[Chris Price (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6316 
 
 
 
  Write up notes on Puppet Settings spike w/Kylo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Chris Price 
 
 
 

Sprint:
 
 Server Emerald 2016-05-18 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6316) Write up notes on Puppet Settings spike w/Kylo

[Chris Price (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price assigned an issue to Chris Price 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6316 
 
 
 
  Write up notes on Puppet Settings spike w/Kylo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Chris Price 
 
 
 

Assignee:
 
 Chris Price 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6316) Write up notes on Puppet Settings spike w/Kylo

[Chris Price (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6316 
 
 
 
  Write up notes on Puppet Settings spike w/Kylo  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/17 7:41 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Chris Price 
 
 
 
 
 
 
 
 
 
 
Write up a summary and mini-proposal for possible next steps on simplifying Puppet settings logic, as per brainstorming sessions with Kylo. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 

Jira (PDB-2655) Create storage refactor design doc

[Steve Quin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Quin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2655 
 
 
 
  Create storage refactor design doc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Quin 
 
 
 

Sprint:
 
 Hopper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2705) (maint) Print test.check configuration first

[Kenneth Barber (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2705 
 
 
 
  (maint) Print test.check configuration first  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Affects Version/s:
 
 PDB 4.0.2 
 
 
 

Fix Version/s:
 
 PDB 4.0.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2705) (maint) Print test.check configuration first

[gepetto-bot (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2705 
 
 
 
  (maint) Print test.check configuration first  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/17 7:36 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
For the convergence_test we sometimes get deadlocks, this patch simply sets the seed manually (using the same methodology as test.check uses for now) and then prints it to the screen very early. 
Signed-off-by: Ken Barber  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
   

Jira (PUP-6303) Acceptance: nim_package_provider test fails on AIX 5.3

[John Duarte (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  PUP-6303 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Acceptance: nim_package_provider test fails on AIX 5.3  
 
 
 
 
 
 
 
 
 
 
After reviewing this with Geoff Nichols, the most likely cause for this is that the lpar had not finished resetting prior to executing the test suite. 
If this behaviour does not repeat itself on the next run, this ticket can be closed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6258) Update Puppet OID lists to add new authorized extensions

[Kevin Corcoran (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Corcoran commented on  PUP-6258 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update Puppet OID lists to add new authorized extensions  
 
 
 
 
 
 
 
 
 
 
Nathaniel Smith - Did you get some answers to your "open questions"? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[Andrew Wasilczuk (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Wasilczuk created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-514 
 
 
 
  Better error reporting for hiera type mismatch  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 HI 1.3.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Community 
 
 
 

Created:
 

 2016/05/17 4:17 AM 
 
 
 

Environment:
 
 
CentOS 6 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Andrew Wasilczuk 
 
 
 
 
 
 
 
 
 
 
The hiera_hash function fails with type error when a key is empty (or wrong type), which makes sense but the error message doesn't provide much information to help debug the issue: 
 
 
 
 
 
 
Error: Could not run: Hiera type mismatch: expected Hash and got NilClass