Jira (PUP-229) User provider password_max_age attribute is flawed under Solaris

[Brian LaMetterey (JIRA)]

Title: Message Title










 

 Brian LaMetterey updated an issue











 






 Puppet /  PUP-229



  User provider password_max_age attribute is flawed under Solaris 










Change By:

 Brian LaMetterey




Assignee:

 Rahul Gopinath












   

 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-3050) Fix cfacter integration to match recent cfacter changes

[Peter Huene (JIRA)]

Title: Message Title










 

 Peter Huene created an issue











 






 Puppet /  PUP-3050



  Fix cfacter integration to match recent cfacter changes 










Issue Type:

  Bug




Assignee:

 Peter Huene




Components:


 Client




Created:


 12/Aug/14 5:25 PM




Fix Versions:


 3.7.0




Priority:

  Normal




Reporter:

 Peter Huene










cfacter has changed its gem so that most of the implementation now lies in the C++ source. This means we can entirely remove lib/facts.rb and change the cfacter option implementation to simply call a single method in the gem.












   

 Add Comment











 

Jira (PUP-3049) mailalias chokes on commas

[Gabriel Filion (JIRA)]

Title: Message Title










 

 Gabriel Filion updated an issue











 






 Puppet /  PUP-3049



  mailalias chokes on commas 










Change By:

 Gabriel Filion









 I'm using puppet 2.7 and on one node, I have a mailalias resource tosetup something for redmine like the following: {code} mailalias {"redmine":recipient =>'|/usr/share/redmine/extra/mail_handler/sub-mailhandler.py -eredm...@redmine.example.com --  /usr/share/redmine/extra/mail_handler/rdm-mailhandler.rb --url  https://redmine.example.com --key somerandomalphanumstring  --no-check-certificate --unknown-user accept --no-permission-check  --allow-override project,tracker,category,priority,status';} {code}   puppet is always refreshing the alias for no reason. changing the valueto the same thing.after doing some more testing, I found out that mailalias bugs in the above manner as soon as there is a comma in the recipient parameter value (e.g. with "...project" it's ok but with "...project," I start seeing the issue).












   

 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-3049) mailalias chokes on commas

[Gabriel Filion (JIRA)]

Title: Message Title










 

 Gabriel Filion created an issue











 






 Puppet /  PUP-3049



  mailalias chokes on commas 










Issue Type:

  Bug




Affects Versions:


 2.7.23




Assignee:


 Unassigned




Created:


 12/Aug/14 5:06 PM




Priority:

  Normal




Reporter:

 Gabriel Filion










I'm using puppet 2.7 and on one node, I have a mailalias resource to setup something for redmine like the following:
 mailalias  { "redmine": recipient => '|/usr/share/redmine/extra/mail_handler/sub-mailhandler.py -e redm...@redmine.example.com -- /usr/share/redmine/extra/mail_handler/rdm-mailhandler.rb --url https://redmine.example.com --key somerandomalphanumstring --no-check-certificate --unknown-user accept --no-permission-check --allow-override project,tracker,category,priority,status'; }
puppet is always refreshing the alias for no reason. changing the value to the same thing.
after doing some more testing, I found out that mailalias bugs in the above manner as soon as there is a comma in the recipient parameter value (e.g. with "...project" it's ok but with "...project," I start seeing the issue).












   

 Add Commen

Jira (PUP-1515) Invalid parameter provider for custom types/providers

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Invalid parameter provider for custom types/providers 










Eric Sorenson: I've put the patch I developed while investigating this issue up as PR 2963.
No tests, no guarantees. But, if someone tries it out and it works, please do let us know!












   

 Add Comment











 













 Puppet /  PUP-1515



  Invalid parameter provider for custom types/providers 







 In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're ...















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




 














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

Jira (PUP-1605) `puppet resource ssh_authorized_key ` should work

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: `puppet resource ssh_authorized_key ` should work 










Ran into this working on the ssh_authorized_key acceptance tests.
`puppet resource ssh_authorized_key  target=authorized_keys_file`
or
`puppet resource ssh_authorized_key  user=$USER`
Work where  is the unique comment from a specific key in the authorized_keys file.
`puppet resource ssh_authorized_key $USER` could conceivably list all keys in the user's authorized key file, but seems like an odd construction.
At the very least there should be a better error message explaining the need to specify target or user.












   

 Add Comment











 













 Puppet /  PUP-1605



  `puppet resource ssh_authorized_key ` should work 







 One of my clients remarked that he was working through the Learning Puppet track and ran into a stack trace.   Learning Puppet teaches the `puppet resource` command, the later has an exercise for the `ssh_authorized_key` resource (on ). Running `puppet resource ssh_authorized_key hunner` throws a stack ...















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




 
   

Jira (HI-284) Specifying stages within hiera

[Aaron Armstrong (JIRA)]

Title: Message Title










 

 Aaron Armstrong updated an issue











 






 Hiera /  HI-284



  Specifying stages within hiera 










Change By:

 Aaron Armstrong




Assignee:

 Aaron Armstrong












   

 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-649) Backport acceptance setup update for RedHat / Fedora into Facter / master

[William Hopper (JIRA)]

Title: Message Title










 

 William Hopper created an issue











 






 Facter /  FACT-649



  Backport acceptance setup update for RedHat / Fedora into Facter / master 










Issue Type:

  Improvement




