Jira (PUP-1743) Catalog retrieval problems

2014-02-21 Thread Jakub Bittner (JIRA) 
Title: Message Title










 

 Jakub Bittner created an issue











 






 Puppet /  PUP-1743



  Catalog retrieval problems 










Issue Type:

  Bug




Affects Versions:


 3.4.2




Assignee:


 Unassigned




Created:


 21/Feb/14 12:07 AM




Environment:


Centos 6.5 with puppet from puppet official repos




Priority:

  Major




Reporter:

 Jakub Bittner










Hello, we have some problems with puppet agent catalog retrieval. When I run puppet agent start -t i got error like:
Error: Could not retrieve catalog from remote server: Could not intern from text/pson: source did not contain any PSON! or Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': Could not intern_multiple from text/pson: source did not contain any PSON!
But! If we try to run it more times in a row it works again. For example I run puppet agent start -t 3 times and on third try it works as expected.

Jira (PUP-1639) Some modules fail to install into target_dir

2014-02-21 Thread Eric Veiras Galisson (JIRA) 
Title: Message Title










 

 Eric Veiras Galisson commented on an issue











 






  Re: Some modules fail to install into target_dir 










Hello,
I got the same problem with puppetlabs/apache v0.11.0 but not v0.10.0

puppet module install puppetlabs/apache --version 0.10.0 --modulepath modules/ Notice: Preparing to install into /etc/puppet/environments/production/modules ... Notice: Downloading from https://forge.puppetlabs.com ... Notice: Installing – do not interrupt ... /etc/puppet/environments/production/modules └─┬ puppetlabs-apache (v0.10.0) └── puppetlabs-concat (v1.0.1)

I remove v0.10.0 before trying to install v0.11.0



rm -fr modules/apache/


puppet module install puppetlabs/apache --version 0.11.0 --modulepath modules/ Notice: Preparing to install into /etc/puppet/environments/production/modules ... Notice: Downloading from https://forge.puppetlabs.com ... Notice: Installing – do not interrupt ... Error: No such file or directory - /etc/puppet/environments/production/modules/apache/spec/acceptance/nodesets/default.yml Error: Try 'puppet help module install' for usage



