Jira (PUP-1712) Add Ubuntu 14.04 to acceptance

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Puppet /  PUP-1712



  Add Ubuntu 14.04 to acceptance 










Change By:

 Kylo Ginsberg




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/d/optout.

Jira (PUP-1712) Add Ubuntu 14.04 to acceptance

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Add Ubuntu 14.04 to acceptance 










In testing from packages this fails during beaker's package installation steps because beaker is using a(n unneeded) apt-get flag, no longer tolerated by trusty's version of apt-get. This was fixed with https://github.com/puppetlabs/beaker/pull/219, which is already merged to beaker.
So next steps include:


We'll need a new version of the beaker gem with the fix above.


Before we can use that, we need to merge https://github.com/puppetlabs/puppet/pull/2556


Bump acceptance/Gemfile to use the new version of the beaker gem.


Try it again ...














   

 Add Comment











 













 Puppet /  PUP-1712



  Add Ubuntu 14.04 to acceptance 














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

Jira (PUP-2080) Support functions written in pp

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Support functions written in pp 










It really should be a QualifiedName if it should behave the same way as if :FUNCTION was not a token. I.e, like this:



Function
  : FUNCTION { result = Factory.QNAME(val[0][:value]) ; loc result, val[0] }



We can use that method when we know the string is not a number.
The 'literal' method produces LiteralStringExpression (i.e. 'function') when given a string. A bare word (that is not an upper case word) produces a QualifiedName (what QNAME factory method produces).
It is the evaluator that turns bare words (i.e. QualifiedName) into a String. It would otherwise not be possible to differentiate between:



"foo"()  # illegal
foo()   # legal, call foo



However , by making it a literal string, we block it from being used as a name, and thus no one can use it as the name of a class, or define, or call a function called 'function'. In a way that reserves it, but people may still need to change their logic later - i.e. $a = function will be a syntax error.
Options:


keep it the way you change it


change it to emit a QualitifedName (i.e. call QNAME instead of literal)


add back FunctionDefinition, and create it, but without any content except the name, then validate it as reserved (this means also adding back a label and a dumper for it, and it is possible to test that it is reserved).


add a general ReservedWordExpression, and validate that


I think option 3 is the best if we want it to not be transparent, option 2 otherwise.












   

 Add Comment










   

Jira (PUP-2080) Support functions written in pp

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Support functions written in pp 










Henrik Lindberg, yeah, I considered putting together the "reserved" model for it, but didn't want to get too side tracked. I chose it to emit the string because that is what I thought it would end up becoming if the FUNCTION token didn't exist. Was that wrong? Would it have been something else? I thought it was just a bareword that ends up being a string.












   

 Add Comment











 













 Puppet /  PUP-2080



  Support functions written in pp 







 Add the ability to write functions in the puppet language.  Functions should be stored under ./functions relative to the root of a module.   Function names should support fully qualified names.















 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/d/op

Jira (PUP-2080) Support functions written in pp

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Support functions written in pp 










I made a comment in the revert about what the grammar builds when it sees the :FUNCTION token. Was the choice of literal string deliberate to block it as a name - i.e. making it a string ? If we want to reserve it (and some additional keywords later), maybe we should do that differently? (in a way it is almost better if it results in an _expression_ that is validated to be "reserved" or similar.












   

 Add Comment











 













 Puppet /  PUP-2080



  Support functions written in pp 







 Add the ability to write functions in the puppet language.  Functions should be stored under ./functions relative to the root of a module.   Function names should support fully qualified names.















 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 

Jira (PUP-2190) Accessing resource metaparameters fails in future evaluator

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow assigned an issue to Unassigned











 






 Puppet /  PUP-2190



  Accessing resource metaparameters fails in future evaluator 










Change By:

 Joshua Partlow




Assignee:

 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/d/optout.

Jira (PUP-2213) The environmentpath setting is ignored by puppet faces unless set in [main]

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: The environmentpath setting is ignored by puppet faces unless set in [main] 










Merged in e21cc5












   

 Add Comment











 













 Puppet /  PUP-2213



  The environmentpath setting is ignored by puppet faces unless set in [main] 







 [~nick.fagerlund] noticed:   1) with environmentpath set in [main],   {code}  puppet config print manifest modulepath --environment doesnotexist  manifest = no_manifest  modulepath =  {code}   is picking up the default configured environment I believe.   2) with environmentpath set in [master]   {code}  puppet config print manifest modulepath --envi...















 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/d/optout.

Jira (PUP-2238) ACL Module - Targeting File Reports Changes for Each Run

[Rob Reynolds (JIRA)]

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: ACL Module - Targeting File Reports Changes for Each Run 










Tony did you run this against a file or a folder? The apearance of your message looks like a directory.
On Friday, April 18, 2014, Tony Vu (JIRA) 
–  Rob Reynolds Developer, Puppet Labs
Join us at **PuppetConf 2014*, September 23-24 in San Francisco


http://puppetconf.com *














   

 Add Comment











 













 Puppet /  PUP-2238



  ACL Module - Targeting File Reports Changes for Each Run 














 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/d/optout.

Jira (PDB-585) PR (927): Allow gem source to come from env vars - grimradical

[Deepak Giridharagopal (JIRA)]

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-585



  PR (927): Allow gem source to come from env vars - grimradical 










Change By:

 Deepak Giridharagopal




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/d/optout.

Jira (PDB-565) Support trusted facts in PuppetDB fact storage

[Patrick Carlisle (JIRA)]

Title: Message Title










 

 Patrick Carlisle commented on an issue











 






  Re: Support trusted facts in PuppetDB fact storage 










Lindsey Smith PO To clarify, the NC service does not use data from PuppetDB to make decisions. We'll need to use PuppetDB from the Console UI in order to show previews of NC changes and estimate current groups.












   

 Add Comment











 













 PuppetDB /  PDB-565



  Support trusted facts in PuppetDB fact storage 







 Since Puppet 3.4, we've added a new top-scope, immutable hash called 'trusted' which is exposed in the DSL and populated with the authenticated certname from the SSL certificate that made the catalog request. In addition, custom attributes can be added to the certificate and will also show up in the trusted hash (see http://docs.puppetlabs.com/puppet/late...















 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

Jira (PUP-2190) Accessing resource metaparameters fails in future evaluator

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow assigned an issue to Joshua Partlow











 






 Puppet /  PUP-2190



  Accessing resource metaparameters fails in future evaluator 










Change By:

 Joshua Partlow




Assignee:

 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/d/optout.

Jira (PUP-2215) An existing directory environment will use config_version from an underlying legacy environment of the same name.

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: An existing directory environment will use config_version from an underlying legacy environment of the same name. 










