date:20151119

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jo Rhett updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5206 
 
 
 
  Puppet filebucket get --local does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jo Rhett 
 
 
 

Affects Version/s:
 
 PUP 4.3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jo Rhett updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5206 
 
 
 
  Puppet filebucket --local uses $bucketdir instead of $clientbucketdir  
 
 
 
 
 
 
 
 
 
 
Turns out that the filebucket commands are inconsistent on which variable they use. Puppet agent backs up files to $clientbucketdir but --local flag uses $bucketdir instead. 
 
 
 
 
 
 
[root@client vagrant]# puppet filebucket -l list --bucketdir=/opt/puppetlabs/puppet/cache/clientbucket 
 
 
 
 
dc9e5754ad2bb6f6c32b954c04431d0a 2015-09-06 20:30:59 /etc/ntp.conf 
 
 
 
 
ff26b20aa0c9fed35515afbcbf7190b0 2015-09-06 20:34:05 /etc/ntp.conf 
 
 
 
 
b751b9441d5057a503c13f5f5da3f1d5 2015-09-07 01:20:09 /etc/ntp.conf 
 
 
 
 
73e68cfd79153a49de6f5721ab60657b 2015-09-08 06:55:17 /etc/puppetlabs/mcollective/server.cfg 
 
 
 
 
7b87eea4021fe1a563f443aa493cf99a 2015-09-08 08:05:22 /etc/puppetlabs/mcollective/server.cfg
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Change By:
 
 Jo Rhett 
 
 
 

Summary:

Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jo Rhett commented on  PUP-5206 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir  
 
 
 
 
 
 
 
 
 
 
Workaround in puppet.conf 
 
 
 
 
 
 
[user] 
 
 
 
 
bucketdir = $clientbucketdir
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5206) Puppet filebucket get --local does not work

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jo Rhett commented on  PUP-5206 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet filebucket get --local does not work  
 
 
 
 
 
 
 
 
 
 
This problem persists with Puppet 4.3, rendering the new bucket commands useless: 
 
 
 
 
 
 
[root@client vagrant]# puppet config --section user print |grep bucket 
 
 
 
 
bucketdir = /opt/puppetlabs/puppet/cache/bucket 
 
 
 
 
clientbucketdir = /opt/puppetlabs/puppet/cache/clientbucket 
 
 
 
 
[root@client vagrant]# puppet config --section agent print |grep bucket 
 
 
 
 
bucketdir = /opt/puppetlabs/puppet/cache/bucket 
 
 
 
 
clientbucketdir = /opt/puppetlabs/puppet/cache/clientbucket 
 
 
 
 
[root@client vagrant]# puppet filebucket -l list  
 
 
 
 
Error: Could not run: File not found 
 
 
 
 
[root@client vagrant]# find /opt/puppetlabs/puppet/cache/clientbucket -type f

Jira (PUP-5392) 'bucketdir' is not used in Puppet 4

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jo Rhett commented on  PUP-5392 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 'bucketdir' is not used in Puppet 4  
 
 
 
 
 
 
 
 
 
 
Actually seems like $bucketdir is used for some commands, instead of $clientbucket 
 
 
 
 
 
 
# puppet config --section user print |grep bucket 
 
 
 
 
bucketdir = /opt/puppetlabs/puppet/cache/bucket 
 
 
 
 
clientbucketdir = /opt/puppetlabs/puppet/cache/clientbucket 
 
 
 
 
[root@client vagrant]# puppet config --section agent print |grep bucket 
 
 
 
 
bucketdir = /opt/puppetlabs/puppet/cache/bucket 
 
 
 
 
clientbucketdir = /opt/puppetlabs/puppet/cache/clientbucket 
 
 
 
 
[root@client vagrant]# puppet filebucket -l list  
 
 
 
 
Error: Could not run: File not found 
 
 
 
 
[root@client vagrant]# puppet filebucket -l list --bucketdir=/opt/puppetlabs/puppet/cache/clientbucket 
 
 
 
 
dc9e5754ad2bb6f6c32b954c04431d0a 2015-09-06 20:30:59

