Jira (PUP-3060) Remove Warning on Ruby 2.0 / Windows about "DL is deprecated, please use Fiddle"

2014-08-18 Thread Josh Cooper (JIRA) 
Title: Message Title










 

 Josh Cooper assigned an issue to Josh Cooper











 






 Puppet /  PUP-3060



  Remove Warning on Ruby 2.0 / Windows about "DL is deprecated, please use Fiddle" 










Change By:

 Josh Cooper




Assignee:

 Josh Cooper












   

 Add Comment











 










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




 














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

Jira (PUP-2986) Update Windows Installer license file to reference Unknownr addition that is MIT licensed

2014-08-18 Thread Josh Cooper (JIRA) 
Title: Message Title










 

 Josh Cooper assigned an issue to Josh Cooper











 






 Puppet /  PUP-2986



  Update Windows Installer license file to reference Unknownr addition that is MIT licensed 










Change By:

 Josh Cooper




Assignee:

 Josh Cooper












   

 Add Comment











 










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




 














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

Jira (PUP-3047) Validate Puppet -x64-mingw32 gem dependencies on x64

2014-08-18 Thread Josh Cooper (JIRA) 
Title: Message Title










 

 Josh Cooper commented on an issue











 






  Re: Validate Puppet -x64-mingw32 gem dependencies on x64 










On Mac, build the gem packages:


$ git rev-parse HEAD
ac8d4e257f69beaf87489b2e2a57f8aaab512edc
$ bundle update
...
$ bundle exec rake package:implode package:bootstrap package:gem
...
$ ls -1 pkg
puppet-3.6.2.1006-x64-mingw32.gem
puppet-3.6.2.1006-x86-mingw32.gem
puppet-3.6.2.1006.gem



On Windows, ruby 1.9.3 x86, install the puppet gem:


C:\temp>ruby --version
ruby 1.9.3p545 (2014-02-24) [i386-mingw32]

C:\temp>gem install puppet-3.6.2.1006-x86-mingw32.gem
...
Successfully installed ffi-1.9.3-x86-mingw32
Successfully installed win32-dir-0.4.9
Successfully installed win32-security-0.2.5
Successfully installed win32console-1.3.2-x86-mingw32
Successfully installed facter-2.1.0-x86-mingw32
Successfully installed hiera-1.3.4
Successfully installed rgen-0.6.6
Successfully installed win32-eventlog-0.6.1
Successfully installed win32-process-0.7.4
Successfully installed win32-service-0.8.5
Successfully installed minitar-0.5.4
Successfully installed puppet-3.6.2.1006-x86-mingw32
12 gems installed

C:\temp>gem dependency puppet
Gem puppet-3.6.2.1006-x86-mingw32
  facter (< 3, > 1.6)
  ffi (= 1.9.3)
  hiera (~> 1.0)
  json_pure (>= 0)
  minitar (~> 0.5.4)
  rgen (~> 0.6.5)
  win32-dir (~> 0.4.9)
  win32-eventlog (~> 0.6.1)
  win32-process (~> 0.7.4)
  win32-security (~> 0.2.5)
  win32-service (~> 0.8.4)
  win32console (= 1.3.2)



Note there are no dependencies on windows-pr, win32-api, or windows-api. On x86, we do have a dependency on win32console to handle colorized output.
On Windows ruby 2.0.0 x64, install the puppet gem:


C:\temp>ruby --version
ruby 2.0.0p481 (2014-05-08) [x64-mingw32]

C:\temp>gem install puppet-3.6.2.1006-x64-mingw32.gem

Successfully installed ffi-1.9.3-x64-mingw32
Successfully installed win32-dir-0.4.9
Successfully installed win32-security-0.2.5
Successfully installed facter-2.1.0-x64-mingw32
Successfully installed json_pure-1.8.1
Successfully installed hiera-1.3.4
Successfully installed rgen-0.6.6
Successfully installed win32-eventlog-0.6.1
Successfully installed win32-process-0.7.4
Successfully installed win32-service-0.8.5
Successfully installed minitar-0.5.4
Successfully installed puppet-3.6.2.1006-x64-mingw32
12 gems installed

C:\temp>gem dependency puppet
Gem puppet-3.6.2.1006-x64-mingw32
  facter (< 3, > 1.6)
  ffi (= 1.9.3)
  hiera (~> 1.0)
  json_pure (>= 0)
  minitar (~> 0.5.4)
  rgen (~> 0.6.5)
  win32-dir (~> 0.4.9)
  win32-eventlog (~> 0.6.1)
  win32-process (~> 0.7.4)
  win32-security (~> 0.2.5)
  win32-service (~> 0.8.4)



Again no dependencies on windows-pr, win32-api, or windows-api. And on x64 we do not depend on win32console, since ruby 2 natively handles colorized output.

Jira (PUP-2889) Upgrade win32-eventlog

2014-08-18 Thread Josh Cooper (JIRA) 
Title: Message Title










 

 Josh Cooper commented on an issue











 






  Re: Upgrade win32-eventlog 










The dependency on 0.5.3 is a problem, because it causes puppet to pull in windows-pr, etc gems. It looks like the gem dependency bump was reverted in 35b1abc1, and then reimplemented in 537b0572, but the corresponding eventlog dependency was not bumped. I fixed this in ac8d4e2. Also note, puppet already depended on version 0.6.1 for x64, and for both of our vendored ruby branches:
https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3-x86/ruby/lib/ruby/gems/1.9.1/gems https://github.com/puppetlabs/puppet-win32-ruby/tree/2.0.0-x64/ruby/lib/ruby/gems/2.0.0/gems












   

 Add Comment











 













 Puppet /  PUP-2889



  Upgrade win32-eventlog 







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















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




 














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

Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation 










Based on the above, this appears to fix the issue, so moving this to Ready for Merge.












   

 Add Comment











 













 Puppet /  PUP-2817



  Solaris Zone properties ip, dataset and inherit are not set upon zone creation 







 The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like:   {code}  {    ensure => :absent  }  {code}  ...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-3021) User resource on AIX returns a non-working structure or 'attributes'

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: User resource on AIX returns a non-working structure or 'attributes' 










Reminder not to let this roll over to the next sprint.












   

 Add Comment











 













 Puppet /  PUP-3021



  User resource on AIX returns a non-working structure or 'attributes' 







 The `user` resource on AIX returns back non-working Puppet code for the 'attributes' key.   Example:   {code:title=puppet resource user root|borderStyle=solid}  # puppet resource user root | tee /tmp/root.pp   user { 'root':    ensure => 'present',    attributes => {'account_locked' => 'false', 'admin' => 'true', 'auditclasses' => 'gene...















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




 














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

Jira (PUP-3047) Validate Puppet -x64-mingw32 gem dependencies on x64

2014-08-18 Thread Josh Cooper (JIRA) 
Title: Message Title










 

 Josh Cooper assigned an issue to Josh Cooper











 






 Puppet /  PUP-3047



  Validate Puppet -x64-mingw32 gem dependencies on x64 