Affects Versions:


 2.2.0




Assignee:

 William Hopper




Created:


 12/Aug/14 4:00 PM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 William Hopper










This commit was lost in the facter-2 / master merge.












   

 Add Comment











 





   

Jira (FACT-648) Backport lost Xen 4.0 command support into Facter / master

[William Hopper (JIRA)]

Title: Message Title










 

 William Hopper created an issue











 






 Facter /  FACT-648



  Backport lost Xen 4.0 command support into Facter / master 










Issue Type:

  Improvement




Affects Versions:


 2.2.0




Assignee:

 William Hopper




Created:


 12/Aug/14 3:59 PM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 William Hopper










This commit was lost in the facter-2 / master merge.












   

 Add Comment











 






 

Jira (FACT-647) Backport lost SELinux exception handling into Facter / master

[William Hopper (JIRA)]

Title: Message Title










 

 William Hopper created an issue











 






 Facter /  FACT-647



  Backport lost SELinux exception handling into Facter / master 










Issue Type:

  Improvement




Affects Versions:


 2.2.0




Assignee:

 William Hopper




Created:


 12/Aug/14 3:58 PM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 William Hopper










This commit was lost in the facter-2 / master merge.












   

 Add Comment











 






  

Jira (FACT-646) Backport Debian/control change to Facter / master

[William Hopper (JIRA)]

Title: Message Title










 

 William Hopper created an issue











 






 Facter /  FACT-646



  Backport Debian/control change to Facter / master 










Issue Type:

  Improvement




Affects Versions:


 2.2.0




Assignee:

 William Hopper




Created:


 12/Aug/14 3:57 PM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 William Hopper










This commit was lost in the facter-2 / master merge.












   

 Add Comment











 






  

Jira (PUP-229) User provider password_max_age attribute is flawed under Solaris

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: User provider password_max_age attribute is flawed under Solaris 










Rahul Gopinath can you take a look at this one?












   

 Add Comment











 













 Puppet /  PUP-229



  User provider password_max_age attribute is flawed under Solaris 







 A user reported this, and did an excellent write up of the issue and a possible fix, so I'm just going to paste that:   The password_max_age logic is flawed on Solaris. At first, it seems to work:   {noformat}  # tail -1 /etc/passwd  foobar:x:911:911::/home/foobar:/bin/sh   # tail -1 /etc/shadow  foobar:GI2XGzW0DitJk:15931::182:28:::  {noformat}   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.google.com/d/optout.

Jira (PDB-823) Remove saucy from build_defaults.yaml

[Melissa Stone (JIRA)]

Title: Message Title










 

 Melissa Stone created an issue











 






 PuppetDB /  PDB-823



  Remove saucy from build_defaults.yaml 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 12/Aug/14 3:36 PM




Priority:

  Normal




Reporter:

 Melissa Stone










Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then.












   

 Add Comment











 










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




 

Jira (PUP-3048) Remove saucy from build_defaults.yaml

[Melissa Stone (JIRA)]

Title: Message Title










 

 Melissa Stone created an issue











 






 Puppet /  PUP-3048



  Remove saucy from build_defaults.yaml 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 12/Aug/14 3:35 PM




Priority:

  Normal




Reporter:

 Melissa Stone










Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then.












   

 Add Comment











 










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




 

Jira (FACT-645) Remove saucy from build_defaults.yaml

[Melissa Stone (JIRA)]

Title: Message Title










 

 Melissa Stone created an issue











 






 Facter /  FACT-645



  Remove saucy from build_defaults.yaml 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Created:


 12/Aug/14 3:34 PM




Priority:

  Normal




Reporter:

 Melissa Stone










Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then.












   

 Add Comment











 










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




 









   

Jira (HI-285) Remove saucy from build_defaults.yaml

[Melissa Stone (JIRA)]

Title: Message Title










 

 Melissa Stone created an issue











 






 Hiera /  HI-285



  Remove saucy from build_defaults.yaml 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 12/Aug/14 3:34 PM




Priority:

  Normal




Reporter:

 Melissa Stone










Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then.












   

 Add Comment











 










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




 






   

Jira (PUP-1515) Invalid parameter provider for custom types/providers

[Eric Sorenson (JIRA)]

Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Invalid parameter provider for custom types/providers 










Wow, that's great. Sounds like a very targeted fix that could help a lot of people. Would it be possible to get a branch or "DO NOT MERGE" PR up with a quick spike? That way people affected by it could try out the branch to see if it works in their environments.












   

 Add Comment











 













 Puppet /  PUP-1515



  Invalid parameter provider for custom types/providers 







 In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're ...















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




 














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

Jira (PUP-1874) Deprecate the inventory service on master

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Deprecate the inventory service on master 










The documentation has been updated to list what is being deprecated:

The Inventory Service is Deprecated!
The inventory service is deprecated and will be removed in Puppet 4.0.
We’re removing it because PuppetDB does the same job, many times better. If you’re doing anything with the inventory service, switching to PuppetDB will let you do it faster, easier, and more reliably. For more information, see:


Installing PuppetDB


Overview of the PuppetDB API


The parts of Puppet that will be removed as part of the inventory service deprecation are:


The puppet master server’s facts and facts_search HTTP endpoints


The inventory_active_record terminus for the facts indirection