If I try to install somewhere else (/tmp/modules) I got the same error when running as root but not when running with another user.
Puppet is 3.4.2-1puppetlabs1 on Debian Wheezy.
(see this discussion https://github.com/puppetlabs/puppetlabs-apache/issues/628)












   

 Add Comment











 













 Puppet /  PUP-1639



  Some modules fail to install into target_dir

Jira (PUP-1744) User creation fails on OS X 10.9 if user is added to more than one group

2014-02-21 Thread Thomas Steinert (JIRA) 
Title: Message Title










 

 Thomas Steinert created an issue











 






 Puppet /  PUP-1744



  User creation fails on OS X 10.9 if user is added to more than one group 










Issue Type:

  Bug




Affects Versions:


 3.4.3




Assignee:


 Unassigned




Created:


 21/Feb/14 2:52 AM




Environment:


OS: Mac OS X 10.9




Fix Versions:


 3.4.2




Priority:

  Normal




Reporter:

 Thomas Steinert










When I try to create a user with more then one group on Mac OS X 10.9 with puppet 3.4.3 errors are thrown:


change from absent to admin,wheel failed: undefined method `split' for :absent:Symbol

Could not prefetch user provider 'directoryservice': invalid byte sequence in US-ASCII

undefined method `split' for :absent:Symbol

Failed to apply catalog: incompatible character encodings: UTF-8 and ASCII-8BIT

Jira (PUP-1745) Could not autoload puppet/util/ tagmail reports when catalog fails

2014-02-21 Thread Jo Rhett (JIRA) 
Title: Message Title










 

 Jo Rhett created an issue











 






 Puppet /  PUP-1745



  Could not autoload puppet/util/ tagmail reports when catalog fails 










Issue Type:

  Bug




Affects Versions:


 3.4.3




Assignee:


 Unassigned




Created:


 21/Feb/14 3:39 AM




Environment:


wheezy/sid Linux sunstone 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
and
FreeBSD fireagate 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013 r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64




Priority:

  Normal




Reporter:

 Jo Rhett










I started getting tagmail e-mails of this nature yesterday.

Fri Feb 21 03:19:09 -0800 2014 Puppet (err): Could not autoload puppet/util/instrumentation/listeners/performance: Class Performance is already defined in Puppet::Util::Instrumentation Fri Feb 21 03:19:09 -0800 2014 Puppet (err): Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/performance: Class Performance is already defined in Puppet::Util::Instrumentation

Likewise, I started getting this similar but different report from FreeBSD

Jira (PUP-1746) Adjust Puppet-Common Dependency for Ubuntu 12.04 Precise

2014-02-21 Thread Ronald Valente (JIRA) 
Title: Message Title










 

 Ronald Valente created an issue











 






 Puppet /  PUP-1746



  Adjust Puppet-Common Dependency for Ubuntu 12.04 Precise 










Issue Type:

  Bug




Affects Versions:


 3.4.2




Assignee:


 Unassigned




Created:


 21/Feb/14 4:47 AM




Environment:


Ubuntu 12.04 LTS Minimal VM




Priority:

  Normal




Reporter:

 Ronald Valente










Even if I have ruby1.9.3 package installed, puppet-common and thus puppet will try and install Ruby 1.8.7.
puppet Depends: puppet-common




Depends: ruby ruby1.8 Depends:  ruby1.8 ruby1.9.1 Suggests: puppet-el Suggests: vim-puppet Recommends:  ruby

Jira (PUP-1745) Could not autoload puppet/util/ tagmail reports

2014-02-21 Thread Jo Rhett (JIRA) 
Title: Message Title










 

 Jo Rhett updated an issue











 






 Puppet /  PUP-1745



  Could not autoload puppet/util/ tagmail reports 










Adjusted since my original report was wrong – it wasn't related to catalog failures. The problem continues.










Change By:

 Jo Rhett




Summary:

 Could not autoload puppet/util/ tagmail reports  when catalog fails









 I started getting tagmail e-mails of this nature yesterday.{quote}Fri Feb 21 03:19:09 -0800 2014 Puppet (err): Could not autoload puppet/util/instrumentation/listeners/performance: Class Performance is already defined in Puppet::Util::InstrumentationFri Feb 21 03:19:09 -0800 2014 Puppet (err): Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/performance: Class Performance is already defined in Puppet::Util::Instrumentation{quote}Likewise, I started getting this similar but different report from FreeBSD{code}Fri Feb 21 03:22:02 -0800 2014 /File[/var/puppet/lib] (err): Failed to generate additional resources using 'eval_generate: uninitialized constant Puppet::FileSystem::FileFri Feb 21 03:22:02 -0800 2014 Puppet (err): Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::InstrumentationFri Feb 21 03:22:02 -0800 2014 Puppet (err): Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation{code} Huh? I didn't have time to look into yet until today. When I did I found something completely different: This does not show up when run from the command line {code}root@sunstone:/etc# puppet agent --testInfo: Retrieving pluginInfo: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/pe_version.rbInfo: Loading facts in /var/lib/puppet/lib/facter/ssldir.rbInfo: Loading facts in /var/lib/puppet/lib/facter/pkgng.rbInfo: Loading facts in /var/lib/puppet/lib/facter/root_home.rbInfo: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Error Info :  Could not retrieve  Caching  catalog  from remote server: Error 400 on SERVER: Could not find resource 'File[/etc/mcollective/ssl]'  for  relationship from 'Package[mcollective]' on node  sunstone.example.net Warning Info :  Not using cache on failed catalog  Applying configuration version '1392985112'  Error Notice :  Could not retrieve  Finished  catalog ; skipping  run  in 1.62 seconds {code}Oddly enough, the tagmail report from the manual run matches what is on the screen.     It's the agent runs which produce this odd report.

Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment

2014-02-21 Thread Damon Atkins (JIRA) 
Title: Message Title










 

 Damon Atkins commented on an issue











 






  Re: Make modulepath, manifest, and config_version configurable per-environment 










modulepath also needs OS flavour e.g. solaris, linux, aix, windows etc.  You could do osfamily
manifest = $confdir/manifest/$environment modulepath = $confdir/modules/$environment:$confdir/modules/$environment/$osflavour:configdir/modules/$osflavour:$confdir/modules/common Note: $osfamily is to specific... i.e. RHEL, OEL, Deb etc are 97% the same so "linux" would be best to describe them as a set.
If you have windows systems and linux systems in the same environment unix code will try to run on windows system?












   

 Add Comment











 













 Puppet /  PUP-1596



  Make modulepath, manifest, and config_version configurable per-environment 







 In order to make the new environment system fully usable, the default modulepath, manifest, and config_version needs to be overridable on a per-environment basis. This is possible in the current system with the environment stanzas and similar flexibility needs to be retained in the directory environments.   Each environment should optionally have an {{en...















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

Jira (PUP-1592) Puppet excessively stats the filesystem when looking for defined types

2014-02-21 Thread Brice Figureau (JIRA) 
Title: Message Title










 

 Brice Figureau commented on an issue











 






  Re: Puppet excessively stats the filesystem when looking for defined types  










Funny, this is exactly how Peter Meier and I thought about fixing it first when at the cfgmgmtcamp, then thought it was kind of too hackish to be accepted upstream and rejected it  Anyway, thanks for the fix!












   

 Add Comment











 













 Puppet /  PUP-1592



  Puppet excessively stats the filesystem when looking for defined types  







 [~masterzen] and I realized that when puppet tries to resolve a defined type, it always tries to first find the defined type within all the plugin directories as it tries to first load it as a resource type and then as a defined type.   We should be able to avoid a lot of stats on the filesystem by simply changing the lookup order.   [~masterzen] has so...















 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-724) Could not autoload puppet /util /instrumentation /listeners /log

2014-02-21 Thread Andrew Parker (JIRA) 
Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Could not autoload puppet /util /instrumentation /listeners /log 










Ronald Valente, are you seeing this issue on 3.4.3? If so, could you provide any information about when it occurs, the system it is running on (OS, filesystem, etc), the puppet version, and ruby version?












   

 Add Comment











 













 Puppet /  PUP-724



  Could not autoload puppet /util /instrumentation /listeners /log 














 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-1572) useradd provider should support usermod's move-home option if managehome is enabled

2014-02-21 Thread Francisco Cabrita (JIRA) 
Title: Message Title










 

 Francisco Cabrita updated an issue











 






 Puppet /  PUP-1572



  useradd provider should support usermod's move-home option if managehome is enabled 










Change By:

 Francisco Cabrita




Priority:

 Normal 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-1572) useradd provider should support usermod's move-home option if managehome is enabled

