Jira (FACT-376) Backport OpenBSD changes to Facter 2

2014-05-12 Thread Jasper Lievisse Adriaanse (JIRA)
Title: Message Title










 

 Jasper Lievisse Adriaanse commented on an issue











 






  Re: Backport OpenBSD changes to Facter 2 










Thank you very much!












   

 Add Comment











 













 Facter /  FACT-376



  Backport OpenBSD changes to Facter 2 







 Not a bug per se, but I was wondering about some code I've written last year for Facter that never got included into a release because they were features, not bugfixes. However, looking at the rc1 of facter 2.0.1 I noticed the code was most still not there:   https://github.com/puppetlabs/facter/commits?author=jasperla   https://github.com/puppetlabs/fa...















 This 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-2551) Certname must be lowercase error not helpful

2014-05-12 Thread Chad Metcalf (JIRA)
Title: Message Title










 

 Chad Metcalf created an issue











 






 Puppet /  PUP-2551



  Certname must be lowercase error not helpful 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 12/May/14 10:19 PM




Priority:

  Normal




Reporter:

 Chad Metcalf










Currently if you set a non lowercase certname you get this error:



Error: Could not initialize global default settings: Certificate names must be lower case; see #1168



Its not terribly helpful for a couple reasons.


We've moved away from RedMine. Only seasoned puppet veterans will see #1168 and say "oh right, redmine, duh."


#1168 is an ancient thread that represents a dark time in puppet's history we'd all rather forget. Who cares about these comments? We need a succinct snippet for why we require lowercase names. Not force new users to read the insane old days. Especially since there really isn't any resolution on that thread.


I seem to recall there was a better resource somewhere that had a more definitive explanation. I've helped numerous people get past this.











  

Jira (PUP-2395) Installation problem for puppetmaster-puppet 3.5.1 on Ubuntu 13.10

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-2395



  Installation problem for puppetmaster-puppet 3.5.1 on Ubuntu 13.10 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.6.0 RC




Fix Version/s:

 3.6.0












   

 Add Comment











 










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




 














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


Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Merge puppet 3.6 into pe-puppet 3.3.x 










Branan Purvine-Riley over in the mco room, Nick Lewis said "It's in a build, and the smoke tests worked! (well that one did, now other problems)" so ... at least one step closer to reattempting the promotion. I wanted to make sure you were in the loop 












   

 Add Comment











 













 Puppet /  PUP-2404



  Merge puppet 3.6 into pe-puppet 3.3.x 







 pe-puppet/3.3.x is based on puppet 3.6.x















 This 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-2382) Standardize existing FFI code and refactor where necessary

2014-05-12 Thread Ethan Brown (JIRA)
Title: Message Title










 

 Ethan Brown commented on an issue











 






  Re: Standardize existing FFI code and refactor where necessary 










I'm not sure yet how we're going to approach the CloseHandle calls. That's the only redundant definition as far as I can tell... so perhaps we end up with a small module that we can mix-in.












   

 Add Comment











 













 Puppet /  PUP-2382



  Standardize existing FFI code and refactor where necessary 







 We need to standardize on how windows types, e.g. DWORD, HANDLE, etc are represented in FFI, and refactor places where duplicate methods are defined, e.g. CloseHandle, etc.















 This 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-184) Using 'ip addr' over ifconfig

2014-05-12 Thread Patrick Hemmer (JIRA)
Title: Message Title










 

 Patrick Hemmer commented on an issue











 






  Re: Using 'ip addr' over ifconfig 










For anyone else interested, this is the custom fact I'm using to get the proper IP:



Facter.add(:ip) do
  confine :kernel => :linux
  setcode do
default_route_line = %x{ip route}.split("\n").find{|l| l.match(/^default /)}
if default_route_line then
  default_gw = default_route_line.match(/ via (\S+)/)[1]
  ip = %x{ip route get #{default_gw}}.match(/ src (\S+)/)[1]
else
  ip = %x{ip addr}.match(/inet ([^\/]+).* scope global/)[1]
end
  end
end



Unfortunately it had to be called ip. You can't call it ipaddress as custom facts don't override built-in facts. And it can't be called ipaddr as it then causes issues with the ruby IPAddr built-in class.
This will get the IP address the system uses by default. If the system has more than one default route, it will pick the first one. If the system has no default route, it will pick the first global scope address (address reachable by other hosts). If the system has no global scope address, it will error (easy to modify, but didn't think worth it).












   

 Add Comment











 













 Facter /  FACT-184



  Using 'ip addr' over ifconfig 







   # facter  /usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:85: command not found: /sbin/ifconfig -a  /usr/bin/facter:54: command not found: /sbin/ifconfig -a  /usr/bin/facter:54: command not found: dnsdomainname  /usr/bin/facter:54: command not found: domainname  /usr/bin/facter:54: command not found: /sbin/ifconfig  architecture => i386  domain => int...




Jira (PUP-2519) Settings catalog should create the default environment if environmentpath set.

2014-05-12 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-2519



  Settings catalog should create the default environment if environmentpath set. 










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-1736) Add encoding information to debug output

2014-05-12 Thread Kurt Wall (JIRA)
Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1736



  Add encoding information to debug output 










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-2287) Lambda with default valued parameter cannot be overridden

2014-05-12 Thread Kurt Wall (JIRA)
Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-2287



  Lambda with default valued parameter cannot be overridden 










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-2288) access operation vs. liststart causes confusing errors...

2014-05-12 Thread Kurt Wall (JIRA)
Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-2288



  access operation vs. liststart causes confusing errors... 










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-2240) support unfold/splat of array

2014-05-12 Thread Kurt Wall (JIRA)
Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-2240



  support unfold/splat of array 










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 (FACT-451) Cumulus Linux distro detection needs to be ported to facter-2

2014-05-12 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Facter /  FACT-451



  Cumulus Linux distro detection needs to be ported to facter-2 