The puppet facts upload and puppet facts find --terminus rest commands















   

 Add Comment











 













 Puppet /  PUP-1874



  Deprecate the inventory service on master 




   

Jira (PUP-744) Pool HTTPS connections

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Pool HTTPS connections 










Denis Boulas, assuming that this passes testing it will be available in puppet 3.7.0. There are some new settings to control the connection pooling, but it should be enabled by default (https://github.com/puppetlabs/puppet/pull/2863/files#diff-908b50f77db1b5645f5c125514deccd3R413)












   

 Add Comment











 













 Puppet /  PUP-744



  Pool HTTPS connections 







 Reduce network traffic and latency















 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-1874) Deprecate the inventory service on master

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-1874



  Deprecate the inventory service on master 










Change By:

 Andy Parker




Assignee:

 Andy Parker












   

 Add Comment











 










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




 














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

Jira (PUP-3031) simplify/move warn_if_near_expiration

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-3031



  simplify/move warn_if_near_expiration 










Change By:

 Andy Parker




Component/s:

 Networking Services




Component/s:

 DOCS












   

 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-3031) simplify/move warn_if_near_expiration

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker assigned an issue to Christopher Price











 






 Puppet /  PUP-3031



  simplify/move warn_if_near_expiration 










Change By:

 Andy Parker




Assignee:

 Eric Sorenson Christopher Price












   

 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-3031) simplify/move warn_if_near_expiration

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: simplify/move warn_if_near_expiration 










I'm also on board with that plan. I don't think there is any need on the puppet-4 branch to retain any of the code.












   

 Add Comment











 













 Puppet /  PUP-3031



  simplify/move warn_if_near_expiration 







 See related PE ticket; this is largely a placeholder just to make sure we've tried to address this before 3.7.0 release.   In `http/handler.rb`'s `process` method, there is a call to a method named `warn_if_near_expiration`. The goal of this method appears to be simply to check the expiration date of the client certificate, and log a warning message if i...















 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-3047) Validate Puppet -x64-mingw32 gem dependencies on x64

[Ethan Brown (JIRA)]

Title: Message Title










 

 Ethan Brown created an issue











 






 Puppet /  PUP-3047



  Validate Puppet -x64-mingw32 gem dependencies on x64 










Issue Type:

  Task




Affects Versions:


 3.7.0




Assignee:

 Kylo Ginsberg




Components:


 Client




Created:


 12/Aug/14 2:36 PM




Fix Versions:


 3.7.0




Priority:

  Normal




Reporter:

 Ethan Brown










Ensure that 


We release a mingw x64 gem that includes appropriate dependencies


That all of the expected dependencies resolve correctly (necessary for other things that depend on puppet gem, such as current module testing)










 

Jira (PUP-3046) Create a new documentation to replace the current RDoc implementation.

[Hailee Kenney (JIRA)]

Title: Message Title










 

 Hailee Kenney created an issue











 






 Puppet /  PUP-3046



  Create a new documentation to replace the current RDoc implementation. 










Issue Type:

  Epic




Assignee:


 Unassigned




Created:


 12/Aug/14 2:32 PM




Priority:

  Normal




Reporter:

 Hailee Kenney












   

 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-2944) yum provider should use osfamily instead of operatingsystem fact

[Eric Thompson (JIRA)]

Title: Message Title










 

 Eric Thompson updated an issue











 






 Puppet /  PUP-2944



  yum provider should use osfamily instead of operatingsystem fact 










Change By:

 Eric Thompson




QA Contact:

 Narmadha Perumal 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-2944) yum provider should use osfamily instead of operatingsystem fact

[Eric Thompson (JIRA)]

Title: Message Title










 

 Eric Thompson updated an issue











 






 Puppet /  PUP-2944



  yum provider should use osfamily instead of operatingsystem fact 










Change By:

 Eric Thompson




QA Contact:

 Eric Thompson Kurt Wall












   

 Add Comment











 










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




 














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

Jira (HI-284) Specifying stages within hiera

[Jay Wallace (JIRA)]

Title: Message Title










 

 Jay Wallace created an issue











 






 Hiera /  HI-284



  Specifying stages within hiera 










Issue Type:

  New Feature




Affects Versions:


 1.3.4




Assignee:

 Aaron Armstrong




Components:


 PE




Created:


 12/Aug/14 2:19 PM




Labels:


 customer




Priority:

  Normal




Reporter:

 Jay Wallace










Users should be able to specify stages in hiera when using hiera_include. Currently, You cannot assign a class to a run stage when declaring it with the include function and are forced to use the resource-like class declaration syntax with stages. It is not uncommon for a user to want to include several classes via and specify the stage.












   

   

Jira (PUP-2889) Upgrade win32-eventlog

[Rob Reynolds (JIRA)]

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Upgrade win32-eventlog 










Looks like we may have missed upgrading the gem dependency for event log - https://github.com/puppetlabs/puppet/blob/master/ext/project_data.yaml#L34












   

 Add Comment











 













 Puppet /  PUP-2889



  Upgrade win32-eventlog 







 We need to either upgrade or replace the use of win32-eventlog. During some upgrading we found issues, which lead to this particular ticket out of PUP-392.















 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-3031) simplify/move warn_if_near_expiration

[Eric Sorenson (JIRA)]

Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: simplify/move warn_if_near_expiration 