Jira (PUP-2011) Puppet 3.4.3 fails to run on OS X 10.9.2

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Denver McAnally commented on  PUP-2011 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet 3.4.3 fails to run on OS X 10.9.2  
 
 
 
 
 
 
 
 
 
 
my version of macosx.rb is the same as yours. I'm not sure what is different about my environment. 
Thanks for the back and forth! I really appreciate it. When I figure out what my problem is, I'll leave a comment incase someone else has the same issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5521) Puppet labs reboot resource is not functioning

2015-11-19 Thread Abhay Joshi (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Abhay Joshi created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5521 
 
 
 
  Puppet labs reboot resource is not functioning  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.3 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Modules 
 
 
 

Created:
 

 2015/11/19 11:02 AM 
 
 
 

Environment:
 
 
Using puppet labs open source on Ubuntu 14.04.1 platform. 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Abhay Joshi 
 
 
 
 
 
 
 
 
 
 
We are trying to install packages for kernel upgrade on Ubuntu-14.04.1 platform. Subsequent to the packages needed to be installed to upgrade the default kernel for Ubuntu 14.04.1 from 3.13.0-32 to 3.13.0-40, we use the "reboot" resource to reboot the machine for the upgraded kernel to take effect. Below are the packages we try to install.  
linux-headers-3.13.0-40 linux-headers-3.13.0-40-generic linux-image-3.13.0-40-generic linux-image-extra-3.13.0-40-generic 
We are experiencing that sometimes the "reboot" resource is not taking effect. As a result, puppet catalog execution, which is

Jira (PUP-5520) Exclude sendsigs from service init provider

2015-11-19 Thread Rick Sherman (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Sherman created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5520 
 
 
 
  Exclude sendsigs from service init provider  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Rick Sherman 
 
 
 

Created:
 

 2015/11/19 10:09 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rick Sherman 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2011) Puppet 3.4.3 fails to run on OS X 10.9.2

Title: Message Title

Denver McAnally commented on PUP-2011

Re: Puppet 3.4.3 fails to run on OS X 10.9.2

It turns out that your initial comment about UTF-8 was the right direction...
The root user's account does not have LANG defined as an environment variable

locale LANG= LC_COLLATE="C" LC_CTYPE="C" LC_MESSAGES="C" LC_MONETARY="C" LC_NUMERIC="C" LC_TIME="C" LC_ALL=

exit logout $ locale LANG="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_CTYPE="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_ALL=

If I define LANG with "export LANG=en_US.UTF-8" for the root user, facter and puppet begin running manually just fine.
Thanks for helping me get to the resolution. Please note, I am writing a custom script that calls puppet manually as the root user and since root could not run puppet, my script was failing. now puppet runs cleanly and the script works!
Thanks, Denver

Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

--
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-2208) simultaneously restarting PDB instances during an initial sync can lead to bad outcomes

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2208 
 
 
 
  simultaneously restarting PDB instances during an initial sync can lead to bad outcomes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/11/19 5:00 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
If you have an existing PDB instance A, and you want to spin up blank instance B, B will enter an initial sync phase that may last some time. If you restart both instances simultaneously during the initial sync, B might come up first. In that case it becomes the preferred target for sticky querying, which could really mess you up if you make heavy use of exported resources. Under these circumstances the two will eventually converge, but we may want to use a lock file for the initial sync that will prevent this from happening. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-1455) Puppet should utilize CFPropertyList to read/write plist files

2015-11-19 Thread Michael Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith assigned an issue to Eric Sorenson 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1455 
 
 
 
  Puppet should utilize CFPropertyList to read/write plist files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Assignee:
 
 Michael Smith Eric Sorenson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-1455) Puppet should utilize CFPropertyList to read/write plist files

2015-11-19 Thread Michael Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith assigned an issue to Michael Smith 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1455 
 
 
 
  Puppet should utilize CFPropertyList to read/write plist files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Assignee:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-1031) Improve Puppet's handling of non-ASCII character encodings