Change By:

 Josh Cooper




Assignee:

 Josh Cooper












   

 Add Comment











 










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




 














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

Jira (PUP-3047) Validate Puppet -x64-mingw32 gem dependencies on x64

2014-08-18 Thread Josh Cooper (JIRA) 
Title: Message Title










 

 Josh Cooper updated an issue











 






 Puppet /  PUP-3047



  Validate Puppet -x64-mingw32 gem dependencies on x64 










Change By:

 Josh Cooper




Sprint:

 2014-08-20












   

 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-2614) Deprecate default source_permissions :use on all platforms

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Deprecate default source_permissions :use on all platforms 










Resolved as Won't Fix, as discussed above. Also I put a DOCS component on PUP-2613 this ticket's sibling for 4.0.












   

 Add Comment











 













 Puppet /  PUP-2614



  Deprecate default source_permissions :use on all platforms 







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















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




 














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

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

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-2613



  Change source_permissions default to :ignore 










Change By:

 Kylo Ginsberg




Component/s:

 Types and Providers




Component/s:

 DOCS












   

 Add Comment











 










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




 














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

Jira (PUP-2986) Update Windows Installer license file to reference Unknownr addition that is MIT licensed

2014-08-18 Thread Josh Cooper (JIRA) 
Title: Message Title










 

 Josh Cooper commented on an issue











 






  Re: Update Windows Installer license file to reference Unknownr addition that is MIT licensed 










Moving to FR, since the change is to the windows installer (MSI) and we don't run CI against the MSI.
To verify, grab a recent MSI with this change, run the GUI installer, and verify the additional license info is present.












   

 Add Comment











 













 Puppet /  PUP-2986



  Update Windows Installer license file to reference Unknownr addition that is MIT licensed 







 As of 3.7.0 and the taskscheduler rewrite, we now incorporate some rewritten parts of the Unknownr library, which helps to provide COM / FFI bindings.   It is MIT licensed and is hosted on GitHub here:  https://github.com/rpeev/Unknownr   Update the Windows installer license files accordingly.















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




 














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

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

2014-08-18 Thread Kenneth Barber (JIRA) 
Title: Message Title










 

 Kenneth Barber assigned an issue to Wyatt Alt











 






 PuppetDB /  PDB-821



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










Change By:

 Kenneth Barber




Assignee:

 Wyatt Alt












   

 Add Comment











 










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




 














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

Jira (PDB-829) PR (1051): (maint) Add pretty SQL formatting - kbarber

2014-08-18 Thread gepetto-bot (JIRA) 
Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1051): (maint) Add pretty SQL formatting - kbarber 










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












   

 Add Comment











 













 PuppetDB /  PDB-829



  PR (1051): (maint) Add pretty SQL formatting - kbarber 







 h2. (maint) Add pretty SQL formatting   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 1051 Discussion|https://github.com/puppetlabs/puppetdb/pull/1051]  * [Pull Request 1051 File Diff|https://github.com/puppetlabs/puppetdb/pull/1051/files]  h2. Pull Request Description --...















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




 














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

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

2014-08-18 Thread Ryan Coleman (JIRA) 
Title: Message Title










 

 Ryan Coleman commented on an issue











 






  Re: puppet module list --tree output shows dependencies incorrectly 










Eric Sorenson, I don't remember de-prioritizing it but a lot of things were being traded in and out of PE 3.4 via https://confluence.puppetlabs.com/display/PROD/PMT+Improvements+for+PE+3.4. 
That said, this is not critical compared to some other usability bugs being addressed. +1 to move it out of 3.7.0 but I'd like to see it addressed in the next release, if possible. 












   

 Add Comment











 













 Puppet /  PUP-2301



  puppet module list --tree output shows dependencies incorrectly 







 After deinstalling a module with dependencies, the dependency graph of locally installed modules displayed by {{puppet module list - - tree}} is incorrect, which makes the {{- - tree}} option of limited use.   Steps to reproduce:  # Install monolithic Puppet 3.2  # Run {{puppet module list --tree}} which will give the following output:  {noformat}  /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 t

Jira (PUP-744) Pool HTTPS connections

2014-08-18 Thread Michael Smith (JIRA) 
Title: Message Title










 

 Michael Smith commented on an issue











 






  Re: Pool HTTPS connections 










Performance measurements using https://gist.github.com/MikaelSmith/0f619d0dcb0638644855: Before PUP-744: real 1m16.128s, user 0m44.709s, sys 0m7.101s After PUP-744: real 0m39.642s, user 0m25.460s, sys 0m6.565s
Functional Review Scenarios (1) and (2)
Both long-running agent scenarios were simulated using a site.pp with 'exec  { "/bin/sleep N": }
', where N is a number of seconds (1, 8, 15, and 200 in testing).
Puppet Agent ran without errors in each case. For times 8, 15, and 200, an extra SSL handshake is noted in the --http_debug output after the sleep as a result of the connection being invalidated. Performance testing (sleep 8) shows the same absolute performance gains as those measured in the gist above: Before PUP-744: real 2m36.437s, user 0m44.999s, sys 0m7.216s After PUP-744: real 2m0.777s, user 0m26.312s, sys 0m6.687s A 36s real-time difference.












   

 Add Comment











 













 Puppet /  PUP-744



  Pool HTTPS connections 







 Reduce network traffic and latency















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

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

2014-08-18 Thread Josh Cooper (JIRA) 
Title: Message Title










 

 Josh Cooper commented on an issue











 






  Re: Deprecate default source_permissions :use on all platforms 










This ticket is similar to the deprecation warning we added for the package parameter allow_virtual. The thinking in that case was we wanted to ensure users specified a value (and didn't rely on the default behavior which we're changing in Puppet 4.0). This caused a number of issues – you had to be running both agent and master at the latest version to set a resource default, and generally made it difficult to turn off the warning (

PUP-2650
, PE-4202, etc).
Given that experience, I would fine closing this issue, and make sure we call out in the release notes that the default behavior for source_permissions will be changed from :use to :ignore in Puppet 4.0.












   

 Add Comment











 













 Puppet /  PUP-2614



  Deprecate default source_permissions :use on all platforms 







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















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

Jira (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo assigned an issue to Unassigned











 






 Puppet /  PUP-3021



  User resource on AIX returns a non-working structure or 'attributes' 










Change By:

 Adrien Thebo




Assignee:

 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-3021) User resource on AIX returns a non-working structure or 'attributes'

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: User resource on AIX returns a non-working structure or 'attributes' 










