date:20140210

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (630): Add LXC detection to virtual and is_virtual fact - jeffmccune 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Facter /  FACT-320



  PR (630): Add LXC detection to virtual and is_virtual fact - jeffmccune 







 h2. Add LXC detection to virtual and is_virtual fact   * Author: Jeff McCune   * Company: Puppet Labs  * Github ID: [jeffmccune|https://github.com/jeffmccune]  * [Pull Request 630 Discussion|https://github.com/puppetlabs/facter/pull/630]  * [Pull Request 630 File Diff|https://github.com/puppetlabs/facter/pull/630/files]  h2. Pull Requ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1626) dpkg provider works incorrect on non english locales

2014-02-10 Thread Roman Shipovskij (JIRA)

Title: Message Title










 

 Roman Shipovskij created an issue











 






 Puppet /  PUP-1626



  dpkg provider works incorrect on non english locales 










Issue Type:

  Bug




Affects Versions:


 3.4.2




Assignee:


 Unassigned




Created:


 10/Feb/14 1:06 AM




Environment:


Ubuntu 12.04




Priority:

  Normal




Reporter:

 Roman Shipovskij










regular _expression_: self::DPKG_PACKAGE_NOT_FOUND_REGEX = /no package.*match/i doesn't work on non english locales, for example on uk_UA locale dpkg-query return:


/usr/bin/dpkg-query -W --showformat '$ {Status}
 $ {Package}
 $ {Version}
 :DESC: $ {Description}
\n:DESC:\n' somepackage Шаблону somepackage не відповідає жоден пакунок.

Jira (PUP-1626) dpkg provider works incorrect on non english locales

2014-02-10 Thread Roman Shipovskij (JIRA)

Title: Message Title










 

 Roman Shipovskij updated an issue











 






 Puppet /  PUP-1626



  dpkg provider works incorrect on non english locales 










Change By:

 Roman Shipovskij









 regular _expression_: bq. self::DPKG_PACKAGE_NOT_FOUND_REGEX = /no package.*match/idoesn't work on non english locales, for example on uk_UA locale dpkg-query return: bq. # /usr/bin/dpkg-query -W --showformat '${Status} ${Package} ${Version} :DESC: ${Description}\n:DESC:\n' somepackage bq. Шаблону somepackage не відповідає жоден пакунок. 












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1627) puppet does not lock catalog when generating SSL key

2014-02-10 Thread Roman Shipovskij (JIRA)

Title: Message Title










 

 Roman Shipovskij created an issue











 






 Puppet /  PUP-1627



  puppet does not lock catalog when generating SSL key 










Issue Type:

  Bug




Affects Versions:


 3.4.2




Assignee:


 Unassigned




Created:


 10/Feb/14 2:31 AM




Environment:


Ubuntu 12.04




Priority:

  Normal




Reporter:

 Roman Shipovskij










key generating takes some time, as result we can initiate it twice simultaneously by executing puppet agent -t when daemon generates key, and if autosigning enabled on master this issue can cause certificate mismatch error












   

 Add Comment

Jira (MCO-170) Update stomp gem rpm

Title: Message Title










 

 Pieter Loubser commented on an issue











 






  Re: Update stomp gem rpm 










Have you tried 1.3.2? We are aware that 1.3.0 and 1.3.1 do not work.












   

 Add Comment











 













 MCollective /  MCO-170



  Update stomp gem rpm 







 The current rubygem rpm is version 1.2.2-1. Some MCollective features require version 1.2.10 and above.   https://groups.google.com/d/msg/mcollective-users/uDGP87TSw2I/PC1H6TTjQUkJ















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1030) FreeBSD: Puppet triggers loading of ZFS module

Title: Message Title










 

 Remko Catersels commented on an issue











 






  Re: FreeBSD: Puppet triggers loading of ZFS module 










Issue also happens with Puppet 3.4.2.












   

 Add Comment











 













 Puppet /  PUP-1030



  FreeBSD: Puppet triggers loading of ZFS module 







 When puppet starts the puppet ZFS provider issues the zfs command. On FreeBSD this automatically loads the ZFS kernel module. Even when ZFS is not used on that host. The provider should first check if ZFS is enabled or not. If it's not enabled it shouldn't execute any zpool or zfs commands as those will trigger the automatic load of the kernel module.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1030) FreeBSD: Puppet triggers loading of ZFS module

Title: Message Title










 

 Remko Catersels updated an issue











 






 Puppet /  PUP-1030



  FreeBSD: Puppet triggers loading of ZFS module 










Change By:

 Remko Catersels




Affects Version/s:

 3.4.2












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1030) FreeBSD: Puppet triggers loading of ZFS module

Title: Message Title










 

 Remko Catersels commented on an issue











 






  Re: FreeBSD: Puppet triggers loading of ZFS module 










root@w4:~ # kldstat Id Refs Address Size Name 1 1 0x8020 15b9440 kernel root@w4:~ # puppet agent -v --test Info: Retrieving plugin Info: Loading facts in /var/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/puppet/lib/facter/concat_basedir.rb Info: Loading facts in /var/puppet/lib/facter/root_home.rb Info: Loading facts in /var/puppet/lib/facter/pkgng.rb Info: Loading facts in /var/puppet/lib/facter/role.rb Info: Loading facts in /var/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/puppet/lib/facter/mountpoints.rb Info: Loading facts in /var/puppet/lib/facter/pe_version.rb /usr/local/lib/ruby/site_ruby/1.9/puppet/provider/package/freebsd.rb:18: warning: class variable access from toplevel /usr/local/lib/ruby/site_ruby/1.9/puppet/provider/package/freebsd.rb:19: warning: class variable access from toplevel Info: Caching catalog for w4.example.com Info: Applying configuration version '1391422624' Notice: Finished catalog run in 15.41 seconds root@w4:~ # kldstat Id Refs Address Size Name 1 9 0x8020 15b9440 kernel 4 1 0x81812000 1583db zfs.ko 5 1 0x8196b000 56f7 opensolaris.ko












   

 Add Comment











 













 Puppet /  PUP-1030



  FreeBSD: Puppet triggers loading of ZFS module 







 When puppet starts the puppet ZFS provider issues the zfs command. On FreeBSD this automatically loads the ZFS kernel module. Even when ZFS is not used on that host. The provider should first check if ZFS is enabled or not. If it's not enabled it shouldn't execute any zpool or zfs commands as those will trigger the automatic load of the kernel module.

Jira (PUP-1030) FreeBSD: Puppet triggers loading of ZFS module

Title: Message Title










 

 Remko Catersels updated an issue











 






 Puppet /  PUP-1030



  FreeBSD: Puppet triggers loading of ZFS module 










Change By:

 Remko Catersels




Assignee:

 Kylo Ginsberg












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-170) Update stomp gem rpm

2014-02-10 Thread Daniel Eichten (JIRA)

Title: Message Title










 

 Daniel Eichten commented on an issue











 






  Re: Update stomp gem rpm 










Tried 1.3.2 and 1.3.0 before reverting back to 1.2.10 which then was working for me.












   

 Add Comment











 













 MCollective /  MCO-170



  Update stomp gem rpm 







 The current rubygem rpm is version 1.2.2-1. Some MCollective features require version 1.2.10 and above.   https://groups.google.com/d/msg/mcollective-users/uDGP87TSw2I/PC1H6TTjQUkJ















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-178) Plugin Packager documentation

Title: Message Title










 

 Pieter Loubser created an issue











 






 MCollective /  MCO-178



  Plugin Packager documentation 










Issue Type:

  Improvement




Assignee:

 Pieter Loubser