2014-02-21 Thread Francisco Cabrita (JIRA) 
Title: Message Title










 

 Francisco Cabrita commented on an issue











 






  Re: useradd provider should support usermod's move-home option if managehome is enabled 










Usermod is not working properly
Take this example:
root@deb702:/home# getent passwd foo
root@deb702:/home# puppet resource user foo ensure=present home=/home/foo managehome=true Notice: /User[foo]/ensure: created user  { 'foo': ensure => 'present', home => '/home/foo', }
root@deb702:/home# getent passwd foo foo:x:1001:1002::/home/foo:/bin/sh
root@deb702:/home# ls foo main vagrant
root@deb702:/home# puppet resource user foo ensure=present home=/home/BAR managehome=true Notice: /User[foo]/home: home changed '/home/foo' to '/home/BAR' user  { 'foo': ensure => 'present', home => '/home/BAR', }
root@deb702:/home# getent passwd foo foo:x:1001:1002::/home/BAR:/bin/sh
root@deb702:/home# ls foo main vagrant












   

 Add Comment











 













 Puppet /  PUP-1572



  useradd provider should support usermod's move-home option if managehome is enabled 







 The useradd provider does not support the -m option to move a users original home directory if managehome is enabled and a users home directory is being modified.















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

Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log

2014-02-21 Thread Joshua Cooper (JIRA) 
Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Could not autoload puppet /util /instrumentation /listeners /log 