Change By:

 Adrien Thebo




Assignee:

 Eric Sorenson 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-2530) Syntax validator for EPP

2014-05-12 Thread Henrik Lindberg (JIRA)
Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Syntax validator for EPP 










You and Andy Parker must have hit "new ticket" at the same time - there is also PUP-2351 












   

 Add Comment











 













 Puppet /  PUP-2530



  Syntax validator for EPP 







 There should be some equivalent to "puppet parser validate" for EPP files. For ERB it is done by piping them through erb to take away all the non ruby code: "erb -x file.erb | ruby -c"















 This 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-376) Backport OpenBSD changes to Facter 2

2014-05-12 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Backport OpenBSD changes to Facter 2 










Backported into facter-2 and merged in 627; this should be released in 2.1.0.












   

 Add Comment











 













 Facter /  FACT-376



  Backport OpenBSD changes to Facter 2 







 Not a bug per se, but I was wondering about some code I've written last year for Facter that never got included into a release because they were features, not bugfixes. However, looking at the rc1 of facter 2.0.1 I noticed the code was most still not there:   https://github.com/puppetlabs/facter/commits?author=jasperla   https://github.com/puppetlabs/fa...















 This 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-2534) Puppet 3.6.0 2014-05-13 Release

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-2534



  Puppet 3.6.0 2014-05-13 Release 










Change By:

 Kylo Ginsberg




Story Points:

 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-2547) Update the downloads page

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2547



  Update the downloads page 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Update downloads page


Update misc/download-options to reflect the new builds you just pushed and also make sure they're displayed. It's a good idea to make sure this looks like it's supposed to


NOTE: this page will hopefully be deprecated soon. The idea is that docs with update their documentation to include "latest release version" and where to download files. This page will then be changed to redirect to docs.puppetlabs.com and will no longer need updating.
Dependencies:


Go / No Go meeting (Status - Ship it!)














   

 Add Comment






Jira (PUP-2534) Puppet 3.6.0 2014-05-13 Release

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2534



  Puppet 3.6.0 2014-05-13 Release 










Issue Type:

  Task




Assignee:

 Release Engineering




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Puppet 3.6.0 2014-05-13 Release
When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items.


The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them.


Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward.


When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.














  

Jira (PUP-2545) Push tag

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2545



  Push tag 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb.
Dependencies:


Go / No Go meeting (except where it's required to push the tag to build packages - MSIs)














   

 Add Comment











 










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


 

Jira (PUP-2549) Send out announcements

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2549



  Send out announcements 










Issue Type:

  Sub-task




Assignee:

 Eric Sorenson




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg












Update the release google document (ask around for location).


Send the drafted release notes email.


If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev).


If RC only send to the specific distribution lists.


Make a PSA on IRC letting those kiddos know about the new release.


Something along the lines of "PSA: facter 1.7.3-rc1 now available"


Dependencies:


Prepare long form release notes and short form release story


Packages pushed




Jira (PUP-2544) Go/no-go meeting

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2544



  Go/no-go meeting 










Issue Type:

  Sub-task




Assignee:

 Ethan Brown




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Get a yes/no for the release from dev, docs, product, qa, releng.
This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release.
Dependencies:


Smoke testing














   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6

Jira (PUP-2536) Is there a JIRA ticket targeted at the release for every commit?

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2536



  Is there a JIRA ticket targeted at the release for every commit? 










Issue Type:

  Sub-task




Assignee:

 Ethan Brown




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Ensure all tickets referenced in the commit log have a bug targeted at the release


git log ..


look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release


Also, make sure the code itself is sane, that you understand why the change was made, etc. etc.


ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release)














   

  

Jira (PUP-2546) Packages pushed

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2546



  Packages pushed 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Push packages


run `rake pl:jenkins:uber_ship`


You will need the keys to the castle (aka the passphrase) for this to work.


Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms.


Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay.


If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file.


If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Matthaus Owens for more details. This file also needs to be manually signed.


Dependencies:


 

Jira (PUP-2539) Merge master into stable

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2539



  Merge master into stable 










Issue Type:

  Sub-task




Assignee:

 Ethan Brown




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










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


git fetch upstream
git rebase upstream/master

git checkout stable
git rebase upstream/stable

git merge master --no-ff --log



Once that looks good:


git push origin
git push upstream



After merging to stable, the jobs on jenkins may require updates (spec, acceptance, etc) when you merge master into stable. Please ensure that the jenkins jobs are updated if necessary.
Dependencies:


Is the code ready for release?


Is there a commit for every JIRA ticket targeted at the release?



Jira (PUP-2538) Update version number in source

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2538



  Update version number in source 










Issue Type:

  Sub-task




Assignee:

 Ethan Brown




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Bump VERSION in lib/ {#project}
/version.rb to correct version.


Commit the updated version file.


e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3-rc1".


If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask).


Once this is done, hand the SHA to be built to RelEng to be tagged.


Dependencies:


Is the code ready for release?


Is there a commit for every JIRA ticket targeted at the release?












Jira (PUP-2550) Close all resolved tickets in Jira

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2550



  Close all resolved tickets in Jira 










Issue Type:

  Sub-task




Assignee:

 Ethan Brown




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Close any tickets that have been resolved for the release.
NOTE: This link may not work properly for RC releases. Edit it to remove the "-rc#". https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%223.6.0%22%20AND%20status%20%3D%20Resolved
There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route:


Select Bulk Change - All # issues


Step 1 - choose all relevant issues (likely all of them)


Step 2 - Select "Transition Issues"


Step 3 - Select "Closed"


Step 4 - Select "Fixed" in Change Resolution.


View what is about to change and confirm it. Then commit the change.


Dependencies:


   

Jira (PUP-2543) Smoke test packages

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2543



  Smoke test packages 










Issue Type:

  Sub-task




