date:20141021

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Remove support for yaml on the network 










The exercise of removing yaml on the network and removal of SafeYaml proved to be a bit difficult.


The code paths for serialization and deserialization are quite different which makes the code base time consuming to navigate and understand. Writing goes via ZAML (and monkey patched classes) to YAML (Psych). Reading used to go via SafeYaml via Psych, now directly via Psych.


The act of deserializing is named intern which makes it very hard to find the places that perform deserialization (since there are numerous calls to intern to create symbols)


Serialization is handled by code in the "network" namespace but is also used for serialization that is not "over the network".


Safe Yaml produces hashes whereas Psych Yaml produces object directly.


Some(?, at least one Resource::Status) optimizes serialization to serialize a TagSet as an Array. When Safe Yaml is no longer used the logic in the class is not triggered since Psych sets the values directly with instance_variable_set.


The TagSet class lies in its to_data_hash and returns an Array !!!


Psych has a callback that can take over the setting for all attributes called init_with that is given a Psych::Coder that can be asked for a Hash using the map method. (Older methods yaml_new, yaml_initialize have either been removed or are deprecated, we have some traces of these old methods in our code base - for Ruby 1.8.7 ?)


So, how to fix this mess?


If we want to keep the optimization (avoiding serialization of the list of tags as a Ruby object (causes bloat)) we can:


refactor the logic for TagSet which is a very thin wrapper around a Hash used as a Set. It is typically used via inclusion of the module Tagging - but it is still complicated and affects quite a large portion of the functionality since Tagging is used in many places - not certain if all serialization of a TagSet uses the same optimization though, and if such a change breaks other logic / serialization format/API.


Accept that classes that serialize/deserialize and need processing on deserialization must implement the init_with method

Jira (PUP-1521) Allow configuration of SSL ciphers

2014-10-21 Thread c lang (JIRA)

Title: Message Title










 

 c lang commented on an issue











 






  Re: Allow configuration of SSL ciphers 










Can this be reopened? We can't even vote on it. Thanks!












   

 Add Comment











 













 Puppet /  PUP-1521



  Allow configuration of SSL ciphers 







 We run puppet in a secure environment. One of the policies in place states that no weak ciphers (key length < 128 bit) are allowed anywhere.   Our puppetmasterd got flagged by a review recently as it allows such ciphers on incoming connections. I temporarily worked around it with this horrible hack in /usr/lib/ruby/1.8/webrick/ssl.rb:     ctx.verify...















 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-3471) Windows Puppet x86 Installer on x64 system issue

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Windows Puppet x86 Installer on x64 system issue 










It should work. Can you give it another shot? 












   

 Add Comment











 













 Puppet /  PUP-3471



  Windows Puppet x86 Installer on x64 system issue 







 When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards.   In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments   For example, before Puppet installation we had:  PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo...















 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-3471) Windows Puppet x86 Installer on x64 system issue

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Windows Puppet x86 Installer on x64 system issue 










r...@puppetlabs.com is giving you errors?












   

 Add Comment











 













 Puppet /  PUP-3471



  Windows Puppet x86 Installer on x64 system issue 







 When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards.   In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments   For example, before Puppet installation we had:  PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo...















 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-3471) Windows Puppet x86 Installer on x64 system issue

2014-10-21 Thread Baptiste Hebert (JIRA)

Title: Message Title










 

 Baptiste Hebert commented on an issue











 






  Re: Windows Puppet x86 Installer on x64 system issue 










Just sent it. No error so far 












   

 Add Comment











 













 Puppet /  PUP-3471



  Windows Puppet x86 Installer on x64 system issue 







 When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards.   In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments   For example, before Puppet installation we had:  PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo...















 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-947) Export from puppetdb (HSQLDB) abnormally slow

2014-10-21 Thread Wyatt Alt (JIRA)

Title: Message Title










 

 Wyatt Alt commented on an issue











 






  Re: Export from puppetdb (HSQLDB) abnormally slow 










jon yeargers You could upload it to dropbox, google drive, s3, etc... It's probably too big for email but you can try sending it to wy...@puppetlabs.com as well.












   

 Add Comment











 













 PuppetDB /  PDB-947



  Export from puppetdb (HSQLDB) abnormally slow 







 Started 'puppetdb export --outfile ' on 2014/10/07 06:30 am. As of 2014/10/09 04:00 am it has dumped ~75 / 110 servers.   Expected: it shouldn't take this long. This means the data that will be imported into Postgres (ultimate goal of this exercise) will be > 48 hours out of date.   System: Dell PE 2950 8 Core / 32Gb RAM / CentOS 6.5 x64   Insta...















 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-3471) Windows Puppet x86 Installer on x64 system issue

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Windows Puppet x86 Installer on x64 system issue 










Got it this time. Yes, I should have reminded you to rename the file so it would not get flagged by the email system as a potentially dangerous attachment.












   

 Add Comment











 













 Puppet /  PUP-3471



  Windows Puppet x86 Installer on x64 system issue 







 When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards.   In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments   For example, before Puppet installation we had:  PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo...















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

Jira (PUP-3494) Could not create vm on azure

2014-10-21 Thread Thiago Custodio (JIRA)

Title: Message Title










 

 Thiago Custodio created an issue











 






 Puppet /  PUP-3494



  Could not create vm on azure 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Components:


 Test Infrastructure




Created:


 21/Oct/14 9:25 AM




Environment:


Azure VM created with Puppet Enterprise template




Priority:

  Critical




Reporter:

 Thiago Custodio