See also PUP-1745












   

 Add Comment











 













 Puppet /  PUP-724



  Could not autoload puppet /util /instrumentation /listeners /log 














 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-1745) Could not autoload puppet/util/ tagmail reports

2014-02-21 Thread Joshua Cooper (JIRA) 
Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Could not autoload puppet/util/ tagmail reports 










Christian Hoge reported to me that he sometimes seems the uninitialized constant Puppet::FileSystem::File error. Please run with --trace and post the backtrace.












   

 Add Comment











 













 Puppet /  PUP-1745



  Could not autoload puppet/util/ tagmail reports 







 I started getting tagmail e-mails of this nature yesterday.   {quote}  Fri Feb 21 03:19:09 -0800 2014 Puppet (err): Could not autoload puppet/util/instrumentation/listeners/performance: Class Performance is already defined in Puppet::Util::Instrumentation  Fri Feb 21 03:19:09 -0800 2014 Puppet (err): Failed to apply catalog: Could not autoload puppet/uti...















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

Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log

2014-02-21 Thread Ronald Valente (JIRA) 
Title: Message Title










 

 Ronald Valente commented on an issue











 






  Re: Could not autoload puppet /util /instrumentation /listeners /log 










OS: Ubuntu 12.04.04 LTS FS: ext4/lvm Ruby: 1.8.7 (only because puppet-common still depends on ruby1.8 for precise even though it ships with 1.9.3)


ruby -v
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]





puppet --version
3.4.3



Also Note: A force of a puppet run will complete without error. (See manual run below)


puppet agent --test
Info: Applying configuration version '1392948172'
Notice: Finished catalog run in 16.18 seconds
Changes:
Events:
Resources:
Total: 253
Time:
   Filebucket: 0.00
  Vcsrepo: 0.00
 Schedule: 0.00
   Anchor: 0.00
Group: 0.00
   Ssh authorized key: 0.00
 User: 0.01
 Exec: 0.86
   Augeas: 0.92
  Service: 1.08
 Last run: 1393002908
Total: 15.73
   Config retrieval: 2.78
 File: 2.79
  Package: 7.27
Version:
   Config: 1392948172
   Puppet: 3.4.3



Also Note2:This is only happening on one of my nodes.












   

 Add Comment











 













 Puppet /  PUP-724



  Could not autoload puppet /util /instrumentation /listeners /log

Jira (PUP-1745) Could not autoload puppet/util/ tagmail reports

2014-02-21 Thread Ronald Valente (JIRA) 
Title: Message Title










 

 Ronald Valente commented on an issue











 






  Re: Could not autoload puppet/util/ tagmail reports 










I posted this on the closed bug by accident.
OS: Ubuntu 12.04.04 LTS FS: ext4/lvm Ruby: 1.8.7 (only because puppet-common still depends on ruby1.8 for precise even though it ships with 1.9.3)


ruby -v
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]





puppet --version
3.4.3



Also Note: A force of a puppet run will complete without error. (See manual run below)


puppet agent --test
Info: Applying configuration version '1392948172'
Notice: Finished catalog run in 16.18 seconds
Changes:
Events:
Resources:
Total: 253
Time:
   Filebucket: 0.00
  Vcsrepo: 0.00
 Schedule: 0.00
   Anchor: 0.00
Group: 0.00
   Ssh authorized key: 0.00
 User: 0.01
 Exec: 0.86
   Augeas: 0.92
  Service: 1.08
 Last run: 1393002908
Total: 15.73
   Config retrieval: 2.78
 File: 2.79
  Package: 7.27
Version:
   Config: 1392948172
   Puppet: 3.4.3



Also Note2:This is only happening on one of my nodes.












   

 Add Comment











 













 Puppet /  PUP-1745



  Could not autoload puppet/util/ tagmail reports

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

2014-02-21 Thread David Gwilliam (JIRA) 
Title: Message Title










 

 David Gwilliam commented on an issue











 






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










Shifting perspective from a documentation angle to an education angle, this is pretty bad behavior. Is there a specific reason that hiera doesn't handle this the way humans seem to expect it to? e.g. hiera cli doesn't care/enforce whether you use ::fqdn or fqdn?












   

 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-1745) Could not autoload puppet/util/ tagmail reports