Assignee:

 Ethan Brown




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Procedure may vary by project and point in the release cycle. Ask around.
In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through this testing. Lighter testing is acceptable.


Add a link to the Packages repository that you receive from the "Tag and create packages" subtask


Ping folks on your team for help with different platforms.


When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.


When all platforms picked have been smoke tested, move this ticket to done.


Example: Smoke test platforms:


pick some platforms such as


  

Jira (PUP-2537) Is there a commit for every JIRA ticket targeted at the release?

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2537



  Is there a commit for every JIRA ticket targeted at the release? 










Issue Type:

  Sub-task




Assignee:

 Ethan Brown




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Ensure all tickets targeted at the release have a corresponding commit


git log ..


This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers


ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release)














   

 Add Comment





   

Jira (PUP-2542) Tag the release and create packages

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2542



  Tag the release and create packages 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Tag and create packages


Developer provides the SHA - Ethan Brown - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)


checkout the sha


NOTE: If this is a final release, make sure you're releasing only the code that already went through rc, so don't let any new code get into the final release


Make sure you are about to tag the correct thing


Create the tag e.g.) git tag -s -u {GPG key}
 -m "1.7.3-rc1" 1.7.3-rc1


You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.


DO NOT push the tag to the repo, keep it local only


`git descri

Jira (PUP-2540) Is a new version created in Jira for the next version in the series?

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2540



  Is a new version created in Jira for the next version in the series? 










Issue Type:

  Sub-task




Assignee:

 Ethan Brown




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










This happens on Jira - there needs to be a version we can target future issues or issues that didn't make it into the current release.


e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future)


If releasing an RC, ensure you create the RC version e.g 3.6.0 RC (leave RC number off of here).














   

 Add Comment











 




 

Jira (PUP-2535) Is the code ready for release?

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2535



  Is the code ready for release? 










Issue Type:

  Sub-task




Assignee:

 Ethan Brown




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










All tests (spec, acceptance) should be passing on all platforms for both stable & master.


If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc.


If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests


Move all items that should be moved from Ready for CI to Ready for Review


Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board.
NOTE: This link may not work properly for RC releases. Edit it to remove the "-rc#". https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.6.0%22












   
 

Jira (PUP-2548) Docs pushed

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2548



  Docs pushed 










Issue Type:

  Sub-task




Assignee:

 Nicholas Fagerlund




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Push the documentation updates to docs.puppetlabs.com.
Dependencies:


Go / No Go meeting (Status - Ship it!)














   

 Add Comment











 










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




 

 

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

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2541



  Prepare long form release notes and short form release story 










Issue Type:

  Sub-task




Assignee:

 Nicholas Fagerlund




Created:


 12/May/14 4:11 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Collaborating with product for release story
Dependencies:


Is there a JIRA ticket targeted at the release for every commit?


Is there a commit for every JIRA ticket targeted at the release?














   

 Add Comment











 










 This me

Jira (PUP-2484) `puppet module build` should provide deprecated functionality with warning until Puppet v4

2014-05-12 Thread Kurt Wall (JIRA)
Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-2484



  `puppet module build` should provide deprecated functionality with warning until Puppet v4 










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-2519) Settings catalog should create the default environment if environmentpath set.

2014-05-12 Thread Joshua Partlow (JIRA)
Title: Message Title










 

 Joshua Partlow assigned an issue to Unassigned











 






 Puppet /  PUP-2519



  Settings catalog should create the default environment if environmentpath set. 










Change By:

 Joshua Partlow




Assignee:

 Joshua Partlow












   

 Add Comment











 










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




 














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


Jira (PUP-1597) "contain" cannot contain a fully qualified class

2014-05-12 Thread Henrik Lindberg (JIRA)
Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: "contain" cannot contain a fully qualified class 










Merged to master fbc9664












   

 Add Comment











 













 Puppet /  PUP-1597



  "contain" cannot contain a fully qualified class 







 nested contains don't appeare to work. I'm hitting this issue when trying to {{contain}} puppetlabs/mysql::client, but the issue can be reproduced quite simply:   {code}  #  class mybug::client (    $package_ensure = 'present',    $package_name = 'mysql',  ){    package { 'mybug_client':  ensure => $mybug::client::package_ensure,  name => $...















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




 














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


Jira (PUP-2519) Settings catalog should create the default environment if environmentpath set.

2014-05-12 Thread Joshua Partlow (JIRA)
Title: Message Title










 

 Joshua Partlow assigned an issue to Joshua Partlow











 






 Puppet /  PUP-2519



  Settings catalog should create the default environment if environmentpath set. 










Change By:

 Joshua Partlow




Assignee:

 Joshua Partlow












   

 Add Comment











 










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




 














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


Jira (PUP-2484) `puppet module build` should provide deprecated functionality with warning until Puppet v4

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-2484



  `puppet module build` should provide deprecated functionality with warning until Puppet v4 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.6.0 RC




Fix Version/s:

 3.6.0












   

 Add Comment











 










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




 














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


Jira (PUP-2182) Package resource not working as expected in 3.5.0

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-2182



  Package resource not working as expected in 3.5.0 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.6.0




Fix Version/s:

 3.6.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-2522) The transaction_uuid should be available to a node terminus

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-2522



  The transaction_uuid should be available to a node terminus 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.6.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-2253) Enable manifest ordering by default

2014-05-12 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-2253



  Enable manifest ordering by default 










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-1028) Test future evaluator impl of Node Expresson

2014-05-12 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Test future evaluator impl of Node Expresson 










Reviewed by me and Henrik Lindberg. Merged into master in 11a192.












   

 Add Comment











 













 Puppet /  PUP-1028



  Test future evaluator impl of Node Expresson 







 The NodeExpressions are implemented and on master. There are only a few tests specific for the future parser/evaluator for node expressions.  Assess if the available acceptance tests provide enough coverage. Implement missing tests as unit tests.















 This 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-2177) PR (2494) Insecure shipped Cipher settings in Passenger example config

2014-05-12 Thread Aaron Zauner (JIRA)
Title: Message Title










 

 Aaron Zauner commented on an issue











 






  Re: PR (2494) Insecure shipped Cipher settings in Passenger example config  










Hi,
Sorry for the late reply, have been busy all week.
We've worked on a solution for the issue at hand (as it does not only affect puppet related services) and I think we've found a proper solution. See: http://lists.cert.at/pipermail/ach/2014-May/001347.html
The ciphersuite would now look like this (in the GitHub thread we've removed AES256 by accident and removed CAMELLIA among other stuff, I'd like to keep on track with the ciphersuite recommended in the paper and reviewed by a lot of people [devs, cryptographers and security researchers among them]):
EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:DHE-RSA-CAMELLIA256-SHA:DHE-RSA-CAMELLIA128-SHA:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA












   

 Add Comment











 













 Puppet /  PUP-2177



  PR (2494) Insecure shipped Cipher settings in Passenger example config  






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















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




 

 

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

2014-05-12 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo commented on an issue











 






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










Merged in 4b81af6.












   

 Add Comment











 













 Puppet /  PUP-2303



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







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















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




 














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


Jira (PUP-2182) Package resource not working as expected in 3.5.0

2014-05-12 Thread Michael Stahnke (JIRA)
Title: Message Title










 

 Michael Stahnke commented on an issue











 






  Re: Package resource not working as expected in 3.5.0 










Jason A. Smith there are two (maybe 3) reasons to do virtual packages. One is to say that package supplies something like a mail transport as is the case for sendmail/postfix. Another is to say a package has superseded an older package, such as puppet with hiera-pupppet. (A third and much less used virtual provides is for package groups). 
We follow the guidelines from the Fedora project as much as possible. See https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages for how we did this. 












   

 Add Comment











 













 Puppet /  PUP-2182



  Package resource not working as expected in 3.5.0 







 One of my modules has the following code:   {code}  package { 'inetd': ensure => absent; }  {code}   On the next Puppet run, Puppet tries to remove the xinetd package (debug output):  {code}  Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'  Debug: Executing '/bin/rpm -q i...















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




 








   

Jira (PUP-2182) Package resource not working as expected in 3.5.0

2014-05-12 Thread Peter Huene (JIRA)
Title: Message Title










 

 Peter Huene commented on an issue











 






  Re: Package resource not working as expected in 3.5.0 










Behavior with the proposed fix:



[vagrant@localhost puppet]$ sudo -E bundle exec puppet apply -e 'package { "vim": ensure => installed }'
Notice: Compiled catalog for localhost.sd.cox.net in environment production in 0.38 seconds
Warning: The allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
   (at /home/vagrant/src/puppet/lib/puppet/type.rb:816:in `set_default')