Gonna remove this from being a 3.7.0 blocker.












   

 Add Comment











 













 Puppet /  PUP-3021



  User resource on AIX returns a non-working structure or 'attributes' 







 The `user` resource on AIX returns back non-working Puppet code for the 'attributes' key.   Example:   {code:title=puppet resource user root|borderStyle=solid}  # puppet resource user root | tee /tmp/root.pp   user { 'root':    ensure => 'present',    attributes => {'account_locked' => 'false', 'admin' => 'true', 'auditclasses' => 'gene...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-3021) User resource on AIX returns a non-working structure or 'attributes'

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-3021



  User resource on AIX returns a non-working structure or 'attributes' 










Change By:

 Eric Sorenson




Fix Version/s:

 3.7.0




Fix Version/s:

 4.x












   

 Add Comment











 










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




 














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

Jira (PUP-2924) Puppet searches disk for whit classes

2014-08-18 Thread Eric Thompson (JIRA) 
Title: Message Title










 

 Eric Thompson updated an issue











 






 Puppet /  PUP-2924



  Puppet searches disk for whit classes 










Change By:

 Eric Thompson




QA Contact:

 Narmadha Perumal Eric Thompson












   

 Add Comment











 










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




 














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

Jira (PUP-2924) Puppet searches disk for whit classes

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Puppet searches disk for whit classes 










Verified:
On 3.6.2:


strace -o strace.out -e trace=stat -- bundle exec puppet apply -e 'notify { "hello": message => "world" }'; echo "Admissible:"; grep -c admissible strace.out ; echo "Completed:"; grep -c completed strace.out
Unable to open /dev/zfs: Permission denied.
Unable to open /dev/zfs: Permission denied.
Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.03 seconds
Notice: world
Notice: /Stage[main]/Main/Notify[hello]/message: defined 'message' as 'world'
Notice: Finished catalog run in 0.18 seconds
Admissible:
648
Completed:
648



On master (dbf3021):


strace -o strace.out -e trace=stat -- bundle exec puppet apply -e 'notify { "hello": message => "world" }'; echo "Admissible:"; grep -c admissible strace.out ; echo "Completed:"; grep -c completed strace.out
Unable to open /dev/zfs: Permission denied.
Unable to open /dev/zfs: Permission denied.
Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.02 seconds
Notice: world
Notice: /Stage[main]/Main/Notify[hello]/message: defined 'message' as 'world'
Notice: Finished catalog run in 0.13 seconds
Admissible:
0
Completed:
0



For this trivial example it looks like catalog application time is roughly the same.












   

 Add Comment











 













 Puppet /  PUP-2924



  Puppet searches disk for whit classes 







 Our P

Jira (PUP-2924) Puppet searches disk for whit classes

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Puppet /  PUP-2924



  Puppet searches disk for whit classes 










Change By:

 Adrien Thebo




Assignee:

 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-229) User provider password_max_age attribute is flawed under Solaris

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo assigned an issue to Unassigned











 






 Puppet /  PUP-229



  User provider password_max_age attribute is flawed under Solaris 










Change By:

 Adrien Thebo




Assignee:

 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-2907) Regression when pluginsyncing external facts on Windows

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo assigned an issue to Unassigned











 






 Puppet /  PUP-2907



  Regression when pluginsyncing external facts on Windows 










Change By:

 Adrien Thebo




Assignee:

 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-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation

2014-08-18 Thread Charlie Sharpsteen (JIRA) 
Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation 










Ah! Good catch! The create_args line was totally the culprit. Didn't inspect the manifest closely after pasting it in 












   

 Add Comment











 













 Puppet /  PUP-2817



  Solaris Zone properties ip, dataset and inherit are not set upon zone creation 







 The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like:   {code}  {    ensure => :absent  }  {code}  ...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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 ht

Jira (FACT-458) Implement changes for AIX Memory facts (already commited)

2014-08-18 Thread William Hopper (JIRA) 
Title: Message Title










 

 William Hopper commented on an issue











 






  Re: Implement changes for AIX Memory facts (already commited) 










Kylo Ginsberg I just took a look at master and these changes are actually already in, with the API updates and everything. Was there something that indicates that the fix wasn't working on AIX?












   

 Add Comment











 













 Facter /  FACT-458



  Implement changes for AIX Memory facts (already commited) 







 We are running facter 1.7.3 on AIX systems and they are not reporting memorysize and memoryfree facts.   This has already been implemented on May 31st 2013 according to the git history:   Commit: 183b2ba4035cd0e532a7bfcb90047c816a4dfd4d (#20994) fix incorrect memoryfree fact on AIX (was set to 0)  Commit: b739a96626a5bbc48ffa99a5b5f3fb9ce5f8bf83 (#2099...















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




 














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

Jira (PUP-3078) Virtual and Exported Resources Should Validate at Declaration

2014-08-18 Thread Zachary Stern (JIRA) 
Title: Message Title










 

 Zachary Stern updated an issue











 






 Puppet /  PUP-3078



  Virtual and Exported Resources Should Validate at Declaration 










Change By:

 Zachary Stern




Labels:

 customer support












   

 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-3078) Virtual and Exported Resources Should Validate at Declaration

2014-08-18 Thread Zachary Stern (JIRA) 
Title: Message Title










 

 Zachary Stern created an issue











 






 Puppet /  PUP-3078



  Virtual and Exported Resources Should Validate at Declaration 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 18/Aug/14 4:25 PM




Priority:

  Normal




Reporter:

 Zachary Stern










Virtual and exported resources aren't validated when they are declared, and so problems aren't visible until they're collected.
E.g.:



[root@mgtm6e8juxq8e3n ~]# cat foo.pp
@sshkey { "${::fqdn}_dsa":
  host_aliases => [$::fqdn, $::hostname],
  type => dsa,
  key  => $::fdslkfjsdlfkj,
}
[root@mgtm6e8juxq8e3n ~]# puppet apply foo.pp
Notice: Compiled catalog for mgtm6e8juxq8e3n.delivery.puppetlabs.net in environment production in 0.08 seconds
Notice: Finished catalog run in 0.03 seconds



And now let's collect it:



[root@mgtm6e8juxq8e3n ~]# cat foo.pp
@sshkey { "${::fqdn}_dsa":
  host_aliases => [$::fqdn, $::hostname],
  type => dsa,
  key  => $::fdslkfjsdlfkj,
}
Sshkey <| |>
[root@mgtm6e8juxq8e3n ~]# puppet apply foo.pp
Notice: Compiled catalog for mgtm6e8juxq8e3n.delivery.puppetlabs.net in environment production in 0.08 seconds
Notice: /Stage[main]/Main/Sshkey[mgtm6e8juxq8e3n.delivery.puppetlabs.net_dsa]/ensure: created
Error: /Stage[main]/Main/Sshkey[mgtm6e8juxq8e3n.delivery.puppetlabs.net_dsa]: Could not evaluate: Field 'key' is required
Notice: Finished catalog run in 0.02 seconds



The same is true for exported resources. Debugging these sorts of issues would be far easier if the resources we

Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily

2014-08-18 Thread Joshua Partlow (JIRA) 
Title: Message Title










 

 Joshua Partlow assigned an issue to Unassigned











 






 Puppet /  PUP-2728



  zypper should always be the default package provider for Suse osfamily 










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 (FACT-629) ec2 facts should ignore proxy