2014-02-21 Thread Andrew Parker (JIRA) 
Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Could not autoload puppet/util/ tagmail reports 










Jo Rhett, Ronald Valente, to be perfectly honest this issue has been a bit of a mystery. When we created the patch for 

PUP-724
, we had done a lot of investigation and it turned out that puppet was, for some reason, seeing different fractions of a second on a file stat's mtime (specifically puppet/util/instrumentation/listeners/log), which caused it to try to reload it when the pluginsync stage called reload_changed. We never figured out why the mtime seemed change the fractional seconds, but the patch was to have it only pay attention to the full seconds.
The main thing to diagnose this is to run with --trace so that we can get an indication of what code paths are triggering this.
Also, the issue with Puppet::FileSystem::File missing is a new one. I'm not sure if it is related to the 

PUP-724
 issue or not.












   

 Add Comment











 













 Puppet /  PUP-1745



  Could not autoload puppet/util/ tagmail reports 







 I started getting tagmail e-mails of this nature yesterday.   {quote}  Fri Feb 21 03:19:09 -0800 2014 Puppet (err): Could not autoload puppet/util/instrumentation/listeners/performance: Class Performance is already defined in Puppet::Util::Instrumentation  Fri Feb 21 03:19:09 -0800 2014 Puppet (err): Failed to apply catalog: Could not autoload puppet/uti...

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

2014-02-21 Thread David Gwilliam (JIRA) 
Title: Message Title










 

 David Gwilliam commented on an issue











 






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










Via Justin Holguin, there is a ticket that reflects my concerns: HI-184












   

 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-1114) Deprecate environment configuration in puppet.conf

2014-02-21 Thread Andrew Parker (JIRA) 
Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1114



  Deprecate environment configuration in puppet.conf 










Change By:

 Andrew Parker




Fix Version/s:

 4.0.0




Fix Version/s:

 3.6.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-1114) Deprecate environment configuration in puppet.conf

2014-02-21 Thread Andrew Parker (JIRA) 
Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Deprecate environment configuration in puppet.conf 










Based on a use case provided by Jason Antman the $environment may still be needed. 












   

 Add Comment











 













 Puppet /  PUP-1114



  Deprecate environment configuration in puppet.conf 







 There's a confusing overload between the config stanzas in puppet.conf, some of which are used for run-mode-specific configuration and others for environments.















 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-1592) Puppet excessively stats the filesystem when looking for defined types

2014-02-21 Thread Andrew Parker (JIRA) 
Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Puppet excessively stats the filesystem when looking for defined types  










Brice Figureau, we figured that the amount of work to get the cache in place, make sure that it doesn't have unwanted side effects, make sure it gets cleaned up at the right times, etc. was just too much work on a system that we are looking toward reworking for Puppet 4  So we went with this.












   

 Add Comment











 













 Puppet /  PUP-1592



  Puppet excessively stats the filesystem when looking for defined types  







 [~masterzen] and I realized that when puppet tries to resolve a defined type, it always tries to first find the defined type within all the plugin directories as it tries to first load it as a resource type and then as a defined type.   We should be able to avoid a lot of stats on the filesystem by simply changing the lookup order.   [~masterzen] has so...















 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

Jira (PUP-879) Deprecate "host{csr,privkey,pubkey}" Settings

2014-02-21 Thread JIRA 
Title: Message Title










 

 Erik Dalén commented on an issue











 






  Re: Deprecate "host{csr,privkey,pubkey}" Settings 










I've used these in many scripts, like "puppet agent --configprint hostprivkey", what is the canonical way to get that info without that option? I think that might even be mentioned in some curl tips for puppetdb, not sure though.












   

 Add Comment











 













 Puppet /  PUP-879



  Deprecate "host{csr,privkey,pubkey}" Settings 







 These settings are not used anywhere in the codebase.















 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-1747) Selinux parsing with multiple levels

2014-02-21 Thread Matt Ruge (JIRA) 
Title: Message Title










 

 Matt Ruge created an issue











 






 Puppet /  PUP-1747



  Selinux parsing with multiple levels 