Error: Could not find package vim
Error: /Stage[main]/Main/Package[vim]/ensure: change from absent to present failed: Could not find package vim
Notice: Finished catalog run in 0.45 seconds
[vagrant@localhost puppet]$ sudo -E bundle exec puppet apply -e 'package { "vim": ensure => installed, allow_virtual => true }'
Notice: Compiled catalog for localhost.sd.cox.net in environment production in 0.39 seconds
Notice: Finished catalog run in 0.13 seconds
[vagrant@localhost puppet]$ sudo -E bundle exec puppet apply -e 'package { "vim": ensure => installed, allow_virtual => false }'
Notice: Compiled catalog for localhost.sd.cox.net in environment production in 0.37 seconds
Error: Could not find package vim
Error: /Stage[main]/Main/Package[vim]/ensure: change from absent to present failed: Could not find package vim
Notice: Finished catalog run in 0.45 seconds















   

 Add Comment











 













 Puppet /  PUP-2182



  Package resource not working as expected in 3.5.0 







 One of my modules has the following code:   {code}  package { 'inetd': ensure => absent; }  {code}   On the next Puppet run, Puppet tries to remove the xinetd package (debug output):  {code}  Debug: Executing '/bin/rpm -q inetd --

Jira (PUP-1028) Test future evaluator impl of Node Expresson

2014-05-12 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-1028



  Test future evaluator impl of Node Expresson 










Change By:

 Andy Parker




Assignee:

 Henrik Lindberg 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-2182) Package resource not working as expected in 3.5.0

2014-05-12 Thread Jason A. Smith (JIRA)
Title: Message Title










 

 Jason A. Smith commented on an issue











 






  Re: Package resource not working as expected in 3.5.0 










I am not a yum or rpm expert, but usually when I see virtual package names, they are truly virtual names, not names of old deprecated packages, like sendmail/postfix (output abbreviated):


$ rpm -q postfix --provides
MTA  
config(postfix) = 2:2.6.6-6.el6_5
server(smtp)  
smtpd  
smtpdaemon  
postfix = 2:2.6.6-6.el6_5

$ rpm -q sendmail --provides
MTA  
config(sendmail) = 8.14.4-8.el6
server(smtp)  
smtpdaemon  
sendmail = 8.14.4-8.el6



MTA and smtpdaemon are the virtual names. I could be wrong, but I don't think they normally mix virtual names with real package names. Doing that can cause these types of problems. This should be what the Obsoletes tag is for, and that is already in the puppet spec file. Isn't that enough?












   

 Add Comment











 













 Puppet /  PUP-2182



  Package resource not working as expected in 3.5.0 







 One of my modules has the following code:   {code}  package { 'inetd': ensure => absent; }  {code}   On the next Puppet run, Puppet tries to remove the xinetd package (debug output):  {code}  Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'  Debug: Executing '/bin/rpm -q i...















 This message was sen

Jira (PUP-2182) Package resource not working as expected in 3.5.0

