date:20140331

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-561



  Rename name to certname in nodes endpoint 










Change By:

 Kenneth Barber




Fix Version/s:

 2.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 (PDB-564) Add OpenBSD to puppetdb.env

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-564



  Add OpenBSD to puppetdb.env 










Change By:

 Kenneth Barber




Sprint:

 20140326 to 20140409












   

 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-553) PR (903): Removed unused command attribute "puppetdb-version" - senior

2014-03-31 Thread gepetto-bot (JIRA)

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (903): Removed unused command attribute "puppetdb-version" - senior 










kbarber commented:
@pljenkinsro retest this please












   

 Add Comment











 













 PuppetDB /  PDB-553



  PR (903): Removed unused command attribute "puppetdb-version" - senior 







 h2. Removed unused command attribute "puppetdb-version"   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 903 Discussion|https://github.com/puppetlabs/puppetdb/pull/903]  * [Pull Request 903 File Diff|https://github.com/puppetlabs/puppetdb/pull/903/files]  h2. Pull Request Descri...















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




 














-- 
You received this message because you are subscribed to 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-563) puppet nodes status -- SSL problesm

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: puppet nodes status -- SSL problesm 










Put the certname = setting inside your [main] section, this way all tools get to use it.
Puppet node status doesn't use either the [agent] or [master] section, it probably uses [node] if anything, but putting it in [main] should mean all sections get it by default. Right now the tool is falling back to the systems FQDN most probably, because it doesn't see a 'certname' setting in its own scope.












   

 Add Comment











 













 PuppetDB /  PDB-563



  puppet nodes status -- SSL problesm 







 We are getting a SSL error while calling  {code}  # puppet node status puppetdb-test02.domain.net  Error: Could not retrieve status for puppetdb-test02.domain.net: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A  {code}   In the puppetdb log we see this:   {code}  2014-03-28 15:46:06,694 DEBUG [qtp1303770546-46] [nio.ssl] SCEP@7705bc1...















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




 














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

Jira (PDB-561) Rename name to certname in nodes endpoint

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-561



  Rename name to certname in nodes endpoint 










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-560) PR (904): Fixed 'same file' error when running rake install - Ginja

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-560



  PR (904): Fixed 'same file' error when running rake install - Ginja 










Change By:

 Kenneth Barber




Sprint:

 20140326 to 20140409












   

 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-563) puppet nodes status -- SSL problesm

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-563



  puppet nodes status -- SSL problesm 










Change By:

 Kenneth Barber




Sprint:

 20140326 to 20140409












   

 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-563) puppet nodes status -- SSL problems

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-563



  puppet nodes status -- SSL problems 










Change By:

 Kenneth Barber




Summary:

 puppet nodes status -- SSL  problesm  problems












   

 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-554) EC2 instances are being left behind and not cleaned up

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: EC2 instances are being left behind and not cleaned up 










28 zombies this time with the following failures:
https://jenkins.puppetlabs.com/view/B_PuppetDB/job/PuppetDB%20Acceptance%20IN%20THE%20CLOUD/738/ https://jenkins.puppetlabs.com/view/B_PuppetDB/job/PuppetDB%20Acceptance%20IN%20THE%20CLOUD/739/ https://jenkins.puppetlabs.com/view/B_PuppetDB/job/PuppetDB%20Acceptance%20IN%20THE%20CLOUD/740/












   

 Add Comment











 













 PuppetDB /  PDB-554



  EC2 instances are being left behind and not cleaned up 







 It seems that some of our EC2 instances are not being cleaned up. We found almost 200+ instances in EC2 from us dating from March 18th. While I have manually removed these now, this is costing us a lot - needs to be fixed ASAP.















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




 














-- 
You received this message because you are subscribed to 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 t

Jira (PDB-553) PR (903): Removed unused command attribute "puppetdb-version" - senior

2014-03-31 Thread gepetto-bot (JIRA)

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (903): Removed unused command attribute "puppetdb-version" - senior 










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












   

 Add Comment











 













 PuppetDB /  PDB-553



  PR (903): Removed unused command attribute "puppetdb-version" - senior 







 h2. Removed unused command attribute "puppetdb-version"   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 903 Discussion|https://github.com/puppetlabs/puppetdb/pull/903]  * [Pull Request 903 File Diff|https://github.com/puppetlabs/puppetdb/pull/903/files]  h2. Pull Request Descri...















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




 














-- 
You received this message because you are subscribed to 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 gro

Jira (PUP-1550) Allow for a hiera configuration specific to an environment

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Allow for a hiera configuration specific to an environment 










Removing this from the "enumerating environments" epic since it isn't tied to getting feature parity with the existing environment system.












   

 Add Comment











 













 Puppet /  PUP-1550



  Allow for a hiera configuration specific to an environment 







 Right now there is no way to have a hiera configuration specific to an environment. This needs to be rectified so that each environment can have a {{hiera.yaml}} that configures hiera for the specific environment.   It isn't clear to me if hiera 1.x can even support this in a robust manner at the moment.















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




 














-- 
You received this message because you are subscribed to 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-553) PR (903): Removed unused command attribute "puppetdb-version" - senior

2014-03-31 Thread gepetto-bot (JIRA)

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (903): Removed unused command attribute "puppetdb-version" - senior 