This does indeed look to be fixed in 3.6.0. I'm bumping this over to functional review for another pair of eyes.












   

 Add Comment











 













 Puppet /  PUP-2215



  An existing directory environment will use config_version from an underlying legacy environment of the same name. 







 [~nick.fagerlund] also noticed the following excitement:  Given a puppet.conf:  {code} environmentpath=$confdir/environments [legacy] config_version = /usr/bin/false {code}  And a directory $confdir/environments/legacy  then you have:  {code} [root@ueu8qnql450gx07 ~]# puppet agent -t --environment legacy Info: Retrieving pluginfacts Info: Retrieving plugi...















 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://gr

Jira (PDB-585) PR (927): Allow gem source to come from env vars - grimradical

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-585



  PR (927): Allow gem source to come from env vars - grimradical 










Change By:

 Kenneth Barber




Sprint:

 20140409 to 20140423












   

 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/d/optout.

Jira (PUP-2215) An existing directory environment will use config_version from an underlying legacy environment of the same name.

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-2215



  An existing directory environment will use config_version from an underlying legacy environment of the same name. 










Change By:

 Joshua Partlow









 [~nick.fagerlund] also noticed the following excitement:   Given a puppet.conf:   {code}   environmentpath=$ condir confdir /environments   [legacy]   config_version = /usr/bin/false   {code}   And a directory $confdir/environments/legacy   then you have:   {code}   [root@ueu8qnql450gx07 ~]# puppet agent -t --environment legacy   Info: Retrieving pluginfacts   Info: Retrieving plugin   Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Execution of config_version command `/usr/bin/false` failed: Execution of '/usr/bin/false' returned 1:  on node ueu8qnql450gx07.delivery.puppetlabs.net   Warning: Not using cache on failed catalog   Error: Could not retrieve catalog; skipping run   {code}  












   

 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/d/optout.

Jira (PUP-2290) ca_server and directory based environments don't play nice together

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: ca_server and directory based environments don't play nice together 










This must be happening because all requests to the master require an environment. One of the "advantages" of the new directory based environments is that the master is able to determine when an environment doesn't exist and return a 404 for the request. Unfortunately, this means that for requests that have absolutely nothing to do with the environment will still need to use a valid environment in order to be able to make requests to the master.












   

 Add Comment











 













 Puppet /  PUP-2290



  ca_server and directory based environments don't play nice together 







 When a Puppet Master is stared and is a CA but does not have any environments in {{/etc/puppet/environments}} even though it is configured for directory based environments it stops accepting CSR's.   We have a Puppet Master that is CA-only and therefor don't deploy the environments to it. The fix was to simply remove the {{environmentpath}} setting from ...















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

Jira (PUP-2290) ca_server and directory based environments don't play nice together

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: ca_server and directory based environments don't play nice together 










It appears the conditions can be relaxed even further:


The master is configured such that directory environments are enabled.




The agent checks in for the first time and requests a non-existant environment: puppet agent -t --environment=nonexistant














   

 Add Comment











 













 Puppet /  PUP-2290



  ca_server and directory based environments don't play nice together 







 When a Puppet Master is stared and is a CA but does not have any environments in {{/etc/puppet/environments}} even though it is configured for directory based environments it stops accepting CSR's.   We have a Puppet Master that is CA-only and therefor don't deploy the environments to it. The fix was to simply remove the {{environmentpath}} setting from ...















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




 

Jira (PUP-2213) The environmentpath setting is ignored by puppet faces unless set in [main]

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow assigned an issue to Andy Parker











 






 Puppet /  PUP-2213



  The environmentpath setting is ignored by puppet faces unless set in [main] 










Change By:

 Joshua Partlow




Assignee:

 Andy Parker












   

 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/d/optout.

Jira (PUP-2215) An existing directory environment will use config_version from an underlying legacy environment of the same name.

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow assigned an issue to Joshua Partlow











 






 Puppet /  PUP-2215



  An existing directory environment will use config_version from an underlying legacy environment of the same name. 










Change By:

 Joshua Partlow




Assignee:

 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/d/optout.

Jira (PUP-2290) ca_server and directory based environments don't play nice together

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: ca_server and directory based environments don't play nice together 










Managed to re-produce this. Having an external CA is not necessary, the behavior occurs with a vanilla all-in-one master under the following conditions:


The master is configured with an environmentpath that points to an empty or non-existent directory.




The agent is configured to explicitly request an environment ( environment = consuela above).