2014-05-12 Thread Matthaus Owens (JIRA)
Title: Message Title










 

 Matthaus Owens commented on an issue











 






  Re: Package resource not working as expected in 3.5.0 










Kylo Ginsberg From a packaging standpoint, puppet will always provide hiera-puppet, as the hiera puppet backend is inside of puppet. That might be a change worth considering for puppet 4.












   

 Add Comment











 













 Puppet /  PUP-2182



  Package resource not working as expected in 3.5.0 







 One of my modules has the following code:   {code}  package { 'inetd': ensure => absent; }  {code}   On the next Puppet run, Puppet tries to remove the xinetd package (debug output):  {code}  Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'  Debug: Executing '/bin/rpm -q 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, vi

Jira (PUP-42) Support data and puppet extensions contributed from modules

2014-05-12 Thread Zachary Stern (JIRA)
Title: Message Title










 

 Zachary Stern updated an issue











 






 Puppet /  PUP-42



  Support data and puppet extensions contributed from modules  










Change By:

 Zachary Stern




Labels:

 customer












   

 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-1157) puppet should support data in modules

2014-05-12 Thread Zachary Stern (JIRA)
Title: Message Title










 

 Zachary Stern updated an issue











 






 Puppet /  PUP-1157



  puppet should support data in modules 










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 (PDB-667) PR (965): Unpin the version of beaker - kbarber

2014-05-12 Thread gepetto-bot (JIRA)
Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (965): Unpin the version of beaker - kbarber 










Pull request Unpin the version of beaker has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-667



  PR (965): Unpin the version of beaker - kbarber 







 h2. Unpin the version of beaker   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 965 Discussion|https://github.com/puppetlabs/puppetdb/pull/965]  * [Pull Request 965 File Diff|https://github.com/puppetlabs/puppetdb/pull/965/files]  h2. Pull Request Description   We had...















 This 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-667) PR (965): Unpin the version of beaker - kbarber

2014-05-12 Thread gepetto-bot (JIRA)
Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (965): Unpin the version of beaker - kbarber 










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












   

 Add Comment











 













 PuppetDB /  PDB-667



  PR (965): Unpin the version of beaker - kbarber 







 h2. Unpin the version of beaker   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 965 Discussion|https://github.com/puppetlabs/puppetdb/pull/965]  * [Pull Request 965 File Diff|https://github.com/puppetlabs/puppetdb/pull/965/files]  h2. Pull Request Description   We had...















 This 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-b

Jira (PUP-1597) "contain" cannot contain a fully qualified class

2014-05-12 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-1597



  "contain" cannot contain a fully qualified class 










Change By:

 Andy Parker




Assignee:

 Henrik Lindberg












   

 Add Comment











 










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




 














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


Jira (PUP-1263) Synonyms (title, namevar, name) make it confusing.

2014-05-12 Thread J.D. Welch (JIRA)
Title: Message Title










 

 J.D. Welch updated an issue











 






 Puppet /  PUP-1263



  Synonyms (title, namevar, name) make it confusing. 










Change By:

 J.D. Welch




Assignee:

 J.D. Welch 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-1890) URI.unescape mangles UTF-8 paths producing invalid ASCII strings

2014-05-12 Thread Ben Hagen (JIRA)
Title: Message Title










 

 Ben Hagen commented on an issue











 






  Re: URI.unescape mangles UTF-8 paths producing invalid ASCII strings 










There is no need for a puppetmaster to trigger this bug:


mkdir -p /tmp/src; touch /tmp/ö.txt; puppet apply --trace --exec 'file { "/tmp/dst":ensure => directory, recurse => true, source => "/tmp/src" }'





puppet 3.4.3
ruby 1.9.3p484 (2013-11-22 revision 43786) [i686-linux]
ubuntu 14.04















   

 Add Comment











 













 Puppet /  PUP-1890



  URI.unescape mangles UTF-8 paths producing invalid ASCII strings 







 Hi,   I am running a puppet server under Ubuntu 12.04 (Puppet 2.7.11) and a puppet client under Ubuntu 14.04 (Puppet 3.4.2).   I am distributing a directory of ttf fonts from the server to the clients, the rule is     file{"/usr/local/share/fonts/FreeFonts":  ensure => directory,  mode => 0444,  recurse => true,   ...















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




 

Jira (PUP-2271) yumrepo attributes cannot be set to '_none_'

2014-05-12 Thread Doug Ritchie (JIRA)
Title: Message Title










 

 Doug Ritchie commented on an issue











 






  Re: yumrepo attributes cannot be set to '_none_' 










Just want to note that this did work prior to 3.5.0, but it looks like yumrepo.rb didn't validate parameters at all prior to that release. I don't know how common it is to use proxy = none (we use it on all of our internally-hosted repositories), but our test upgrade from 3.3.1 failed in lab on this issue.












   

 Add Comment











 













 Puppet /  PUP-2271



  yumrepo attributes cannot be set to '_none_' 







 The {{yumrepo}} attribute cannot be set to the value "_none_" even though this is a supported value for the yum {{proxy}} parameter. We should fix this.   {code}  $ puppet apply -e "yumrepo {'base': proxy => '_none_'}"  Notice: Compiled catalog for localhost.localdomain in environment production in 0.03 seconds  Error: Parameter proxy failed on Yumrepo[b...















 This 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 puppe

Jira (PUP-1890) URI.unescape mangles UTF-8 paths producing invalid ASCII strings

2014-05-12 Thread Matthaus Owens (JIRA)
Title: Message Title










 

 Matthaus Owens commented on an issue











 






  Re: URI.unescape mangles UTF-8 paths producing invalid ASCII strings 










The launchpad bug has this nicely small test case:

the following line will trigger the bug:
mkdir -p /tmp/src; touch /tmp/ö.txt; puppet apply --exec 'file 

Unknown macro: { "/tmp/dst"}

'













   

 Add Comment











 













 Puppet /  PUP-1890



  URI.unescape mangles UTF-8 paths producing invalid ASCII strings 







 Hi,   I am running a puppet server under Ubuntu 12.04 (Puppet 2.7.11) and a puppet client under Ubuntu 14.04 (Puppet 3.4.2).   I am distributing a directory of ttf fonts from the server to the clients, the rule is     file{"/usr/local/share/fonts/FreeFonts":  ensure => directory,  mode => 0444,  recurse => true,   ...















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




 








Jira (PDB-667) PR (965): Unpin the version of beaker - kbarber

2014-05-12 Thread gepetto-bot (JIRA)
Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (965): Unpin the version of beaker - kbarber 










kbarber commented:
@pljenkinsro retest this please












   

 Add Comment











 













 PuppetDB /  PDB-667



  PR (965): Unpin the version of beaker - kbarber 







 h2. Unpin the version of beaker   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 965 Discussion|https://github.com/puppetlabs/puppetdb/pull/965]  * [Pull Request 965 File Diff|https://github.com/puppetlabs/puppetdb/pull/965/files]  h2. Pull Request Description   We had...















 This 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-2512) Validation for `enable` in service{} is lacking.

2014-05-12 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Validation for `enable` in service{} is lacking. 










Ashley Penney could you determine if this was a regression or if this has always been a problem?












   

 Add Comment











 













 Puppet /  PUP-2512



  Validation for `enable` in service{} is lacking. 







 [root@ccoifar9r5c1giy postgresql]# puppet resource service postgresql enable=running  Error: The systemd provider can not handle attribute enable  Error: /Service[postgresql]/enable: change from true to running failed: The systemd provider can not handle attribute enable   I discovered this while breaking Postgresql. It happily passes a value of running...















 This 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-2512) Validation for `enable` in service{} is lacking.

2014-05-12 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo updated an issue











 






 Puppet /  PUP-2512



  Validation for `enable` in service{} is lacking. 










Change By:

 Adrien Thebo




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-2512) Validation for `enable` in service{} is lacking.