Components:


 DOCS




Created:


 10/Feb/14 3:49 AM




Priority:

  Normal




Reporter:

 Pieter Loubser










http://docs.puppetlabs.com/mcollective/deploy/plugins.html
The Packaging Custom Plugins section mentions that "we hope to publish a guide to the packaging tool soon. "
We need to write this guide.












   

 Add Comment











 










 This message was sent by At

Jira (MCO-179) Remove reference to package iteration in #package_information

Title: Message Title










 

 Pieter Loubser created an issue











 






 MCollective /  MCO-179



  Remove reference to package iteration in #package_information 










Issue Type:

  Bug




Affects Versions:


 2.4.0




Assignee:

 Pieter Loubser




Created:


 10/Feb/14 4:10 AM




Fix Versions:


 2.4.1




Priority:

  Normal




Reporter:

 Pieter Loubser










When deprecating and renaming the iteration flag one reference to it was left in OspackagePackager#package_information.












   

 Add Comment

Jira (MCO-179) Remove reference to package iteration in #package_information

Title: Message Title










 

 Pieter Loubser updated an issue











 






 MCollective /  MCO-179



  Remove reference to package iteration in #package_information 










Change By:

 Pieter Loubser




Sprint:

 2014_02_12-2014_02_26












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-180) Release MCollective 2.4.1

Title: Message Title










 

 Richard Clamp created an issue











 






 MCollective /  MCO-180



  Release MCollective 2.4.1 










Issue Type:

  Task




Assignee:

 Pieter Loubser




Created:


 10/Feb/14 4:12 AM




Fix Versions:


 2.4.1




Priority:

  Normal




Reporter:

 Richard Clamp












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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.
T

Jira (MCO-179) Remove reference to package iteration in #package_information

Title: Message Title










 

 Pieter Loubser updated an issue











 






 MCollective /  MCO-179



  Remove reference to package iteration in #package_information 










Change By:

 Pieter Loubser




Sprint:

 2014_02_12 2014_01_29 - 2014_02_26 2014_02_12












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-180) Release MCollective 2.4.1

Title: Message Title










 

 Richard Clamp updated an issue











 






 MCollective /  MCO-180



  Release MCollective 2.4.1 










Change By:

 Richard Clamp




Sprint:

 2014_01_29-2014_02_12












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-170) Update stomp gem rpm

Title: Message Title










 

 Pieter Loubser commented on an issue











 






  Re: Update stomp gem rpm 










Thanks for the feedback. Would it be possible to give us a bit more information regarding how it doesn't work with the 1.3.2 gem?












   

 Add Comment











 













 MCollective /  MCO-170



  Update stomp gem rpm 







 The current rubygem rpm is version 1.2.2-1. Some MCollective features require version 1.2.10 and above.   https://groups.google.com/d/msg/mcollective-users/uDGP87TSw2I/PC1H6TTjQUkJ















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1583) Puppet agent doesn't start on server power on

2014-02-10 Thread Vadim Nevorotin (JIRA)

Title: Message Title










 

 Vadim Nevorotin updated an issue











 






 Puppet /  PUP-1583



  Puppet agent doesn't start on server power on 










Change By:

 Vadim Nevorotin









 Puppet packages from official Puppet repo for Debian has a bug: if there is non-ASCII comments (!) in puppet.conf, such as{noformat}# Что-то там{noformat}then puppet agent willn't start on server power on with this error:{quote}Could not parse /etc/puppet/puppet.conf: invalid byte sequence in US-ASCII{quote}Manually service launched perfectly (with service puppet start), problem is here only on power on.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-181) Add --[no-]daemonize flag to mcollectived

Title: Message Title










 

 Richard Clamp created an issue











 






 MCollective /  MCO-181



  Add --[no-]daemonize flag to mcollectived 










Issue Type:

  Improvement




Assignee:

 Pieter Loubser




Created:


 10/Feb/14 4:24 AM




Priority:

  Normal




Reporter:

 Richard Clamp










As seen in MCO-167 there's an improvement to be made in allowing the init script/upstart/runit layer tell mcollectived whether it should daemonise or not, overriding the setting in server.cfg.
Suggested fix is to add a --daemonize flag to mcollectived, so at the point of use the init script writer will know if mcollective will daemonize, without having to infer the value of daemonize in server.cfg.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (MCO-170) Update stomp gem rpm

2014-02-10 Thread Daniel Eichten (JIRA)

Title: Message Title










 

 Daniel Eichten commented on an issue











 






  Re: Update stomp gem rpm 










Unfortunately I don't have the logs anymore. But I remember that the heartbeat handshake wasn't exchanged correctly which resulted in the client neither sending not receiving a heartbeat. But this might also be caused by my specific setup. I also had to fight with a level-7 firewall in between.












   

 Add Comment











 













 MCollective /  MCO-170



  Update stomp gem rpm 







 The current rubygem rpm is version 1.2.2-1. Some MCollective features require version 1.2.10 and above.   https://groups.google.com/d/msg/mcollective-users/uDGP87TSw2I/PC1H6TTjQUkJ















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1134) Service Provider 'init' does not detect correct location for script directory on AIX - Patch included

2014-02-10 Thread Klaus Wagner (JIRA)

Title: Message Title










 

 Klaus Wagner assigned an issue to Unassigned











 







Since migration to jira the assignment has been empty it seems.









 Puppet /  PUP-1134



  Service Provider 'init' does not detect correct location for script directory on AIX - Patch included 












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-170) Update stomp gem rpm

Title: Message Title










 

 Pieter Loubser updated an issue











 






 MCollective /  MCO-170



  Update stomp gem rpm 










Change By:

 Pieter Loubser




Priority:

 Major Critical












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1628) Add mount provider for AIX

2014-02-10 Thread redmine.exporter (JIRA)

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1628



  Add mount provider for AIX 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 10/Feb/14 6:09 AM




Labels:


 redmine customer




Priority:

  Normal




Reporter:

 redmine.exporter










Puppet does not provides a correct provider for the mount type on AIX.
A new provider must be created.
Mountpoints in AIX are managed by the commands: crfs, lsfs, rmfs, chfs (http://publib.boulder.ibm.com/infocenter/aix/v6r1/index.jsp?topic=/com.ibm.aix.cmds/doc/aixcmds1/crfs.htm). For nfs mountpoints the commands mknfsmnt, chnfsmnt, rmnfsmnt and chnfsmnt are provided, but they can partially be managed with former commands.
The commands update the file /etc/filesystems that has following syntax:
 /usr: dev = /dev/hd2 vfs = jfs2 log = /dev/hd8 mount = automatic check = false type = bootfs vol = /usr free = false
 /var: dev = /dev/hd9var vfs = jfs2 log = /dev/hd8 mount = automatic check = false type = bootfs vol = /var free = false
*IMPORTANT*: crfs (create) and rmfs (remove), if it is a local filesystem, will create and format (using jfs/jfs2) the needed Logical Volume, or directly remove the Logical Volume losing data. 
Two approaches: 1. Use command line tools and operate as expected by AIX commands: Operate on the LV. In that case type should be extended with new parameters (Volume Group, LV name, size...) 2. Modify directly /etc/filesystems files, and manage the Logical Volumes using a LVM type (as in

Jira (MCO-170) Update stomp gem rpm

Title: Message Title










 

 Pieter Loubser updated an issue











 






 MCollective /  MCO-170



  Update stomp gem rpm 










Change By:

 Pieter Loubser




Priority:

 Critical Major












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1628) Add mount provider for AIX

2014-02-10 Thread Mike Bryant (JIRA)

Title: Message Title










 

 Mike Bryant updated an issue











 






 Puppet /  PUP-1628



  Add mount provider for AIX 










Change By:

 Mike Bryant




Component/s:

 Types and Providers












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1629) WIndows 2008r2 fails to load() a file it previously store()d