Issue Type:

  Bug




Assignee:


 Unassigned




Attachments:


 selinux.rb.patch




Created:


 21/Feb/14 12:39 PM




Priority:

  Normal




Reporter:

 Matt Ruge










The parsing portion of set_selinux_context(file, value, component = false) does not account for multiple levels/sensitivities. The range component can contain a ":" on MLS systems for example 

"unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c255 user : role : type : range "

When the function splits on ":" it causes only the first part of the range to be reset, and the second half to be preserved. This makes the selrange to grow indefinitely 
Example: Initial


security.selinux="system_u:object_r:auditd_log_t:s15:c0.c16383" After 1 puppet run


security.selinux="system_u:object_r:auditd_log_t:s15:c0.c16383:c0.c16383" etc.


I have attached a patch that seems to fix it on my system, but the parse_selinux_context() function seems to do it better, so i'll leave it up to people with more ruby-fu than I have

Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment

2014-02-21 Thread Andrew Parker (JIRA) 
Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1596



  Make modulepath, manifest, and config_version configurable per-environment 










Change By:

 Andrew Parker




Issue Type:

 Bug Improvement












   

 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-1596) Make modulepath, manifest, and config_version configurable per-environment

2014-02-21 Thread Andrew Parker (JIRA) 
Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Make modulepath, manifest, and config_version configurable per-environment 