That plan sounds good to me, I need to defer the implementation to you and Andy though.












   

 Add Comment











 













 Puppet /  PUP-3031



  simplify/move warn_if_near_expiration 







 See related PE ticket; this is largely a placeholder just to make sure we've tried to address this before 3.7.0 release.   In `http/handler.rb`'s `process` method, there is a call to a method named `warn_if_near_expiration`. The goal of this method appears to be simply to check the expiration date of the client certificate, and log a warning message if i...















 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-2972) Implementation of +=/-= is potentially confusing

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Implementation of +=/-= is potentially confusing 










Merged to master at 824e389












   

 Add Comment











 













 Puppet /  PUP-2972



  Implementation of +=/-= is potentially confusing 







 It seems to me that += and -= are more confusing than useful, and I would argue that they simply shouldn't exist.   Right now (with "--parser future"), these operators implicitly create a new variable that may shadow one from an outer scope, appending/removing the RHS to the outer scope variable if it exists. If the variable has already been defined in 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-3031) simplify/move warn_if_near_expiration

[Christopher Price (JIRA)]

Title: Message Title










 

 Christopher Price commented on an issue











 






  Re: simplify/move warn_if_near_expiration 










Eric Sorenson I can move it into the Rack portion of the code pretty easily if that's OK. This was one of the other options I discussed with Josh Cooper last week. I think we were saying that if we went that route we might just leave it out of the webrick code though?
Eric Sorenson Andy Parker so, this is what I'm thinking I'll do:
File one PR against the 3.7 branch that does this:
1. Remove the call from `handler.rb` 2. Add it to the Rack code 3. See if I can similarly add it to the webrick code
Open a new JIRA to capture Deepak Giridharagopal's comment about eventually making a CLI tool for it.
File a second PR against the 4.x branch that removes the call entirely, and maybe on the method definition, add a comment with a link to the above Jira?












   

 Add Comment











 













 Puppet /  PUP-3031



  simplify/move warn_if_near_expiration 







 See related PE ticket; this is largely a placeholder just to make sure we've tried to address this before 3.7.0 release.   In `http/handler.rb`'s `process` method, there is a call to a method named `warn_if_near_expiration`. The goal of this method appears to be simply to check the expiration date of the client certificate, and log a warning message if i...















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

Jira (PUP-3031) simplify/move warn_if_near_expiration

[Eric Sorenson (JIRA)]

Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: simplify/move warn_if_near_expiration 










I think it would be a semver break to just remove it. Sounds like it can and should go away in the puppet-4 branch, so it's clear to delete there.
But I don't think we need to support it through jetty, Christopher Price is it possible to intercept this before it hits the ruby code path and just return "this is not implemented"?












   

 Add Comment











 













 Puppet /  PUP-3031



  simplify/move warn_if_near_expiration 







 See related PE ticket; this is largely a placeholder just to make sure we've tried to address this before 3.7.0 release.   In `http/handler.rb`'s `process` method, there is a call to a method named `warn_if_near_expiration`. The goal of this method appears to be simply to check the expiration date of the client certificate, and log a warning message if i...















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

Jira (PUP-3008) Already initialized constant warning when running puppet

[Rob Reynolds (JIRA)]

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-3008



  Already initialized constant warning when running puppet 










Change By:

 Rob Reynolds




Affects Version/s:

 3.7.0












   

 Add Comment











 










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




 














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

Jira (PDB-112) Provide means to request events from latest report in timeframe

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Provide means to request events from latest report in timeframe 










We are releasing PuppetDB 2.2.0 at the end of the month FYI. This ticket should be complete for that release, otherwise it will not make it for PE 3.4, at least not according to the current schedule.












   

 Add Comment











 













 PuppetDB /  PDB-112



  Provide means to request events from latest report in timeframe 







 h2. Summary   Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630].   h2. Des...















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

Jira (PUP-511) Specify Resource Expression Evaluation

[Eric Thompson (JIRA)]

Title: Message Title










 

 Eric Thompson commented on an issue











 






  Re: Specify Resource _expression_ Evaluation 