2014-05-12 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo updated an issue











 






 Puppet /  PUP-2512



  Validation for `enable` in service{} is lacking. 










Change By:

 Adrien Thebo




Component/s:

 Types and Providers












   

 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-2512) Validation for `enable` in service{} is lacking.

2014-05-12 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo updated an issue











 






 Puppet /  PUP-2512



  Validation for `enable` in service{} is lacking. 










Change By:

 Adrien Thebo




Labels:

 service












   

 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-2531) Provide validation tool for EPP

2014-05-12 Thread Henrik Lindberg (JIRA)
Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Provide validation tool for EPP 










Testing templates in a vacuum requires being able to pass a hash map of name to values. It would also be very beneficial to be able to render the result of the template interactively. These two features suggest that there should be a separate command for epp - e.g. 



epp validate mytemplate.epp --values '{a => foo, b=> 10}'
epp render mytemplate.epp --values '{a => foo, b=> 10}'



These are evaluated in an environment. Since they may reference global variables, the initial import must also take place just as it does for puppet parser validate, but it cannot run an actual compilation (while that reports issues, it would then be meaningless to have a separate validate, since the templates are validated when parsed and evaluated anyway).
Thus, for well written templates, that only access local variables (and globals) these to features of an epp face / command are of great value. 












   

 Add Comment











 













 Puppet /  PUP-2531



  Provide validation tool for EPP 







 For {{.pp}} files users have {{puppet parser validate}} to check if the syntax is right. However, for EPP there is no equivalent command. There needs to be one.   If it is possible to accurately detect the file type maybe {{puppet parser validate}} could do the determination automagically. If there isn't, then we could maybe add a flag to the command to ...









  

Jira (PUP-2532) parameter lookup produces screwy result for default values

2014-05-12 Thread Henrik Lindberg (JIRA)
Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: parameter lookup produces screwy result for default values 










Link added to 

PUP-488
 which describes the problem in its referenced pre-docs (i.e. lookup of parameter value changes depending on perspective).












   

 Add Comment











 













 Puppet /  PUP-2532



  parameter lookup produces screwy result for default values 







 When the future parser "lookup resource parameter" evaluates and there is no parameter value set by the evaluated manifest logic at that point, the evaluator then looks up the default value for that parameter.   This unfortunately looks up the default value as seen from the perspective of the "lookup resource parameter" scope/context, and not the context...















 This 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

Jira (PUP-2532) parameter lookup produces screwy result for default values

2014-05-12 Thread Henrik Lindberg (JIRA)
Title: Message Title










 

 Henrik Lindberg created an issue











 






 Puppet /  PUP-2532



  parameter lookup produces screwy result for default values 










Issue Type:

  Bug




Assignee:

 Andy Parker




Components:


 DSL




Created:


 12/May/14 9:40 AM




Fix Versions:


 3.7.0




Priority:

  Normal




Reporter:

 Henrik Lindberg










When the future parser "lookup resource parameter" evaluates and there is no parameter value set by the evaluated manifest logic at that point, the evaluator then looks up the default value for that parameter.
This unfortunately looks up the default value as seen from the perspective of the "lookup resource parameter" scope/context, and not the context in which the resource was defined. Thus, the evaluator will produce a "lie" in every other context except the one where the resource was defined.
This is unacceptable.
There are different ways to solve this:


Do not every lookup default (rationale: we don't know what the value ending up in the catalog will be until it is actually computed at the end of the compilation when no more user logic will be evaluated).


Do the same kind of

Jira (PUP-1597) "contain" cannot contain a fully qualified class

2014-05-12 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: "contain" cannot contain a fully qualified class 










I changed include to return the resources that it brought in. I just want to make sure that these don't leak into the manifests since the language cannot handle the resource objects themselves.












   

 Add Comment











 













 Puppet /  PUP-1597



  "contain" cannot contain a fully qualified class 







 nested contains don't appeare to work. I'm hitting this issue when trying to {{contain}} puppetlabs/mysql::client, but the issue can be reproduced quite simply:   {code}  #  class mybug::client (    $package_ensure = 'present',    $package_name = 'mysql',  ){    package { 'mybug_client':  ensure => $mybug::client::package_ensure,  name => $...















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




 














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

Jira (PUP-1028) Test future evaluator impl of Node Expresson

2014-05-12 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-1028



  Test future evaluator impl of Node Expresson 










Change By:

 Andy Parker




Assignee:

 Henrik Lindberg












   

 Add Comment











 










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




 














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


Jira (PUP-2214) Many puppet commands fail when using a configured or requested directory environment that doesn't exist.

2014-05-12 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker assigned an issue to Joshua Partlow











 






 Puppet /  PUP-2214



  Many puppet commands fail when using a configured or requested directory environment that doesn't exist. 










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-1597) "contain" cannot contain a fully qualified class

2014-05-12 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-1597



  "contain" cannot contain a fully qualified class 










Change By:

 Andy Parker




Assignee:

 Henrik Lindberg 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-2531) Provide validation tool for EPP

2014-05-12 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker created an issue











 






 Puppet /  PUP-2531



  Provide validation tool for EPP 










Issue Type:

  New Feature




Assignee:

 Andy Parker




Components:


 DSL




Created:


 12/May/14 8:46 AM




Priority:

  Normal




Reporter:

 Andy Parker










For .pp files users have puppet parser validate to check if the syntax is right. However, for EPP there is no equivalent command. There needs to be one.
If it is possible to accurately detect the file type maybe puppet parser validate could do the determination automagically. If there isn't, then we could maybe add a flag to the command to indicate that it is an epp file.












   

 Add Comment











 







 

Jira (PUP-2530) Syntax validator for EPP

2014-05-12 Thread JIRA
Title: Message Title










 

 Erik Dalén created an issue











 






 Puppet /  PUP-2530



  Syntax validator for EPP 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 12/May/14 8:33 AM




Priority:

  Normal




Reporter:

 Erik Dalén










There should be some equivalent to "puppet parser validate" for EPP files. For ERB it is done by piping them through erb to take away all the non ruby code: "erb -x file.erb | ruby -c"












   

 Add Comment











 










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




 







   

Jira (PUP-457) (#18730) Add a Hiera node terminus

2014-05-12 Thread JIRA
Title: Message Title










 

 Erik Dalén commented on an issue











 






  Re: (#18730) Add a Hiera node terminus 










This was shipped in a module but then broken by puppet 3.4.0: PUP-1843












   

 Add Comment











 













 Puppet /  PUP-457



  (#18730) Add a Hiera node terminus 







 Allows using hiera as node terminus instead of doing something like  include hiera_array('puppet::classes') in site.pp.   It uses the keys puppet::classes, puppet::parameters &  puppet::environment.















 This 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-1963) Generated resources never receive dependency edges

2014-05-12 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Generated resources never receive dependency edges 










Yeah, #2 would be a breaking change so would be nice to get into puppet 4.
Charlie Sharpsteen I haven't looked at the code enough to consider what this would take. Have you spiked the implementation for either #1 or #2? 
Basically I'm wondering about LOE, so if you've investigated enough to warrant a guess, that'd be great. If not, we might want to add an "investigating" ticket to the board to spike this. (We also might want to break out #1 and #2 into separate tickets, but we that can be part of the investigation.)












   

 Add Comment











 













 Puppet /  PUP-1963



  Generated resources never receive dependency edges 







 First off I will quickly explain what it is I'm trying to do. I have installed the puppetlabs-apache-0.0.3 module that provides a new type called a2mod. My goal is to use virtual resources to collect a list of modules to enable/disable on a node. I would also however, like to ensure that all other apache modules are disabled on the system. I found the...















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




 






  

Jira (PDB-667) PR (965): Unpin the version of beaker - kbarber

2014-05-12 Thread gepetto-bot (JIRA)
Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (965): Unpin the version of beaker - kbarber 










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












   

 Add Comment











 













 PuppetDB /  PDB-667



  PR (965): Unpin the version of beaker - kbarber 







 h2. Unpin the version of beaker   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 965 Discussion|https://github.com/puppetlabs/puppetdb/pull/965]  * [Pull Request 965 File Diff|https://github.com/puppetlabs/puppetdb/pull/965/files]  h2. Pull Request Description   We had...















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




 














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

Jira (PDB-551) Make a statement about new API versioning for 2.0.0

2014-05-12 Thread Kenneth Barber (JIRA)
Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Make a statement about new API versioning for 2.0.0 










PR for index is here: https://github.com/puppetlabs/puppet-docs/pull/321












   

 Add Comment











 













 PuppetDB /  PDB-551



  Make a statement about new API versioning for 2.0.0 







 This stems from constant discussions about what changes are acceptable where for different API changes. We always forget the decisions of the past, and we'd rather just have a policy to some extent. Also we want to relax some of our previous rules about changing 'stable' APIs and that requires a public statement about the future for API consumers.   I've...















 This 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-667) PR (965): Unpin the version of beaker - kbarber

2014-05-12 Thread Kenneth Barber (JIRA)
Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-667



  PR (965): Unpin the version of beaker - kbarber 










Change By:

 Kenneth Barber




Story Points:

 0




Affects Version/s:

 1.6.3




Fix Version/s:

 1.6.x




Issue Type:

 Task 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 (PDB-667) PR (965): Unpin the version of beaker - kbarber

2014-05-12 Thread Kenneth Barber (JIRA)
Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-667



  PR (965): Unpin the version of beaker - kbarber 










Change By:

 Kenneth Barber




Sprint:

 20140507 to 20140521












   

 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-667) PR (965): Unpin the version of beaker - kbarber