Pull request Removed unused command attribute "puppetdb-version" has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-553



  PR (903): Removed unused command attribute "puppetdb-version" - senior 







 h2. Removed unused command attribute "puppetdb-version"   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 903 Discussion|https://github.com/puppetlabs/puppetdb/pull/903]  * [Pull Request 903 File Diff|https://github.com/puppetlabs/puppetdb/pull/903/files]  h2. Pull Request Descri...















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




 














-- 
You received this message because you are subscribed to 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-555) Add last_environment support to /v4/nodes for showing the last environment seen for each object type

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Add last_environment support to /v4/nodes for showing the last environment seen for each object type 










A concept of 'last_environment' that doesn't care about the object last reported would be a nice helper for API consumers. It could probably just be 'environment', which would then make it look a lot like the other API end-points.












   

 Add Comment











 













 PuppetDB /  PDB-555



  Add last_environment support to /v4/nodes for showing the last environment seen for each object type 







 This entails adding the parameters:   * facts_last_environment  * catalog_last_environment  * report_last_environment   To the /v4/nodes end point results, and providing some way to query on these as well. Or at least this is the rough idea.   This is broken out from PDB-454 because the concept of an environment for a node is transient and is based on ...















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




 














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

Jira (PUP-2036) ACL - Changing owner, group or protect takes two runs to converge permissions

Title: Message Title










 

 Peter Huene assigned an issue to Peter Huene











 






 Puppet /  PUP-2036



  ACL - Changing owner, group or protect takes two runs to converge permissions 










Change By:

 Peter Huene




Assignee:

 Peter Huene












   

 Add Comment











 










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




 














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

Jira (PDB-564) Add OpenBSD to puppetdb.env

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-564



  Add OpenBSD to puppetdb.env 










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-560) PR (904): Fixed 'same file' error when running rake install - Ginja

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-560



  PR (904): Fixed 'same file' error when running rake install - Ginja 










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 (PUP-2100) Allow Inheritance when setting Deny ACEs

Title: Message Title










 

 Rob Reynolds created an issue











 






 Puppet /  PUP-2100



  Allow Inheritance when setting Deny ACEs 










Issue Type:

  Bug




Assignee:

 Rob Reynolds




Created:


 31/Mar/14 9:54 AM




Fix Versions:


 3.6.0




Priority:

  Normal




Reporter:

 Rob Reynolds












   

 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.

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

2014-03-31 Thread Reid Vandewiele (JIRA)

Title: Message Title










 

 Reid Vandewiele commented on an issue











 






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










Kenneth Barber if I understand the end use-case correctly, we will need to gather data on events for every node. Will this proposal allow for that? The specific example you've written seems limited to a single node per query. If it is limited to a single node per query, is that acceptable? I could see the overhead getting pretty high for thousands of nodes.
If it's not limited to a single node per query, could you show an unconstrained example?












   

 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 yo

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

Title: Message Title










 

 Kenneth Barber commented on an issue











 






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










Reid Vandewiele sorry, my example could work without a constraint as well, that was just an example.
For unconstrained you could do:



curl -sG 'http://ubuntu:8080/v3/events' \
  --data-urlencode \
  'query=["and",
   [">", "timestamp", "2013-10-30T14:50:00-07:00"],
   ["<", "timestamp", "2013-10-30T14:55:00-07:00"],
   ["in", "report",
 ["extract", "hash",
   ["select-report",
 ["limit", 1
   ["order-by", [{"field":"end-time","order":"desc"}],
 ["<", "end-time", "2013-10-30T14:55:00-07:00"]]]'















   

 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)

Jira (PUP-2048) Allow suppressing diffs on augeas

Title: Message Title










 

 Peter Huene assigned an issue to Peter Huene











 






 Puppet /  PUP-2048



  Allow suppressing diffs on augeas 










Change By:

 Peter Huene




Assignee:

 Peter Huene












   

 Add Comment











 










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




 














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

Jira (PUP-2101) resource parser: add the resource name on the validation error message when using create_resources

2014-03-31 Thread David Portabella (JIRA)

Title: Message Title










 

 David Portabella created an issue











 






 Puppet /  PUP-2101



  resource parser: add the resource name on the validation error message when using create_resources 










Issue Type:

  Bug




Affects Versions:


 M




Assignee:


 Unassigned




Created:


 31/Mar/14 10:06 AM




Priority:

  Normal




Reporter:

 David Portabella










using create_resources on a new provider type, if there is a validation error (a wrong parameter), puppet does show the name of the wrong parameter, but it does not show the name of the provider type.
to reproduce, place these files under ~/test/



./simple.pp
./modules/util/lib/puppet/provider/simple.rb
./modules/util/lib/puppet/type/simple.rb



simple.pp



$res = {
  'some_useless_file' => {
path   => '/tmp',
ensure => 'present',
wrong_param => 'hello',
  }
}
create_resources('simple', $res)



get the two other files from https://gist.github.com/dayglojesus/2569267



$ puppet apply --modulepath=~/test/modules/  simple.pp 
Error: Invalid parameter wrong_param on node mac4c.local

Jira (PUP-2101) resource parser: add the resource name on the validation error message when using create_resources

2014-03-31 Thread David Portabella (JIRA)

Title: Message Title










 

 David Portabella commented on an issue











 






  Re: resource parser: add the resource name on the validation error message when using create_resources 










pull request: https://github.com/puppetlabs/puppet/pull/2489












   

 Add Comment











 













 Puppet /  PUP-2101



  resource parser: add the resource name on the validation error message when using create_resources 







 using create_resources on a new provider type,  if there is a validation error (a wrong parameter),  puppet does show the name of the wrong parameter, but it does not show the name of the provider type.   to reproduce, place these files under ~/test/  {code}  ./simple.pp  ./modules/util/lib/puppet/provider/simple.rb  ./modules/util/lib/puppet/type/simple...















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




 














-- 
You received this message because you are subscribed to 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.

Jira (PUP-2061) Prepare long form release notes and short form release story

2014-03-31 Thread Eric Sorenson (JIRA)

Title: Message Title










 

 Eric Sorenson commented on an issue











 






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










+1 just the right level of detail
do we always say "flurry" of improvements?












   

 Add Comment











 













 Puppet /  PUP-2061



  Prepare long form release notes and short form release story 







 Collaborating with product for release story















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




 














-- 
You received this message because you are subscribed to 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-2048) Allow suppressing diffs on augeas

2014-03-31 Thread Kylo Ginsberg (JIRA)

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Allow suppressing diffs on augeas 










For functional review see below. But NOTE: this will trash your /etc/hosts. Do it in a vm.



> cat pup2048.pp
augeas{"test1" :
  context => "/files/etc/hosts",
  changes => [
"set 1/ipaddr 1.2.3.4",
"set 1/canonical foobar",
  ],
  #show_diff => false,
}



And then run puppet apply pup2048.pp -

debug. You need the 
-debug to see the diffs. Then, restore /etc/hosts, uncomment the commented line and run it again.












   

 Add Comment











 













 Puppet /  PUP-2048



  Allow suppressing diffs on augeas 







 The file type got the ability to turn off diffs for specific resources in [Redmine #16412|http://projects.puppetlabs.com/issues/16412]. This is useful for suppressing output of sensitive data and would be useful for the augeas system as well, since it also can show diffs.















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

Jira (PUP-2102) CLONE - [Windows] Copying file resources from non-NTFS volumes causes Invalid DACL errors

2014-03-31 Thread Eric Sorenson (JIRA)

Title: Message Title










 

 Rob Reynolds created an issue











 






 Puppet /  PUP-2102



  CLONE - [Windows] Copying file resources from non-NTFS volumes causes Invalid DACL errors 










Issue Type:

  Bug




Affects Versions:


 3.4.0, 3.4.1, 3.4.2




Assignee:


 Unassigned




Created:


 31/Mar/14 10:22 AM




Fix Versions:


 3.5.0




Labels:


 3.5.0 wf001 windows




Priority:

  Normal




Reporter:

 Rob Reynolds










This was originally reported with vagrant-windows, but could have an effect anytime you would copy from a fileshare that is not Windows specific.


Error: /Stage[main]/Main/File[c:/Bob/jenkins-slave/jenkins-slave.exe]: Could not evaluate: 
Invalid DACL:  The access control list (ACL) structure is invalid. Could not retrieve file 
metadata for puppet:///modules/jenkins/jenkins-slave.exe: 
Invalid DACL:  The access control list (ACL) structure is invalid.
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util/errors.rb:97:in `fail'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/type/file/source.rb

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

2014-03-31 Thread Deepak Giridharagopal (JIRA)

Title: Message Title

Deepak Giridharagopal commented on an issue

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

This is an interesting idea! But the problem with the limit/order-by idea is that it doesn't work when what you're limiting spans > 1 logical entity. The first example works because it's a single certname, thus the resultset produced is a single, time-ordered stream of things that you could take the top entry from. The second example would only work if you wanted a single report, no matter the host. But what people want from this ticket is a way to snag events from the last report in a given timeframe...I think for that, under the hood, you'd have to implement it using something like "distinct on".
I'd prefer to have a specific operator for this, and have things like order-by and limit be implemented as query parameters (as opposed to part of the query itself).

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)

Jira (PUP-2061) Prepare long form release notes and short form release story

2014-03-31 Thread Nicholas Fagerlund (JIRA)

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






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










No, I must have written that when I was still kind of in "a what are all these tickets" mode.  We can change it. 












   

 Add Comment











 













 Puppet /  PUP-2061



  Prepare long form release notes and short form release story 







 Collaborating with product for release story















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




 














-- 
You received this message because you are subscribed to 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-2065) Smoke test packages

Title: Message Title










 

 Peter Huene assigned an issue to Peter Huene











 






 Puppet /  PUP-2065



  Smoke test packages 










Change By:

 Peter Huene




Assignee:

 Andy Parker Peter Huene












   

 Add Comment











 










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




 














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

Jira (PUP-1937) Acceptance tests assume ruby is in path on windows

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1937



  Acceptance tests assume ruby is in path on windows 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (PUP-2103) Puppet client does not update and does consult the crl during authentication

2014-03-31 Thread Tom Limoncelli (JIRA)

Title: Message Title










 

 Tom Limoncelli created an issue











 






 Puppet /  PUP-2103



  Puppet client does not update and does consult the crl during authentication 










Issue Type:

  Bug




Affects Versions:


 3.4.3




Assignee:


 Unassigned




Created:


 31/Mar/14 11:04 AM




Priority:

  Critical




Reporter:

 Tom Limoncelli










I my tests puppet client never updates it’s /var/lib/puppet/ssl/crl.pem from the master when it changes.
Though the CRL is initially downloaded from a CA and ‘cached’ that cache is never cleared causing multi-master setups to run with an increasingly outdated CRL.
I think this bug is dangerous especially because the separate CA thing is new and people don’t realize, nor is it documented, that this is the current behavior.












   

 Add Comment

Jira (PUP-2039) rpm provider broken for architecture specifications in 3.5.0-RC2 due to whatprovides functionality change

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-2039



  rpm provider broken for architecture specifications in 3.5.0-RC2 due to whatprovides functionality change 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (PUP-2045) puppet module generate should produce a skeleton Rakefile

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-2045



  puppet module generate should produce a skeleton Rakefile 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (PUP-2045) puppet module generate should produce a skeleton Rakefile

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: puppet module generate should produce a skeleton Rakefile 










The most recent build I could find, pl-puppet-3acebbd84ea8295826eb879bdd8ad54f5f614b2d, does not have this change:



$ cd /usr/lib/ruby/site_ruby/1.8/puppet/module_tool/skeleton/templates/generator
$ ls -l
total 20
drwxr-xr-x. 2 root root 4096 Mar 31 11:10 manifests
-rw-r--r--. 1 root root  348 Mar 31 10:40 Modulefile.erb
-rw-r--r--. 1 root root  199 Mar 31 10:40 README.erb
drwxr-xr-x. 2 root root 4096 Mar 31 11:10 spec
drwxr-xr-x. 2 root root 4096 Mar 31 11:10 tests



Perhaps it will be a later build?












   

 Add Comment











 













 Puppet /  PUP-2045



  puppet module generate should produce a skeleton Rakefile 







 # Overview #   Currently in 2.7.x puppet module generates the following structure: % puppet module generate puppetlabs-test  notice: Generating module at /Users/jeff/vms/puppet/tmp/puppetlabs-test  puppetlabs-test  puppetlabs-test/Modulefile  puppetlabs-test/README  puppetlabs-test/manifests  puppetlabs-test/manifests/init.pp  puppetlabs-test/m...















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

Jira (PUP-2100) Allow Inheritance when setting Deny ACEs

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-2100



  Allow Inheritance when setting Deny ACEs 










Change By:

 Rob Reynolds









 We are currently using AddAccessDeniedAce http://msdn.microsoft.com/en-us/library/windows/desktop/aa374962(v=vs.85).aspx which does not include inheritance and propagation, but AddAccessDeniedAceEx () does.












   

 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-2100) Allow Inheritance when setting Deny ACEs

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-2100



  Allow Inheritance when setting Deny ACEs 










Change By:

 Rob Reynolds









 We are currently using  [  AddAccessDeniedAce |  http://msdn.microsoft.com/en-us/library/windows/desktop/aa374962(v=vs.85).aspx ]  which does not include inheritance and propagation, but  [  AddAccessDeniedAceEx |http://msdn.microsoft.com/en-us/library/windows/desktop/aa374964  ( v=vs.85 ) .aspx]  does. We are already using AddAccessAllowedAceEx when setting allowed ACEs and we should use the same behavior for denied ACEs.












   

 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-1937) Acceptance tests assume ruby is in path on windows

2014-03-31 Thread Justin Stoller (JIRA)

Title: Message Title










 

 Justin Stoller commented on an issue











 






  Re: Acceptance tests assume ruby is in path on windows 










When will this be merged in pe-puppet?












   

 Add Comment











 













 Puppet /  PUP-1937



  Acceptance tests assume ruby is in path on windows 







 Which isn't the case when running PE.   If we are going to be able to ensure open source functionality we need to make sure that we can run the tests against PE. PE doesn't include Ruby in the path after its installed. This is an issue with a few tests that directly call ruby.















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




 














-- 
You received this message because you are subscribed to 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-2100) Allow Inheritance when setting Deny ACEs

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-2100



  Allow Inheritance when setting Deny ACEs 










Change By:

 Rob Reynolds









 We are With Access Control Entries (ACEs) on Windows, we  currently  using  use  [AddAccessDeniedAce|http://msdn.microsoft.com/en-us/library/windows/desktop/aa374962(v=vs.85).aspx] which does not include inheritance and /or  propagation  to child objects , but [AddAccessDeniedAceEx|http://msdn.microsoft.com/en-us/library/windows/desktop/aa374964(v=vs.85).aspx] does.  We are already using AddAccessAllowedAceEx when setting  access  allowed ACEs and we should use the same behavior for denied ACEs.












   

 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-2100) Allow Inheritance when setting Deny ACEs

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-2100



  Allow Inheritance when setting Deny ACEs 










Change By:

 Rob Reynolds




Sprint:

 Week 2014-3-26 to 2014-4-02












   

 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-2100) Allow Inheritance when setting Deny ACEs

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-2100



  Allow Inheritance when setting Deny ACEs 










Change By:

 Rob Reynolds




Labels:

 windows












   

 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-2100) Allow Inheritance when setting Deny ACEs

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Allow Inheritance when setting Deny ACEs 










The fix will need to be backported into PUP-1987 targeted at Puppet.version less than 3.6.0. That will be tracked as part of ticket PUP-1987.












   

 Add Comment











 













 Puppet /  PUP-2100



  Allow Inheritance when setting Deny ACEs 







 With Access Control Entries (ACEs) on Windows, we currently use [AddAccessDeniedAce|http://msdn.microsoft.com/en-us/library/windows/desktop/aa374962(v=vs.85).aspx] which does not include inheritance and/or propagation to child objects, but [AddAccessDeniedAceEx|http://msdn.microsoft.com/en-us/library/windows/desktop/aa374964(v=vs.85).aspx] does. We are al...















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




 














-- 
You received this message because you are subscribed to 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-1586) PR (2331) Cron Type sanity check for the command parameter is broken

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: PR (2331) Cron Type sanity check for the command parameter is broken 










This fix is not present in the latest puppet build I could find (puppet-3.5.0-rc3):



# crontab -l
7 * * * * /usr/local/bin/party-down
# Puppet Name: hourlytask
2 4 * * * /usr/bin/true

# puppet apply -e 'cron { "hourlytask": minute => 3, }
Notice: Compiled catalog for centos6-master.localdomain in environment production in 0.04 seconds
Error: Could not prefetch cron provider 'crontab': No command, somehow at /root/pup-1586.pp:3
Notice: /Stage[main]/Main/Cron[hourlytask]/ensure: created
"-":9: bad command
errors in crontab file, can't install.
Notice: Finished catalog run in 0.04 seconds















   

 Add Comment











 













 Puppet /  PUP-1586



  PR (2331) Cron Type sanity check for the command parameter is broken 







 When there is a crontab like this   {code}  2 4 * * * /sbin/foobar  # Puppet Name: hourlytask  7 * * * * /usr/local/bin/kick-idlers  {code}  and I apply this manifest:  {code}  cron { "hourlytask": minute => 4 }  {code}  puppet should change the minute field of the 'hourlytask' to 4 and do nothing else.   Instead, it fails to identify the existing job a...















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

Jira (PUP-1586) PR (2331) Cron Type sanity check for the command parameter is broken

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1586



  PR (2331) Cron Type sanity check for the command parameter is broken 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (PUP-1586) PR (2331) Cron Type sanity check for the command parameter is broken

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: PR (2331) Cron Type sanity check for the command parameter is broken 










Sorry, should have clarified that this was merged to the "master" branch. It won't show up in 3.5.x builds, only 3.6.x builds.












   

 Add Comment











 













 Puppet /  PUP-1586



  PR (2331) Cron Type sanity check for the command parameter is broken 







 When there is a crontab like this   {code}  2 4 * * * /sbin/foobar  # Puppet Name: hourlytask  7 * * * * /usr/local/bin/kick-idlers  {code}  and I apply this manifest:  {code}  cron { "hourlytask": minute => 4 }  {code}  puppet should change the minute field of the 'hourlytask' to 4 and do nothing else.   Instead, it fails to identify the existing job a...















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




 














-- 
You received this message because you are subscribed to 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.

Jira (PUP-1987) ACLs - Deny ACL does not set inheritance properly

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-1987



  ACLs - Deny ACL does not set inheritance properly 










Change By:

 Rob Reynolds




Sprint:

 Week 2014-3-26 to 2014-4-02












   

 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

Title: Message Title










 

 Kenneth Barber commented on an issue











 






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










Okay, I think I see the distinction:


The example I have provided only finds the last report for a single node.


Using "distinct on" we can use "SELECT DISTINCT ON (certname) ... ORDER BY end-time" to get a list of all latest reports (ordered by end-time for example) for all certnames.














   

 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)

Jira (HI-127) Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement 










After discussion during the 3/26/2014 PR triage, it was decide to:


Proceed with the 'literal' function.




Drop the "% {%}
" shorthand.




Leave "%%{}" as an undocumented and untested behavior.


PR 185 updated and merged into master in commit 73da4ee.












   

 Add Comment











 













 Hiera /  HI-127



  Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement 







 I have some data that contains Apache variables (such as %{SERVER_NAME}, %{QUERY_STRING}, etc )  in a Hiera file (Yaml backend). However, when I retrieve the value, the string is replaced with  empty value. For instance, for:   myserver: http://%{SERVER_NAME}   I got the value "http//"   I found out that during the lookup in the YAML backend, the answ...

Jira (HI-127) Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Hiera /  HI-127



  Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement 










Change By:

 Charlie Sharpsteen




Fix Version/s:

 1.4.0












   

 Add Comment











 










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




 














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

Jira (PUP-2065) Smoke test packages

Title: Message Title










 

 Peter Huene commented on an issue











 






  Re: Smoke test packages 










Gem looks good on OSX and CentOS. Successfully applied manifests with apply and master/agent. Verified it contains the fix to the regression in RC2.












   

 Add Comment











 













 Puppet /  PUP-2065



  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-1988) ACL - Removing ACEs should properly report the permissions changes

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-1988



  ACL - Removing ACEs should properly report the permissions changes 










Change By:

 Rob Reynolds




Sprint:

 Week 2014-3-26 to 2014-4-02












   

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

Title: Message Title










 

 Peter Huene commented on an issue











 






  Re: Smoke test packages 










Looking at:


tarball


rpm


dmg


gem (+ windows specific)


deb














   

 Add Comment











 













 Puppet /  PUP-2065



  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 receiv

Jira (PUP-2065) Smoke test packages

Title: Message Title










 

 Peter Huene commented on an issue











 






  Re: Smoke test packages 










Windows-specific gem looks good.












   

 Add Comment











 













 Puppet /  PUP-2065



  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 (FACT-236) Facter RPM should not require virt-what

2014-03-31 Thread Adrien Thebo (JIRA)

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Facter RPM should not require virt-what 










The branch containing the EC2 fixes is up at https://github.com/puppetlabs/facter/pull/657 ; if you could pull down that code and verify that it works in your environment that would help greatly.












   

 Add Comment











 













 Facter /  FACT-236



  Facter RPM should not require virt-what 







 There is a bug in virt-what that causes facter to behave incorrectly.  https://bugzilla.redhat.com/show_bug.cgi?id=973663  http://projects.puppetlabs.com/issues/7559#note-71   I'm currently in the process of updating my automation to install facter (and thus puppet) as gems instead of RPM's due to the fact that the RPM (after v1.6.10) requires the virt-w...















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




 














-- 
You received this message because you are subscribed to 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://g

Jira (PUP-1586) PR (2331) Cron Type sanity check for the command parameter is broken

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: PR (2331) Cron Type sanity check for the command parameter is broken 










The RPM was built at SHA=3acebbd84ea8295826eb879bdd8ad54f5f614b2d, which I thought was in master.












   

 Add Comment











 













 Puppet /  PUP-1586



  PR (2331) Cron Type sanity check for the command parameter is broken 







 When there is a crontab like this   {code}  2 4 * * * /sbin/foobar  # Puppet Name: hourlytask  7 * * * * /usr/local/bin/kick-idlers  {code}  and I apply this manifest:  {code}  cron { "hourlytask": minute => 4 }  {code}  puppet should change the minute field of the 'hourlytask' to 4 and do nothing else.   Instead, it fails to identify the existing job a...















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




 














-- 
You received this message because you are subscribed to 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-451) Cumulus Linux

2014-03-31 Thread Leslie Carr (JIRA)

Title: Message Title










 

 Leslie Carr created an issue











 






 Facter /  FACT-451



  Cumulus Linux 










Issue Type:

  Bug




Affects Versions:


 2.0.1




Assignee:

 Eric Sorenson




Created:


 31/Mar/14 1:23 PM




Environment:


Cumulus Linux os




Priority:

  Normal




Reporter:

 Leslie Carr










In facter 2.0.1-0.1rc4 (as on master), the osfamily fact for CumulusLinux is displayed as "Linux" when it should be "Debian" A pull request is forthcoming to fix this issue












   

 Add Comment

Jira (FACT-451) Cumulus Linux

2014-03-31 Thread Leslie Carr (JIRA)

Title: Message Title










 

 Leslie Carr commented on an issue











 






  Re: Cumulus Linux 










https://github.com/puppetlabs/facter/pull/658 has been created for this issue












   

 Add Comment











 













 Facter /  FACT-451



  Cumulus Linux 







 In facter 2.0.1-0.1rc4 (as on master), the osfamily fact for CumulusLinux is displayed as "Linux" when it should be "Debian" A pull request is forthcoming to fix this issue















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




 














-- 
You received this message because you are subscribed to 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-1840) Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1840



  Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (PUP-2065) Smoke test packages

Title: Message Title










 

 Peter Huene commented on an issue











 






  Re: Smoke test packages 










Tarbell looks good. Untar'd, ran install.rb, tested puppet apply, puppet master/agent, and puppet resource on OSX.












   

 Add Comment











 













 Puppet /  PUP-2065



  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-1840) Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts 










Assigning to Adrien Thebo and moving back to TODO per Rob's last update.
 #include 












   

 Add Comment











 













 Puppet /  PUP-1840



  Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts 







 I'm using Puppet in part to ensure [Federal Information Processing Standard 140-2](http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf) (FIPS 140-2) compliance on my network. Part of this compliance for the system underlying Puppet is to make sure that only [FIPS Approved](http://csrc.nist.gov/publications/fips/fips140-2/fips1402annexa.pdf) algo...















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




 














-- 
You received this message because you are subscribed to 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 (PUP-1840) Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts

Title: Message Title










 

 Kurt Wall updated an issue











 






 Puppet /  PUP-1840



  Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall Adrien Thebo












   

 Add Comment











 










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




 














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

Jira (PUP-1586) PR (2331) Cron Type sanity check for the command parameter is broken

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: PR (2331) Cron Type sanity check for the command parameter is broken 










Hmm. Yes that SHA should be from the master branch, I'll check it out.












   

 Add Comment











 













 Puppet /  PUP-1586



  PR (2331) Cron Type sanity check for the command parameter is broken 







 When there is a crontab like this   {code}  2 4 * * * /sbin/foobar  # Puppet Name: hourlytask  7 * * * * /usr/local/bin/kick-idlers  {code}  and I apply this manifest:  {code}  cron { "hourlytask": minute => 4 }  {code}  puppet should change the minute field of the 'hourlytask' to 4 and do nothing else.   Instead, it fails to identify the existing job a...















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




 














-- 
You received this message because you are subscribed to 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-450) DST in France cause puppet to fail (aka 'Could not intern from pson: "\x92" on US-ASCII')

2014-03-31 Thread Adrien Thebo (JIRA)

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: DST in France cause puppet to fail (aka 'Could not intern from pson: "\x92" on US-ASCII') 










What locale is in use on the operating system running the agent? In addition, what is the output of the following command?



ruby -e 'puts Time.now.zone' | xxd















   

 Add Comment











 













 Facter /  FACT-450



  DST in France cause puppet to fail (aka 'Could not intern from pson: "\x92" on US-ASCII') 






  Starting today, I got:   Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from pson: "\x92" on US-ASCII  Warning: Not using cache on failed catalog  Error: Could not retrieve catalog; skipping run   I spend 2h removing the " ' " from comments of my .pp files.   Turns out that the error is in facter:  rubyve...















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




 














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

Jira (PUP-2104) Make puppet able to configure a facter implementation to use

2014-03-31 Thread Kylo Ginsberg (JIRA)

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2104



  Make puppet able to configure a facter implementation to use 










Issue Type:

  Task




Affects Versions:


 3.5.0




Assignee:

 Kylo Ginsberg




Components:


 Catalog Application




Created:


 31/Mar/14 1:34 PM




Environment:


This would allow puppet to plugin alternate facter implementations. Since puppet defaults.rb relies on facter in a few places, some work will be required there, perhaps to lazy-interpret uses of facter.




Fix Versions:


 3.6.0




Priority:

  Normal




Reporter:

 Kylo Ginsberg












   

 Add Comment

Jira (PUP-2105) Puppet config face and the --configprint option operate directly on environment.conf.

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-2105



  Puppet config face and the --configprint option operate directly on environment.conf. 










Change By:

 Joshua Partlow




Issue Type:

 Improvement Bug












   

 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-2105) Puppet config face and the --configprint option operate directly on environment.conf.

Title: Message Title










 

 Joshua Partlow created an issue











 






 Puppet /  PUP-2105



  Puppet config face and the --configprint option operate directly on environment.conf. 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 31/Mar/14 1:35 PM




Fix Versions:


 4.0.0




Priority:

  Normal




Reporter:

 Joshua Partlow










In Puppet 4.0.0, deprecated environment settings will be removed, and the config face will no longer be able to print or set modulepath, manifest and config_version.
The config face needs to be enhanced to include these key environment attributes from the chosen --environment's (or default) environment.conf attributes.
Potentially we can allow setting of these attributes as well to a particular directory environment's environment.conf. This may require creation of the first element of environmentpath, plus the --environment directory. And there may be further pitfalls when allowing 'set' to work for these attributes?
At the same time, we need to figure out how `puppet  --configprint (modulepath|manifest|config_version)` should behave, as this functionality will be broken for the former environment settings as well.

Jira (PUP-1433) Deprecate 'implicit' environment settings and update packaging

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Deprecate 'implicit' environment settings and update packaging 










Deferring the config work to 4.0 (PUP-2105)












   

 Add Comment











 













 Puppet /  PUP-1433



  Deprecate 'implicit' environment settings and update packaging 







 With the new dynamic environments support, we are no longer going to support an "implicit" environment where the modulepath, manifest and config_version location is set explicitly in Puppet's configuration. Instead, packaging should ensure that the environments directory is populated with a default environment with a site.pp.   The manifestdir setting wi...















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




 














-- 
You received this message because you are subscribed to 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-2065) Smoke test packages

Title: Message Title










 

 Peter Huene commented on an issue











 






  Re: Smoke test packages 










.dmg looks good. Installed (not signed, so had to go through the system security settings to allow the install), tested puppet apply, puppet master/agent, and puppet resource on OSX.












   

 Add Comment











 













 Puppet /  PUP-2065



  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-1433) Deprecate 'implicit' environment settings and update packaging

Title: Message Title










 

 Joshua Partlow assigned an issue to Andy Parker











 






 Puppet /  PUP-1433



  Deprecate 'implicit' environment settings and update packaging 










Change By:

 Joshua Partlow




Assignee:

 Andy Parker












   

 Add Comment











 










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




 














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

Jira (PUP-2097) Could not evaluate: Failed to get security information: Incorrect function

Title: Message Title










 

 Andy Parker assigned an issue to Joshua Cooper











 






 Puppet /  PUP-2097



  Could not evaluate: Failed to get security information: Incorrect function 










Change By:

 Andy Parker




Assignee:

 Andy Parker Joshua Cooper












   

 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-2097) Could not evaluate: Failed to get security information: Incorrect function

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2097



  Could not evaluate: Failed to get security information: Incorrect function 










Change By:

 Andy Parker




Component/s:

 DSL












   

 Add Comment











 










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




 














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

Jira (PUP-1937) Acceptance tests assume ruby is in path on windows

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Acceptance tests assume ruby is in path on windows 










Justin Stoller Do you want this to land in 3.2.x? For 3.2.2?
Also, what was merged into Puppet does not include Colin's original change to the acceptance/tests/modules/install/with_version.rb, as that was breaking acceptance in FOSS. So that test may fail in PE?
How should we capture the need to fix up that test so that it works in both testing environments?












   

 Add Comment











 













 Puppet /  PUP-1937



  Acceptance tests assume ruby is in path on windows 







 Which isn't the case when running PE.   If we are going to be able to ensure open source functionality we need to make sure that we can run the tests against PE. PE doesn't include Ruby in the path after its installed. This is an issue with a few tests that directly call ruby.















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




 














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

Jira (HI-46) Hiera should support alternate environments

2014-03-31 Thread Nick Walker (JIRA)

Title: Message Title










 

 Nick Walker commented on an issue











 






  Re: Hiera should support alternate environments 










Even if you specify hiera_config to use the $environment variable it is only loaded once upon startup so you end up with $envrionment = production. 


hiera_config = $confdir/environments/$environment/hiera.yaml



Ends up being equivalent to:


hiera_config = $confdir/environments/production/hiera.yaml















   

 Add Comment











 













 Hiera /  HI-46



  Hiera should support alternate environments 







 Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive.   Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment.















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

Jira (PUP-2065) Smoke test packages

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Smoke test packages 










Checking Debian 6












   

 Add Comment











 













 Puppet /  PUP-2065



  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-1928) puppet's idea of /etc/hosts management does not match real world use

2014-03-31 Thread Alexander Ilyin (JIRA)

Title: Message Title










 

 Alexander Ilyin updated an issue











 






 Puppet /  PUP-1928



  puppet's idea of /etc/hosts management does not match real world use 










Change By:

 Alexander Ilyin









 Here is a valid extract from an  {{  /etc/hosts }}  files on a RHEL box: {noformat} 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 {noformat} Here is the code to make puppet add these entries: {noformat} host { 'localhost':ip => '127.0.0.1',host_aliases => [ 'localhost.localdomain','localhost4', 'localhost4.localdomain4', ],}   host { 'localhost':   ip => '::1',   host_aliases => [ 'localhost.localdomain',   'localhost6', 'localhost6.localdomain6', ],   } {noformat} Notice the "localhost" part is the same in both cases. This causes a problem: {noformat} Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate definition: Host[localhost] is already defined in file /etc/puppet/modules/networking/manifests/init.pp {noformat} puppet-2.7.6-2.el6.noarch












   

 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-1105) The host type should allow multiple IP addresses for a host

2014-03-31 Thread Alexander Ilyin (JIRA)

Title: Message Title










 

 Alexander Ilyin updated an issue











 






 Puppet /  PUP-1105



  The host type should allow multiple IP addresses for a host 










Change By:

 Alexander Ilyin









 It's becoming common for one host to have many possible IP addresses, especially with IPv6, the host type should support this:A possibility would be to allow an array of IPs:  {noformat} host { 'example.com':  ensure   => 'present',  ip   => ['127.0.0.1', '::1'],  target   => '/tmp/hosts',}  {noformat} but alas,  {{  /tmp/hosts }}  only get:  {noformat} 127.0.0.1   example.com  {noformat} 












   

 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-450) DST in France cause puppet to fail (aka 'Could not intern from pson: "\x92" on US-ASCII')

2014-03-31 Thread Sylvain Le Gall (JIRA)

Title: Message Title










 

 Sylvain Le Gall commented on an issue











 






  Re: DST in France cause puppet to fail (aka 'Could not intern from pson: "\x92" on US-ASCII') 










Hendrik: I am a bit a junior admin on Windows, do you have any pointer on howto update facter on windows. I have extracted the facter-2.0.1-rc4.tar.gz using cygwin, but I am not sure what the next step
Adrien: C:\Program Files (x86)\Puppet Labs\Puppet\bin>ruby -e 'puts Time.now.zone' | xxd
000: 5061 7269 732c 204d 6164 7269 6420 2868 Paris, Madrid (h 010: 6575 7265 2064 92e9 74e9 290d 0a eure d..t.)..
C:\Program Files (x86)\Puppet Labs\Puppet\bin>ruby -e 'puts Encoding.default_external' CP850












   

 Add Comment











 













 Facter /  FACT-450



  DST in France cause puppet to fail (aka 'Could not intern from pson: "\x92" on US-ASCII') 






  Starting today, I got:   Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from pson: "\x92" on US-ASCII  Warning: Not using cache on failed catalog  Error: Could not retrieve catalog; skipping run   I spend 2h removing the " ' " from comments of my .pp files.   Turns out that the error is in facter:  rubyve...















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

Jira (PUP-1433) Deprecate 'implicit' environment settings and update packaging

Title: Message Title










 

 Andy Parker assigned an issue to Joshua Partlow











 






 Puppet /  PUP-1433



  Deprecate 'implicit' environment settings and update packaging 










Change By:

 Andy Parker




Assignee:

 Andy Parker Joshua Partlow












   

 Add Comment











 










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




 














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

Jira (PUP-1937) Acceptance tests assume ruby is in path on windows

2014-03-31 Thread Justin Stoller (JIRA)

Title: Message Title

Justin Stoller commented on an issue

Re: Acceptance tests assume ruby is in path on windows

Justin Stoller Do you want this to land in 3.2.x? For 3.2.2?

I don't care exactly when, though, if this reversion causes the pe-puppet tests to go red, then the work in this ticket made the suite less red, but still red, and still confusing for releasing PE. I would want the test changes to go in as soon as possible (but its not a drop everything kinda urgency).

Also, what was merged into Puppet does not include Colin's original change to the acceptance/tests/modules/install/with_version.rb, as that was breaking acceptance in FOSS. So that test may fail in PE?

See above, but yeah, that this might cause false positives in pe-puppet is my primary concern. And since there isn't a definite statement that, yes, this will break pe-puppet, I'd like to see it merged into pe-puppet so we can definitely see yes or no.

How should we capture the need to fix up that test so that it works in both testing environments?

I think this should follow whatever is the best workflow for you team

Add Comment

Puppet / PUP-1937

Acceptance tests assume ruby is in path on windows

Which isn't the case when running PE. If we are going to be able to ensure open source functionality we need to make sure that we can run the tests against PE. PE doesn't include Ruby in the path after its installed. This is an issue with a few tests that directly call ruby.

Jira (PUP-1320) service puppet ensure stopped kills off cron-run puppet with "Caught TERM; calling stop"

2014-03-31 Thread Zachary Stern (JIRA)

Title: Message Title










 

 Zachary Stern updated an issue











 






 Puppet /  PUP-1320



  service puppet ensure stopped kills off cron-run puppet with "Caught TERM; calling stop" 










Change By:

 Zachary Stern




Labels:

 customer redmine












   

 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-2056) Is checklist current

Title: Message Title










 

 Peter Huene assigned an issue to Peter Huene











 






 Puppet /  PUP-2056



  Is checklist current 










Change By:

 Peter Huene




Assignee:

 Peter Huene












   

 Add Comment











 










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




 














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

Jira (PDB-554) EC2 instances are being left behind and not cleaned up