Andy Parker aha! sorry, i should have known from the epic link... but... still have the same effect as my comment above.  bundle exec puppet resource --parser future --edit user 'a' edit 'a' to be one of 4, 3.14, foo, etc things that should not work, work, and vice versa as in list above... maybe we can do a hangout today and you can show me what i'm doing wrong?












   

 Add Comment











 













 Puppet /  PUP-511



  Specify Resource _expression_ Evaluation 







 Resource _expression_ Evaluation requires a specification of the behavior.   Here are some examples of issues in need of resolution:   * if title is undef - error  * if title is an array, several resources are created - what happens if    and entry is undef? Is this silently ignored, or is it an error?    * suggest it is an error (i.e. user would have to ...















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

Jira (PUP-2972) Implementation of +=/-= is potentially confusing

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Implementation of +=/-= is potentially confusing 










A short conversation on puppet-dev came to the same conclusion as the filer of this ticket. The 

= and 

= operators are more confusing than they are worth. With the changes in the future parser, where they are now just synonyms for the + and - operators plus assignment, there is no need to keep them. Since 
= only ever existed in the future parser, dropping it is not a concern. Dropping support for 
= is a small concern, but it is so seldom used and there are other ways of achieving the same goals:
Translations for += when used with


Strings: use interpolation (e.g. {{$a = "$a$b" }}).


Arrays: in the future parser (4x language) simply use + (e.g. $a = $a + $b), in the current parser (3x language) use a custom function such as concat from stdlib (e.g. $a = concat($a, $b) (WARNING: some versions of stdlib's concat will modify the arrays causing this to change the outer scope $a).


Hashes: in the future parser (4x language) simply use + (e.g. $a = $a + $b), in the current parser (3x language) use a custom function such as merge from stdlib (e.g. $a = merge($a, $b).














   

 Add Comment











 













 Puppet /  PUP-2972



  Implementation of +=/-= is potentially confusing 






  

Jira (PUP-511) Specify Resource Expression Evaluation

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Specify Resource _expression_ Evaluation 










Eric Thompson, you need to use the future parser with this.












   

 Add Comment











 













 Puppet /  PUP-511



  Specify Resource _expression_ Evaluation 







 Resource _expression_ Evaluation requires a specification of the behavior.   Here are some examples of issues in need of resolution:   * if title is undef - error  * if title is an array, several resources are created - what happens if    and entry is undef? Is this silently ignored, or is it an error?    * suggest it is an error (i.e. user would have to ...















 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-511) Specify Resource Expression Evaluation

[Eric Thompson (JIRA)]

Title: Message Title










 

 Eric Thompson commented on an issue











 






  Re: Specify Resource _expression_ Evaluation 










using SHA ec173ba on osx: puppet resource --edit user 'blah': user  { default: ensure => 'absent', }
Error: Could not parse for environment production: Syntax error at ':'; expected '}' at /Users/erict/repos/puppet/x2puppet20140812-78223-e88rkp:1 on node erict-mbp.delivery.puppetlabs.net Error: Could not parse for environment production: Syntax error at ':'; expected '}' at /Users/erict/repos/puppet/x2puppet20140812-78223-e88rkp:1 on node erict-mbp.delivery.puppetlabs.net same with [default], [foo, default].  works fine with 'Default' titles that should not work, but do include: 4 3.14 [foo, undef]












   

 Add Comment











 













 Puppet /  PUP-511



  Specify Resource _expression_ Evaluation 







 Resource _expression_ Evaluation requires a specification of the behavior.   Here are some examples of issues in need of resolution:   * if title is undef - error  * if title is an array, several resources are created - what happens if    and entry is undef? Is this silently ignored, or is it an error?    * suggest it is an error (i.e. user would have to ...















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




 

Jira (PUP-511) Specify Resource Expression Evaluation

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Specify Resource _expression_ Evaluation 










Eric Thompson, the specification of resource expressions should contain all of the information about what is allowed and what isn't. The purpose of this ticket was to make that clear and complete. If it isn't then we need to do some more work.












   

 Add Comment











 













 Puppet /  PUP-511



  Specify Resource _expression_ Evaluation 







 Resource _expression_ Evaluation requires a specification of the behavior.   Here are some examples of issues in need of resolution:   * if title is undef - error  * if title is an array, several resources are created - what happens if    and entry is undef? Is this silently ignored, or is it an error?    * suggest it is an error (i.e. user would have to ...















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

Jira (PUP-1515) Invalid parameter provider for custom types/providers

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Invalid parameter provider for custom types/providers 










I've encountered this code before. Unfortunately we don't have time before 3.7 to get a fix in for this. I'm going to target it at 4.0.0 instead, since fixing it might also cause some API breaks.












   

 Add Comment











 













 Puppet /  PUP-1515



  Invalid parameter provider for custom types/providers 







 In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're ...















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




 














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

Jira (PUP-1515) Invalid parameter provider for custom types/providers

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-1515



  Invalid parameter provider for custom types/providers 










Change By:

 Andy Parker




Fix Version/s:

 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-3031) simplify/move warn_if_near_expiration

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker assigned an issue to Eric Sorenson











 







I'm not wedded to this functionality. The expiration check has come up as a problem multiple times.
The functionality itself solves a user problem where they need to be informed that certificates are expiring, but maybe it isn't the best place to do it and instead having a command that can check for expiring certificates is better.
Can this functionality actually be removed in 3.7? That seems like a breaking change for anyone who might be relying on this.









 Puppet /  PUP-3031



  simplify/move warn_if_near_expiration 










Change By:

 Andy Parker




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-822) Acceptance tests for structured/trusted facts

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-822



  Acceptance tests for structured/trusted facts 










Change By:

 Kenneth Barber




Story Points:

 3 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-3031) simplify/move warn_if_near_expiration

[Christopher Price (JIRA)]

Title: Message Title










 

 Christopher Price commented on an issue











 






  Re: simplify/move warn_if_near_expiration 










Eric Sorenson Andy Parker I'm going to be working on this this week; do you guys want to weigh in on Deepak Giridharagopal's suggestion? Otherwise I'm probably just going to move forward with removing that call.












   

 Add Comment











 













 Puppet /  PUP-3031



  simplify/move warn_if_near_expiration 







 See related PE ticket; this is largely a placeholder just to make sure we've tried to address this before 3.7.0 release.   In `http/handler.rb`'s `process` method, there is a call to a method named `warn_if_near_expiration`. The goal of this method appears to be simply to check the expiration date of the client certificate, and log a warning message if i...















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




 














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

Jira (PUP-1515) Invalid parameter provider for custom types/providers

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1515



  Invalid parameter provider for custom types/providers 










Change By:

 Charlie Sharpsteen




Assignee:

 Charlie Sharpsteen Andy Parker












   

 Add Comment











 










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




 














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

Jira (PUP-1515) Invalid parameter provider for custom types/providers

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1515



  Invalid parameter provider for custom types/providers 










Change By:

 Charlie Sharpsteen




Component/s:

 Server












   

 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-1515) Invalid parameter provider for custom types/providers

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Invalid parameter provider for custom types/providers 










So, what is happening here is that the Autoloader isn't switching environments correctly.
When the Vcsrepo type is loaded, a call of this form is used:



typeloader.load(name, Puppet.lookup(:current_environment))



Where the typeloader is an Autoloader instance. In this case, we explicitly pass the current environment that the master is compiling for.
Once the type is loaded, we then load all known providers for that type:



klass.providerloader.loadall



Where providerloader is another Autoloader instance. Note that no environment is passed to this call. Because no environment is passed, there are two places where nil gets used instead. This causes the Autoloader to search Puppet[:environment] instead of the current_environment.
So, to summarize: when the Puppet master loads a Type, it searches the environment that the agent requested. When it loads providers for that type, it searches the default environment instead of the one the agent requested.
Andy Parker: This is a different issue from PUP-731 and one that we could fix. Handing back to you to decide if this should be scheduled for a release.












   

 Add Comment











 













 Puppet /  PUP-1515



  Invalid parameter provider for custom types/providers 







  

Jira (PUP-2614) Deprecate default source_permissions :use on all platforms

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Deprecate default source_permissions :use on all platforms 










I'm going to move this to Needs Information while we consider whether this makes sense, per Josh's comment above.












   

 Add Comment











 













 Puppet /  PUP-2614



  Deprecate default source_permissions :use on all platforms 







 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 is about issuing a deprecation warning when {{:source_permiss...















 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-817) PR (1038): (maint) Fix old acceptance test refspec issue - kbarber

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber assigned an issue to Kenneth Barber











 






 PuppetDB /  PDB-817



  PR (1038): (maint) Fix old acceptance test refspec issue - kbarber 










Change By:

 Kenneth Barber




Assignee:

 Kenneth Barber












   

 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-817) PR (1038): (maint) Fix old acceptance test refspec issue - kbarber

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-817



  PR (1038): (maint) Fix old acceptance test refspec issue - kbarber 










Change By:

 Kenneth Barber




Story Points:

 1












   

 Add Comment











 










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




 














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

Jira (PDB-817) PR (1038): (maint) Fix old acceptance test refspec issue - kbarber

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-817



  PR (1038): (maint) Fix old acceptance test refspec issue - kbarber 










Change By:

 Kenneth Barber




Fix Version/s:

 2.2.0












   

 Add Comment











 










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




 














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

Jira (PDB-817) PR (1038): (maint) Fix old acceptance test refspec issue - kbarber

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-817



  PR (1038): (maint) Fix old acceptance test refspec issue - kbarber 










Change By:

 Kenneth Barber




Sprint:

 20140730 to 20140813












   

 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-817) PR (1038): (maint) Fix old acceptance test refspec issue - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1038): (maint) Fix old acceptance test refspec issue - kbarber 