2014-05-12 Thread gepetto-bot (JIRA)
Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-667



  PR (965): Unpin the version of beaker - kbarber 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 12/May/14 6:23 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Unpin the version of beaker


Author: Ken Barber 


Company: Puppet Labs Inc.


Github ID: kbarber


Pull Request 965 Discussion


Pull Request 965 File Diff


Pull Request Description

We had pinned beaker previously because we were waiting for some of our new EC2 customisations to be merged in and released. This has been done now.
Signed-off-by: Ken Barber 

(webhooks-id: c9b301f29508b441d55b3379d65ba7ad)
  

Jira (PUP-2529) Vim syntax file performs incorrect indent for if.. else..

2014-05-12 Thread N David Brown (JIRA)
Title: Message Title










 

 N David Brown updated an issue











 






 Puppet /  PUP-2529



  Vim syntax file performs incorrect indent for if.. else.. 










Change By:

 N David Brown









 Support for Vim has been provided here:  https://github.com/puppetlabs/puppet/tree/master/ext/vimWith the current syntax file indentation is performed incorrectly for  Java-style  if.. else.. :{noformat}if $condition {$myvar = -1} else {$myvar = 0}{noformat}Many of us don't use C-style if.. else.. so we'd be grateful for a fix.












   

 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-2529) Vim syntax file performs incorrect indent for if.. else..

2014-05-12 Thread N David Brown (JIRA)
Title: Message Title










 

 N David Brown created an issue











 






 Puppet /  PUP-2529



  Vim syntax file performs incorrect indent for if.. else.. 










Issue Type:

  Bug




Affects Versions:


 3.5.1 RC




Assignee:


 Unassigned




Created:


 12/May/14 4:33 AM




Environment:


All




Priority:

  Trivial




Reporter:

 N David Brown










Support for Vim has been provided here:
 https://github.com/puppetlabs/puppet/tree/master/ext/vim
With the current syntax file indentation is performed incorrectly for if.. else.. :
 if $condition  { $myvar = -1 }
 else  { $myvar = 0 }
Many of us don't use C-style if.. else.. so we'd be grateful for a fix.












   

 Add Comment
   

Jira (PUP-2529) Vim syntax file performs incorrect indent for if.. else..

2014-05-12 Thread N David Brown (JIRA)
Title: Message Title










 

 N David Brown updated an issue











 






 Puppet /  PUP-2529



  Vim syntax file performs incorrect indent for if.. else.. 










Change By:

 N David Brown









 Support for Vim has been provided here:  https://github.com/puppetlabs/puppet/tree/master/ext/vimWith the current syntax file indentation is performed incorrectly for if.. else.. : {noformat} if $condition {$myvar = -1} else {$myvar = 0} {noformat}   Many of us don't use C-style if.. else.. so we'd be grateful for a fix.












   

 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-2516) Delete a clients certificate with HTTP API no longer working

2014-05-12 Thread Thomas Martensson (JIRA)
Title: Message Title










 

 Thomas Martensson updated an issue











 






 Puppet /  PUP-2516



  Delete a clients certificate with HTTP API no longer working 










Change By:

 Thomas Martensson









 When deploying openvz images, we use a init-script to delete puppets ssl directory on the client and then run curl to deletes the clients certificate from the puppet server:{code}curl -k -X DELETE -H "Accept: pson" "https://puppet.example.com:8140/production/certificate_status/client.examle.com"{code}After upgrading to puppet 3.5.1 this stopped working, I have read that I need to revoke the certificate first and that works:{code}curl -k -X PUT -H "Content-Type: text/pson" --data '{"desired_state":"revoked"}' https://puppet.example.com:8140/production/certificate_status/client.example.com{code}I have verified that the certificate gets revoked on the server:{code}[root@puppet ~]# puppet cert list client.example.com- "client.example.com" (SHA256) A9:FD:2D:C3:E4:7C:84:12:9C:D0:B2:4C:F2:81:AB:A0:BE:9C:A4:40:A7:8E:4A:6A:D8:E0:A4:D7:10:A9:4B:E2 (certificate revoked){code}After this, the documentation says that I should run the DELETE command described above but that fails (using | sed for readability):{code}curl -k -X DELETE -H "Accept: pson" https://puppet.example.com:8140/production/certificate_status/ work-reduce203 client . trioptima example .com | sed 's/,/\n/g'{"issue_kind":"RUNTIME_ERROR""message":"Server Error: undefined method `each' for nil:NilClass""stacktrace":["/usr/lib/ruby/site_ruby/1.8/puppet/network/http/route.rb:72:in `process'""/usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:63:in `process'""/usr/lib/ruby/site_ruby/1.8/puppet/util/profiler/none.rb:6:in `profile'""/usr/lib/ruby/site_ruby/1.8/puppet/util/profiler.rb:43:in `profile'""/usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:61:in `process'""/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick/rest.rb:31:in `service'""/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'""/usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'""/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:36:in `listen'""/usr/lib/ruby/1.8/webrick/server.rb:173:in `call'""/usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'""/usr/lib/ruby/1.8/webrick/server.rb:162:in `start'""/usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'""/usr/lib/ruby/1.8/webrick/server.rb:95:in `start'""/usr/lib/ruby/1.8/webrick/server.rb:92:in `each'""/usr/lib/ruby/1.8/webrick/server.rb:92:in `start'""/usr/lib/ruby/1.8/webrick/server.rb:23:in `start'""/usr/lib/ruby/1.8/webrick/server.rb:82:in `start'""/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:30:in `listen'""/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `initialize'""/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `new'""/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `listen'""/usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:27:in `start'""/usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:139:in `start'""/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:284:in `start_webrick_master'""/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:200:in `main'""/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:160:in `run_command'""/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:372:in `run'""/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:479:in `plugin_hook