2014-02-10 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall created an issue











 






 Puppet /  PUP-1629



  WIndows 2008r2 fails to load() a file it previously store()d 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 10/Feb/14 6:47 AM




Priority:

  Normal




Reporter:

 Kurt Wall










While running Puppet-Specs-Windows-master on Windows 2008r2, rspec ./spec/unit/util/storage_spec.rb fails thus:



  1) Puppet::Util::Storage when storing to the state file should load() the same information that it store()s
 Failure/Error: Puppet::Util::Storage.load
 RuntimeError:
   Got 2 failure(s) while initializing: File[C:/Windows/Temp/rspecrun20130927-3068-1bon8ji/tmp_settings20130927-3068-2mjwk0/etc/ssl/private]: change from absent to directory failed: Could not set 'directory' on ensure: can't convert Bignum into String; File[C:/Windows/Temp/rspecrun20130927-3068-1bon8ji/tmp_settings20130927-3068-2mjwk0/etc/ssl/private_keys]: change from absent to directory failed: Could not set 'directory' on ensure: can't convert Bignum into String
 # ./lib/puppet/settings.rb:924:in `block in use'
 # ./lib/puppet/resource/catalog.rb:176:in `apply'
 # ./lib/puppet/settings.rb:914:in `use'
 # ./lib/puppet/util/storage.rb:45:in `load'
 # ./spec/unit/util/storage_spec.rb:205:in `block (3 levels) in '



https://jenkins.puppetlabs.com/job/Puppet-Specs-Windows-master/nodes=win2008r2/1597/console

Jira (PUP-1630) Windows 2008r2 fails search/by_keyword and search/by_module_name

2014-02-10 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall created an issue











 






 Puppet /  PUP-1630



  Windows 2008r2 fails search/by_keyword and search/by_module_name 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 10/Feb/14 6:58 AM




Priority:

  Normal




Reporter:

 Kurt Wall










Two module tests failed on Windows 2008r2 in Puppet-Acceptance-Future-Parser-master-vcloud-and-github:



  Test Case tests/modules/search/by_keyword.rb reported: #"/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB}" PATH="/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH}" puppet module search github  
Last 10 lines of output were:
	Notice: Searching https://forge.puppetlabs.com ...>
  Test Case tests/modules/search/by_module_name.rb reported: #"/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB}" PATH="/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH}" puppet module search geordi  
Last 10 lines of output were:
	Notice: Searching https://forge.puppetlabs.com ...>



https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Future-Parser-master-vcloud-and-github/label=acc-coord,platform=win2008r2/65/console












   

 Add Comment

Jira (PUP-1135) Undeprecate 'puppet kick' run mode

2014-02-10 Thread Nikita Stupin (JIRA)

Title: Message Title










 

 Nikita Stupin commented on an issue











 






  Re: Undeprecate 'puppet kick' run mode 










mcollective this is extra software and extra daemon. Also mcollective on master node is require java, activemq/rabbitmq daemons. I would like send easy kick to puppet agent, nothing more. Why i must use all of the above?












   

 Add Comment











 













 Puppet /  PUP-1135



  Undeprecate 'puppet kick' run mode 







 bq. Please not deprecate puppet kick. We use puppet in some our projects, and not use mcollective, also don’t plan use mcollective. Why? Mcollective is require mq (activemq/rabbitmq & etc) and provides unneeded functionality. We can use one function from mcollective – puppet agent runonce, but why do we need to install extra software, and extra daemon on ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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

Jira (PDB-434) PR (841): Fixed an anonymizer test hidden behind a lazy seq - senior

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-434



  PR (841): Fixed an anonymizer test hidden behind a lazy seq - senior 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 10/Feb/14 7:29 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Fixed an anonymizer test hidden behind a lazy seq


Author: Ryan Senior 


Company:


Github ID: senior


Pull Request 841 Discussion


Pull Request 841 File Diff


Pull Request Description

Since coll? doesn't force the seq, essentially the function under test wasn't being ran. The test had a vector where a map was expected which fails when the seq is forced.

(webhooks-id: aff84e917324d42e5c1911078a07d0a3)

Jira (PUP-1631) Wrapped exceptions of functions are still hiding that they were raised in a function

2014-02-10 Thread redmine.exporter (JIRA)

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1631



  Wrapped exceptions of functions are still hiding that they were raised in a function 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 10/Feb/14 7:41 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










As noted in #22729 the source of an exception that is thrown in a function, is still completely hidden to the user in the output:



puppet --version 3.3.0


puppet apply -e "notice reject(['a','b'],'b')" Error: reject(): wrong argument type (String; must be a parameterized block. at line 1 on node foo Wrapped exception: reject(): wrong argument type (String; must be a parameterized block. Error: reject(): wrong argument type (String; must be a parameterized block. at line 1 on node foo 


There is no way that I can see that this exception was actually raised in the function itself and I need to use `--trace` to see the actual source of the problem. Also the actual Error and the wrapped exception output look identical to me and it makes no sense to have this output doubled.
As a user I'd like to be able to:
1. See the message of the raised exception 2. See the actual source of the raised exception (in the case above t

Jira (PDB-434) PR (841): Fixed an anonymizer test hidden behind a lazy seq - senior

2014-02-10 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-434



  PR (841): Fixed an anonymizer test hidden behind a lazy seq - senior 










Change By:

 Ryan Senior




Sprint:

 20140205 to 20140212












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PDB-401) PR (826): Port to trapperkeeper 0.3.0 - cprice404

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (826): Port to trapperkeeper 0.3.0 - cprice404 










pljenkinsro commented:
:red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/214/












   

 Add Comment











 













 PuppetDB /  PDB-401



  PR (826): Port to trapperkeeper 0.3.0 - cprice404 







 h2. Port to trapperkeeper 0.3.0   * Author: Chris Price <>  * Company:   * Github ID: [cprice404|https://github.com/cprice404]  * [Pull Request 826 Discussion|https://github.com/puppetlabs/puppetdb/pull/826]  * [Pull Request 826 File Diff|https://github.com/puppetlabs/puppetdb/pull/826/files]  h2. Pull Request Description   This commit updates PuppetD...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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

Jira (MCO-177) mcollective client not working in threaded mode

Title: Message Title










 

 Richard Clamp commented on an issue











 






  Re: mcollective client not working in threaded mode 










I'm not seeing the exception in that log, but I am seeing a lot of discarded messages as one thread is discarding the responses intended for the other threads, as the client code isn't thread-safe in this manner. 
A possible fix for this would involve making the client incorporate the thread-id into it's reply-to address and then being more judicious in which subscriptions it will take messages from in each thread. This would probably require significant rewrite of the client code.
Updating affects-versions as this affects every version of MCollective.












   

 Add Comment











 













 MCollective /  MCO-177



  mcollective client not working in threaded mode 







 Ubuntu: 13.10  ruby: 1.8.7   I`m attached a script that can reproduce the problem.  In my configuration I`m using activemq as midleware.  When client trying to work with multiple collectives in threads, client not able to understand who is who and falls with exception. 















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
Y

Jira (MCO-177) mcollective client not working in threaded mode

Title: Message Title










 

 Richard Clamp updated an issue











 






 MCollective /  MCO-177



  mcollective client not working in threaded mode 










Change By:

 Richard Clamp




Priority:

 Major Normal












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-177) mcollective client not working in threaded mode

Title: Message Title










 

 Richard Clamp updated an issue











 






 MCollective /  MCO-177



  mcollective client not working in threaded mode 










Change By:

 Richard Clamp




Affects Version/s:

 2.4.1




Affects Version/s:

 2.3.3




Affects Version/s:

 2.4.0












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1617) Allow simplified configuration to upgrade older clients.

2014-02-10 Thread Eric Sorenson (JIRA)

Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-1617



  Allow simplified configuration to upgrade older clients. 










Change By:

 Eric Sorenson




Reporter:

 redmine.exporter Jo Rhett












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-297) PR (625): (fact-81) Use Emit.dump rather than to_plist - kylog

Title: Message Title










 

 Adrien Thebo assigned an issue to Unassigned











 






 Facter /  FACT-297



  PR (625): (fact-81) Use Emit.dump rather than to_plist - kylog 










Change By:

 Adrien Thebo




Assignee:

 Adrien Thebo












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-321) Remove deprecated code for 2.0