Pull request (maint) Fix old acceptance test refspec issue has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-817



  PR (1038): (maint) Fix old acceptance test refspec issue - kbarber 







 h2. (maint) Fix old acceptance test refspec issue   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 1038 Discussion|https://github.com/puppetlabs/puppetdb/pull/1038]  * [Pull Request 1038 File Diff|https://github.com/puppetlabs/puppetdb/pull/1038/files]  h2. Pull Request De...















 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-3043) 100% CPU usage

[Daniel Dreier (JIRA)]

Title: Message Title










 

 Daniel Dreier commented on an issue











 






  Re: 100% CPU usage 










This is still the case in 3.6.2, despite being originally reported four years ago, as demonstrated with the following test case:



file { '/tmp/foo':
  owner => "root",
  group => "root",
  recurse => "true",
  ensure => "directory",
  checksum => undef
}



The first time you run it, it'll run very quickly. Run 



for filename in {1..5} ; do touch /tmp/foo/$filename ; done



Then re-run the puppet test case. On a fast i7 CPU with an SSD, it was still running after 15 minutes when I killed it.












   

 Add Comment











 













 Puppet /  PUP-3043



  100% CPU usage 







 Hi,   I've been experimenting with Puppet for a few days now, and overall I'm pretty impressed on how easy Puppet makes it to manage configurations.  However, one thing has been ruining my enthusiasm thoroughly, and that is the massive CPU consumption of Puppet.   At first I used puppet to source in and manage a few hundred megabytes of data, so I presu...















 This message was sent by Atlassian JIRA

Jira (PUP-3043) 100% CPU usage

[Daniel Dreier (JIRA)]

Title: Message Title










 

 Daniel Dreier updated an issue











 






 Puppet /  PUP-3043



  100% CPU usage 










Change By:

 Daniel Dreier




Affects Version/s:

 3.6.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 (PDB-822) Acceptance tests for structured/trusted facts

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber created an issue











 






 PuppetDB /  PDB-822



  Acceptance tests for structured/trusted facts 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 12/Aug/14 7:50 AM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 Kenneth Barber