2014-08-18 Thread Joshua Partlow (JIRA) 
Title: Message Title










 

 Joshua Partlow updated an issue











 






 Facter /  FACT-629



  ec2 facts should ignore proxy 










Change By:

 Joshua Partlow




Fix Version/s:

 2.2.0












   

 Add Comment











 










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




 














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

Jira (FACT-458) Implement changes for AIX Memory facts (already commited)

2014-08-18 Thread William Hopper (JIRA) 
Title: Message Title










 

 William Hopper commented on an issue











 






  Re: Implement changes for AIX Memory facts (already commited) 










Kylo Ginsberg Definitely! I'll jump on it right now.












   

 Add Comment











 













 Facter /  FACT-458



  Implement changes for AIX Memory facts (already commited) 







 We are running facter 1.7.3 on AIX systems and they are not reporting memorysize and memoryfree facts.   This has already been implemented on May 31st 2013 according to the git history:   Commit: 183b2ba4035cd0e532a7bfcb90047c816a4dfd4d (#20994) fix incorrect memoryfree fact on AIX (was set to 0)  Commit: b739a96626a5bbc48ffa99a5b5f3fb9ce5f8bf83 (#2099...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-458) Implement changes for AIX Memory facts (already commited)

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Implement changes for AIX Memory facts (already commited) 










William Hopper can you take a look at this one? It's not a perfectly clean cherry-pick but I think it's just b/c of some internal API renames, nothing worse than that.












   

 Add Comment











 













 Facter /  FACT-458



  Implement changes for AIX Memory facts (already commited) 







 We are running facter 1.7.3 on AIX systems and they are not reporting memorysize and memoryfree facts.   This has already been implemented on May 31st 2013 according to the git history:   Commit: 183b2ba4035cd0e532a7bfcb90047c816a4dfd4d (#20994) fix incorrect memoryfree fact on AIX (was set to 0)  Commit: b739a96626a5bbc48ffa99a5b5f3fb9ce5f8bf83 (#2099...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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 ht

Jira (FACT-458) Implement changes for AIX Memory facts (already commited)

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg assigned an issue to William Hopper











 






 Facter /  FACT-458



  Implement changes for AIX Memory facts (already commited) 










Change By:

 Kylo Ginsberg




Assignee:

 William Hopper












   

 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-744) Pool HTTPS connections

2014-08-18 Thread Michael Smith (JIRA) 
Title: Message Title










 

 Michael Smith commented on an issue











 






  Re: Pool HTTPS connections 










Script to reproduce the performance testing Josh outlines: https://gist.github.com/MikaelSmith/0f619d0dcb0638644855
Testing scenarios 1. Long-running agent, so that connection is invalidated on both ends (> 15 seconds). 2. Medium-running agent, so that connection is invalidated but server hasn't timed out (~10 seconds). 3. Multiple masters: one for manifest/resources, one for report. 4. Multiple agents (I assume this is covered by acceptance tests).
Examine agent -http_debug output to review http interactions.












   

 Add Comment











 













 Puppet /  PUP-744



  Pool HTTPS connections 







 Reduce network traffic and latency















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




 














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

Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation

2014-08-18 Thread Rahul Gopinath (JIRA) 
Title: Message Title










 

 Rahul Gopinath commented on an issue











 






  Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation 










Could you remove the create_args? it essentially creates a new interface (though it shouldn't have created one with the same name, but that would be a bug in solaris) Here is what should be used:


 class monitise_zone {
  zone { 'myzone1':
ensure => 'running',
path => '/zones/myzone1',
ip => 'ixgbe0:172.16.12.68:172.16.13.254',
iptype => 'shared',
  }
}
include monitise_zone















   

 Add Comment











 













 Puppet /  PUP-2817



  Solaris Zone properties ip, dataset and inherit are not set upon zone creation 







 The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like:   {code}  {    ensure => :absent  }  {code}  ...















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

Jira (PUP-2914) Update packages to use RGen 0.7.0

2014-08-18 Thread Henrik Lindberg (JIRA) 
Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Update packages to use RGen 0.7.0 










So, by poking around I think I figured out how the safe_yaml and semantic are vendored. Basically, the task is to:


make a copy of rgen 0.7.0 and place it's root in lib/puppet/vendor/rgen


Write a loader that adds it to the path - the same way that load_semantic.rb does it


We do not want to load rgen early on demand since it is not required unless --parser future is on (so doing it the same way as for load semantic; e.g. make a note in 'require_vendored.rb'.


At the point where rgen code is actually required, ensure that it is on the path, this should probably be in pops.rb














   

 Add Comment











 













 Puppet /  PUP-2914



  Update packages to use RGen 0.7.0 







 PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{>= 0.6.5}}.   We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.

Jira (PUP-2907) Regression when pluginsyncing external facts on Windows

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Regression when pluginsyncing external facts on Windows 










Verified that pluginsync on Windows running against master no longer logs a warning.












   

 Add Comment











 













 Puppet /  PUP-2907



  Regression when pluginsyncing external facts on Windows 







 Ticket PUP-2705 restored the ability for pluginsync to preserve permissions for external facts synced to {{facts.d}}. However, on Windows, it generates a deprecation warning, which users cannot fix:   {noformat}  C:\work\puppet> bundle exec puppet agent -t  ...  Info: Retrieving pluginfacts  Warning: Copying owner/mode/group from the source file on Windo...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation

2014-08-18 Thread Charlie Sharpsteen (JIRA) 
Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation 










I am using the same puppet manifest you ran your tests with:



class monitise_zone {
  zone { 'myzone1':
ensure => 'running',
path => '/zones/myzone1',
ip => 'ixgbe0:172.16.12.68:172.16.13.254',
create_args => "\nadd net\nset address=172.16.12.6\nset physical=ixgbe0\nend",
#create_args => "add net set address=172.16.12.6 set physical=ixgbe0",
iptype => 'shared',
  }
}
include monitise_zone



Here's the output of the commands. I can't get a clean run with --debug due to the "undefined method tags" error mentioned in ENTERPRISE-273, so I just left it at --verbose:


bash-4.3# zoneadm list
global


bash-4.3# zonecfg -z myzone1 info
myzone1: No such zone configured


bash-4.3# /opt/puppet/bin/puppet apply --verbose --trace zone_with_ip.pp 
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/concat_basedir.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/custom_auth_conf.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/ip6tables_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/iptables_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_build.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_postgres_default_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_puppetdb_server_status.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/platform_tag.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/postgres_default_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/root_home.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/staging_http_get.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/windows.rb
Notice: Compiled catalog for pe-331-agent-solaris.puppetdebug.vlan in environment production in 0.05 seconds
Info: Applying configuration version '1408402484'
Notice: /Stage[main]/Monitise_zone/Zone[myzone1]/ensure: created
Notice: Finished catalog run in 168.53 seconds


bash-4.3# zoneadm list
global
myzone1


bash-4.3# zonecfg -z myzone1 info
zonename: myzone1
zonepath: /zones/myzone1
brand: native
autoboot: true
bootargs: 
pool: 
limitpriv: 
scheduling-class: 
ip-type: shared
hostid: 
net:
	address: 172.16.12.6
	physical: ixgbe0
	defrouter not specified
net:
	address: 172.16.12.68
	physical: ixgbe0
	defrouter: 172.16.13.254















   

 Add

Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation

2014-08-18 Thread Rahul Gopinath (JIRA) 
Title: Message Title










 

 Rahul Gopinath commented on an issue











 






  Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation 










That is really odd, since it is creating two interfaces with the same name ixgbe0 , can you provide your puppet file? Also, could you give me the output of these commands


# before running puppet
zoneadm list
zonecfg -z myzone1 info
puppet apply --debug --verbose --trace puppet.pp
zoneadm list
zonecfg -z myzone1 info















   

 Add Comment











 













 Puppet /  PUP-2817



  Solaris Zone properties ip, dataset and inherit are not set upon zone creation 







 The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like:   {code}  {    ensure => :absent  }  {code}  ...















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

Jira (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master

2014-08-18 Thread John Duarte (JIRA) 
Title: Message Title










 

 John Duarte commented on an issue











 






  Re: Backport lost Solaris 10 zfs_version fix into Facter / master 










Eric Thompson +1 to resolve.












   

 Add Comment











 













 Facter /  FACT-641



  Backport lost Solaris 10 zfs_version fix into Facter / master 







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















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation

2014-08-18 Thread Charlie Sharpsteen (JIRA) 
Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation 










After applying the patch, I get the following when after applying the manifest given above:


# zonecfg -z myzone1 info
zonename: myzone1
zonepath: /zones/myzone1
brand: native
autoboot: true
bootargs: 
pool: 
limitpriv: 
scheduling-class: 
ip-type: shared
hostid: 
net:
	address: 172.16.12.6
	physical: ixgbe0
	defrouter not specified
net:
	address: 172.16.12.68
	physical: ixgbe0
	defrouter: 172.16.13.254



So, the IP interface declared in the catalog getting added on zone creation, but we still have an interface getting created that was not declared in the manifest. Running a second catalog application destroys the 172.16.12.6 interface, but it should not be created during the initial sync.
The patch does appear to resolve the issue with sparse zones. After patching, the catalog below no longer tries to reset inherited directories on each catalog application:



zone {"test":
  path => "/zones/test",
  inherit => ['/lib','/opt/puppet','/sbin','/usr'],
}















   

 Add Comment











 













 Puppet /  PUP-2817



  Solaris Zone properties ip, dataset and inherit are not set upon zone creation 







 The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When

Jira (PUP-2914) Update packages to use RGen 0.7.0

2014-08-18 Thread Melissa Stone (JIRA) 
Title: Message Title










 

 Melissa Stone updated an issue











 






 Puppet /  PUP-2914



  Update packages to use RGen 0.7.0 










Change By:

 Melissa Stone




Fix Version/s:

 3.7.0












   

 Add Comment











 










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




 














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

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

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2614



  Deprecate default source_permissions :use on all platforms 










Change By:

 Eric Sorenson




Assignee:

 Kylo Ginsberg












   

 Add Comment











 










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




 














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

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

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Deprecate default source_permissions :use on all platforms 










Kylo Ginsberg said he's going to talk with Josh Cooper and see if this is still relevant/doable in 3.7.0.












   

 Add Comment











 













 Puppet /  PUP-2614



  Deprecate default source_permissions :use on all platforms 







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















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




 














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

Jira (PUP-3047) Validate Puppet -x64-mingw32 gem dependencies on x64

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Validate Puppet -x64-mingw32 gem dependencies on x64 










ping Josh Cooper if we're going to make this in time for 3.7.0 it needs assignment and work in the next week..who should be the owner?












   

 Add Comment











 













 Puppet /  PUP-3047



  Validate Puppet -x64-mingw32 gem dependencies on x64 







 Ensure that   * We release a mingw x64 gem that includes appropriate dependencies  * That all of the expected dependencies resolve correctly (necessary for other things that depend on puppet gem, such as current module testing)  















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-2914) Update packages to use RGen 0.7.0

2014-08-18 Thread Melissa Stone (JIRA) 
Title: Message Title










 

 Melissa Stone updated an issue











 






 Puppet /  PUP-2914



  Update packages to use RGen 0.7.0 










Change By:

 Melissa Stone




Assignee:

 Melissa Stone 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-2914) Update packages to use RGen 0.7.0

2014-08-18 Thread Melissa Stone (JIRA) 
Title: Message Title










 

 Melissa Stone commented on an issue











 






  Re: Update packages to use RGen 0.7.0 










Henrik Lindberg it looks like we're going to vendor rgen, rather than update the packages in the dependency repo. I'm going to hand this ticket off to you for that work.












   

 Add Comment











 













 Puppet /  PUP-2914



  Update packages to use RGen 0.7.0 







 PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{>= 0.6.5}}.   We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-410) Complete Implementation of Language based on the EGrammar

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-410



  Complete Implementation of Language based on the EGrammar 