Title: Message Title










 

 Adrien Thebo created an issue











 






 Facter /  FACT-321



  Remove deprecated code for 2.0 










Issue Type:

  Improvement




Assignee:

 Eric Sorenson




Created:


 10/Feb/14 8:27 AM




Fix Versions:


 2.0




Priority:

  Normal




Reporter:

 Adrien Thebo










There are a bunch of code paths that have been deprecated and are slated for removal in Facter 2.0. We need to go through and ensure that all code paths that have been appropriately marked have been removed.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (FACT-278) Is checklist current

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Is checklist current 










There's been some activity on the doc, but I don't think it needs to affect this release ticket, more forward looking. So no changes to the subtasks. Melissa Stone correct me if I'm wrong.












   

 Add Comment











 













 Facter /  FACT-278



  Is checklist current 







 Do sub-tickets here match steps in https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process? And do those steps need updating for any recent tooling changes?















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-183) PR (163): (packaging) Update buildrequires for rhel7 - haus

Title: Message Title










 

 gepetto-bot created an issue











 






 MCollective /  MCO-183



  PR (163): (packaging) Update buildrequires for rhel7 - haus 










Issue Type:

  Task




Assignee:

 Pieter Loubser




Created:


 10/Feb/14 8:38 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(packaging) Update buildrequires for rhel7


Author: Matthaus Owens 


Company: Puppet Labs


Github ID: haus


Pull Request 163 Discussion


Pull Request 163 File Diff


Pull Request Description

The systemd-units package is not available on rhel7, so this commit moves rhel7 and later into the same BuildRequires as f18 and later.

(webhooks-id: d8b737797cb58837d3420896d06a3b3b)

Jira (MCO-182) PR (162): (packaging) Update buildrequires for rhel7 - haus

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (162): (packaging) Update buildrequires for rhel7 - haus 