Damon Atkins, interpolating facts into the settings isn't something that is currently support, nor do I think it is something that will be supported. Deciding what modules to use based on the node is something that should be done in the puppet manifests.












   

 Add Comment











 













 Puppet /  PUP-1596



  Make modulepath, manifest, and config_version configurable per-environment 







 In order to make the new environment system fully usable, the default modulepath, manifest, and config_version needs to be overridable on a per-environment basis. This is possible in the current system with the environment stanzas and similar flexibility needs to be retained in the directory environments.   Each environment should optionally have an {{en...















 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

Jira (PUP-1748) mco package status "undefined method `new' for nil:NilClass"

2014-02-21 Thread Jascha Lee (JIRA) 
Title: Message Title










 

 Jascha Lee created an issue











 






 Puppet /  PUP-1748



  mco package status "undefined method `new' for nil:NilClass" 










Issue Type:

  Bug




Affects Versions:


 3.4.3




Assignee:


 Unassigned




Attachments:


 errors.txt




Created:


 21/Feb/14 2:40 PM




Environment:


CentOS 5.8 mcollective-2.4.0-1.el5 mcollective-package-4.2.2-1.el5




Priority:

  Normal




Reporter:

 Jascha Lee










After upgrading from 3.3.1 to 3.4.3, mco package status reports: undefined method `new' for nil:NilClass related to not being able to autoload various puppet/provider/package for most hosts. This makes mco package status unreliable.
Downgrading back to puppet 3.3.1 fixes the problem.

Jira (PUP-1749) Puppet module tool does not work on Solaris

2014-02-21 Thread Reid Vandewiele (JIRA) 
Title: Message Title










 

 Reid Vandewiele created an issue











 






 Puppet /  PUP-1749



  Puppet module tool does not work on Solaris 










Issue Type:

  Bug




Affects Versions:


 3.4.2




Assignee:


 Unassigned




Created:


 21/Feb/14 2:44 PM




Priority:

  Normal




Reporter:

 Reid Vandewiele










The Puppet module tool currently doesn't work on Solaris 10 in the absence of specially installed GNU utilities (specifically, gtar is required). The current state is effectively "workaround required".
Solaris 10 is a PE supported platform, and the module tool should work out of the box to enable local testing and module installation.
How the Puppet module tool currently fails on Solaris 10 is displayed below.


/opt/puppet/bin/puppet module install seteam/opencsw --module_repository=http://forgeapi.puppetlabs.com
Notice: Preparing to install into /etc/puppetlabs/puppet/modules ...
Notice: Downloading from http://forgeapi.puppetlabs.com ...
Error: Could not extract contents of module archive: Execution of 'tar xzf /var/opt/lib/pe-puppet/puppet-module/cache/seteam-opencsw20140221-10168-3p88ey --no-same-owner -C /var/opt/lib/pe-puppet/puppet-module/cache/tmp-unpacker20140221-10168-1nlhuor' returned 1: tar: z: unknown function modifier
Usage: tar {c|r|t|u|x}[BDeEFhilmnopPqTvw@[0-7]][bfk][X...] [blocksize] [tarfile] [size] [exclude-file...] {file | -I include-file | -C directory file}...

Error: Try 'puppet help module install' for usage

Jira (PUP-1585) cron resources with target specified generate duplicate entries

2014-02-21 Thread Charlie Sharpsteen (JIRA) 
Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: cron resources with target specified generate duplicate entries 










Felix Frank I've been reviewing this along with PUP-1624 and PR-2342. It seems the problem is both the :user and :target properties of the Cron type try to manage which crontab a job is written into (despite what the docs say these properties are supposed to do). Chaos ensues when these properties are not set to the same value.
Really, it seems that the root cause of this issue is that one of these properties should be depreciated and removed from the Cron type since having both is redundant and only causes confusion.
Does this sound like a correct assessment of the issue?












   

 Add Comment











 













 Puppet /  PUP-1585



  cron resources with target specified generate duplicate entries 







 The following resource results in duplicate cron entry added with each puppet run:  {noformat} cron { 'bacula_vacuumdb':    ensure => present,    minute => '00',    hour => '12',    command => 'vacuumdb --analyze -U postgres bacula',    target => 'postgres',  }{noformat}   Example of Cron:  {noformat}~# crontab -l ...















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

Jira (PUP-1678) Environment Endpoint should show configuration and not all modules

2014-02-21 Thread Andrew Parker (JIRA) 
Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Environment Endpoint should show configuration and not all modules 










Merged into master in 92ef36












   

 Add Comment











 













 Puppet /  PUP-1678



  Environment Endpoint should show configuration and not all modules 







 Right now the environments endpoint is showing all of the modules for an environment. After talking with the group that is going to be using this information, they actually need to know something else. They need to know the settings of the environment, specifically the {{modulepath}} and {{manifest}} values.   We need to remove the list of modules and re...















 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-1585) cron resources with target specified generate duplicate entries

2014-02-21 Thread Felix Frank (JIRA) 
Title: Message Title










 

 Felix Frank commented on an issue











 






  Re: cron resources with target specified generate duplicate entries 










Almost.
I concur that the target property should be deprecated for resources that use the crontab provider. It makes little sense, can be a source of confusion and adds no usability value.
On type level, I'd be inclined to hang on to the property. it's conceivable that future providers will use e.g. files in /etc/cron.d/, in which the user to run the task is explicitly named. Here, the target property does make sense, even though it has a vastly different semantics.
So, let's get rid of it in crontab context, and repurpose it for other possible providers.












   

 Add Comment











 













 Puppet /  PUP-1585



  cron resources with target specified generate duplicate entries 







 The following resource results in duplicate cron entry added with each puppet run:  {noformat} cron { 'bacula_vacuumdb':    ensure => present,    minute => '00',    hour => '12',    command => 'vacuumdb --analyze -U postgres bacula',    target => 'postgres',  }{noformat}   Example of Cron:  {noformat}~# crontab -l ...















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

Jira (PUP-1585) cron resources with target specified generate duplicate entries

2014-02-21 Thread Charlie Sharpsteen (JIRA) 
Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: cron resources with target specified generate duplicate entries 










I guess I'm not proposing getting rid of anything at the moment as that is a discussion for another day when we're closer to Puppet 4. Getting the two properties to sync is definitely the right short term fix.
I just wanted to make sure that I have the problem properly outlined.












   

 Add Comment











 













 Puppet /  PUP-1585



  cron resources with target specified generate duplicate entries 







 The following resource results in duplicate cron entry added with each puppet run:  {noformat} cron { 'bacula_vacuumdb':    ensure => present,    minute => '00',    hour => '12',    command => 'vacuumdb --analyze -U postgres bacula',    target => 'postgres',  }{noformat}   Example of Cron:  {noformat}~# crontab -l ...















 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