Digging a little further to see if I can get the root cause of this behavior.












   

 Add Comment











 













 Puppet /  PUP-2290



  ca_server and directory based environments don't play nice together 







 When a Puppet Master is stared and is a CA but does not have any environments in {{/etc/puppet/environments}} even though it is configured for directory based environments it stops accepting CSR's.   We have a Puppet Master that is CA-only and therefor don't deploy the environments to it. The fix was to simply remove the {{environmentpath}} setting from ...















 This message was sent by Atlassian JIRA (v6.

Jira (PUP-2238) ACL Module - Targeting File Reports Changes for Each Run

[Tony Vu (JIRA)]

Title: Message Title










 

 Tony Vu assigned an issue to Tony Vu











 






 Puppet /  PUP-2238



  ACL Module - Targeting File Reports Changes for Each Run 










Change By:

 Tony Vu




Assignee:

 Tony Vu












   

 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/d/optout.

Jira (PUP-2238) ACL Module - Targeting File Reports Changes for Each Run

[Tony Vu (JIRA)]

Title: Message Title










 

 Tony Vu commented on an issue











 






  Re: ACL Module - Targeting File Reports Changes for Each Run 










Verified.
Adding 


 target => "C:\some\filepath" 


 did not add unnecessary reporting during an agent run.












   

 Add Comment











 













 Puppet /  PUP-2238



  ACL Module - Targeting File Reports Changes for Each Run 














 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/d/optout.

Jira (PUP-1799) New Function API

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: New Function API 










I'm going to split up the Function API into 2 parts: an external, simpler form, and an internal larger feature set one. I think this is needed so that we limit the public API for a while until we have some more experience around the larger one that is currently in the code from the initial work.
There is already a ticket (PUP-1806) to handle giving some more polish to how dispatches are declared for varargs, so I'll leave that for now. However, since this is going to be going out in 3.6.0 we need to make clear that none of this API yet final.












   

 Add Comment











 













 Puppet /  PUP-1799



  New Function API 














 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/d/optout.

Jira (PUP-2306) Puppet::Util::Execution.execute no longer returns a String

[Lee Lowder (JIRA)]

Title: Message Title










 

 Lee Lowder created an issue











 






 Puppet /  PUP-2306



  Puppet::Util::Execution.execute no longer returns a String 










Issue Type:

  Bug




Affects Versions:


 3.4.0




Assignee:


 Unassigned




Created:


 18/Apr/14 12:52 PM




Priority:

  Normal




Reporter:

 Lee Lowder










Commit 732d450 ( https://github.com/puppetlabs/puppet/commit/732d450 ) changed the return type of Puppet::Util::Execution.execute from a String, to a new string subclass Puppet::ProcessOutput.
This is not a fully backwards compatible change, and causes problems where things do strict type checking - for example, the chomp() function in stdlib.












   

 Add Comment











 





  

Jira (PUP-2305) atboot time => false always creates /etc/fstab entry

[Alex Sla (JIRA)]

Title: Message Title










 

 Alex Sla updated an issue











 






 Puppet /  PUP-2305



  atboot time => false always creates /etc/fstab entry 










Change By:

 Alex Sla









 While running a mount of  block devices via puppet, there is a problem with attribute {{atboot => false}}. It will always created a entry in the {{/etc/fstab}}, regardless of the atboot value. This will lead to a problem while the OS will then try to mount the block devices at boot time. It's unclean: Is this intended or is this not working?The documentation is point to the fact that this in not supported at 'some' platform. Does this include Linux?Example:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}This will lead to this line in the {{/etc/fstab}}{noformat}/dev/mapper/ torrent- data /var/lib/ transmission-daemon/ downloads ext4 rw 0 0{noformat}I used puppet 3.4.3 on different Ubuntu version (12.04, 13.10 and 14.04) the behavior was always the same.How to reproduce on an example VM:{code}vagrant@example:~$ sudo mkdir -p  /var/lib/downloadsvagrant@example:~$ sudo dd if=/dev/zero of=/asd bs=1M count=1024vagrant@example:~$ sudo losetup /dev/loop0 /asdvagrant@example:~$ sudo mkfs.ext4 /dev/loop0 {code}Now running this {{test.pp}}:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}{noformat}vagrant@example:~$ sudo puppet apply -v -d test.pp Debug: Failed to load library 'selinux' for feature 'selinux'Notice: Compiled catalog for example.vbox.net in environment production in 0.05 secondsDebug: Creating default schedulesDebug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport does not existDebug: Puppet::Type::User::ProviderLdap: true value when expecting falseDebug: Puppet::Type::User::ProviderPw: file pw does not existDebug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not existDebug: /User[puppet]: Provider useradd does not support features libuser; not managing attribute forcelocalDebug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not existDebug: Puppet::Type::Group::ProviderLdap: true value when expecting falseDebug: Puppet::Type::Group::ProviderPw: file pw does not existDebug: /Group[puppet]: Provider groupadd does not support features libuser; not managing attribute forcelocalDebug: Using settings: adding file resource 'privatedir': 'File[/var/lib/puppet/ssl/private]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/lib/puppet/ssl/private"}'Debug: Using settings: adding file resource 'logdir': 'File[/var/log/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/log/puppet"}'Debug: Using settings: adding file resource 'hostcrl': 'File[/var/lib/puppet/ssl/crl.pem]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:file, :owner=>"puppet", :mode=>"644", :backup=>false, :path=>"/var/lib/puppet/ssl/crl.pem"}'Debug: Using settings: adding file resource 'vardir': 'File[/var/lib/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, 

Jira (PUP-2305) atboot time => false always creates /etc/fstab entry

[Alex Sla (JIRA)]

Title: Message Title










 

 Alex Sla updated an issue











 






 Puppet /  PUP-2305



  atboot time => false always creates /etc/fstab entry 










Change By:

 Alex Sla









 While running a mount of  block devices via puppet, there is a problem with attribute {{atboot => false}}. It will always created a entry in the {{/etc/fstab}}, regardless of the atboot value. This will lead to a problem while the OS will then try to mount the block devices at boot time. It's unclean: Is this intended or is this not working?The documentation is point to the fact that this in not supported at 'some' platform. Does this include Linux?Example:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}This will lead to this line in the {{/etc/fstab}}{noformat}/dev/mapper/torrent-data /var/lib/transmission-daemon/downloads ext4 rw 0 0{noformat}I used puppet 3.4.3 on different Ubuntu version (12.04, 13.10 and 14.04) the behavior was always the same.How to reproduce on an example VM:{code}vagrant@example:~$ sudo mkdir -p  /var/lib/downloadsvagrant@example:~$ sudo dd if=/dev/zero of=/asd bs=1M count=1024vagrant@example:~$ sudo losetup /dev/loop0 /asdvagrant@example:~$ sudo mkfs.ext4 /dev/loop0 {code}Now running this {{test.pp}}:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}{noformat}vagrant@example:~$ sudo puppet apply -v -d test.pp Debug: Failed to load library 'selinux' for feature 'selinux'Notice: Compiled catalog for example.vbox.net in environment production in 0.05 secondsDebug: Creating default schedulesDebug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport does not existDebug: Puppet::Type::User::ProviderLdap: true value when expecting falseDebug: Puppet::Type::User::ProviderPw: file pw does not existDebug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not existDebug: /User[puppet]: Provider useradd does not support features libuser; not managing attribute forcelocalDebug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not existDebug: Puppet::Type::Group::ProviderLdap: true value when expecting falseDebug: Puppet::Type::Group::ProviderPw: file pw does not existDebug: /Group[puppet]: Provider groupadd does not support features libuser; not managing attribute forcelocalDebug: Using settings: adding file resource 'privatedir': 'File[/var/lib/puppet/ssl/private]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/lib/puppet/ssl/private"}'Debug: Using settings: adding file resource 'logdir': 'File[/var/log/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/log/puppet"}'Debug: Using settings: adding file resource 'hostcrl': 'File[/var/lib/puppet/ssl/crl.pem]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:file, :owner=>"puppet", :mode=>"644", :backup=>false, :path=>"/var/lib/puppet/ssl/crl.pem"}'Debug: Using settings: adding file resource 'vardir': 'File[/var/lib/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :own

Jira (PUP-2305) atboot time => false always creates /etc/fstab entry

[Alex Sla (JIRA)]

Title: Message Title










 

 Alex Sla updated an issue











 






 Puppet /  PUP-2305



  atboot time => false always creates /etc/fstab entry 










Change By:

 Alex Sla









 While running a mount of  block devices via puppet, there is a problem with attribute {{atboot => false}}. It will always created a entry in the {{/etc/fstab}}, regardless of the atboot value. This will lead to a problem while the OS will then try to mount the block devices at boot time. It's unclean: Is this intended or is this not working?The documentation is point to the fact that this in not supported at 'some' platform. Does this include Linux?Example:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}This will lead to this line in the {{/etc/fstab}}{noformat}/dev/mapper/torrent-data /var/lib/transmission-daemon/downloads ext4 rw 0 0{noformat}I used puppet 3.4.3 on different Ubuntu version (12.04, 13.10 and 14.04) the behavior was always the same.How to reproduce on an example VM:{code}vagrant@example:~$ sudo mkdir -p  /var/lib/downloadsvagrant@example:~$ sudo dd if=/dev/zero of=/asd bs=1M count=1024vagrant@example:~$ sudo losetup /dev/loop0 /asdvagrant@example:~$ sudo mkfs.ext4 /dev/loop0 {code}Now running this {{test.pp}}:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}{noformat}vagrant@example:~$ sudo puppet apply -v -d test.pp Debug: Failed to load library 'selinux' for feature 'selinux'Notice: Compiled catalog for example.vbox.net in environment production in 0.05 secondsDebug: Creating default schedulesDebug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport does not existDebug: Puppet::Type::User::ProviderLdap: true value when expecting falseDebug: Puppet::Type::User::ProviderPw: file pw does not existDebug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not existDebug: /User[puppet]: Provider useradd does not support features libuser; not managing attribute forcelocalDebug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not existDebug: Puppet::Type::Group::ProviderLdap: true value when expecting falseDebug: Puppet::Type::Group::ProviderPw: file pw does not existDebug: /Group[puppet]: Provider groupadd does not support features libuser; not managing attribute forcelocalDebug: Using settings: adding file resource 'privatedir': 'File[/var/lib/puppet/ssl/private]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/lib/puppet/ssl/private"}'Debug: Using settings: adding file resource 'logdir': 'File[/var/log/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/log/puppet"}'Debug: Using settings: adding file resource 'hostcrl': 'File[/var/lib/puppet/ssl/crl.pem]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:file, :owner=>"puppet", :mode=>"644", :backup=>false, :path=>"/var/lib/puppet/ssl/crl.pem"}'Debug: Using settings: adding file resource 'vardir': 'File[/var/lib/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :own

Jira (PUP-2305) atboot time => false always creates /etc/fstab entry

[Alex Sla (JIRA)]

Title: Message Title










 

 Alex Sla updated an issue











 






 Puppet /  PUP-2305



  atboot time => false always creates /etc/fstab entry 










Change By:

 Alex Sla









 While running a mount of  block devices via puppet, there is a problem with attribute {{atboot => false}}. It will always created a entry in the {{/etc/fstab}}, regardless of the atboot value. This will lead to a problem while the OS will then try to mount the block devices at boot time. It's unclean: Is this intended or is this not working?The documentation is point to the fact that this in not supported at 'some' platform. Does this include Linux?Example:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}This will lead to this line in the {{/etc/fstab}}{noformat}/dev/mapper/torrent-data /var/lib/transmission-daemon/downloads ext4 rw 0 0{noformat}I used puppet 3.4.3 on different Ubuntu version (12.04, 13.10 and 14.04) the behavior was always the same.How to reproduce on an example VM:{code}vagrant@example:~$ sudo mkdir -p  /var/lib/downloadsvagrant@example:~$ sudo dd if=/dev/zero of=/asd bs=1M count=1024vagrant@example:~$ sudo losetup /dev/loop0 /asdvagrant@example:~$ sudo mkfs.ext4 /dev/loop0 {code}Now running this {{test.pp}}:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}{noformat}vagrant@example:~$ sudo puppet apply -v -d test.pp Debug: Failed to load library 'selinux' for feature 'selinux'Notice: Compiled catalog for example.vbox.net in environment production in 0.05 secondsDebug: Creating default schedulesDebug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport does not existDebug: Puppet::Type::User::ProviderLdap: true value when expecting falseDebug: Puppet::Type::User::ProviderPw: file pw does not existDebug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not existDebug: /User[puppet]: Provider useradd does not support features libuser; not managing attribute forcelocalDebug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not existDebug: Puppet::Type::Group::ProviderLdap: true value when expecting falseDebug: Puppet::Type::Group::ProviderPw: file pw does not existDebug: /Group[puppet]: Provider groupadd does not support features libuser; not managing attribute forcelocalDebug: Using settings: adding file resource 'privatedir': 'File[/var/lib/puppet/ssl/private]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/lib/puppet/ssl/private"}'Debug: Using settings: adding file resource 'logdir': 'File[/var/log/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/log/puppet"}'Debug: Using settings: adding file resource 'hostcrl': 'File[/var/lib/puppet/ssl/crl.pem]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:file, :owner=>"puppet", :mode=>"644", :backup=>false, :path=>"/var/lib/puppet/ssl/crl.pem"}'Debug: Using settings: adding file resource 'vardir': 'File[/var/lib/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :own

Jira (PUP-2305) atboot time => false always creates /etc/fstab entry

[Alex Sla (JIRA)]

Title: Message Title










 

 Alex Sla updated an issue











 






 Puppet /  PUP-2305



  atboot time => false always creates /etc/fstab entry 










Change By:

 Alex Sla









 While running a mount of  block devices via puppet, there is a problem with attribute {{atboot => false}}. It will always created a entry in the {{/etc/fstab}}, regardless of the atboot value. This will lead to a problem while the OS will then try to mount the block devices at boot time. It's unclean: Is this intended or is this not working?The documentation is point to the fact that this in not supported at 'some' platform. Does this include Linux?Example:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}This will lead to this line in the {{/etc/fstab}}{noformat}/dev/mapper/torrent-data /var/lib/transmission-daemon/downloads ext4 rw 0 0{noformat}I used puppet 3.4.3 on different Ubuntu version (12.04, 13.10 and 14.04) the behavior was always the same.How to reproduce on an example VM:{code}vagrant@example:~$ sudo mkdir -p  /var/lib/downloadsvagrant@example:~$ sudo dd if=/dev/zero of=/asd bs=1M count=1024vagrant@example:~$ sudo losetup /dev/loop0 /asdvagrant@example:~$ sudo mkfs.ext4 /dev/loop0 {code}Now running this {{test.pp}}:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}{noformat}vagrant@example:~$ sudo puppet apply -v -d test.pp Debug: Failed to load library 'selinux' for feature 'selinux'Notice: Compiled catalog for example.vbox.net in environment production in 0.05 secondsDebug: Creating default schedulesDebug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport does not existDebug: Puppet::Type::User::ProviderLdap: true value when expecting falseDebug: Puppet::Type::User::ProviderPw: file pw does not existDebug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not existDebug: /User[puppet]: Provider useradd does not support features libuser; not managing attribute forcelocalDebug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not existDebug: Puppet::Type::Group::ProviderLdap: true value when expecting falseDebug: Puppet::Type::Group::ProviderPw: file pw does not existDebug: /Group[puppet]: Provider groupadd does not support features libuser; not managing attribute forcelocalDebug: Using settings: adding file resource 'privatedir': 'File[/var/lib/puppet/ssl/private]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/lib/puppet/ssl/private"}'Debug: Using settings: adding file resource 'logdir': 'File[/var/log/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/log/puppet"}'Debug: Using settings: adding file resource 'hostcrl': 'File[/var/lib/puppet/ssl/crl.pem]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:file, :owner=>"puppet", :mode=>"644", :backup=>false, :path=>"/var/lib/puppet/ssl/crl.pem"}'Debug: Using settings: adding file resource 'vardir': 'File[/var/lib/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :own

Jira (PUP-2305) atboot time => false always creates /etc/fstab entry

[Alex Sla (JIRA)]

Title: Message Title










 

 Alex Sla updated an issue











 






 Puppet /  PUP-2305



  atboot time => false always creates /etc/fstab entry 










Picture of a example vagrant VM.










Change By:

 Alex Sla




Attachment:

 rdesktop - 127.0.01_006.png












   

 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/d/optout.

Jira (PUP-2305) atboot time => false always creates /etc/fstab entry

[Alex Sla (JIRA)]

Title: Message Title










 

 Alex Sla updated an issue











 






 Puppet /  PUP-2305



  atboot time => false always creates /etc/fstab entry 










Change By:

 Alex Sla









 While running a mount of  block devices via puppet, there is a problem with attribute {{atboot => false}}. It will always created a entry in the {{/etc/fstab}}, regardless of the atboot value. This will lead to a problem while the OS will then try to mount the block devices at boot time. It's unclean: Is this intended or is this not working?The documentation is point to the fact that this in not supported at 'some' platform. Does this include Linux?Example:{code} :   mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}This will lead to this line in the {{/etc/fstab}}{noformat}/dev/mapper/torrent-data /var/lib/transmission-daemon/downloads ext4 rw 0 0{noformat}I used puppet 3.4.3 on different Ubuntu version (12.04, 13.10 and 14.04) the behavior was always the same.How to reproduce on an example VM:{code}vagrant@example:~$ sudo mkdir -p  /var/lib/downloadsvagrant@example:~$ sudo dd if=/dev/zero of=/asd bs=1M count=1024vagrant@example:~$ sudo losetup /dev/loop0 /asdvagrant@example:~$ sudo mkfs.ext4 /dev/loop0 {code}Now running this {{test.pp}}:{code}  mount {'data':ensure  => mounted,atboot  => false,device  => '/dev/mapper/data',fstype  => ext4,options => 'rw',name=> '/var/lib/downloads',  }{code}{noformat}vagrant@example:~$ sudo puppet apply -v -d test.pp Debug: Failed to load library 'selinux' for feature 'selinux'Notice: Compiled catalog for example.vbox.net in environment production in 0.05 secondsDebug: Creating default schedulesDebug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport does not existDebug: Puppet::Type::User::ProviderLdap: true value when expecting falseDebug: Puppet::Type::User::ProviderPw: file pw does not existDebug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not existDebug: /User[puppet]: Provider useradd does not support features libuser; not managing attribute forcelocalDebug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not existDebug: Puppet::Type::Group::ProviderLdap: true value when expecting falseDebug: Puppet::Type::Group::ProviderPw: file pw does not existDebug: /Group[puppet]: Provider groupadd does not support features libuser; not managing attribute forcelocalDebug: Using settings: adding file resource 'privatedir': 'File[/var/lib/puppet/ssl/private]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/lib/puppet/ssl/private"}'Debug: Using settings: adding file resource 'logdir': 'File[/var/log/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :backup=>false, :path=>"/var/log/puppet"}'Debug: Using settings: adding file resource 'hostcrl': 'File[/var/lib/puppet/ssl/crl.pem]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:file, :owner=>"puppet", :mode=>"644", :backup=>false, :path=>"/var/lib/puppet/ssl/crl.pem"}'Debug: Using settings: adding file resource 'vardir': 'File[/var/lib/puppet]{:group=>"puppet", :loglevel=>:debug, :links=>:follow, :ensure=>:directory, :

Jira (PUP-2305) atboot time => false always creates /etc/fstab entry

[Alex Sla (JIRA)]

Title: Message Title










 

 Alex Sla created an issue











 






 Puppet /  PUP-2305



  atboot time => false always creates /etc/fstab entry 










Issue Type:

  Bug




Affects Versions:


 3.4.3




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 18/Apr/14 12:10 PM




Environment:


Ubuntu 12.04 Ubuntu 13.10 Ubuntu 14.04




Fix Versions:


 3.4.3




Labels:


 block devices mount fstab




Priority:

  Minor




Reporter:

 Alex Sla










While running a mount of block devices via puppet, there is a problem with attribute atboot => false. It will always created a e

Jira (PUP-1806) Varargs support for the new function API

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Varargs support for the new function API 










Description from 

PUP-2245
, which is a duplicate of this.

Right now the interface for the new function api to specify parameters is (for example):



param Integer, 'a'
param Integer, 'b'
arg_count 1, 2



The param calls are fairly obvious, but the arg_count is hard to understand. We should extend the functionality of param to be able to express "required", "optional", and "last-captures-rest" kinds of parameters.












   

 Add Comment











 













 Puppet /  PUP-1806



  Varargs support for the new function API 







 There needs to be some way of specify varargs in the new function API, but in a way that still lets us do some type checking of the arguments.















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




 


  

Jira (PUP-2304) Implement "requirements" support for the PMT

[Pieter van de Bruggen (JIRA)]

Title: Message Title










 

 Pieter van de Bruggen created an issue











 






 Puppet /  PUP-2304



  Implement "requirements" support for the PMT 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 18/Apr/14 11:56 AM




Fix Versions:


 3.7.0




Priority:

  Normal




Reporter:

 Pieter van de Bruggen










We should implement support for validated (at install time) requirements for modules, particularly for Puppet and Facter. As an example, if a release of module is published with a 'puppet' requirement and the current Puppet version does not fall in that range PMT should refuse to install that release.
This behaviour can be bypassed with the --ignore-requirements flag.
When a module fails to install because of not matching a requirement the user should be informed and given the option to use the --ignore-requirements flag to bypass this.












   

 Add Comment






 

Jira (PDB-565) Support trusted facts in PuppetDB fact storage

[Lindsey Smith PO (JIRA)]

Title: Message Title










 

 Lindsey Smith PO commented on an issue











 






  Re: Support trusted facts in PuppetDB fact storage 










Kenneth Barber If I understand correctly, until trusted facts are in PuppetDB then the NC service cannot make decisions based on them. And the same would be true when, eventually, structured facts were available to Puppet.












   

 Add Comment











 













 PuppetDB /  PDB-565



  Support trusted facts in PuppetDB fact storage 







 Since Puppet 3.4, we've added a new top-scope, immutable hash called 'trusted' which is exposed in the DSL and populated with the authenticated certname from the SSL certificate that made the catalog request. In addition, custom attributes can be added to the certificate and will also show up in the trusted hash (see http://docs.puppetlabs.com/puppet/late...















 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

Jira (PUP-2080) Support functions written in pp

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2080



  Support functions written in pp 










Change By:

 Andy Parker




Sprint:

 Week 2014-4-02 to 2014-4-09, Week 2014-4-09 to 2014-4-16 , Week 2014-4-16 to 2014-4-23












   

 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/d/optout.

Jira (PUP-2080) Support functions written in pp

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Support functions written in pp 










Reverted in 97d84e5












   

 Add Comment











 













 Puppet /  PUP-2080



  Support functions written in pp 







 Add the ability to write functions in the puppet language.  Functions should be stored under ./functions relative to the root of a module.   Function names should support fully qualified names.















 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/d/optout.

Jira (PUP-2080) Support functions written in pp

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2080



  Support functions written in pp 










Change By:

 Andy Parker




Sprint:

 Week 2014-4-02 to 2014-4-09, Week 2014-4-09 to 2014-4-16 , Week 2014-4-16 to 2014-4-23












   

 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/d/optout.

Jira (PUP-2080) Support functions written in pp

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker assigned an issue to Joshua Partlow











 






 Puppet /  PUP-2080



  Support functions written in pp 










Change By:

 Andy Parker




Assignee:

 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/d/optout.

Jira (PUP-1699) Cache environments

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-1699



  Cache environments 










Change By:

 Andy Parker




Assignee:

 Henrik Lindberg












   

 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/d/optout.

Jira (PUP-2303) ArgumentErrors in file_server config parser are swallowed by raising the error wrong

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier commented on an issue











 






  Re: ArgumentErrors in file_server config parser are swallowed by raising the error wrong 










https://github.com/puppetlabs/puppet/pull/2553












   

 Add Comment











 













 Puppet /  PUP-2303



  ArgumentErrors in file_server config parser are swallowed by raising the error wrong 







 Within the parser for the file_serving config, multiple ArgumentErrors are raised with the wrong amount of arguments, raising a different ArgumentError.   Like: Yo dawg, I heard you like ArgumentErrors so I put an ArgumentError in your ArgumentError.   PR coming.















 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/d/optout.

Jira (PUP-2303) ArgumentErrors in file_server config parser are swallowed by raising the error wrong

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier updated an issue











 






 Puppet /  PUP-2303



  ArgumentErrors in file_server config parser are swallowed by raising the error wrong 










Change By:

 Peter Meier




Summary:

 ArgumentErrors in file_server config parser are swallowed by raising the  exception  error  wrong












   

 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/d/optout.

Jira (PUP-2303) ArgumentErrors in file_server config parser are swallowed by raising the exception wrong

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier created an issue











 






 Puppet /  PUP-2303



  ArgumentErrors in file_server config parser are swallowed by raising the exception wrong 










Issue Type:

  Bug




Affects Versions:


 3.5.1




Assignee:


 Unassigned




Created:


 18/Apr/14 11:09 AM




Priority:

  Normal




Reporter:

 Peter Meier










Within the parser for the file_serving config, multiple ArgumentErrors are raised with the wrong amount of arguments, raising a different ArgumentError.
Like: Yo dawg, I heard you like ArgumentErrors so I put an ArgumentError in your ArgumentError.
PR coming.












   

 Add Comment











 

Jira (PDB-585) PR (927): Allow gem source to come from env vars - grimradical

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (927): Allow gem source to come from env vars - grimradical 










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












   

 Add Comment











 













 PuppetDB /  PDB-585



  PR (927): Allow gem source to come from env vars - grimradical 







 h2. Allow gem source to come from env vars   * Author: Deepak Giridharagopal <>  * Company:   * Github ID: [grimradical|https://github.com/grimradical]  * [Pull Request 927 Discussion|https://github.com/puppetlabs/puppetdb/pull/927]  * [Pull Request 927 File Diff|https://github.com/puppetlabs/puppetdb/pull/927/files]  h2. Pull Request Description   Th...















 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://gro

Jira (PUP-2300) Prune dead code from PMT

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2300



  Prune dead code from PMT 










Change By:

 Kenn Hussey




Fix Version/s:

 3.6.0




Fix Version/s:

 3.7.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/d/optout.

Jira (PUP-2301) puppet module list --tree output shows dependencies incorrectly

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2301



  puppet module list --tree output shows dependencies incorrectly 










Change By:

 Kenn Hussey




Fix Version/s:

 3.6.0




Fix Version/s:

 3.7.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/d/optout.

Jira (PDB-465) Add Trusty (Ubuntu 14.04) Packaging Support

[Melissa Stone (JIRA)]

Title: Message Title










 

 Melissa Stone commented on an issue











 






  Re: Add Trusty (Ubuntu 14.04) Packaging Support 










Kenneth Barber This builds and installs for Trusty. I tested the build off the master branch, but I wanted to see if you were interested in getting this out as 1.6.3? We can just build the package, smoke test the one, and drop it in to the public repos if you are interested.












   

 Add Comment











 













 PuppetDB /  PDB-465



  Add Trusty (Ubuntu 14.04) Packaging Support 







 This involves adding/updating spen and acceptance tests for trusty, and making sure the build_defaults has been updated accordingly















 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/d/optout.

Jira (PUP-2144) yumhelper.py uses whichever python shows up in the path first

[Dominic Cleal (JIRA)]

Title: Message Title










 

 Dominic Cleal commented on an issue











 






  Re: yumhelper.py uses whichever python shows up in the path first 










This is much the same problem as described (poorly) in PUP-1362. I think my comment here still applies: https://tickets.puppetlabs.com/browse/PUP-1362?focusedCommentId=56377&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-56377
We could probably safely hardcode /usr/bin/python, or prefer /usr/bin/python to run yumhelper and fall back to the current "command" search of PATH.












   

 Add Comment











 













 Puppet /  PUP-2144



  yumhelper.py uses whichever python shows up in the path first 







 You'll get an error like this if you install a newer version of python and it shows up in the path before the system python that yum uses.   {noformat}  Error: Could not prefetch package provider 'yum': Execution of '/usr/local/bin/python /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/package/yumhelper.py' returned 1: 














 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 

Jira (PUP-916) Document report format changes for improved agent reporting

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Document report format changes for improved agent reporting 










Jason Antman yeah this makes me sad too. The hold-up is just there being too few hours in the day.
Wrt PE, rest assured I totally agree that they're just one more consumer of the report format, and in fact are mostly an interested stakeholder rather than a definer of the details. E.g. the current breakdown of tasks in the linked epic (PUP-283) was motivated in part by conversations in IRC a few months ago.
If you have additional error scenarios or additional comments on what report changes you'd like to see (or patches :>), please add them to either this ticket or the parent epic.












   

 Add Comment











 













 Puppet /  PUP-916



  Document report format changes for improved agent reporting 







 This should allow the report reader to determine:  * if a cached catalog was used  * if so, whether it was due to preference or an error during the agent run  * if an error, at what step in the agent run  * if during catalog compilation, any error messages the server makes available   This proposal should be run by the PE / PuppetDB folks since they will...















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




 

Jira (PUP-2080) Support functions written in pp

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2080



  Support functions written in pp 










Change By:

 Andy Parker




Sprint:

 Week 2014-4-02 to 2014-4-09, Week 2014-4-09 to 2014-4-16 , Week 2014-4-16 to 2014-4-23












   

 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/d/optout.

Jira (PUP-2176) 4x function API for puppet function should require namespaced functions

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2176



  4x function API for puppet function should require namespaced functions 










Change By:

 Andy Parker




Sprint:

 Week 2014-4-09 to 2014-4-16 , Week 2014-4-16 to 2014-4-23












   

 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/d/optout.

Jira (PDB-585) PR (927): Allow gem source to come from env vars - grimradical

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-585



  PR (927): Allow gem source to come from env vars - grimradical 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 18/Apr/14 10:07 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Allow gem source to come from env vars


Author: Deepak Giridharagopal <>


Company:


Github ID: grimradical


Pull Request 927 Discussion


Pull Request 927 File Diff


Pull Request Description

This will allow CI (among other things) to use a different mirror should they so choose.

(webhooks-id: 40e932a7b8cb62aa2556351a81eefbd0)



   

Jira (PUP-2176) 4x function API for puppet function should require namespaced functions

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2176



  4x function API for puppet function should require namespaced functions 










Change By:

 Andy Parker




Fix Version/s:

 3.6.0




Fix Version/s:

 4.x












   

 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/d/optout.

Jira (PUP-2176) 4x function API for puppet function should require namespaced functions

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: 4x function API for puppet function should require namespaced functions 










Since we are going to delay trying to get puppet language functions in, I'm removing this for now and putting it back to "Designing". There are still design discussions that need to happen on the puppet-dev list for this and the overall PUP-2080.












   

 Add Comment











 













 Puppet /  PUP-2176



  4x function API for puppet function should require namespaced functions 







 The ability to write functions in the Puppet Programming Language is a new feature slated for Puppet 3.6.0. The current implementation allows such functions to be placed in the global name space. This support also means that functions placed under  {code}  /functions  {code}  are considered global, and functions in the module's name space must...















 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

Jira (PUP-2302) New evaluator does not properly handle resource defaults

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker created an issue











 






 Puppet /  PUP-2302



  New evaluator does not properly handle resource defaults 










Issue Type:

  Bug




Affects Versions:


 3.5.0




Assignee:

 Andy Parker




Components:


 DSL




Created:


 18/Apr/14 9:57 AM




Fix Versions:


 3.x




Priority:

  Normal




Reporter:

 Andy Parker










Resource defaults in the new evaluator appear to not be working for defined resource types.


Testing manifest



define testing::thing($msg = 'param default') {
  notify { 'name': message => $msg }
}

Testing::Thing  {
msg => 'resource default'
}

testing::thing { 'name': }



If the above code is run with the new evaluator, then it will output param default rather than the expected resource default.

Jira (FACT-453) selinux fact fails on centos/lxc

[Kenton Brede (JIRA)]

Title: Message Title










 

 Kenton Brede commented on an issue











 






  Re: selinux fact fails on centos/lxc 










I'm having the same issue with OL6 and facter 2.0.1. It looks like the same bug that was reported here:
https://projects.puppetlabs.com/issues/18429
The patch listed in that thread for /usr/lib/ruby/site_ruby/1.8/facter/selinux.rb also works.












   

 Add Comment











 













 Facter /  FACT-453



  selinux fact fails on centos/lxc 







 facter v2.0.1 spits out this on CentOS 6.5 in lxc.   Could not retrieve fact='selinux', resolution='': Invalid argument - /proc/self/attr/current   This was not a problem with the latest version of facter, before 2.0.















 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/d/op

Jira (PUP-2290) ca_server and directory based environments don't play nice together

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker assigned an issue to Charlie Sharpsteen











 







Charlie Sharpsteen, can you take a look at getting this reproduced?









 Puppet /  PUP-2290



  ca_server and directory based environments don't play nice together 










Change By:

 Andy Parker




Assignee:

 Charlie Sharpsteen












   

 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/d/optout.

Jira (PUP-1089) Integrated variable checking for defines and parameterized classes.

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Integrated variable checking for defines and parameterized classes. 










Before PUP-514 is implemented, the validation can be performed against types manually (when --parser future is used). In Puppet 3.6 --parser future there is a function called assert_type(type, value), that does what the proposed validate "function" does.












   

 Add Comment











 













 Puppet /  PUP-1089



  Integrated variable checking for defines and parameterized classes. 







 I would like the ability to, in the puppet language, check variables being passed to a class or define for validity.   This can currently be done by throwing a ParseError from a template, but that is quite syntactically heavy.   Current Case: define foo ( $bar ) {    inline_template("<% if not ['true','false'].include?(bar) then raise Puppet::...















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

Jira (PUP-2278) puppet module install fails when given path containing spaces

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2278



  puppet module install fails when given path containing spaces 










Change By:

 Kenn Hussey




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/d/optout.

Jira (PUP-2278) puppet module install fails when given path containing spaces

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2278



  puppet module install fails when given path containing spaces 










Change By:

 Kenn Hussey




Component/s:

 PE












   

 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/d/optout.

Jira (PUP-2301) puppet module list --tree output shows dependencies incorrectly

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2301



  puppet module list --tree output shows dependencies incorrectly 










Change By:

 Kenn Hussey




Component/s:

 PE












   

 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/d/optout.

Jira (PUP-2300) Prune dead code from PMT

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2300



  Prune dead code from PMT 










Change By:

 Kenn Hussey




Component/s:

 PE












   

 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/d/optout.

Jira (PUP-2284) Add a user interview for creating a metadata.json file

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2284



  Add a user interview for creating a metadata.json file 










Change By:

 Kenn Hussey




Assignee:

 Pieter van de Bruggen












   

 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/d/optout.

Jira (PUP-2284) Add a user interview for creating a metadata.json file

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2284



  Add a user interview for creating a metadata.json file 










Change By:

 Kenn Hussey




Component/s:

 PE












   

 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/d/optout.

Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-1977



  `puppet module build` should create `metadata.json` instead of `Modulefile` 










Change By:

 Kenn Hussey




Assignee:

 Pieter van de Bruggen












   

 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/d/optout.

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 










Change By:

 Kenn Hussey




Assignee:

 Pieter van de Bruggen












   

 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/d/optout.

Jira (PUP-2301) puppet module list --tree output shows dependencies incorrectly

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2301



  puppet module list --tree output shows dependencies incorrectly 










Change By:

 Kenn Hussey




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/d/optout.

Jira (PUP-2301) puppet module list --tree output shows dependencies incorrectly

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2301



  puppet module list --tree output shows dependencies incorrectly 










Change By:

 Kenn Hussey




Assignee:

 Pieter van de Bruggen












   

 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/d/optout.

Jira (PUP-2300) Prune dead code from PMT

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey created an issue











 






 Puppet /  PUP-2300



  Prune dead code from PMT 










Issue Type:

  Task




Assignee:

 Pieter van de Bruggen




Created:


 18/Apr/14 8:38 AM




Fix Versions:


 3.6.0




Priority:

  Normal




Reporter:

 Kenn Hussey










PMT still contains code paths intended for it's api v1 interactions. These need to be verified and deleted.












   

 Add Comment











 










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




 

Jira (PUP-2301) puppet module list --tree output shows dependencies incorrectly

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey moved an issue











 






 Puppet /  PUP-2301



  puppet module list --tree output shows dependencies incorrectly 










Change By:

 Kenn Hussey




Component/s:

 PE 3.3




Workflow:

 Forge Platform  Workflow




Key:

 PF PUP - 434 2301




Project:

 Puppet  Forge [Internal]












   

 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/d/optout.

Jira (PUP-2284) Add a user interview for creating a metadata.json file

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-2284



  Add a user interview for creating a metadata.json file 










Change By:

 Kenn Hussey




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/d/optout.

Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-1977



  `puppet module build` should create `metadata.json` instead of `Modulefile` 










Change By:

 Kenn Hussey




Fix Version/s:

 3.7.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/d/optout.

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 










Change By:

 Kenn Hussey




Fix Version/s:

 3.7.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/d/optout.

Jira (PUP-1779) "puppet node clean" is hard-coded to use rails/activerecord backend

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: "puppet node clean" is hard-coded to use rails/activerecord backend 










Kenneth Barber, it should already be calling that. It is for the catalog that it doesn't use the indirector. I think you'd need to add a destroy method to the puppetdb catalog terminus.












   

 Add Comment











 













 Puppet /  PUP-1779



  "puppet node clean" is hard-coded to use rails/activerecord backend 







 See #14721.   PuppetDB already has code to remove a node's data ("puppet node deactivate"), but we can't get it to seamlessly work with "puppet node clean" as long as it's hard-coded to assume legacy storeconfigs. This face should use some manner of indirection to allow other storeconfigs backends to participate in node cleanup.















 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 (PUP-1089) Integrated variable checking for defines and parameterized classes.

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-1089



  Integrated variable checking for defines and parameterized classes. 










Change By:

 Andy Parker




Component/s:

 DSL












   

 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/d/optout.

Jira (PUP-2299) A command that times out will not re-execute if "tries" is set.

[Etrik Patricella (JIRA)]

Title: Message Title










 

 Etrik Patricella commented on an issue











 






  Re: A command that times out will not re-execute if "tries" is set. 










This issue is still present as of puppet version 3.5.1












   

 Add Comment











 













 Puppet /  PUP-2299



  A command that times out will not re-execute if "tries" is set. 







 I was expecting something like this to retry execution if the command timed out:   exec { '/path/to/mycommand':    tries => 2,    timeout => 10,  }   Unfortunately, the exception generated by a timeout resumes control outside of the retry loop:   begin    tries.times do |try|  # Only add debug messages for tr...















 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/d/optout.

Jira (PUP-2299) A command that times out will not re-execute if "tries" is set.

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-2299



  A command that times out will not re-execute if "tries" is set. 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 18/Apr/14 6:33 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










I was expecting something like this to retry execution if the command timed out:
 exec  { '/path/to/mycommand': tries => 2, timeout => 10, }
Unfortunately, the exception generated by a timeout resumes control outside of the retry loop:
 begin tries.times do |try|


Only add debug messages for tries > 1 to reduce log spam. debug("Exec try # {try+1}
/# {tries}
") if tries > 1 @output, @status = provider.run(self.resource[:command]) break if self.should.include?(@status.exitstatus.to_s) if try_sleep > 0 and tries > 1 debug("Sleeping for # {try_sleep}
 seconds between tries") sleep try_sleep end end rescue Timeout::Error self.fail "Command exceeded timeout" % value.inspect end


I'm not sure how to deal with commands that may need to be retried due to timeouts. Would it be possible to move the retry loop outside of the try/catch?

Jira (PUP-916) Document report format changes for improved agent reporting

[Jason Antman (JIRA)]

Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Document report format changes for improved agent reporting 










So now this is pushed back to 4.x?
I'm unclear on what the hold-up is here. It doesn't matter how PE wants to present this data to the user; there's a finite amount of data about errors that can be provided by the agent, this seems like it's just a matter of figuring out how to present that data in the report. I'm a bit worried by the idea that this would be done by the PE team, as opposed to PE being just another consumer of the API.












   

 Add Comment











 













 Puppet /  PUP-916



  Document report format changes for improved agent reporting 







 This should allow the report reader to determine:  * if a cached catalog was used  * if so, whether it was due to preference or an error during the agent run  * if an error, at what step in the agent run  * if during catalog compilation, any error messages the server makes available   This proposal should be run by the PE / PuppetDB folks since they will...















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




 














-- 
You received this message because you are subscribed to th

Jira (PUP-1073) Common package name in two different providers

[Jason Antman (JIRA)]

Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Common package name in two different providers 










I'll also throw in my support for Pedro's suggestion. I see the idealistic side of wanting this to work for all types and be fixed in the RAL, but on the other hand, I've heard a lot of complaints/questions/confusion about this issue. Almost all of them involved the Package type. I think even fixing it in a sub-optimal way for the Package type is a big win for end users.












   

 Add Comment











 













 Puppet /  PUP-1073



  Common package name in two different providers 







 I have a common package name, that's in two different package managers  (one with yum the other with gem)   package { "remove-mysql":  name => "mysql",  provider => "yum",  ensure => absent,  }   -   package { "gem-mysql...















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

Jira (PUP-2292) Insufficient tests on yumrepo's => absent

[Julien Pivotto (JIRA)]

Title: Message Title










 

 Julien Pivotto commented on an issue











 






  Re: Insufficient tests on yumrepo's => absent 










Please see https://github.com/puppetlabs/puppet/pull/2545












   

 Add Comment











 













 Puppet /  PUP-2292



  Insufficient tests on yumrepo's => absent 







 When you set => absent on a yumrepo property, the result is a string in ruby. However, it happens that we expect only a symbol there.















 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/d/optout.