2015-11-19 Thread Owen Rodabaugh (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1031 
 
 
 
  Improve Puppet's handling of non-ASCII character encodings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Priority:
 
 Needs Priority Major 
 
 
 

CS Impact:
 
 While our international presence is not yet huge we are growing it and seeing a lot of interest. We need to fix this for both our existing customers that are running into it as well as future customers.The workaround of not using international characters is not an acceptable long term solution. 
 
 
 

CS Severity:
 
 4 
 
 
 

CS Business Value:
 
 5 
 
 
 

CS Frequency:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PDB-2206) indexes on transaction_uuid and hash are not used in querying

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt assigned an issue to Wyatt Alt 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2206 
 
 
 
  indexes on transaction_uuid and hash are not used in querying  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (FACT-1277) `facter -p` should report core Puppet facts like puppetversion

2015-11-19 Thread Michael Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1277 
 
 
 
  `facter -p` should report core Puppet facts like puppetversion  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2011) Puppet 3.4.3 fails to run on OS X 10.9.2

Title: Message Title

Paul Manno commented on PUP-2011

Re: Puppet 3.4.3 fails to run on OS X 10.9.2

Hmm... odd.
I'm using a Linux puppet master, using rack. My clients are Mac Pro machines running 10.9.5 or 10.10.5. My test lab is VMWare Desktop, where I did clean OS installs, then created a snapshot to revert to. I packaged up puppet, hiera, and facter into a tarball that I download from my rack server, untar, execute a script which then installs all the packages and dumps the plist file and puppet.conf file where they need to be based on inputs to my script and reboots. Once that's done, I sign the cert request and that's it...
So I am repeatedly deploying the client after a clean OS install from USB stick images... so it's not like I'm having to do any configuration on top to make it all work.

Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PUP-5522) Puppet node does not keep attributes consistent with parameters

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5522 
 
 
 
  Puppet node does not keep attributes consistent with parameters  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/11/19 1:19 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
The Puppet::Node class has two attributes, environment_name and environment. It also has a parameter named 'environment'. These are not kept in sync which causes problems for the catalog_preview application. See PRE-81. I think it's better to fix this in the puppet code than adding a workaround in the catalog preview program. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PDB-163) Array/list support for "IN" operator for matching against a list of possible items

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-163 
 
 
 
  Array/list support for "IN" operator for matching against a list of possible items  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Sprint:
 
 PuppetDB 2015-12-16 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-163) Array/list support for "IN" operator for matching against a list of possible items

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-163 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Array/list support for "IN" operator for matching against a list of possible items  
 
 
 
 
 
 
 
 
 
 
This is going to be important for HA to reduce the number of requests a PDB makes during initial sync. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5522) Puppet node does not keep attributes consistent with parameters

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5522 
 
 
 
  Puppet node does not keep attributes consistent with parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Fix Version/s:
 
 PUP 3.8.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5522) Puppet node does not keep attributes consistent with parameters

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5522 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet node does not keep attributes consistent with parameters  
 
 
 
 
 
 
 
 
 
 
The only possible validation for this fix is the use case described in PRE-81. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5127) unterminated c-style comment causes hang

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

 
 
 
 
 
 
 
 Puppet /  PUP-5127 
 
 
 
  unterminated c-style comment causes hang  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (HI-471) Allow backends to perform Qualified Key Lookup

2015-11-19 Thread Sean Griffin (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-471 
 
 
 
  Allow backends to perform Qualified Key Lookup  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Assignee:
 
 Sean Griffin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5522) Puppet node does not keep attributes consistent with parameters

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

 
 
 
 
 
 
 
 Puppet /  PUP-5522 
 
 
 
  Puppet node does not keep attributes consistent with parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5127) unterminated c-style comment causes hang

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5127 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unterminated c-style comment causes hang  
 
 
 
 
 
 
 
 
 
 
I can reproduce this with the future parser but not with the regular 3.x parser. There, I instead get "Syntax error at '/' at ..." Henrik Lindberg do you still have the code that you used when you reproduced this on 3.x without future? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5522) Puppet node does not keep attributes consistent with parameters

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5522 
 
 
 
  Puppet node does not keep attributes consistent with parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Fix Version/s:
 
 PUP 4.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5518) Puppet lookup: Decide whether you can mix styles of defaults or not