Change By:

 Eric Sorenson




Fix Version/s:

 3.7.0












   

 Add Comment











 










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




 














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

Jira (PUP-1046) puppet module generate should produce a skeleton spec test

2014-08-18 Thread garrett honeycutt (JIRA) 
Title: Message Title










 

 garrett honeycutt commented on an issue











 






  Re: puppet module generate should produce a skeleton spec test 










Anything you need from me to help get this merged?












   

 Add Comment











 













 Puppet /  PUP-1046



  puppet module generate should produce a skeleton spec test 







 # Overview #   In order to make `rake spec` give meaningful feedback with a module generated using `puppet module generate` once #11285 is implemented, the generate action should produce an example rspec-puppet based spec test for the module.   I think the example could simply add the class to the catalog and make sure it got added.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-3069) Use a manifest setting in [master] as global manifests

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-3069



  Use a manifest setting in [master] as global manifests 










Change By:

 Eric Sorenson




Assignee:

 Andy Parker 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-777) Start deprecating 'versionRequirement' per code comment

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-777



  Start deprecating 'versionRequirement' per code comment 










Change By:

 Eric Sorenson




Assignee:

 Anderson Mills












   

 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-777) Start deprecating 'versionRequirement' per code comment

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-777



  Start deprecating 'versionRequirement' per code comment 










Change By:

 Eric Sorenson




Fix Version/s:

 3.7.0




Fix Version/s:

 4.0.0












   

 Add Comment











 










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




 














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

Jira (PUP-777) Start deprecating 'versionRequirement' per code comment

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Start deprecating 'versionRequirement' per code comment 