Pull request (packaging) Update buildrequires for rhel7 has been closed.












   

 Add Comment











 













 MCollective /  MCO-182



  PR (162): (packaging) Update buildrequires for rhel7 - haus 







 h2. (packaging) Update buildrequires for rhel7   * Author: Matthaus Owens   * Company: Puppet Labs  * Github ID: [haus|https://github.com/haus]  * [Pull Request 162 Discussion|https://github.com/puppetlabs/marionette-collective/pull/162]  * [Pull Request 162 File Diff|https://github.com/puppetlabs/marionette-collective/pull/162/files]...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-183) PR (163): (packaging) Update buildrequires for rhel7 - haus

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (163): (packaging) Update buildrequires for rhel7 - haus 










Pull request (packaging) Update buildrequires for rhel7 has been closed.












   

 Add Comment











 













 MCollective /  MCO-183



  PR (163): (packaging) Update buildrequires for rhel7 - haus 







 h2. (packaging) Update buildrequires for rhel7   * Author: Matthaus Owens   * Company: Puppet Labs  * Github ID: [haus|https://github.com/haus]  * [Pull Request 163 Discussion|https://github.com/puppetlabs/marionette-collective/pull/163]  * [Pull Request 163 File Diff|https://github.com/puppetlabs/marionette-collective/pull/163/files]...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1617) Allow simplified configuration to upgrade older clients.

2014-02-10 Thread Jo Rhett (JIRA)

Title: Message Title










 

 Jo Rhett commented on an issue











 






  Re: Allow simplified configuration to upgrade older clients. 










I noticed yesterday that the environment now includes $::clientversion, which I don't think we had at the time I originally filed this bug. This may be all that is necessary to resolve this issue.












   

 Add Comment











 













 Puppet /  PUP-1617



  Allow simplified configuration to upgrade older clients. 







 we are having problems with incompatibility between older clients and newer configuration syntax.    (in specific, user resource system attribute was added somewhere between 2.6.6 and 2.6.11)   It seems the right thing to do for older clients when they attach is to give them a very short manifest that immediately upgrades them. I'm trying to figure out ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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

Jira (FACT-211) Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-211



  Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp 










Change By:

 Adrien Thebo









 Support for ssh fingerprints (as merged in https://github.com/puppetlabs/facter/pull/162) breaks facter while running on CentOS 6.x on a VM due to a bug with ruby 1.8.7, which is what CentOS 6 provides. {{code}} [acompton@] /usr/lib/ruby/site_ruby/1.8/facter >> facter --debugRelative directory ./facter removed from search path.value for lsbdistid is still nilvalue for ipaddress6_lo is still nilruby-augeas not availablevalue for augeasversion is still nilvalue for sshecdsakey is still nilvalue for sshfp_ecdsa is still nilFound no suitable resolves of 1 for selinux_policyversionvalue for selinux_policyversion is still nilvalue for lsbdistdescription is still nilFound no suitable resolves of 1 for xendomainsvalue for xendomains is still nilvalue for lsbrelease is still nilFound no suitable resolves of 1 for selinux_modevalue for selinux_mode is still nilFound no suitable resolves of 1 for zonenamevalue for zonename is still nilvalue for ipaddress6_eth0 is still nilvalue for cfkey is still nilvalue for lsbdistid is still nilvalue for zpool_version is still nilvalue for macaddress_lo is still nilIllegal instruction[acompton@] /usr/lib/ruby/site_ruby/1.8/facter >> strace -f -- facter 2>&1 | grep -v SIG_ | tailstat("/usr/lib64/site_ruby/1.8/x86_64-linux/digest.rb", 0x7fff6c9843d0) = -1 ENOENT (No such file or directory)stat("/usr/lib64/site_ruby/1.8/x86_64-linux/digest.so", 0x7fff6c9843d0) = -1 ENOENT (No such file or directory)stat("/usr/lib64/site_ruby/digest.rb", 0x7fff6c9843d0) = -1 ENOENT (No such file or directory)stat("/usr/lib64/site_ruby/digest.so", 0x7fff6c9843d0) = -1 ENOENT (No such file or directory)stat("/usr/lib/ruby/1.8/digest.rb", {st_mode=S_IFREG|0644, st_size=1145, ...}) = 0open("/usr/lib/ruby/1.8/digest.rb", O_RDONLY) = 3fstat(3, {st_mode=S_IFREG|0644, st_size=1145, ...}) = 0close(3)= 0--- SIGILL (Illegal instruction) @ 0 (0) ---+++ killed by SIGILL +++(...comment out sshfp support...)[acompton@] /usr/lib/ruby/site_ruby/1.8/facter >> cat ssh.rb# Fact: ssh## Purpose:## Resolution:## Caveats:### ssh.rb## Facts related to SSH##{"SSHDSAKey" => { :file => "ssh_host_dsa_key.pub", :sshfprrtype => 2 } , "SSHRSAKey" => { :file => "ssh_host_rsa_key.pub", :sshfprrtype => 1 }, "SSHECDSAKey" => { :file => "ssh_host_ecdsa_key.pub", :sshfprrtype => 3 } }.each do |name,key|  Facter.add(name) dosetcode do  value = nil  [ "/etc/ssh","/usr/local/etc/ssh","/etc","/usr/local/etc","/etc/opt/ssh",  ].each do |dir|filepath = File.join(dir,key[:file])if FileTest.file?(filepath)  beginvalue = File.read(filepath).chomp.split(/\s+/)[1]break  rescuevalue = nil  endend  end  valueend  end  # Facter.add('SSHFP_' + name[3..-4]) do  #   setcode do

Jira (MCO-182) PR (162): (packaging) Update buildrequires for rhel7 - haus

Title: Message Title










 

 gepetto-bot created an issue











 






 MCollective /  MCO-182



  PR (162): (packaging) Update buildrequires for rhel7 - haus 










Issue Type:

  Task




Assignee:

 Pieter Loubser




Created:


 10/Feb/14 8:38 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(packaging) Update buildrequires for rhel7


Author: Matthaus Owens 


Company: Puppet Labs


Github ID: haus


Pull Request 162 Discussion


Pull Request 162 File Diff


Pull Request Description

The systemd-units package is not available on rhel7, so this commit moves rhel7 and later into the same BuildRequires as f18 and later.

(webhooks-id: 551975106a1a854f9602da871c03db97)

Jira (FACT-211) Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-211



  Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp 










Change By:

 Adrien Thebo









 Support for ssh fingerprints (as merged in https://github.com/puppetlabs/facter/pull/162) breaks facter while running on CentOS 6.x on a VM due to a bug with ruby 1.8.7, which is what CentOS 6 provides.{ { code} }   [acompton@] /usr/lib/ruby/site_ruby/1.8/facter >> facter --debugRelative directory ./facter removed from search path.value for lsbdistid is still nilvalue for ipaddress6_lo is still nilruby-augeas not availablevalue for augeasversion is still nilvalue for sshecdsakey is still nilvalue for sshfp_ecdsa is still nilFound no suitable resolves of 1 for selinux_policyversionvalue for selinux_policyversion is still nilvalue for lsbdistdescription is still nilFound no suitable resolves of 1 for xendomainsvalue for xendomains is still nilvalue for lsbrelease is still nilFound no suitable resolves of 1 for selinux_modevalue for selinux_mode is still nilFound no suitable resolves of 1 for zonenamevalue for zonename is still nilvalue for ipaddress6_eth0 is still nilvalue for cfkey is still nilvalue for lsbdistid is still nilvalue for zpool_version is still nilvalue for macaddress_lo is still nilIllegal instruction[acompton@] /usr/lib/ruby/site_ruby/1.8/facter >> strace -f -- facter 2>&1 | grep -v SIG_ | tailstat("/usr/lib64/site_ruby/1.8/x86_64-linux/digest.rb", 0x7fff6c9843d0) = -1 ENOENT (No such file or directory)stat("/usr/lib64/site_ruby/1.8/x86_64-linux/digest.so", 0x7fff6c9843d0) = -1 ENOENT (No such file or directory)stat("/usr/lib64/site_ruby/digest.rb", 0x7fff6c9843d0) = -1 ENOENT (No such file or directory)stat("/usr/lib64/site_ruby/digest.so", 0x7fff6c9843d0) = -1 ENOENT (No such file or directory)stat("/usr/lib/ruby/1.8/digest.rb", {st_mode=S_IFREG|0644, st_size=1145, ...}) = 0open("/usr/lib/ruby/1.8/digest.rb", O_RDONLY) = 3fstat(3, {st_mode=S_IFREG|0644, st_size=1145, ...}) = 0close(3)= 0--- SIGILL (Illegal instruction) @ 0 (0) ---+++ killed by SIGILL +++(...comment out sshfp support...)[acompton@] /usr/lib/ruby/site_ruby/1.8/facter >> cat ssh.rb# Fact: ssh## Purpose:## Resolution:## Caveats:### ssh.rb## Facts related to SSH##{"SSHDSAKey" => { :file => "ssh_host_dsa_key.pub", :sshfprrtype => 2 } , "SSHRSAKey" => { :file => "ssh_host_rsa_key.pub", :sshfprrtype => 1 }, "SSHECDSAKey" => { :file => "ssh_host_ecdsa_key.pub", :sshfprrtype => 3 } }.each do |name,key|  Facter.add(name) dosetcode do  value = nil  [ "/etc/ssh","/usr/local/etc/ssh","/etc","/usr/local/etc","/etc/opt/ssh",  ].each do |dir|filepath = File.join(dir,key[:file])if FileTest.file?(filepath)  beginvalue = File.read(filepath).chomp.split(/\s+/)[1]break  rescuevalue = nil  endend  end  valueend  end  # Facter.add('SSHFP_' + name[3..-4]) do  #   setcode do

Jira (FACT-211) Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp

Title: Message Title

Adrien Thebo commented on an issue

Re: Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp

If Digest::SHA256.hexdigest is getting SIGILL then I don't think you can trust Ruby at all on the given system. This is not an uncommon thing to do and this sort of invocation could be invoked in a number of other places, https://github.com/puppetlabs/puppet/blob/master/lib/puppet/parser/functions/sha1.rb for instance. Even if we worked around this one specific instance we couldn't make any guarantees about the functionality of the rest of Puppet/Facter.
Out of curiosity where did this version of Ruby come from? On what virtualization platform are you running it? Ruby 1.8.7 is actually pretty dated, would you be able to try Ruby 1.9.3 or newer to see if this still affects you?

Add Comment

Facter / FACT-211

Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp

Support for ssh fingerprints (as merged in https://github.com/puppetlabs/facter/pull/162) breaks facter while running on CentOS 6.x on a VM due to a bug with ruby 1.8.7, which is what CentOS 6 provides. {code} [acompton@] /usr/lib/ruby/site_ruby/1.8/facter >> facter --debug Relative directory ./facter removed from search path. value fo...

This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (FACT-211) Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-211



  Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp 










Change By:

 Adrien Thebo




Assignee:

 Eric Sorenson












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-189) LXC Container support

2014-02-10 Thread Eric Sorenson (JIRA)

Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: LXC Container support 










I think it's "ready for merge".












   

 Add Comment











 













 Facter /  FACT-189



  LXC Container support 







 The virtual fact for facter should support lxc containers.   For more information about lxc: http://lxc.sourceforge.net/   We can detect an running lxc master system, if /cgroup is mounted on the system.  















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PDB-434) PR (841): Fixed an anonymizer test hidden behind a lazy seq - senior

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (841): Fixed an anonymizer test hidden behind a lazy seq - senior 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 PuppetDB /  PDB-434



  PR (841): Fixed an anonymizer test hidden behind a lazy seq - senior 







 h2. Fixed an anonymizer test hidden behind a lazy seq   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 841 Discussion|https://github.com/puppetlabs/puppetdb/pull/841]  * [Pull Request 841 File Diff|https://github.com/puppetlabs/puppetdb/pull/841/files]  h2. Pull Request Descript...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1629) WIndows 2008r2 fails to load() a file it previously store()d

Title: Message Title










 

 Ethan Brown updated an issue











 






 Puppet /  PUP-1629



  WIndows 2008r2 fails to load() a file it previously store()d 










Change By:

 Ethan Brown




Sprint:

 Week 2014-2-5 to 2014-2-12












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-160) Add standard packaging to mcollective-puppet-agent

Title: Message Title










 

 Richard Clamp updated an issue











 






 MCollective /  MCO-160



  Add standard packaging to mcollective-puppet-agent 










Change By:

 Richard Clamp




Sprint:

 2014_02_12-2014_02_26












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (MCO-160) Add standard packaging to mcollective-puppet-agent

Title: Message Title










 

 Richard Clamp updated an issue











 






 MCollective /  MCO-160



  Add standard packaging to mcollective-puppet-agent 










Change By:

 Richard Clamp




Story Points:

 2












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1629) WIndows 2008r2 fails to load() a file it previously store()d

Title: Message Title










 

 Ethan Brown assigned an issue to Ethan Brown











 






 Puppet /  PUP-1629



  WIndows 2008r2 fails to load() a file it previously store()d 










Change By:

 Ethan Brown




Assignee:

 Ethan Brown












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1584) Puppet module tool should work with new directory environments