2015-11-19 Thread Nicholas Fagerlund (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5518 
 
 
 
  Puppet lookup: Decide whether you can mix styles of defaults or not  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.3.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/11/19 3:00 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 
There are three ways to set a default value for a lookup. The tool appears to disagree with itself about whether it's okay to mix these or not. Instead, it should behave consistently. 
 

lookup()'s call signatures will disallow specifying both a fourth argument (default value) and a lambda. It's an error.
 

But setting default_value in the options hash and passing a lambda is fine. (Lambda wins, which seems arbitrary.) Either this should also be an error, or the first case shouldn't.
 

You can also specify default_values_hash along with one or both of the other two styles of default value. I could see this being desired behavior, but am not 100% sure. Are there tests to ensure it continues to work?

Jira (PUP-2011) Puppet 3.4.3 fails to run on OS X 10.9.2

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Denver McAnally commented on  PUP-2011 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet 3.4.3 fails to run on OS X 10.9.2  
 
 
 
 
 
 
 
 
 
 
Paul Manno, 
I actually had tried that and I saw no change in behavior. Have you overcome this issue? What version of ruby/rubylibs do yo have installed? 
Thanks, Denver 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2011) Puppet 3.4.3 fails to run on OS X 10.9.2

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Manno commented on  PUP-2011 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet 3.4.3 fails to run on OS X 10.9.2  
 
 
 
 
 
 
 
 
 
 
Denver, 
hiera 1.3.4 facter 2.4.4 puppet 3.8.3 ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin14] Mac OS 10.9 and 10.10 working. 
Paul 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5059) Add support for --node in 'puppet lookup' command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5059 
 
 
 
  Add support for --node in 'puppet lookup' command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Fix Version/s:
 
 PUP 4.3.2 
 
 
 

Fix Version/s:
 
 PUP 4.3.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2011) Puppet 3.4.3 fails to run on OS X 10.9.2

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Denver McAnally commented on  PUP-2011 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet 3.4.3 fails to run on OS X 10.9.2  
 
 
 
 
 
 
 
 
 
 
Turns out its a facter fact error on my end... 
 Facter::Util::Macosx.os_overview.each do |fact, value| Facter.add("sp_# {fact} 
") do confine :kernel => :darwin setcode do value end end end 
was causing facter and subsequently puppet to die. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5059) Add support for --node in 'puppet lookup' command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow commented on  PUP-5059 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for --node in 'puppet lookup' command  
 
 
 
 
 
 
 
 
 
 
This ticket went back and forth. It was originally in 4.3.0 but did not pass testing in time. So it was re-targeted at a later release, although the code was still in, just unused, as part of the experimental data in modules feature. Thomas and Sean looked at this again, and it turns out that it was behaving as expected so it was resolved. As such, since the code was already in since 4.3.0, I am marking this as 4.3.1. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5059) Add support for --node in 'puppet lookup' command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5059 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for --node in 'puppet lookup' command  
 
 
 
 
 
 
 
 
 
 
Think it needs to be in 4.3.0 since there is no new code for it in 4.3.1 and the release ticket/commit sync-up will report it as a ticket without a corresponding commit. It was also part of a new feature, and was not release noted separately (I think). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2011) Puppet 3.4.3 fails to run on OS X 10.9.2

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Denver McAnally commented on  PUP-2011 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet 3.4.3 fails to run on OS X 10.9.2  
 
 
 
 
 
 
 
 
 
 
if I comment out the fact at line 38 in /Library/Ruby/Site/facter/macosx.rb, puppet begins to run clean as the root user. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-2183) (maint) Add pretty-print option to reports-resources endpoint

2015-11-19 Thread Kenneth Barber (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2183 
 
 
 
  (maint) Add pretty-print option to reports-resources endpoint  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Flagged:
 
 Impediment 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2011) Puppet 3.4.3 fails to run on OS X 10.9.2

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Manno commented on  PUP-2011 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet 3.4.3 fails to run on OS X 10.9.2  
 
 
 
 
 
 
 
 
 
 
Denver, 
Here's my macosx.rb file for a working deployment. I didn't have to change that file at all: 
 

Fact: macosx #
 

Purpose:
 

Returns a number of Mac specific facts, from system profiler and
 

sw_vers. #
 

Resolution:
 

Uses util/macosx.rb to do the fact reconnaissance, then outputs them
 

preceded by `sp_` #
 

Caveats: #
 
 
# 
 