Anderson Mills please submit a pull request against the puppet-4 branch of puppet which removes the code.
We'll just have a doc note for 3.7.












   

 Add Comment











 













 Puppet /  PUP-777



  Start deprecating 'versionRequirement' per code comment 







 in 3.x, module.rb says the following:   {code}    # NOTICE: The fallback to `versionRequirement` is something we'd like to    # not have to support, but we have a reasonable number of releases that    # don't use `version_requirement`. When we can deprecate this, we should.  {code}   This should be slated for warnings in 3.5 and removal in 4.0.















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




 














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

Jira (PUP-2988) PMT dependency resolution happens in a suboptimal order

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2988



  PMT dependency resolution happens in a suboptimal order 










Change By:

 Eric Sorenson




Fix Version/s:

 3.7.0




Fix Version/s:

 4.x












   

 Add Comment











 










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




 














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

Jira (PUP-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: PMT upgrade command returns an error when trying to upgrade a module with only one release 










Ping Anderson Mills for follow-up on possible regression.












   

 Add Comment











 













 Puppet /  PUP-2882



  PMT upgrade command returns an error when trying to upgrade a module with only one release 







 When you use the "puppet module upgrade" command to upgrade a module that has only one published release, it reports that there are no releases available for that module instead of telling you that you already have the latest version.   {code}  $ bin/puppet module install ghoneycutt/sysklogd  Notice: Preparing to install into /Users/jesse/sandbox/puppet/...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2988) PMT dependency resolution happens in a suboptimal order

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2988



  PMT dependency resolution happens in a suboptimal order 










Change By:

 Eric Sorenson




Assignee:

 Pieter van de Bruggen Anderson Mills












   

 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-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2752



  Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format 










Change By:

 Eric Sorenson




Assignee:

 Anderson Mills












   

 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-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format 










Anderson Mills to follow-up on the regression Duarte noted.












   

 Add Comment











 













 Puppet /  PUP-2752



  Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format 







 Since Puppet 3.6.0 the module tool is unable to install new modules if an already existing modules version does not conform to the MAJOR.MINOR.PATCH format.   I believe this behaviour was introduced with the dependency resolver ( https://github.com/puppetlabs/puppet/commit/6fa68b54ac621d60dbf1b062f8dd66b186d1a87f )   How to reproduce problem:  * Place a...















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




 














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

Jira (PUP-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2882



  PMT upgrade command returns an error when trying to upgrade a module with only one release 










Change By:

 Eric Sorenson




Assignee:

 Anderson Mills












   

 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-3013) Add acceptance test for PMT build command changes for 3.7

2014-08-18 Thread Steve Barlow (JIRA) 
Title: Message Title










 

 Steve Barlow updated an issue











 






 Puppet /  PUP-3013



  Add acceptance test for PMT build command changes for 3.7 










Change By:

 Steve Barlow




Fix Version/s:

 3.7.0




Fix Version/s:

 3.7.1




Original Estimate:

 0 minutes












   

 Add Comment











 










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




 














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

Jira (PUP-2300) Prune dead code from PMT

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-2300



  Prune dead code from PMT 










Change By:

 Kylo Ginsberg




Fix Version/s:

 4.0.0




Fix Version/s:

 4.x












   

 Add Comment











 










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




 














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

Jira (PUP-2300) Prune dead code from PMT

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2300



  Prune dead code from PMT 










Change By:

 Eric Sorenson




Fix Version/s:

 4.0.0












   

 Add Comment











 










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




 














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

Jira (PUP-2300) Prune dead code from PMT

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2300



  Prune dead code from PMT 










Change By:

 Eric Sorenson




Fix Version/s:

 3.7.0












   

 Add Comment











 










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




 














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

Jira (PUP-2300) Prune dead code from PMT

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Prune dead code from PMT 










Nice-to-have, not blocking 3.7.0. Adding for 4.x












   

 Add Comment











 













 Puppet /  PUP-2300



  Prune dead code from PMT 







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















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




 














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

Jira (PUP-2300) Prune dead code from PMT

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2300



  Prune dead code from PMT 










Change By:

 Eric Sorenson




Assignee:

 Pieter van de Bruggen Anderson Mills












   

 Add Comment











 










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




 














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

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

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2301



  puppet module list --tree output shows dependencies incorrectly 










Change By:

 Eric Sorenson




Fix Version/s:

 3.7.0












   

 Add Comment











 










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




 














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

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

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: puppet module list --tree output shows dependencies incorrectly 










Ryan Coleman you were invoked as having de-prioritized this? Removing from 3.7.0 blockers. Please correct if not.












   

 Add Comment











 













 Puppet /  PUP-2301



  puppet module list --tree output shows dependencies incorrectly 







 After deinstalling a module with dependencies, the dependency graph of locally installed modules displayed by {{puppet module list - - tree}} is incorrect, which makes the {{- - tree}} option of limited use.   Steps to reproduce:  # Install monolithic Puppet 3.2  # Run {{puppet module list --tree}} which will give the following output:  {noformat}  /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 (PUP-1046) puppet module generate should produce a skeleton spec test

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-1046



  puppet module generate should produce a skeleton spec test 










Change By:

 Eric Sorenson




Fix Version/s:

 3.7.0












   

 Add Comment











 










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




 














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

Jira (PUP-2701) Add acceptance tests for PMT build metadata.json support

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-2701



  Add acceptance tests for PMT build metadata.json support 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.7.0




Fix Version/s:

 3.7.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-1046) puppet module generate should produce a skeleton spec test

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: puppet module generate should produce a skeleton spec test 










ping Pieter van de Bruggen, I'm going to remove this from 3.7.0 so it's not blocking the release, but could this get some attention?












   

 Add Comment











 













 Puppet /  PUP-1046



  puppet module generate should produce a skeleton spec test 







 # Overview #   In order to make `rake spec` give meaningful feedback with a module generated using `puppet module generate` once #11285 is implemented, the generate action should produce an example rspec-puppet based spec test for the module.   I think the example could simply add the class to the catalog and make sure it got added.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-3015) Add acceptance test for PMT search command changes for 3.7

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-3015



  Add acceptance test for PMT search command changes for 3.7 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.7.0




Fix Version/s:

 3.7.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-3012) Add acceptance test for PMT upgrade command changes for 3.7

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-3012



  Add acceptance test for PMT upgrade command changes for 3.7 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.7.0




Fix Version/s:

 3.7.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-3014) Add acceptance test for PMT generate command changes for 3.7

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-3014



  Add acceptance test for PMT generate command changes for 3.7 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.7.0




Fix Version/s:

 3.7.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-3011) Add acceptance test for PMT install command changes for 3.7

2014-08-18 Thread Kylo Ginsberg (JIRA) 
Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-3011



  Add acceptance test for PMT install command changes for 3.7 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.7.0




Fix Version/s:

 3.7.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-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation

2014-08-18 Thread Charlie Sharpsteen (JIRA) 
Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation 