2014-02-10 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow assigned an issue to Joshua Partlow











 






 Puppet /  PUP-1584



  Puppet module tool should work with new directory environments 










Change By:

 Joshua Partlow




Assignee:

 Eric Sorenson Joshua Partlow












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-278) Is checklist current

Title: Message Title










 

 Melissa Stone commented on an issue











 






  Re: Is checklist current 










Kylo Ginsberg I'm fine with that












   

 Add Comment











 













 Facter /  FACT-278



  Is checklist current 







 Do sub-tickets here match steps in https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process? And do those steps need updating for any recent tooling changes?















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PDB-435) Tests are failing on travis

2014-02-10 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-435



  Tests are failing on travis 










Change By:

 Kenneth Barber




Sprint:

 20140205 to 20140212












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PDB-435) Tests are failing on travis

2014-02-10 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber created an issue











 






 PuppetDB /  PDB-435



  Tests are failing on travis 










Issue Type:

  Bug




Affects Versions:


 1.5.x




Assignee:


 Unassigned




Created:


 10/Feb/14 9:30 AM




Fix Versions:


 1.5.x




Priority:

  Normal




Reporter:

 Kenneth Barber










Here is a reference:
https://travis-ci.org/kbarber/puppetdb/jobs/18560159












   

 Add Comment

Jira (PDB-434) PR (841): Fixed an anonymizer test hidden behind a lazy seq - senior

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (841): Fixed an anonymizer test hidden behind a lazy seq - senior 










pljenkinsro commented:
:red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/216/












   

 Add Comment











 













 PuppetDB /  PDB-434



  PR (841): Fixed an anonymizer test hidden behind a lazy seq - senior 







 h2. Fixed an anonymizer test hidden behind a lazy seq   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 841 Discussion|https://github.com/puppetlabs/puppetdb/pull/841]  * [Pull Request 841 File Diff|https://github.com/puppetlabs/puppetdb/pull/841/files]  h2. Pull Request Descript...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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

Jira (PUP-1473) user resource fails on UTF-8 comment

2014-02-10 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene assigned an issue to Peter Huene











 






 Puppet /  PUP-1473



  user resource fails on UTF-8 comment 










Change By:

 Peter Huene




Assignee:

 Peter Huene












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-93) Facter Solaris is outputting to stderr

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Facter Solaris is outputting to stderr 










This was fixed in https://github.com/puppetlabs/facter/pull/571












   

 Add Comment











 













 Facter /  FACT-93



  Facter Solaris is outputting to stderr 







 Also note that we're disabling the Facter Acceptance solaris job pending resolution of this issue. So please re-enable that job as part of fixing this.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1473) user resource fails on UTF-8 comment

2014-02-10 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen commented on an issue











 






  Re: user resource fails on UTF-8 comment 










Charlie Sharpsteen Just making sure you are aware of this effort as our UTF-8 tracker/attacker 












   

 Add Comment











 













 Puppet /  PUP-1473



  user resource fails on UTF-8 comment 







 Setting the gecos/comment field in a local user on debian wheezy with puppet 3.4.2-1puppetlabs1 fails with an ugly error about utf-8 encodings.   As this system is completely utf-8 there is no reason that this should be an invalid value, as can be seen by "puppet resource" and "getent passwd" displaying the value without problems.   {code}  root@puppetm...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-93) Facter Solaris is outputting to stderr

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Facter /  FACT-93



  Facter Solaris is outputting to stderr 










Change By:

 Kylo Ginsberg




Fix Version/s:

 2.0












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-322) Remove special casing of the empty string

Title: Message Title










 

 Adrien Thebo created an issue











 






 Facter /  FACT-322



  Remove special casing of the empty string 










Issue Type:

  Improvement




Assignee:

 Eric Sorenson




Created:


 10/Feb/14 9:41 AM




Fix Versions:


 2.0




Priority:

  Normal




Reporter:

 Adrien Thebo










In Facter 1 the only meaningful data type was the string and empty strings were converted to nil. This behavior was mainly due to the behavior of command execution - it was assumed that if a command didn't return anything on stdout then the value should be considered nil. Since Facter derives a lot of information from commands this use case was optimized for by automatically converting the empty string to nil when running commands and evaluating facts.
Facter 2 introduces the ability to return rich data types, so things like `nil` and `false` can actually be returned. Because of this the special casing of the empty string is no longer needed and may also be very surprising.
We should remove this special casing when evaluating facts and resolutions. We may still need to determine the behavior of executing commands and the behavior of Facter::Util::Resolution when setcode is a given a command, but my inclination is always return a string from .exec and normalize the output of setcode blocks.

Jira (PUP-845) Create a windows provider

2014-02-10 Thread Rob Reynolds (JIRA)

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Create a windows provider 










Thinking we have some a couple of opportunities here. We can either look for a flag we can use ourselves to say, this ACL/ACE is puppet managed or we can move forward with something less than optimistic with some sort of storage on a machine about the particular settings for each managed permission set.












   

 Add Comment











 













 Puppet /  PUP-845



  Create a windows provider 







 Create a basic (empty) windows provider that is only suitable on windows.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1473) user resource fails on UTF-8 comment

2014-02-10 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene assigned an issue to Peter Huene











 






 Puppet /  PUP-1473



  user resource fails on UTF-8 comment 










Change By:

 Peter Huene




Assignee:

 Peter Huene












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-321) Remove deprecated code for 2.0

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-321



  Remove deprecated code for 2.0 










Change By:

 Adrien Thebo




Story Points:

 2












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-322) Remove special casing of the empty string

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-322



  Remove special casing of the empty string 










Change By:

 Adrien Thebo




Sprint:

 Week 2014-2-5 to 2014-2-12












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-322) Remove special casing of the empty string

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-322



  Remove special casing of the empty string 










Change By:

 Adrien Thebo




Story Points:

 2












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-321) Remove deprecated code for 2.0

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-321



  Remove deprecated code for 2.0 










Change By:

 Adrien Thebo




Sprint:

 Week 2014-2-5 to 2014-2-12












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-81) Pull Request (499): (#21530) Rename the .to_plist method in cfpropertylist to .to_cfplist

Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Facter /  FACT-81



  Pull Request (499): (#21530) Rename the .to_plist method in cfpropertylist to .to_cfplist 










Change By:

 Adrien Thebo




Assignee:

 Adrien Thebo












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-321) Remove deprecated code for 2.0

Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Facter /  FACT-321



  Remove deprecated code for 2.0 










Change By:

 Adrien Thebo




Assignee:

 Eric Sorenson Adrien Thebo












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-323) PR (631): Maint/facter 2/remove deprecations - adrienthebo