We've finished a lot of the work for structured facts now, but we lack specific acceptance tests for this work. This ticket is to track the work required to add some basic end-to-end tests, that enable trusted and structured facts from Puppet, and ensure these are propogated to PuppetDB correctly.
Support for testing the puppet fact search functionality would also be a bonus, to ensure that face still works correctly.












   

 Add Comment











 

   

Jira (PDB-28) Support for structured facts

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-28



  Support for structured facts 










Change By:

 Kenneth Barber




Story Points:

 0












   

 Add Comment











 










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




 














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

Jira (PDB-822) Acceptance tests for structured/trusted facts

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-822



  Acceptance tests for structured/trusted facts 










Change By:

 Kenneth Barber




Sprint:

 20140813 to 20140827












   

 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-797) Add 'name' field to 'fact-nodes'

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-797



  Add 'name' field to 'fact-nodes' 










Change By:

 Kenneth Barber









 During the development of fact-nodes I've realised we need a ' fact name ' field so we can do subqueries against /facts. Now [~wyatt] is adding a column to do just that right now in PDB-772. Since the fact-nodes patch landed sooner, this small ticket is to track the addition of that field after PDB-772 is merged.












   

 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-805) PR (1034): (maint) Upgrade trapperkeeper and kitchensink libraries to latest - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1034): (maint) Upgrade trapperkeeper and kitchensink libraries to latest - kbarber 










Pull request WIP: (maint) Upgrade trapperkeeper and kitchensink libraries to latest has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-805



  PR (1034): (maint) Upgrade trapperkeeper and kitchensink libraries to latest - kbarber 







 h2. (maint) Upgrade trapperkeeper and kitchensink libraries to latest   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 1034 Discussion|https://github.com/puppetlabs/puppetdb/pull/1034]  * [Pull Request 1034 File Diff|https://github.com/puppetlabs/puppetdb/pull/1034/files] ...















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




 














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

Jira (PDB-805) PR (1034): (maint) Upgrade trapperkeeper and kitchensink libraries to latest - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1034): (maint) Upgrade trapperkeeper and kitchensink libraries to latest - kbarber 










kbarber commented:
This will be fixed with TK-46 and PDB-813. Closing.












   

 Add Comment











 













 PuppetDB /  PDB-805



  PR (1034): (maint) Upgrade trapperkeeper and kitchensink libraries to latest - kbarber 







 h2. (maint) Upgrade trapperkeeper and kitchensink libraries to latest   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 1034 Discussion|https://github.com/puppetlabs/puppetdb/pull/1034]  * [Pull Request 1034 File Diff|https://github.com/puppetlabs/puppetdb/pull/1034/files] ...















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




 














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

Jira (PDB-813) Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9 










Here is the PR I was raising to upgrade TK (and a few other bits). The fix for refspec is a separate PR already.
I'm saying this because my patch won't merge on its own anyway, and you'll need to upgrade to the latest TK I think to have this patch merge anyway so your patch should really be this PR: https://github.com/puppetlabs/puppetdb/pull/1034 plus your bits for removing the certificate whitelist code (and not to mention the corresponding TK, patch which is really TK-46 for this bug).
I'm closing that PR, and closing the tracking ticket in favour of this one basically.












   

 Add Comment











 













 PuppetDB /  PDB-813



  Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9 







 Upon attempting to upgrade to Trapperkeeper we've realised we have a feature in PuppetDB that is not coverred, namely 'certificate-whitelist':   https://docs.puppetlabs.com/puppetdb/2.1/configure.html#certificate-whitelist   It works as a basic ACL mechanism to only allow named SSL certificates to access your web app.   This is provided here in PuppetD...















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




 

Jira (PDB-809) Switch to using a cache for /facts endpoint

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber assigned an issue to Kenneth Barber











 






 PuppetDB /  PDB-809



  Switch to using a cache for /facts endpoint 










Change By:

 Kenneth Barber




Assignee:

 Kenneth Barber












   

 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-821) How do we simplify searching across fact-nodes, using a subquery from facts

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber created an issue











 






 PuppetDB /  PDB-821



  How do we simplify searching across fact-nodes, using a subquery from facts 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 12/Aug/14 7:32 AM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 Kenneth Barber










Current we support displaying results from /facts with a sub-query across fact-nodes so you get the best of both worlds - fine grained search but coarse grained results.
The idea here is that a searching utility might want to show the entire fact from a search ... so the user can see the full context instead of just the resulting path (with none of its other data around it).
There is something to be said about making this simpler, and perhaps providing a rewrite rule to remove the need for someone to provide a subquery.
Concerns are that a simple path query might not be enough, and that a value and path combination would be more valuable, we'd have to consider this in our design perhaps.
This isn't mandatory for structured facts phase 1, but if we have a simple design for this it would be easy to implement I presume using the new query engine rewrite rule capability. If we can't make a quick decision I say we punt this for phase 2.










   

Jira (PDB-821) How do we simplify searching across fact-nodes, using a subquery from facts

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-821



  How do we simplify searching across fact-nodes, using a subquery from facts 










Change By:

 Kenneth Barber




Sprint:

 20140813 to 20140827












   

 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-820) Consider doing something with the *> operator, its functionality overlaps with ~>

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber created an issue











 






 PuppetDB /  PDB-820



  Consider doing something with the *> operator, its functionality overlaps with ~> 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 12/Aug/14 7:27 AM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 Kenneth Barber