what should I see here instead?

The IP and router specified in the manifest aren't being set on the zone. Instead of 172.16.12.6, you should be seeing the following after Puppet creates the zone:


net:
	address: 172.16.12.68
	physical: ixgbe0
	defrouter: 172.16.13.254



I'll take a look at the patch and if it resolves these issues.












   

 Add Comment











 













 Puppet /  PUP-2817



  Solaris Zone properties ip, dataset and inherit are not set upon zone creation 







 The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like:   {code}  {    ensure => :absent  }  {code}  ...















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

Jira (PUP-2186) Add `puppet module show` action

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Add `puppet module show` action 










Removing fix version of 3.7.0 - PE equivalent was closed Wontfix












   

 Add Comment











 













 Puppet /  PUP-2186



  Add `puppet module show` action 







 The PMT needs a show action to describe installed modules, ideally communicating the same pieces of communication as the module page on the Forge.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-2186) Add `puppet module show` action

2014-08-18 Thread Eric Sorenson (JIRA) 
Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2186



  Add `puppet module show` action 










Change By:

 Eric Sorenson




Fix Version/s:

 3.7.0












   

 Add Comment











 










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




 














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

Jira (PUP-3009) PMT download treats error responses as modules

2014-08-18 Thread Anderson Mills (JIRA) 
Title: Message Title










 

 Anderson Mills updated an issue











 






 Puppet /  PUP-3009



  PMT download treats error responses as modules 










Change By:

 Anderson Mills




Fix Version/s:

 3.7.0












   

 Add Comment











 










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




 














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

Jira (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master

2014-08-18 Thread Eric Thompson (JIRA) 
Title: Message Title










 

 Eric Thompson updated an issue











 






 Facter /  FACT-641



  Backport lost Solaris 10 zfs_version fix into Facter / master 










Change By:

 Eric Thompson




QA Contact:

 Eric Thompson












   

 Add Comment











 










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




 














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

Jira (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master

2014-08-18 Thread Eric Thompson (JIRA) 
Title: Message Title










 

 Eric Thompson commented on an issue











 






  Re: Backport lost Solaris 10 zfs_version fix into Facter / master 










according to the old redmine ticket; facter would leak zfs errors:



[root@rldap1 facter]# /opt/csw/bin/facter zfs_version
unrecognized command 'upgrade'
usage: zfs command args ...


tested on solaris10 u9 (5.10) at SHA 04d331e this version of solaris has zfs upgrade. we could not find a solaris10 box without zfs upgrade.



vagrant@vagrant-sol10-u9:~/facter$ /opt/csw/bin/facter zfs_version
4
root@vagrant-sol10-u9:~# zfs upgrade
This system is currently running ZFS filesystem version 4.

All filesystems are formatted with the current version.



if i remove the zfs binary facter completes without reporting the zfs_version fact; but that's not really a convincing verify...
we can't get the old install media without paying. anyone have issues with moving this to resolved? Kylo Ginsberg John Duarte Dominic Maraglia












   

 Add Comment











 













 Facter /  FACT-641



  Backport lost Solaris 10 zfs_version fix into Facter / master 







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

Jira (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.

2014-08-18 Thread Nicholas Fagerlund (JIRA) 
Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: Puppet's v2 environment listing does not display config_version and environment_timeout as well. 










Henrik Lindberg To finish resolving this ticket, could you please update the API docs in /api/docs to match the changes you made in /api/schemas? Thank you. 












   

 Add Comment











 













 Puppet /  PUP-2426



  Puppet's v2 environment listing does not display config_version and environment_timeout as well. 







 We added config_version and environment_timeout settings to directory environment environment.conf. Puppet's v2 environments listing needs to show these environment parameters as well. (lib/puppet/network/http/api/v2/environments.rb)   Will also need to update the API docs for v2.0/environments















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




 














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

Jira (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.

2014-08-18 Thread Nicholas Fagerlund (JIRA) 
Title: Message Title










 

 Nicholas Fagerlund updated an issue











 






 Puppet /  PUP-2426



  Puppet's v2 environment listing does not display config_version and environment_timeout as well. 










Change By:

 Nicholas Fagerlund




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-2907) Regression when pluginsyncing external facts on Windows

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Puppet /  PUP-2907



  Regression when pluginsyncing external facts on Windows 










Change By:

 Adrien Thebo




Assignee:

 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 (FACT-659) Partitions fact does not correctly parse the filesystem attribute under Linux

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Partitions fact does not correctly parse the filesystem attribute under Linux 










Verified:
Against 19b8b2d:


---
partitions:
  sda1:
uuid: 7de786a9-be75-4711-b782-fb26aec963d4
size: '1024000'
mount: /boot
  sda2:
size: '975747072'
filesystem: LVM2_member" PARTUUID="000443ef-02
  sda3:
size: '2047'



Against c1cc408f:


---
partitions:
  sda1:
uuid: 7de786a9-be75-4711-b782-fb26aec963d4
size: '1024000'
mount: /boot
  sda2:
size: '975747072'
filesystem: LVM2_member
  sda3:
size: '2047'















   

 Add Comment











 













 Facter /  FACT-659



  Partitions fact does not correctly parse the filesystem attribute under Linux 







 {code}  $ be facter partitions -y  ---  partitions:    sda1:  size: '1953523087'  filesystem: ntfs" PARTUUID="d3676ebb-1343-4bac-9521-6bdd9bb2f7db    sdb1:  size: '2014'    sdb2:  uuid: e746c990-fb8d-4449-90ad-c517ccd859f6  size: '204800'  mount: /boot  filesystem: ext2" PARTLABEL="Linux filesystem" PARTUUID="a9ddc9e2-adf2-4134...

Jira (PDB-829) PR (1051): (maint) Add pretty SQL formatting - kbarber

2014-08-18 Thread Kenneth Barber (JIRA) 
Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-829



  PR (1051): (maint) Add pretty SQL formatting - kbarber 










Change By:

 Kenneth Barber




Fix Version/s:

 2.2.0












   

 Add Comment











 










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




 














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

Jira (PDB-829) PR (1051): (maint) Add pretty SQL formatting - kbarber

2014-08-18 Thread gepetto-bot (JIRA) 
Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1051): (maint) Add pretty SQL formatting - kbarber 










kbarber commented:
@grimradical I think a problem with the general direction is that we are modifying the SQL before the tests, this is less desirable since we want to test for production. Perhaps I can just print the pretty SQL to the log, but this is a lot of noise, a pretty SQL then the compressed one.












   

 Add Comment











 













 PuppetDB /  PDB-829



  PR (1051): (maint) Add pretty SQL formatting - kbarber 







 h2. (maint) Add pretty SQL formatting   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 1051 Discussion|https://github.com/puppetlabs/puppetdb/pull/1051]  * [Pull Request 1051 File Diff|https://github.com/puppetlabs/puppetdb/pull/1051/files]  h2. Pull Request Description --...















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




 














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

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

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: User provider password_max_age attribute is flawed under Solaris 










Verified:
Against 3.6.2:


bash-3.2# bundle exec puppet apply /foo.pp --verbose 
Notice: Compiled catalog for solaris-10u11-i386-vbox4210-nocm in environment production in 2.32 seconds
Info: Applying configuration version '1408395629'
Notice: /Stage[main]/Main/User[vagrant]/password_max_age: password_max_age changed '' to '-1'
Notice: Finished catalog run in 0.22 seconds



Against 9953b2c67009013894dcd0bcd5fb11409be16f02:


bash-3.2# bundle exec puppet apply /foo.pp --verbose 
Notice: Compiled catalog for solaris-10u11-i386-vbox4210-nocm in environment production in 2.44 seconds
Info: Applying configuration version '1408395694'
Notice: Finished catalog run in 0.11 seconds















   

 Add Comment











 













 Puppet /  PUP-229



  User provider password_max_age attribute is flawed under Solaris 







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

Jira (PUP-3054) Class inheritance behaving incorrectly in the future parser

2014-08-18 Thread Henrik Lindberg (JIRA) 
Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Class inheritance behaving incorrectly in the future parser 










Merged (manually) to master at dbf30216dfa6656a75bc967c072f7182f3ae08fc after having fixed up one performance enhancement that altered semantics.












   

 Add Comment











 













 Puppet /  PUP-3054



  Class inheritance behaving incorrectly in the future parser 







 [~dalen] commented on PUP-121 with a problem that he uncovered. It looks like class inheritance is encountering problems in the future parser.   {quote}  When I'm testing master atm with future parser:  {noformat}  class bar { notice("This is class $name") }  class foo::bar { notice("This is class $name") }  class foo inherits bar { notice("This is class...















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




 














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

Jira (PUP-3025) resource_type search can produce errors if storedconfigs is not configured.

2014-08-18 Thread Henrik Lindberg (JIRA) 
Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: resource_type search can produce errors if storedconfigs is not configured. 










Thanks Hailee, closing this as a dup of 

PUP-2994
.












   

 Add Comment











 













 Puppet /  PUP-3025



  resource_type search can produce errors if storedconfigs is not configured. 







 (NOTE: the following is run against 2.7 (currently next), I have also seen the same warnings in 2.6.x)   If I have a manifest which tries to export resources, then I get the following warning when retrieving the resource_type:   {code}  # cat /tmp/foo.pp class foo ($bar) {    @@notify { 'foo': }  }   [root@mypuppetmaster motd]# puppet resource_type se...















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




 














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

Jira (PUP-3063) Remove certification expiration check from puppet-4

2014-08-18 Thread Christopher Price (JIRA) 
Title: Message Title










 

 Christopher Price commented on an issue











 






  Re: Remove certification expiration check from puppet-4 










Joshua Partlow this one isn't a blocker for 3.7, obviously, but just in case you weren't aware that I'd created the separate ticket: ping!












   

 Add Comment











 













 Puppet /  PUP-3063



  Remove certification expiration check from puppet-4 







 This ticket is just a follow-on to PUP-3031, where we decided that the current approach for checking whether a client certificate is going to expire soon is a bit heavy-handed and not necessary. It was moved to a better location in 3.7 but is being removed altogether for 4.0.















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




 














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

Jira (FACT-659) Partitions fact does not correctly parse the filesystem attribute under Linux

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Partitions fact does not correctly parse the filesystem attribute under Linux 










Merged in c1cc408.












   

 Add Comment











 













 Facter /  FACT-659



  Partitions fact does not correctly parse the filesystem attribute under Linux 







 {code}  $ be facter partitions -y  ---  partitions:    sda1:  size: '1953523087'  filesystem: ntfs" PARTUUID="d3676ebb-1343-4bac-9521-6bdd9bb2f7db    sdb1:  size: '2014'    sdb2:  uuid: e746c990-fb8d-4449-90ad-c517ccd859f6  size: '204800'  mount: /boot  filesystem: ext2" PARTLABEL="Linux filesystem" PARTUUID="a9ddc9e2-adf2-4134...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-614) Create structured operating system fact

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Create structured operating system fact 










Merged in c0812a8.












   

 Add Comment











 













 Facter /  FACT-614



  Create structured operating system fact 







 Currently, there are several facts related to operating system based data, including:   {noformat}  operatingsystem  operatingsystemmajrelease  operatingsystemrelease  osfamily  {noformat}   Also, there are a handful of lsb* facts for Linux systems, including:   {noformat}  lsbdistcodename  lsbdistdescription  lsbdistid  lsbdistrelease  lsbmajdistrele...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@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-641) Backport lost Solaris 10 zfs_version fix into Facter / master