Title: Message Title










 

 gepetto-bot created an issue











 






 Facter /  FACT-323



  PR (631): Maint/facter 2/remove deprecations - adrienthebo 










Issue Type:

  Task




Assignee:

 Adrien Thebo




Components:


 Community




Created:


 10/Feb/14 10:09 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Maint/facter 2/remove deprecations


Author: Adrien Thebo 


Company: Puppet Labs


Github ID: adrienthebo


Pull Request 631 Discussion


Pull Request 631 File Diff


Pull Request Description

This pull request removes all of the behaviors in Facter 2 that ha

Jira (FACT-189) LXC Container support

2014-02-10 Thread Jeff McCune (JIRA)

Title: Message Title










 

 Jeff McCune commented on an issue











 






  Re: LXC Container support 










Sweet, thanks Eric.












   

 Add Comment











 













 Facter /  FACT-189



  LXC Container support 







 The virtual fact for facter should support lxc containers.   For more information about lxc: http://lxc.sourceforge.net/   We can detect an running lxc master system, if /cgroup is mounted on the system.  















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1632) Hack Day - 7 Feb 2014

2014-02-10 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen created an issue











 






 Puppet /  PUP-1632



  Hack Day - 7 Feb 2014 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 10/Feb/14 10:34 AM




Priority:

  Normal




Reporter:

 Michelle Johansen










Please add a quick summary of your hack day here.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsu

Jira (PUP-1632) Hack Day - 7 Feb 2014

2014-02-10 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1632



  Hack Day - 7 Feb 2014 










Change By:

 Michelle Johansen




Sprint:

 Week 2014-2-5 to 2014-2-12












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1629) WIndows 2008r2 fails to load() a file it previously store()d

Title: Message Title










 

 Ethan Brown commented on an issue











 






  Re: WIndows 2008r2 fails to load() a file it previously store()d 










Doing a manual Jenkins git bisect to track down the offending commit, starting with 64f94d1dcd3441883cd69db7949f58439dd5efb0.
Unfortunately 64f94d1dcd3441883cd69db7949f58439dd5efb0 has completely barfed due to some bad code, so can't anchor off of that point in time.












   

 Add Comment











 













 Puppet /  PUP-1629



  WIndows 2008r2 fails to load() a file it previously store()d 







 While running Puppet-Specs-Windows-master on Windows 2008r2, rspec ./spec/unit/util/storage_spec.rb fails thus:  {code}    1) Puppet::Util::Storage when storing to the state file should load() the same information that it store()s   Failure/Error: Puppet::Util::Storage.load   RuntimeError:     Got 2 failure(s) while initializing: File[C:/Windo...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 pos

Jira (PUP-1629) WIndows 2008r2 fails to load() a file it previously store()d

Title: Message Title










 

 Ethan Brown updated an issue











 






 Puppet /  PUP-1629



  WIndows 2008r2 fails to load() a file it previously store()d 










Change By:

 Ethan Brown




Story Points:

 1












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-268) PR (621): debian/control: Depend on lsb-core. - daenney

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (621): debian/control: Depend on lsb-core. - daenney 










MosesMendoza commented:
I'm not wild about adding this as a dependency. Perhaps a 'recommends' of lsb-release? This would notify the user that some functionality may be enhanced by having lsb-release around, but it isn't a strict requirement. Also, I'm not totally excited about transitively depending on python (though I admit it probably is everywhere, so its probably not a rational dislike of the idea).












   

 Add Comment











 













 Facter /  FACT-268



  PR (621): debian/control: Depend on lsb-core. - daenney 







 h2. debian/control: Depend on lsb-core.   * Author: Daniele Sluijters   * Company:   * Github ID: [daenney|https://github.com/daenney]  * [Pull Request 621 Discussion|https://github.com/puppetlabs/facter/pull/621]  * [Pull Request 621 File Diff|https://github.com/puppetlabs/facter/pull/621/files]  h2. Pull Request Description   In ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
T

Jira (PUP-1632) Hack Day - 7 Feb 2014

2014-02-10 Thread Rob Reynolds (JIRA)

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Hack Day - 7 Feb 2014 










I continued to work on PUP-845












   

 Add Comment











 













 Puppet /  PUP-1632



  Hack Day - 7 Feb 2014 







 Please add a quick summary of your hack day here.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-286) Smoke test packages

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Smoke test packages 










This release is pretty much just initial mavericks support so I'm thinking this smoke test is going to be short but sweet:
Platforms


Precise


Fedora 19


Darwin 10.9


Verify you can:


install package


run facter


run facter --version


man facter (where appropriate)














   

 Add Comment











 













 Facter /  FACT-286



  Smoke test packages 







 Procedure may vary by project and point in the release cycle. Ask around.

Jira (HI-177) Send out the announcements

Title: Message Title










 

 Melissa Stone assigned an issue to Melissa Stone











 






 Hiera /  HI-177



  Send out the announcements 










Change By:

 Melissa Stone




Assignee:

 Melissa Stone












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (HI-177) Send out the announcements

Title: Message Title










 

 Melissa Stone created an issue











 






 Hiera /  HI-177



  Send out the announcements 










Issue Type:

  Sub-task




Assignee:


 Unassigned




Created:


 10/Feb/14 11:02 AM




Priority:

  Normal




Reporter:

 Melissa Stone










Send the release email, do a PSA on #puppet












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1632) Hack Day - 7 Feb 2014

2014-02-10 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Hack Day - 7 Feb 2014 










Updated the acceptance harness to use Beaker 1.6.2, added :preserve_hosts onfail as a default, cleared out some unused rsync code and updated the cleanup task to release vms back to the pooling api.
https://github.com/puppetlabs/puppet/pull/2339
There was a Travis failure on 1.8.7, which I believe was the CRL equality issue that Josh Cooper fixed. I've rebased to get another Travis run.












   

 Add Comment











 













 Puppet /  PUP-1632



  Hack Day - 7 Feb 2014 







 Please add a quick summary of your hack day here.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1473) user resource fails on UTF-8 comment

2014-02-10 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: user resource fails on UTF-8 comment 










Hmm... bummer. I thought we took care of this one with PR 1943.
The error message is indeed odd, at first glance it seems to suggest that we're failing to strip UTF-8 down to raw bytes. I haven't seen that before.












   

 Add Comment











 













 Puppet /  PUP-1473



  user resource fails on UTF-8 comment 







 Setting the gecos/comment field in a local user on debian wheezy with puppet 3.4.2-1puppetlabs1 fails with an ugly error about utf-8 encodings.   As this system is completely utf-8 there is no reason that this should be an invalid value, as can be seen by "puppet resource" and "getent passwd" displaying the value without problems.   {code}  root@puppetm...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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.go

Jira (PUP-1632) Hack Day - 7 Feb 2014

Title: Message Title










 

 Ethan Brown commented on an issue











 






  Re: Hack Day - 7 Feb 2014 










I worked on refreshing our Windows Vagrant boxes that are used for development work. These live at https://github.com/puppetlabs/product-vagrant-boxes
This involved:


Updating to the latest 0.5.1 version of Packer locally, and upgrading the templates accordingly


Upgrading VMWare fusion boxes to version 6 compatibility


Upgrading the local copy of the Cygwin installer (as it was hanging on a dialog box)


Updating to the VirtualBox tools auto-mount, instead of copying / extracting the ISO within the VM (hopefully VMWare also ends up using a similar approach in the future as it does save some time with building out the box, and simplifies the script used to do a tool install)


Taking built Vagrant boxes, and placing them up at http://int-resources.ops.puppetlabs.net/vagrant/puppetless_boxes/