macosx.rb
 

Additional Facts coming from Mac OS X system_profiler command #
 

Copyright (C) 2007 Jeff McCune
 

Author: Jeff McCune  #
 

Jeff McCune
 

There's a lot more information coming out of system_profiler -xml
 

We could add quite a bit more, but I didn't want to overload facter
 

at this point in time.
 

In particular, Installed Software might be an interesting addition.
 
 
if Facter.value(:kernel) == "Darwin" require 'facter/util/macosx' 
 Facter::Util::Macosx.hardware_overview.each do |fact, value| Facter.add("sp_#

Jira (PUP-5059) Add support for --node in 'puppet lookup' command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5059 
 
 
 
  Add support for --node in 'puppet lookup' command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Fix Version/s:
 
 PUP 4.3.1 
 
 
 

Fix Version/s:
 
 PUP 4.3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5059) Add support for --node in 'puppet lookup' command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow commented on  PUP-5059 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for --node in 'puppet lookup' command  
 
 
 
 
 
 
 
 
 
 
OK. I changed it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5523) Incorrect user and group set on /etc/puppetlabs

2015-11-19 Thread Taylor Owen (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Taylor Owen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5523 
 
 
 
  Incorrect user and group set on /etc/puppetlabs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.3.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 AIO 
 
 
 

Created:
 

 2015/11/19 10:14 PM 
 
 
 

Environment:
 
 
Ubuntu 14.04 running on Virtualbox 
 
 
 

Labels:
 

 AIO 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Taylor Owen 
 
 
 
 
 
 
 
 
 
 
When running the following: 
wget https://apt.puppetlabs.com/puppetlabs-release-pc1-trusty.deb sudo dpkg -i puppetlabs-release-pc1-trusty.deb sudo apt-get update sudo apt-get install -y puppetserver sudo service puppetserver start 
The puppet master fails to start since SSL

Jira (PUP-5127) unterminated c-style comment causes hang

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5127 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unterminated c-style comment causes hang  
 
 
 
 
 
 
 
 
 
 
I used a manifest consisting of only /* when I tested. if it worked or not on 3.x without future parser is something we can ignore. It is enough to fix this on 4.x. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5519) puppet lookup --node should fail if is not recognized by the Node Classifier

2015-11-19 Thread Sean Griffin (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5519 
 
 
 
  puppet lookup --node   should fail if  is not recognized by the Node Classifier  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/11/19 7:38 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Sean Griffin 
 
 
 
 
 
 
 
 
 
 
The new puppet lookup command takes a --node option to specify the node for which the look up will occur. This causes a check with the node classifier to get the node's environment name, and looks up the key in the context of that environment. 
If a bogus node name is supplied, look up will issue a warning indicating a missing hostname and/or domain. It will then proceed to look up the symbol in the context of the default environment (production), and exit with an exit code of 0. 
 
 
 
 
 
 
[root@ky0y7to9bef0ky8 results]# puppet lookup --node bogus data_module::key_in_module 
 
 
 
 
Warning: Host is missing hostname and/or domain: bogus 
 
 
 
 
Notice: Scope(Class[Data_module]): Starting data_module init.pp {

Jira (PUP-2011) Puppet 3.4.3 fails to run on OS X 10.9.2

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Manno commented on  PUP-2011 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet 3.4.3 fails to run on OS X 10.9.2  
 
 
 
 
 
 
 
 
 
 
Denver, In case you haven't found the solution yet, you have to add the following dict and key/value pair to your EnvironmentVariables section of your com.puppetlabs.puppet.plist file: 
 LANG en_US.UTF-8  
Full plist file: EnvironmentVariables  LANG en_US.UTF-8  Label com.puppetlabs.puppet KeepAlive  ProgramArguments  /usr/bin/puppet agent --verbose --no-daemonize --logdest console  RunAtLoad  ServiceDescription Puppet agent service ServiceIPC  StandardErrorPath /var/log/puppet/puppet.err StandardOutPath /var/log/puppet/puppet.out   
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-2183) (maint) Add pretty-print option to reports-resources endpoint

2015-11-19 Thread Kenneth Barber (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2183 
 
 
 
  (maint) Add pretty-print option to reports-resources endpoint  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Flagged:
 
 Impediment 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5059) Add support for --node in 'puppet lookup' command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5059 
 
 
 
  Add support for --node in 'puppet lookup' command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes:
 
 Known Issue Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5059) Add support for --node in 'puppet lookup' command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5059 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for --node in 'puppet lookup' command  
 
 
 
 
 
 
 
 
 
 
Garrett Guillotte Unsure how to handle this ticket's release note(s) since it was reported as faulty (a known issue) only to be found that it was a read herring, and that it did in fact work. In summary, the feature is released in 4.3.0 and works. There is no need to release note it separately in 4.3.1 unless it was communicated as a "known issue" in 4.3.0, in which case it should be communicated that it was a red herring. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-2188) Create CLI repo/CI pipeline/build infra etc

2015-11-19 Thread Kenneth Barber (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber commented on  PDB-2188 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create CLI repo/CI pipeline/build infra etc  
 
 
 
 
 
 
 
 
 
 
Just so I don't forget ... we'll also need for the new puppetdb-cli repo: 
 

Jira needs to find this repo now we've created it, thats an ops ticket. We have a few other repos we don't have in Jira.
 

Our ticket creation bot will need to know about this repo, might want to double check it covers our other repos also.
 

License file, apache etc. the plan I guess would be to open-source this eventually so make sure thats in place etc.
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5059) Add support for --node in 'puppet lookup' command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5059 
 
 
 
  Add support for --node in 'puppet lookup' command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Affects Version/s:
 
 PUP 4.3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2011) Puppet 3.4.3 fails to run on OS X 10.9.2

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Denver McAnally commented on  PUP-2011 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet 3.4.3 fails to run on OS X 10.9.2  
 
 
 
 
 
 
 
 
 
 
I am actually having the same exact issue with Facter (2.4.4) and Puppet (3.8.4). 
As normal user... 
$ sudo puppet agent -t Password: Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for hostname.local Info: Applying configuration version '1447943664' Notice: Finished catalog run in 14.41 seconds 
As Root... 
 

puppet agent -t Error: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: undefined method `each' for nil:NilClass Error: Could not prepare for execution: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: undefined method `each' for nil:NilClass undefined method `each' for nil:NilClass
 

facter undefined method `each' for nil:NilClass
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (FACT-1278) Undefined method "match" when using "facter -p pe_build" in 2015.2.3

2015-11-19 Thread Peter Huene (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  FACT-1278 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Undefined method "match" when using "facter -p pe_build" in 2015.2.3  
 
 
 
 
 
 
 
 
 
 
Looks like a dup to me. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-5059) Add support for --node in 'puppet lookup' command

2015-11-19 Thread Garrett Guillotte (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Garrett Guillotte commented on  PUP-5059 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for --node in 'puppet lookup' command  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg I don't see anything known issues in the 4.3 notes, so if there's nothing to note, let's keep the "Not Needed" release notes flag. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-2206) indexes on transaction_uuid and hash are not used in querying

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2206 
 
 
 
  indexes on transaction_uuid and hash are not used in querying  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/11/19 9:39 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
We should either flip them back to an indexed varchar 40, or munge hashes to bytea on the RHS of the equality comparison. We should probably just pick whatever approach is fastest, since this directly influences speed of syncing and the storage benefits of bytea are probably insignificant compared to the kind of json storage we've been adopting. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PDB-2207) benchmark tool needs to do command broadcast

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2207 
 
 
 
  benchmark tool needs to do command broadcast  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/11/19 9:40 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
this will be important for load testing HA setups 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PDB-2206) indexes on transaction_uuid and hash are not used in querying

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2206 
 
 
 
  indexes on transaction_uuid and hash are not used in querying  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Sprint:
 
 PuppetDB 2015-12-02 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-2206) indexes on transaction_uuid and hash are not used in querying

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2206 
 
 
 
  indexes on transaction_uuid and hash are not used in querying  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-2206) indexes on transaction_uuid and hash are not used in querying

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2206 
 
 
 
  indexes on transaction_uuid and hash are not used in querying  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Fix Version/s:
 
 PDB 3.2.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-2206) indexes on transaction_uuid and hash are not used in querying