The existing *> operator isn't that useful now we have the ~> operator. However, we had some intention to add the ** matcher, to match multiple elements that might still make it useful.
This ticket is about making the decision to either drop *> or find more use for it, and then doing the work for either decision.












   

 Add Comment











 




   

Jira (PDB-820) Consider doing something with the *> operator, its functionality overlaps with ~>

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-820



  Consider doing something with the *> operator, its functionality overlaps with ~> 










Change By:

 Kenneth Barber




Sprint:

 20140813 to 20140827












   

 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-718) Fact Path Endpoint

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-718



  Fact Path Endpoint 










Change By:

 Kenneth Barber




Sprint:

 20140813 20140730  to  20140827  20140813












   

 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-816) 'allow' structured facts from terminus

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber assigned an issue to Kenneth Barber











 






 PuppetDB /  PDB-816



  'allow' structured facts from terminus 










Change By:

 Kenneth Barber




Assignee:

 Kenneth Barber












   

 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-816) Configuration option, to 'allow' structured facts

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-816



  Configuration option, to 'allow' structured facts 










Change By:

 Kenneth Barber




Sprint:

 20140813 20140730  to  20140827  20140813












   

 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-816) 'allow' structured facts from terminus

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-816



  'allow' structured facts from terminus 










Change By:

 Kenneth Barber




Summary:

 Configuration option, to  'allow' structured facts  from terminus












   

 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-3045) exec resource with timeout doesn't kill executed command that times out

[Sven Mueller (JIRA)]

Title: Message Title










 

 Sven Mueller commented on an issue











 






  Re: exec resource with timeout doesn't kill executed command that times out 










I tried to come up with a patch that would fix this, but it seems such a patch exceeds my ruby skills.












   

 Add Comment











 













 Puppet /  PUP-3045



  exec resource with timeout doesn't kill executed command that times out 







 Trivial reproduction case:   exec { "sleep":    command => "/bin/sleep 1800",    timeout => 10,  }   With this, Puppet exits after roughly 10 seconds, but the sleep continues to run until the 1800 seconds are over.   My expectation would be for the sleep to get killed after the timeout hits.   As far as I can tell, the relevant code didn't change (muc...















 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-1187) tagmail report sends email when nothing happens

[Jens Pranaitis (JIRA)]

Title: Message Title










 

 Jens Pranaitis commented on an issue











 






  Re: tagmail report sends email when nothing happens 










Whoops, ignore my previous comment, the patch worked fine.












   

 Add Comment











 













 Puppet /  PUP-1187



  tagmail report sends email when nothing happens 







 Since upgrading to the 2.7 series (2.6.8 -> 2.7.3), the tagmail report will send an email with 1 line, shown below, after every run. Before the upgrade, it would only send emails when something occurred during the puppet run.   Steps to reproduce:  Enable tagmail report  Execute a puppet run that produces no updates   Expected result:  No email sent  ...















 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-2790) if initctl --version doesn't list a matching string, upstart service provider fails badly.

[Sven Mueller (JIRA)]

Title: Message Title










 

 Sven Mueller commented on an issue











 






  Re: if initctl --version doesn't list a matching string, upstart service provider fails badly. 










Pull request created against master branch.












   

 Add Comment











 













 Puppet /  PUP-2790



  if initctl --version doesn't list a matching string, upstart service provider fails badly. 







 We are running puppet during the installation process, using Debian installers late_command option.  At this point, calling "status avahi-daemon" returns:  - cut here -   Warning: Fake initctl called, doing nothing.  - cut here -  (As does any other call to initctl, such as "initctl list")  Unfortunately, I was unable to determine if this...















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




 














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

Jira (PUP-2790) if initctl --version doesn't list a matching string, upstart service provider fails badly.

[Sven Mueller (JIRA)]

Title: Message Title










 

 Sven Mueller commented on an issue











 






  Re: if initctl --version doesn't list a matching string, upstart service provider fails badly. 










So, I just checked yesterday. initctl is overridden during the installation, but asking telinit for the version would still work. So checking the version in telinit instead of initctl would be a more reliable way to detect the upstart version.












   

 Add Comment











 













 Puppet /  PUP-2790



  if initctl --version doesn't list a matching string, upstart service provider fails badly. 







 We are running puppet during the installation process, using Debian installers late_command option.  At this point, calling "status avahi-daemon" returns:  - cut here -   Warning: Fake initctl called, doing nothing.  - cut here -  (As does any other call to initctl, such as "initctl list")  Unfortunately, I was unable to determine if this...















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




 














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

Jira (PUP-3045) exec resource with timeout doesn't kill executed command that times out

[Sven Mueller (JIRA)]

Title: Message Title










 

 Sven Mueller created an issue











 






 Puppet /  PUP-3045



  exec resource with timeout doesn't kill executed command that times out 










Issue Type:

  Bug




Affects Versions:


 3.4.2




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 12/Aug/14 1:25 AM




Environment:


Linux




Priority:

  Normal




Reporter:

 Sven Mueller










Trivial reproduction case:
exec  { "sleep": command => "/bin/sleep 1800", timeout => 10, }
With this, Puppet exits after roughly 10 seconds, but the sleep continues to run until the 1800 seconds are over.
My expectation would be for the sleep to get killed after the timeout hits.
As far as I can tell, the relevant code didn't change (much) till current head, so I suspect the issue still exists.