The rebuild of 2008R2 was a success, and the box files have been uploaded. The changes are in the repo here
https://github.com/puppetlabs/product-vagrant-boxes/compare/35f013c7e121442f3cc2d04b74812dbb244d09ba...6fde861a29872ba14fe793ba783f87053316c006
Next step was to bake out a similar template for 2012R2, which required:


Modifications to Autounattend.xml answer file for any changes that were 2012R2 specific.


Updates to template.json for the source ISO installation media (took some digging to find the direct download urls)


Updates to template.json to exclude running scripts to install things like Powershell 3 and .NET 4, which already ship within 2012 as features.


Checks against existing PowerShell installation scripts to verify the OS specific differences that need to be made to these scripts (it turns out that the original scripts I baked were pretty good and didn't require much / any modification)


Moving of shared files out to a common location for Windows based box builds


Building and publishing in the same manner as 2008R2

Jira (PDB-435) Tests are failing on travis

2014-02-10 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior assigned an issue to Ryan Senior











 






 PuppetDB /  PDB-435



  Tests are failing on travis 










Change By:

 Ryan Senior




Assignee:

 Ryan Senior












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-286) Smoke test packages

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Smoke test packages 












fedora 19













   

 Add Comment











 













 Facter /  FACT-286



  Smoke test packages 







 Procedure may vary by project and point in the release cycle. Ask around.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-286) Smoke test packages

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Smoke test packages 












precise













   

 Add Comment











 













 Facter /  FACT-286



  Smoke test packages 







 Procedure may vary by project and point in the release cycle. Ask around.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1473) user resource fails on UTF-8 comment

2014-02-10 Thread Charlie Sharpsteen (JIRA)

Title: Message Title

Charlie Sharpsteen commented on an issue

Re: user resource fails on UTF-8 comment

Ahh. I think I see the problem here. PR 1943 attempts to sort encoding issues by treating user comments as raw byte strings. It does so by calling encode(Encoding::ASCII_8BIT). This is probably the wrong approach.
In ruby 1.9.x, encode attempts to transcode from one encoding to another. This operation attempts to mutate the underlying bytes of the string. We're seeing a failure here because there is no defined transcoding from UTF-8 to ASCII_8BIT. The correct method to call in this situation would be force_encoding which assigns an encoding to a string without attempting to change the underlying bytes.
It looks like PR 1943 originally used force_encoding, but then switched midstream to using a combination of both methods. Commit b173ac0 normalized everything to encode.
force_encoding is the right method to use here, unless there is some reason PR 1943 abandoned it.
Raphaël Pinson, any comments regarding the choice of encode over force_encoding?

Add Comment

Puppet / PUP-1473

user resource fails on UTF-8 comment

Setting the gecos/comment field in a local user on debian wheezy with puppet 3.4.2-1puppetlabs1 fails with an ugly error about utf-8 encodings. As this system is completely utf-8 there is no reason that this should be an invalid value, as can be seen by "puppet resource" and "getent passwd" displaying the value without problems. {code} root@puppetm...

Jira (PDB-435) Tests are failing on travis

2014-02-10 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-435



  Tests are failing on travis 










Change By:

 Ryan Senior




Story Points:

 1












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (FACT-277) Facter 1.7.5 Release

Title: Message Title










 

 Melissa Stone updated an issue











 






 Facter /  FACT-277



  Facter 1.7.5 Release 










Change By:

 Melissa Stone




Fix Version/s:

 1.7.5












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1559) Windows - Specifying well-known SIDs as a group / user in manifests causes errors

2014-02-10 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1559



  Windows - Specifying well-known SIDs as a group / user in manifests causes errors 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (HI-173) Command line variable specification seems to have changed between 1.1.2 & 1.2.1

2014-02-10 Thread Justin Holguin (JIRA)

Title: Message Title










 

 Justin Holguin commented on an issue











 






  Re: Command line variable specification seems to have changed between 1.1.2 & 1.2.1 










Thanks, Marcin Iwinski and Matthew Barr! You are absolutely right. I'll update the command line variables section today to reflect the change.












   

 Add Comment











 













 Hiera /  HI-173



  Command line variable specification seems to have changed between 1.1.2 & 1.2.1 







 Specifying top level facts on the command line used to be:   `hiera LOOKUP fqdn=client.local -d`   Seems like that it now needs to be:   `hiera LOOKUP ::fqdn=client.local -d`The former is supported by documentation such as:

Jira (PUP-1618) Confusing "valid values" documentation for exec logoutput

2014-02-10 Thread Nicholas Fagerlund (JIRA)

Title: Message Title










 

 Nicholas Fagerlund assigned an issue to Nicholas Fagerlund











 






 Puppet /  PUP-1618



  Confusing "valid values" documentation for exec logoutput 










Change By:

 Nicholas Fagerlund




Assignee:

 Nicholas Fagerlund












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1618) Confusing "valid values" documentation for exec logoutput

2014-02-10 Thread Nicholas Fagerlund (JIRA)

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: Confusing "valid values" documentation for exec logoutput 










Yup, this sure seems to not accept valid log levels. 



exec {"/opt/local/bin/cowsay 'She only comes out at night / The lean and hungry type'":
  logoutput => 'debug',
}



Looking into the code now, try and figure out if it used to.












   

 Add Comment











 













 Puppet /  PUP-1618



  Confusing "valid values" documentation for exec logoutput 







 On the page http://docs.puppetlabs.com/references/latest/type.html#exec it says   {quote}logout  ...In addition to the values below, you may set this attribute to any legal log level.   Valid values are true, false, on_failure.{quote}   Huh? So a legal log level is a value, but is not a valid value? ;-)   Testing would indicate that log levels...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because

Jira (PUP-1618) Confusing "valid values" documentation for exec logoutput

2014-02-10 Thread Nicholas Fagerlund (JIRA)

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: Confusing "valid values" documentation for exec logoutput 










Found it. Up through 0.24.1:



newparam(:logoutput) do
desc "Whether to log output.  Defaults to logging output at the
loglevel for the ``exec`` element.  Values are **true**, *false*,
and any legal log level."

values = [:true, :false]
# And all of the log levels
Puppet::Util::Log.eachlevel { |level| values << level }
newvalues(*values)
end



Apparently this never actually worked, though! Or at least that's what Luke implied in commit bb8051bc406d1da67db8212e852bb36d1368e953 (between 0.24.1 and 0.24.2) when he removed it. He didn't update the parameter description string at the same time though, so it's stayed wrong since 2008. 












   

 Add Comment











 













 Puppet /  PUP-1618



  Confusing "valid values" documentation for exec logoutput 







 On the page http://docs.puppetlabs.com/references/latest/type.html#exec it says   {quote}logout  ...In addition to the values below, you may set this attribute to any legal log level.   Valid values are true, false, on_failure.{quote}   Huh? So a legal log level is a value, but is not a valid value? ;-)   Testing would indicate that log levels...

Jira (FACT-323) PR (631): Maint/facter 2/remove deprecations - adrienthebo

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (631): Maint/facter 2/remove deprecations - adrienthebo 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Facter /  FACT-323



  PR (631): Maint/facter 2/remove deprecations - adrienthebo 







 h2. Maint/facter 2/remove deprecations   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 631 Discussion|https://github.com/puppetlabs/facter/pull/631]  * [Pull Request 631 File Diff|https://github.com/puppetlabs/facter/pull/631/files]  h2. Pull R...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.

Jira (PUP-1633) PR (2343): (docs) Update description for Exec type's logoutput parameter - nfagerlund