2014-08-18 Thread Eric Thompson (JIRA) 
Title: Message Title










 

 Eric Thompson assigned an issue to Eric Thompson











 






 Facter /  FACT-641



  Backport lost Solaris 10 zfs_version fix into Facter / master 










Change By:

 Eric Thompson




Assignee:

 Eric Thompson












   

 Add Comment











 










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




 














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

Jira (PUP-3030) Resolve Tempfile handling issues

2014-08-18 Thread Joshua Partlow (JIRA) 
Title: Message Title










 

 Joshua Partlow assigned an issue to Joshua Partlow











 






 Puppet /  PUP-3030



  Resolve Tempfile handling issues 










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-744) Pool HTTPS connections

2014-08-18 Thread Michael Smith (JIRA) 
Title: Message Title










 

 Michael Smith updated an issue











 






 Puppet /  PUP-744



  Pool HTTPS connections 










Whiteboard notes on architecture, and possible failure cases.










Change By:

 Michael Smith




Attachment:

 PUP-744 Overview.jpg












   

 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-3030) Resolve Tempfile handling issues

2014-08-18 Thread Joshua Partlow (JIRA) 
Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-3030



  Resolve Tempfile handling issues 










Change By:

 Joshua Partlow




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-3030) Resolve Tempfile handling issues

2014-08-18 Thread Joshua Partlow (JIRA) 
Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-3030



  Resolve Tempfile handling issues 










Change By:

 Joshua Partlow




Sprint:

 2014-08-20












   

 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-3032) Setting to cache `load_library` failures

2014-08-18 Thread Joshua Partlow (JIRA) 
Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-3032



  Setting to cache `load_library` failures 










Change By:

 Joshua Partlow




Sprint:

 2014-08-20












   

 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-3032) Setting to cache `load_library` failures

2014-08-18 Thread Joshua Partlow (JIRA) 
Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-3032



  Setting to cache `load_library` failures 










Change By:

 Joshua Partlow




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-229) User provider password_max_age attribute is flawed under Solaris

2014-08-18 Thread Adrien Thebo (JIRA) 
Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Puppet /  PUP-229



  User provider password_max_age attribute is flawed under Solaris 










Change By:

 Adrien Thebo




Assignee:

 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.

  1   2   >