I`m trying to automate an infrasctructure using puppet. I could create puppet master an slave using azure portal. Right now, I`m trying to create slaves using puppet cli. I`m following the description from github link.
First, I`ve generated my pem file using the following command:
openssl req \ -x509 -nodes -days 365 \ -newkey rsa:1024 -keyout mycert.pem -out mycert.pem
Then I`ve executed the full command:
puppet azure_vm create --management-certificate pem-or-pfx-file-path --azure-subscription-id=your-subscription-id \ --image b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-13_04-amd64-server-20130501-en-us-30GB --location 'west us'  --vm-name vmname --vm-user username --password ComplexPassword --puppet-master-ip 198.62.195.5
I`ve changed puppet-master-ip and set full path to my pem file on --management-certificate parameter.
I`m getting the following error which give me any idea how to proceed:

Jira (PUP-3372) Remove extlookup function

Title: Message Title










 

 Eric Thompson commented on an issue











 






  Re: Remove extlookup function 










no idea what i was doing yesterday. your commit was in the log, i checked... but it works today, on fedora20 at SHA 4b4cf17 with:






[root@nwcnu55sypxlv68 ~]# puppet apply -e '$extlookup_datadir = "/etc/puppet/manifests/extdata" $extlookup_precedence = "common" $snmp_contact = extlookup("snmp_contact")' --parser future




Error: Evaluation Error: Unknown function: 'extlookup'. at line 1:103 on node nwcnu55sypxlv68.delivery.puppetlabs.net




Error: Evaluation Error: Unknown function: 'extlookup'. at line 1:103 on node nwcnu55sypxlv68.delivery.puppetlabs.net




[root@nwcnu55sypxlv68 ~]# puppet apply -e 'extlookup($foo)'




Error: Unknown function extlookup at line 1 on node nwcnu55sypxlv68.delivery.puppetlabs.net




Error: Unknown function extlookup at line 1 on node nwcnu55sypxlv68.delivery.puppetlabs.net



















   

 Add Comment

Jira (PUP-3404) helper functions in custom function

Title: Message Title










 

 James Shubin commented on an issue











 






  Re: helper functions in custom function 










If you'll allow me a small rant:
This feature (allowing helper functions) somehow dissapeared, as it used to work just fine. I consider this a huge regression, and taking it out without notice, is no way to convince users that puppetlabs is able to maintain stable releases, if the upstream does this. It's also a very useful feature, so seeing this go is sad.

In reply to Andy Parker:
> Please use PuppetX::ModuleOwnerName::ModuleName. This pattern will avoid collisions with other modules. > For example at puppetlabs for the foo module we would put extra helpers in PuppetX::Puppetlabs::Foo.
DON'T do this. It will guarantee that your module is unforkable. binford2k agrees, and instead suggests: 13:48 <@binford2k> Maybe PuppetX::Modulename::Helpers  then
Cheers, James












   

 Add Comment











 













 Puppet /  PUP-3404



  helper functions in custom function 







 Hi,  I have a problem with helper functions in custom function   My puppet-Version: v3.7.1  If you need more information, let me know.  My custom function in very short from, but with the same error.  {noformat}  module Puppet::Parser::Functions    newfunction(:httpd_modules, :type => :rvalue) do |args|  def helper_function(value)    value  e...















 This message was sent by

Jira (PUP-2931) Puppet CA sometimes resets certificate serial counter

2014-10-21 Thread Andy Parker (JIRA)

Title: Message Title

Andy Parker commented on an issue

Re: Puppet CA sometimes resets certificate serial counter

Toomas Pelberg, thanks for brining that up!
According to RFC5280 the maximum length for a serial number is 20 octets (bytes).

Given the uniqueness requirements above, serial numbers can be expected to contain long integers. Certificate users MUST be able to handle serialNumber values up to 20 octets. Conforming CAs MUST NOT use serialNumber values longer than 20 octets.

A UUID is 16 bytes and so fits inside the size limitations of the certificate.
A similar question as this was asked on the OpenSSL users list and the idea of UUIDs was brought up. It appears that the idea of a UUID was acceptable. The better solution, which is recommended in that thread as well as in a previous ticket against puppet itself, is to use chains of authority. A master CA signs the certificates for the various servers and then they get to issue certificates independently. However, that is a much more complicated setup than most puppet users are willing to take on when they just want to scale out their masters. Given the use case of puppet, it seems like using a UUID should work well. There is a slight chance of collision, but such collisions should be highly unlikely and all it would cause, I think, is that a particular certificate with a colliding serial number could not be uniquely revoked. Of course if that occurs, the solution is to simply create a new certificate for the colliding agent.
I'll move this ticket to "accepted", since I don't know when we'll be getting to this on puppet. However, puppet-server is reimplementing the CA and so we'll need to coordinate the two implementations. Christopher Price, do you have any thoughts on this idea?

Add Comment

Puppet / PUP-2931

Puppet CA sometimes resets certificate serial counter

Jira (PUP-3061) Upgrade win32-eventlog to 0.6.2+ once it is released

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3061



  Upgrade win32-eventlog to 0.6.2+ once it is released 










Change By:

 Rob Reynolds




Fix Version/s:

 PUP 3.7.3












   

 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-2931) Puppet CA sometimes resets certificate serial counter

2014-10-21 Thread Christopher Price (JIRA)

Title: Message Title










 

 Christopher Price commented on an issue











 






  Re: Puppet CA sometimes resets certificate serial counter 










We are planning to get rid of that serial.txt file altogether in the Puppet Server CA, to eliminate the race condition and as part of an effort to make it possible to have an HA/load balanced CA setup (to eliminate a single point of failure). That's a little ways down the road and we don't have a final plan for implementation details yet, but hopefully we'll be ironing out the roadmap soon and I can link this to other Jiras that we'll create in the process. I'm totally open to considering the UUID idea, will just need to think through all the use cases, make sure we know how it'd work for upgrades, etc.












   

 Add Comment











 













 Puppet /  PUP-2931



  Puppet CA sometimes resets certificate serial counter 







 We are running our Puppet masters on CentOS 6 with Passenger and stock Apache. Puppet CA's data files reside on NFS storage. Autosigning is turned on.   Sometimes the serials of issued client certificates reset to 0x0001 with serious consequences - when someone revokes the duplicate 0x0001 client's certificate, the CA revokes its own cert too. Revoking ...















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

Jira (PUP-2965) Remove Puppet::Plugins

2014-10-21 Thread Adrien Thebo (JIRA)

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Remove Puppet::Plugins 










Merged in 3d4a2c8.












   

 Add Comment











 













 Puppet /  PUP-2965



  Remove Puppet::Plugins 







 The Puppet::Plugins system is deprecated and needs to be removed at a major version boundary.















 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 (FACT-729) facter prefers hostname -f over hostname

2014-10-21 Thread David Bristow (JIRA)

Title: Message Title










 

 David Bristow created an issue











 






 Facter /  FACT-729



  facter prefers hostname -f over hostname 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 21/Oct/14 11:30 AM




Environment:


Amazon EC2 nodes




Priority:

  Normal




Reporter:

 David Bristow










With facter versions >= 1.7.0, the trailing domain from "hostname -f" is preferred over the domain extracted from the output of "hostname". This bites us as we have customers where their server's hostname is set to their FQDN, and the domain from "hostname -f" is ec2.internal, resulting in facter's fqdn output to be hostname.ec2.internal, instead of hostname.client.com. This doesn't happen with 1.6.x as when the hostname returned by "hostname" has the domain included, and works fine.












   

 Add Comment

Jira (FACT-729) facter prefers hostname -f over hostname

2014-10-21 Thread David Bristow (JIRA)

Title: Message Title










 

 David Bristow updated an issue











 






 Facter /  FACT-729



  facter prefers hostname -f over hostname 










Change By:

 David Bristow









 With facter versions >= 1.7.0, the trailing domain from "hostname -f" is preferred over the domain extracted from the output of "hostname".  This bites us as we have customers where their server's hostname is set to their FQDN, and the domain from "hostname -f" is ec2.internal,  resulting in  making  facter's fqdn  output to be  hostname.ec2.internal ,  instead of hostname.client.com.  This doesn't happen with 1.6.x as when the hostname returned by "hostname" has the domain included, and works fine.












   

 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-3305) Change allow_virtual default to true

Title: Message Title










 

 Eric Thompson updated an issue











 






 Puppet /  PUP-3305



  Change allow_virtual default to true 










Change By:

 Eric Thompson




QA Status:

 Reviewed












   

 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-3495) acceptance pre-suite package install method should accept short SHA

Title: Message Title










 

 Eric Thompson updated an issue











 






 Puppet /  PUP-3495



  acceptance pre-suite package install method should accept short SHA 










Change By:

 Eric Thompson




Assignee:

 Eric Sorenson












   

 Add Comment











 










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




 














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

Jira (PDB-980) Smoke test packages

2014-10-21 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone commented on an issue











 






  Re: Smoke test packages 










packages available at http://builds.puppetlabs.lan/puppetdb/2.2.2/












   

 Add Comment











 













 PuppetDB /  PDB-980



  Smoke test packages 







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















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




 














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

Jira (PUP-3495) acceptance pre-suite package install method should accept short SHA

Title: Message Title










 

 Eric Thompson created an issue











 






 Puppet /  PUP-3495



  acceptance pre-suite package install method should accept short SHA 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Components:


 QA




Created:


 21/Oct/14 11:41 AM




Priority:

  Trivial




Reporter:

 Eric Thompson












   

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

Jira (PDB-980) Smoke test packages

2014-10-21 Thread Wyatt Alt (JIRA)

Title: Message Title










 

 Wyatt Alt commented on an issue











 






  Re: Smoke test packages 










starting testing on debian jessie ami-419ad971












   

 Add Comment











 













 PuppetDB /  PDB-980



  Smoke test packages 







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















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




 














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

Jira (PDB-980) Smoke test packages

2014-10-21 Thread Wyatt Alt (JIRA)

Title: Message Title










 

 Wyatt Alt assigned an issue to Wyatt Alt











 






 PuppetDB /  PDB-980



  Smoke test packages 










Change By:

 Wyatt Alt




Assignee:

 Wyatt Alt












   

 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-3250) Remove secret_agent

Title: Message Title










 

 Eric Thompson commented on an issue











 






  Re: Remove secret_agent 










verified on fedora20 at SHA 3d4a2c8 with:






[root@j4fa5ru7qqa5fef ~]# puppet help secret_agent




Error: Could not load help for the face secret_agent.




[...]




 




[root@j4fa5ru7qqa5fef puppet]# man puppet-secret_agent




No manual entry for puppet-secret_agent




 




[root@j4fa5ru7qqa5fef puppet]# puppet secret_agent -t




Error: Unknown Puppet subcommand 'secret_agent'




See 'puppet help' for help on available puppet subcommands

Jira (PDB-947) Export from puppetdb (HSQLDB) abnormally slow

2014-10-21 Thread jon yeargers (JIRA)

Title: Message Title










 

 jon yeargers commented on an issue











 






  Re: Export from puppetdb (HSQLDB) abnormally slow 










See if this works: https://drive.google.com/file/d/0B-yw5RzCHN0eWElrVFJfdDZNNVk/view?usp=sharing












   

 Add Comment











 













 PuppetDB /  PDB-947



  Export from puppetdb (HSQLDB) abnormally slow 







 Started 'puppetdb export --outfile ' on 2014/10/07 06:30 am. As of 2014/10/09 04:00 am it has dumped ~75 / 110 servers.   Expected: it shouldn't take this long. This means the data that will be imported into Postgres (ultimate goal of this exercise) will be > 48 hours out of date.   System: Dell PE 2950 8 Core / 32Gb RAM / CentOS 6.5 x64   Insta...















 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-3496) Ability to set default provider or require `provider` to be set

2014-10-21 Thread Hunter Haugen (JIRA)

Title: Message Title










 

 Hunter Haugen created an issue











 






 Puppet /  PUP-3496



  Ability to set default provider or require `provider` to be set 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 21/Oct/14 12:16 PM




Priority:

  Normal




Reporter:

 Hunter Haugen










When creating custom types and providers, there is no way to 1) set a globally-default provider, 2) require the user to explicitly set a provider, or 3) get rid of the "Warning: Found multiple default providers for ..." warning without hacky hacks.
More details: 1) globally-default provider provider.rb gives the ability to set defaultfor based on availability of a :feature or on the matching of a fact, but there is no "always default" setting (link). The closest I've gotten is setting defaultfor :feature => :posix (link) when I don't need windows defaults, but ran into trouble when trying to defaultfor on a device because of PUP-2717 (facts don't work for devices). The next best thing was to create a "puppet feature" and use that to set a default (link) (private link). It's all gross.
2) Require the user to explicitly set provider From type.rb during a catalog application, self.instances (which is called before processing catalog resources) calls self.providers_by_source which calls self.defaultprovider which will randomly pick a default provider if no default is discoverable (link). It doesn't seem to care whether a resource has a provider attribute set by self.instances or in the catalog, it still prints a warning.
Then the catalog resource begin their processing and validation, but at that point all types already have a default provider and we cannot tell if a user explicitly set the provider or not, and therefore cannot tell if the provider is even the right one.
The hacky solution to this was to use the "global default" provider hack above, but with a "dummy" resource that just raises an error to tell the user to choose a provider (link) (exce

Jira (PUP-3250) Remove secret_agent

Title: Message Title










 

 Eric Thompson updated an issue











 






 Puppet /  PUP-3250



  Remove secret_agent 










Change By:

 Eric Thompson




QA Contact:

 Erik Dasher Eric Thompson




QA Status:

 Reviewed












   

 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-3302) Puppet resource broken when directory environments enabled

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3302



  Puppet resource broken when directory environments enabled 










Change By:

 Rob Reynolds




Fix Version/s:

 PUP 3.7.2




Fix Version/s:

 PUP 3.7.3












   

 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-3396) Add support for testing 4x functions in modules

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3396



  Add support for testing 4x functions in modules 










Change By:

 Rob Reynolds




Fix Version/s:

 PUP 3.7.2




Fix Version/s:

 PUP 3.7.3












   

 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-2560) Remove inventory service on the master

Title: Message Title










 

 Eric Thompson updated an issue











 






 Puppet /  PUP-2560



  Remove inventory service on the master 










Change By:

 Eric Thompson




QA Contact:

 Kurt Wall Eric Thompson




QA Status:

 Reviewed












   

 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-3227) Upgrade conflict: puppetmaster-common and puppet-common

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3227



  Upgrade conflict: puppetmaster-common and puppet-common 










Change By:

 Rob Reynolds




Fix Version/s:

 PUP 4.0.0




Fix Version/s:

 PUP 3.7.2












   

 Add Comment











 










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




 














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

Jira (PUP-3227) Upgrade conflict: puppetmaster-common and puppet-common

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Upgrade conflict: puppetmaster-common and puppet-common 










Merged into stable at 4e88867c to be released with 3.7.2












   

 Add Comment











 













 Puppet /  PUP-3227



  Upgrade conflict: puppetmaster-common and puppet-common 







 We've already addressed an issue where man pages were moved from the puppet packages to the puppet-common package. Unfortunately, we're seeing this conflict again when upgrading a system with both puppet and puppetmaster installed. The conflict here being that puppetmaster-common now owns man pages that were previously packaged in puppet-common (or at lea...















 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-3227) Upgrade conflict: puppetmaster-common and puppet-common

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3227



  Upgrade conflict: puppetmaster-common and puppet-common 










Change By:

 Rob Reynolds




Sprint:

 Platform Server 2014-10-29












   

 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-3227) Upgrade conflict: puppetmaster-common and puppet-common

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3227



  Upgrade conflict: puppetmaster-common and puppet-common 










Change By:

 Rob Reynolds




Flagged:

 Impediment












   

 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-3227) Upgrade conflict: puppetmaster-common and puppet-common

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3227



  Upgrade conflict: puppetmaster-common and puppet-common 










Change By:

 Rob Reynolds




Component/s:

 Server




Component/s:

 RE












   

 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-3227) Upgrade conflict: puppetmaster-common and puppet-common

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Upgrade conflict: puppetmaster-common and puppet-common 










Kylo Ginsberg Melissa Stone this doesn't have an estimate on it. I assume that since this was merged into stable, it was meant to be released with 3.7.2. If this is not the case we need to fix and remove. I also added to the platform board for this iteration.












   

 Add Comment











 













 Puppet /  PUP-3227



  Upgrade conflict: puppetmaster-common and puppet-common 







 We've already addressed an issue where man pages were moved from the puppet packages to the puppet-common package. Unfortunately, we're seeing this conflict again when upgrading a system with both puppet and puppetmaster installed. The conflict here being that puppetmaster-common now owns man pages that were previously packaged in puppet-common (or at lea...















 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.

Jira (PUP-3227) Upgrade conflict: puppetmaster-common and puppet-common

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3227



  Upgrade conflict: puppetmaster-common and puppet-common 










Change By:

 Rob Reynolds




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 (PUP-3248) Update PMT tests for directory environment support

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3248



  Update PMT tests for directory environment support 










Change By:

 Rob Reynolds




Fix Version/s:

 PUP 3.7.2












   

 Add Comment











 










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




 














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

Jira (PUP-3449) Puppet::Node::Facts allows a fact named 'trusted' that collides with the reserved top scope puppet variable name 'trusted'.

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3449



  Puppet::Node::Facts allows a fact named 'trusted' that collides with the reserved top scope puppet variable name 'trusted'. 










Change By:

 Rob Reynolds




Fix Version/s:

 PUP 3.7.2












   

 Add Comment











 










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




 














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

Jira (PUP-3226) Non-existent directory environments should raise a helpful error

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3226



  Non-existent directory environments should raise a helpful error 










Change By:

 Rob Reynolds




Fix Version/s:

 PUP 3.7.2












   

 Add Comment











 










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




 














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

Jira (PUP-3226) Non-existent directory environments should raise a helpful error

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3226



  Non-existent directory environments should raise a helpful error 










Change By:

 Rob Reynolds




Fix Version/s:

 PUP 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-3226) Non-existent directory environments should raise a helpful error

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Non-existent directory environments should raise a helpful error 










Switching the fixVersion from 3.7.2 to 3.7.0 since this relates to 

PUP-2519
.












   

 Add Comment











 













 Puppet /  PUP-3226



  Non-existent directory environments should raise a helpful error 







 If in puppet.conf I have:  {noformat}  [main]  basemodulepath = /etc/puppetlabs/puppet/modules  environmentpath = /etc/puppetlabs/puppet/envs  {noformat}  and if /etc/puppetlabs/puppet/modules/test/manifests/init.pp exists with `class test { }` in it, and if /etc/puppetlabs/puppet/envs/production does not exist, when I run {{puppet agent -t}} I get {{Erro...















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

Jira (PUP-3404) helper functions in custom function

2014-10-21 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: helper functions in custom function 










James Shubin: I dug into this a bit more and couldn't reproduce a working function using historical versions of Puppet. The error is present in 3.0.0, 2.7.26 – all the way back to 2.6.18. Then I tried on a system running under Ruby 1.8.7 and everything works fine. So, this break was induced by some sort of scoping change in Ruby 1.9 and not by any change to the Puppet codebase.
The reason we didn't notice this is that neither the core Puppet Functions or any functions in Puppet Labs modules like stdlib contain these sort of helper methods — so there were no tests exercising this functionality. We try very hard to be intentional about breaking backwards compatibility and to do so appropriately using major versions and by documenting backwards incompatibilities. Unfortunately, this change was not the result of an intentional, or even unintentional, action on our part and so 












   

 Add Comment











 













 Puppet /  PUP-3404



  helper functions in custom function 







 Hi,  I have a problem with helper functions in custom function   My puppet-Version: v3.7.1  If you need more information, let me know.  My custom function in very short from, but with the same error.  {noformat}  module Puppet::Parser::Functions    newfunction(:httpd_modules, :type => :rvalue) do |args|  def helper_function(value)    value  e...















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

Jira (PUP-3404) helper functions in custom function

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: helper functions in custom function 










Going forward we have a new API for functions (simply called 4x function API) that will be released in Puppet 4.0 (it can be used since 3.6 with the --parser future option). In the new API you can place helper methods inside the body of code that implements the function, you can have multiple dispatch (different type signatures) and get automatic type checking of arguments. The new functions API also solves a number of other problems.












   

 Add Comment











 













 Puppet /  PUP-3404



  helper functions in custom function 







 Hi,  I have a problem with helper functions in custom function   My puppet-Version: v3.7.1  If you need more information, let me know.  My custom function in very short from, but with the same error.  {noformat}  module Puppet::Parser::Functions    newfunction(:httpd_modules, :type => :rvalue) do |args|  def helper_function(value)    value  e...















 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 e

Jira (PUP-3404) helper functions in custom function

Title: Message Title










 

 James Shubin commented on an issue











 






  Re: helper functions in custom function 










RE: Charlie,
Interesting, I did not consider the ruby version differences, but I was fairly sure this was working with Ruby 2.0.0 at some point. In any case, this should work IMO, because the amount of boilerplate required to add a function is terrible. I also don't like the forced splitting up of different functions that should really be the same. The lambda approach works great, which is what I was using this as. Thanks for looking into this.












   

 Add Comment











 













 Puppet /  PUP-3404



  helper functions in custom function 







 Hi,  I have a problem with helper functions in custom function   My puppet-Version: v3.7.1  If you need more information, let me know.  My custom function in very short from, but with the same error.  {noformat}  module Puppet::Parser::Functions    newfunction(:httpd_modules, :type => :rvalue) do |args|  def helper_function(value)    value  e...















 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.

Jira (PUP-3404) helper functions in custom function

Title: Message Title










 

 James Shubin commented on an issue











 






  Re: helper functions in custom function 










RE: Henrik,
Sounds like an improvement! Is there any documentation on this that I can look at?
Thanks, James












   

 Add Comment











 













 Puppet /  PUP-3404



  helper functions in custom function 







 Hi,  I have a problem with helper functions in custom function   My puppet-Version: v3.7.1  If you need more information, let me know.  My custom function in very short from, but with the same error.  {noformat}  module Puppet::Parser::Functions    newfunction(:httpd_modules, :type => :rvalue) do |args|  def helper_function(value)    value  e...















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

Jira (PUP-3302) Puppet resource broken when directory environments enabled

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3302



  Puppet resource broken when directory environments enabled 










Change By:

 Rob Reynolds




Flagged:

 Impediment












   

 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-3409) Is the code ready for release?

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Is the code ready for release? 










Waiting on one ticket to pass CI and another to pass FR.












   

 Add Comment











 













 Puppet /  PUP-3409



  Is the code ready for release? 







 All tests (spec, acceptance) should be passing on all platforms for both stable & master.    * If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc.   * If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through sp...















 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-3404) helper functions in custom function

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: helper functions in custom function 










https://github.com/puppetlabs/puppet-specifications/blob/master/language/func-api.md
Since 3.7 the iterative functions (each, map, filter, reduce, slice) are implemented with this API, so you can see some examples of some more complex functions using the API.












   

 Add Comment











 













 Puppet /  PUP-3404



  helper functions in custom function 







 Hi,  I have a problem with helper functions in custom function   My puppet-Version: v3.7.1  If you need more information, let me know.  My custom function in very short from, but with the same error.  {noformat}  module Puppet::Parser::Functions    newfunction(:httpd_modules, :type => :rvalue) do |args|  def helper_function(value)    value  e...















 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-3396) Add support for testing 4x functions in modules

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3396



  Add support for testing 4x functions in modules 










Change By:

 Rob Reynolds




Flagged:

 Impediment












   

 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-3404) helper functions in custom function

Title: Message Title










 

 James Shubin commented on an issue











 






  Re: helper functions in custom function 










RE: Henrik,
Cool... So to confirm, would this be a valid function:
 Puppet::Functions.create_function(:foo) do def foo(bar, baz) def inner_foo(inner_bar, inner_baz) return inner_bar+inner_baz end return 42+inner_foo(bar, baz) end end  ?
Thanks, James












   

 Add Comment











 













 Puppet /  PUP-3404



  helper functions in custom function 







 Hi,  I have a problem with helper functions in custom function   My puppet-Version: v3.7.1  If you need more information, let me know.  My custom function in very short from, but with the same error.  {noformat}  module Puppet::Parser::Functions    newfunction(:httpd_modules, :type => :rvalue) do |args|  def helper_function(value)    value  e...















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

Jira (PUP-3414) Is the Jira tidy-up done for this release and prepared for the next one?

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Is the Jira tidy-up done for this release and prepared for the next one? 










Introduced in 3.7.1 - 


https://tickets.puppetlabs.com/issues/?filter=12833


Fixes for 3.7.2 - 


https://tickets.puppetlabs.com/issues/?filter=12834














   

 Add Comment











 













 Puppet /  PUP-3414



  Is the Jira tidy-up done for this release and prepared for the next one? 







 This happens on Jira - we need to clean up the current release and prepare for the next release.   * Mark the version that's going out as "Released" in the Project Admin -> Versions panel.   * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7...















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

Jira (PDB-989) Update dujour for new release

2014-10-21 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone assigned an issue to Melissa Stone











 






 PuppetDB /  PDB-989



  Update dujour for new release 










Change By:

 Melissa Stone




Assignee:

 Melissa Stone












   

 Add Comment











 










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




 














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

Jira (PUP-3404) helper functions in custom function

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: helper functions in custom function 










No, but this would:






Puppet::Functions.create_function(:foo) do




def foo(bar, baz)




return 42+inner_foo(bar, baz)




end




 




def inner_foo(inner_bar, inner_baz)




  return inner_bar+inner_baz




end




end







The inner_foo method will never be called by puppet. if you like you can add:






private :inner_foo

Jira (PUP-3227) Upgrade conflict: puppetmaster-common and puppet-common

2014-10-21 Thread Kylo Ginsberg (JIRA)

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Upgrade conflict: puppetmaster-common and puppet-common 










+1 on this for 3.7.2.












   

 Add Comment











 













 Puppet /  PUP-3227



  Upgrade conflict: puppetmaster-common and puppet-common 







 We've already addressed an issue where man pages were moved from the puppet packages to the puppet-common package. Unfortunately, we're seeing this conflict again when upgrading a system with both puppet and puppetmaster installed. The conflict here being that puppetmaster-common now owns man pages that were previously packaged in puppet-common (or at lea...















 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-3415) Prepare long form release notes and short form release story

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Prepare long form release notes and short form release story 










Nicholas Fagerlund ping. Will this be you?












   

 Add Comment











 













 Puppet /  PUP-3415



  Prepare long form release notes and short form release story 







 Collaborating with product for release story  Dependencies:   * Is there a JIRA ticket targeted at the release for every commit?   * Is there a commit for every JIRA ticket targeted at the release?















 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-3409) Is the code ready for release?

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Is the code ready for release? 










Down to one FR now.












   

 Add Comment











 













 Puppet /  PUP-3409



  Is the code ready for release? 







 All tests (spec, acceptance) should be passing on all platforms for both stable & master.    * If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc.   * If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through sp...















 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.

2014-10-21 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. 










Acceptance ballooned up to 592 failures on the 17th I believe. I've been looking into the first failures, allow_arbitrary_node_name_fact_for_agent.rb, and this is because something has changed to cause the directory environment loader to churn out production environments with incorrect modulepath ([/etc/puppetlabs/puppet/modules, /opt/puppet/share/puppet/modules]) and manifest (/etc/puppetlabs/puppet/manifests/site.pp). This seems to be because these values are getting called early on and cached in Puppet.settings, perhaps before puppet.conf, with it's environmentpath override has been loaded? Why this is suddenly happening in pe-puppet, is unknown.












   

 Add Comment











 













 Puppet /  PUP-3277



  Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. 







 A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 















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




 














-- 
You received this message because you are

Jira (PUP-3414) Is the Jira tidy-up done for this release and prepared for the next one?

2014-10-21 Thread Kylo Ginsberg (JIRA)

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Is the Jira tidy-up done for this release and prepared for the next one? 










Rob Reynolds Re the "Introduced in ..." link, I think we usually do it for the version we are just now releasing. E.g. here it would be "Introduced in 3.7.2" (not 3.7.1).
So that then can be used in release notes like: https://docs.puppetlabs.com/puppet/latest/reference/release_notes.html#all-resolved-issues-for-371












   

 Add Comment











 













 Puppet /  PUP-3414



  Is the Jira tidy-up done for this release and prepared for the next one? 







 This happens on Jira - we need to clean up the current release and prepare for the next release.   * Mark the version that's going out as "Released" in the Project Admin -> Versions panel.   * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7...















 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

Jira (PUP-3414) Is the Jira tidy-up done for this release and prepared for the next one?

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Is the Jira tidy-up done for this release and prepared for the next one? 










Kylo Ginsberg thanks for the clarification, doesn't quite make sense to me yet though. It's probably why I called it out above in my first comment.












   

 Add Comment











 













 Puppet /  PUP-3414



  Is the Jira tidy-up done for this release and prepared for the next one? 







 This happens on Jira - we need to clean up the current release and prepare for the next release.   * Mark the version that's going out as "Released" in the Project Admin -> Versions panel.   * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7...















 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 option

Jira (PUP-3227) Upgrade conflict: puppetmaster-common and puppet-common

Title: Message Title










 

 Eric Thompson assigned an issue to Eric Thompson











 






 Puppet /  PUP-3227



  Upgrade conflict: puppetmaster-common and puppet-common 










Change By:

 Eric Thompson




Assignee:

 Eric Thompson












   

 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-3414) Is the Jira tidy-up done for this release and prepared for the next one?

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Is the Jira tidy-up done for this release and prepared for the next one? 










Still doesn't make sense. That is affectedVersion, which means things that are now broke in at least 3.7.1. The second link to me is things we fixed for this release.












   

 Add Comment











 













 Puppet /  PUP-3414



  Is the Jira tidy-up done for this release and prepared for the next one? 







 This happens on Jira - we need to clean up the current release and prepare for the next release.   * Mark the version that's going out as "Released" in the Project Admin -> Versions panel.   * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7...















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

Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3471



  Windows Puppet x86 Installer on x64 system issue 










Change By:

 Rob Reynolds




Affects Version/s:

 PUP 3.7.2












   

 Add Comment











 










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




 














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

Jira (PUP-3414) Is the Jira tidy-up done for this release and prepared for the next one?

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Is the Jira tidy-up done for this release and prepared for the next one? 










And there is this as well https://tickets.puppetlabs.com/secure/ReleaseNote.jspa?projectId=10102&version=11925












   

 Add Comment











 













 Puppet /  PUP-3414



  Is the Jira tidy-up done for this release and prepared for the next one? 







 This happens on Jira - we need to clean up the current release and prepare for the next release.   * Mark the version that's going out as "Released" in the Project Admin -> Versions panel.   * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7...















 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/

Jira (PUP-3413) Merge master into stable

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Merge master into stable 










Nope.












   

 Add Comment











 













 Puppet /  PUP-3413



  Merge master into stable 







 For some releases, the code base will need to be merged down to stable.  *NOTE:* This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket.   Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: {noformat} git fetch upstre...















 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-3412) Update version number in source

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Update version number in source 










https://github.com/puppetlabs/puppet/commit/652bc05e123a78ffe7b34f9b9f674e6e04be6ee5
652bc05e123a78ffe7b34f9b9f674e6e04be6ee5












   

 Add Comment











 













 Puppet /  PUP-3412



  Update version number in source 







 Bump VERSION in lib/{#project}/version.rb to correct version.    * Commit the updated version file. * e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3".   * If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask).   * Once this is done, hand the SHA to be built to RelEng to be tagged















 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-3227) Upgrade conflict: puppetmaster-common and puppet-common

Title: Message Title










 

 Eric Thompson updated an issue











 






 Puppet /  PUP-3227



  Upgrade conflict: puppetmaster-common and puppet-common 










Change By:

 Eric Thompson




QA Contact:

 Eric Thompson




QA Status:

 Reviewed




Assignee:

 Eric Thompson












   

 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-3416) Tag the release and create packages

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Tag the release and create packages 










Melissa Stone Here is the SHA 652bc05e123a78ffe7b34f9b9f674e6e04be6ee5.
Thanks! 












   

 Add Comment











 













 Puppet /  PUP-3416



  Tag the release and create packages 







 Tag and create packages    * Developer provides the SHA - [~rob] - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)   * checkout the sha * Make sure you are about to tag the correct thing   * Create the tag e.g.) git tag -s -u {GPG key} -m "1.7.3" 1.7.3 * You need to know the pass phrase for t...















 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-3467) Reject SSLv3 connections in Puppet

2014-10-21 Thread Kylo Ginsberg (JIRA)

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-3467



  Reject SSLv3 connections in Puppet 










Change By:

 Kylo Ginsberg




Security:

 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 (FACT-720) No eth0 causes error

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 redmine.exporter created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-720 
 
 
 
  No eth0 causes error  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Created:
 

 21/Oct/14 2:59 PM 
 
 
 

Labels:
 

 redmine customer 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 redmine.exporter 
 
 
 
 
 
 
 
 
 
 
When the mcollective-metadata cron runs, the lack of eth0 causes this error to appear "arping: unknown iface eth0", which ends up spamming logs every run. The customer also got the error when manually running facter: 
 

facter -p | grep eth arping: unknown iface eth0 interfaces => eth3,lo ipaddress_eth3 => xx.xx.xx.xx macaddress_eth3 => 00:15:5D:AB:xx:xx netmask_eth3 => 255.255.252.0 network_eth3 => xx.xx.xx.0
 
 
Currently they are working around it with "# Puppet Name: pe-mcollective-metadata 0,15,30,45 * * * * /opt/puppet/sbin/refresh-mcollective-metadata > /dev/null 2>&1" 
I'm looking into a workaround that's a little cleaner and only target the eth0 fact.

Jira (PUP-3393) Improve puppet's error handling and exit code correctness.

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 redmine.exporter created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3393 
 
 
 
  Improve puppet's error handling and exit code correctness.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 21/Oct/14 3:01 PM 
 
 
 

Labels:
 

 redmine 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 redmine.exporter 
 
 
 
 
 
 
 
 
 
 
This is an umbrella bug for a slew of issues around un-informative or misleading error reporting, incorrect exit codes, and unhelpful help. 
See the 'related bugs' field for a full list. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-3417) Smoke test packages

2014-10-21 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone commented on an issue











 






  Re: Smoke test packages 










packages available at http://builds.puppetlabs.lan/puppet/3.7.2/












   

 Add Comment











 













 Puppet /  PUP-3417



  Smoke test packages 







 Procedure may vary by project and point in the release cycle. Ask around.  In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc).  For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be li...















 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-1526) Package type should support environment variables

2014-10-21 Thread Dan Bode (JIRA)

Title: Message Title










 

 Dan Bode commented on an issue











 






  Re: Package type should support environment variables 










I think I ran into this when trying to use eatmydata to speed up package installs for test systems.
eatmydata need to set the LD_PRELOAD environment variable to work.












   

 Add Comment











 













 Puppet /  PUP-1526



  Package type should support environment variables 







 ## Overview ##   With the release of Debian Squeeze, a customer mentioned some Debian packages are beginning to use environment variables to override behavior. For example, the sudo-ldap package will not install if there is no password set on the root account.   # This is needed for removing the sudo package since it won't uninstall  # when the...















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




 














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

Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-990



  PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 21/Oct/14 3:09 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Ticket/master/pdb 954 fallback acceptance


Author: Wyatt Alt <>


Company:


Github ID: wkalt


Pull Request 1129 Discussion


Pull Request 1129 File Diff


Pull Request Description


(webhooks-id: 46820d93dd546e859a6f1e8c3e2337b7)

Jira (PUP-3417) Smoke test packages

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Smoke test packages 










Andy Parker / Joshua Partlow Didn't we remove the need for most of these to be smoke tested? With the exception of windows and ...?












   

 Add Comment











 













 Puppet /  PUP-3417



  Smoke test packages 







 Procedure may vary by project and point in the release cycle. Ask around.  In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc).  For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be li...















 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-3415) Prepare long form release notes and short form release story

2014-10-21 Thread Nicholas Fagerlund (JIRA)

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: Prepare long form release notes and short form release story 










https://github.com/puppetlabs/puppet-docs/blob/pup372/source/puppet/3.7/reference/release_notes.markdown In a branch and ready to go. 












   

 Add Comment











 













 Puppet /  PUP-3415



  Prepare long form release notes and short form release story 







 Collaborating with product for release story  Dependencies:   * Is there a JIRA ticket targeted at the release for every commit?   * Is there a commit for every JIRA ticket targeted at the release?















 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-3415) Prepare long form release notes and short form release story

2014-10-21 Thread Nicholas Fagerlund (JIRA)

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: Prepare long form release notes and short form release story 










http://docspreview2.puppetlabs.lan/puppet/3.7/reference/release_notes.html And the preview, if you have VPN.












   

 Add Comment











 













 Puppet /  PUP-3415



  Prepare long form release notes and short form release story 







 Collaborating with product for release story  Dependencies:   * Is there a JIRA ticket targeted at the release for every commit?   * Is there a commit for every JIRA ticket targeted at the release?















 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-3417) Smoke test packages

Title: Message Title










 

 Eric Thompson commented on an issue











 






  Re: Smoke test packages 










smoke testing debian wheezy (7.7)












   

 Add Comment











 













 Puppet /  PUP-3417



  Smoke test packages 







 Procedure may vary by project and point in the release cycle. Ask around.  In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc).  For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be li...















 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-1498) scheduled_task won't update command

Title: Message Title










 

 Josh Cooper commented on an issue











 






  Re: scheduled_task won't update command 










c lang during the 3.7.x release we rewrote the task scheduler gem, vendoring it within puppet, and fixing a number of issues. We also identified and fixed the spurious "trigger changed" messages in 3.7.2. Can you please retest with 3.7.2 (when it comes out in the next day or so) and let us know if that works. If it doesn't, please provide a sample manifest.












   

 Add Comment











 













 Puppet /  PUP-1498



  scheduled_task won't update command 







 if you update a scheduled_task's command, Puppet does not make the change in the task scheduler. Other changes, e.g. the trigger, appear to work, but not the command.   I've had to work around by deleting the old task and creating a new one with a different name. 















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

Jira (PUP-1498) scheduled_task won't update command

Title: Message Title










 

 Josh Cooper updated an issue











 






 Puppet /  PUP-1498



  scheduled_task won't update command 










Change By:

 Josh Cooper




Assignee:

 Josh Cooper c lang












   

 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 (FACT-696) facts.d module "external" facts get put in client dir which facter doesn't look at by default

Title: Message Title










 

 Josh Cooper updated an issue











 






 Facter /  FACT-696



  facts.d module "external" facts get put in client dir which facter doesn't look at by default 










Change By:

 Josh Cooper




Assignee:

 Josh Cooper 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 (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt 










pljenkinsro commented:
Test PASSed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/120/












   

 Add Comment











 













 PuppetDB /  PDB-990



  PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt 







 h2. Ticket/master/pdb 954 fallback acceptance   * Author: Wyatt Alt <>  * Company:   * Github ID: [wkalt|https://github.com/wkalt]  * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129]  * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files]  h2. Pull Request Description  (webhooks-id...















 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

Jira (PUP-2716) ssl_server_ca_chain and ssl_client_ca_chain are dead settings

Title: Message Title










 

 Josh Cooper updated an issue











 






 Puppet /  PUP-2716



  ssl_server_ca_chain and ssl_client_ca_chain are dead settings 










Change By:

 Josh Cooper




Summary:

 ssl_server_ca_chain  is  and ssl_client_ca_chain are  dead  settings












   

 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-2716) ssl_server_ca_chain is dead

Title: Message Title










 

 Josh Cooper updated an issue











 






 Puppet /  PUP-2716



  ssl_server_ca_chain is dead 










Change By:

 Josh Cooper




Fix Version/s:

 PUP 4.0.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-2716) ssl_server_ca_chain is dead

Title: Message Title










 

 Josh Cooper updated an issue











 






 Puppet /  PUP-2716



  ssl_server_ca_chain is dead 










Change By:

 Josh Cooper




Summary:

 ssl_server_ca_chain is  not documented  dead












   

 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-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt 










pljenkinsro commented:
Test FAILed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/121/












   

 Add Comment











 













 PuppetDB /  PDB-990



  PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt 







 h2. Ticket/master/pdb 954 fallback acceptance   * Author: Wyatt Alt <>  * Company:   * Github ID: [wkalt|https://github.com/wkalt]  * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129]  * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files]  h2. Pull Request Description  (webhooks-id...















 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

Jira (PUP-2613) Change source_permissions default to :ignore

2014-10-21 Thread Michael Smith (JIRA)

Title: Message Title










 

 Michael Smith commented on an issue











 






  Re: Change source_permissions default to :ignore 










New PR #3221 fixed the help text specifying the default for source_permissions.












   

 Add Comment











 













 Puppet /  PUP-2613



  Change source_permissions default to :ignore 







 Currently, puppet will copy the owner/group/mode from sourced files when those properties are unspecified. This leads to surprising results, e.g. PUP-1986.   We discussed changing the default behavior in https://groups.google.com/forum/#!msg/puppet-users/XNy8gI3jcf0/HufQkYQdKMAJ   This ticket calls for changing the default value of {{:source_permissions...















 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-3498) Create rubygem confine for use with providers

2014-10-21 Thread Reid Vandewiele (JIRA)

Title: Message Title










 

 Reid Vandewiele created an issue











 






 Puppet /  PUP-3498



  Create rubygem confine for use with providers 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 21/Oct/14 6:14 PM




Priority:

  Normal




Reporter:

 Reid Vandewiele










Currently, if a provider requires a particular rubygem to be installed in order to function, it is difficult to indicate, or confine, that provider to systems that have the gem installed WHILE allowing in-run installation of the gem. E.g. have Puppet pluginsync down a new mount provider, my_provider, from a module, and specify a package resource, with the gem provider, that will install a requisite gem prior to a mount resource that specifies provider=my_provider. Visually, this pattern:






package { 'somegem':




  ensure   => present,




  provider => gem,




}

Jira (PDB-970) PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt 










ghoneycutt commented:
@kbarber ping












   

 Add Comment











 













 PuppetDB /  PDB-970



  PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt 







 h2. Allow only TLS - Fixes POODLE CVE-2014-3566   * Author: Garrett Honeycutt   * Company:   * Github ID: [ghoneycutt|https://github.com/ghoneycutt]  * [Pull Request 150 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/150]  * [Pull Request 150 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/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 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-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt