Jira (PUP-1639) Some modules fail to install into target_dir

[Ger Apeldoorn (JIRA)]

Title: Message Title










 

 Ger Apeldoorn commented on an issue











 






  Re: Some modules fail to install into target_dir 










Jefferey Smith's workaround is allowing me to install modules. However, after I do this, I get 'Forbidden' errors getting catalogs, during pluginsync, and submitting reports.
However, if keep /etc/puppet intact and just link the environments-directories from /var, everything seems to work.
IMHO, fixing this on the module-building side is not enough. There will be modules with symlinks for quite some time, the module tool should be able to circumvent this problem during installation. Just my 2 cents. 












   

 Add Comment











 













 Puppet /  PUP-1639



  Some modules fail to install into target_dir 







 puppet module install puppetlabs/apache -i puppet/forge-modules   Notice: Preparing to install into /home/www/puppet/forge-modules ...  Notice: Created target directory /home/www/puppet/forge-modules  Notice: Downloading from https://forge.puppetlabs.com ...  Notice: Installing -- do not interrupt ...  Error: No such file or directory - /home/www/puppet/...















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




 







  

Jira (PUP-3073) Error message "Could not send report": appear when puppet client is pulling config from puppet master

[Ganesh Nalawade (JIRA)]

Title: Message Title










 

 Ganesh Nalawade created an issue











 






 Puppet /  PUP-3073



   Error message "Could not send report": appear when puppet client is pulling config from puppet master 










Issue Type:

  Bug




Affects Versions:


 3.6.1




Assignee:

 Kylo Ginsberg




Attachments:


 send_report_err_memory_usage.txt, send_report_err_puppet_debug_logs.txt, send_report_err_puppet_verbose_logs.txt, send_report_err_site.pp




Components:


 Client




Created:


 18/Aug/14 4:12 AM




Environment:


Puppet on Junos (Juniper device which has jpuppet package installed)




Priority:

  Normal




Reporter:

 Ganesh Nalawade










Please find attached log files for more details
Error message "Could not send report": appear when puppet client is pulling config from puppet master with vlan configuration i.e..vlan count greater than 460 and less than 700.
   

Jira (PUP-3074) Error message "Could not run: failed to allocate memory" is seen when more than 700 vlans is configured on Juniper device (Puppet client)

[Ganesh Nalawade (JIRA)]

Title: Message Title










 

 Ganesh Nalawade created an issue











 






 Puppet /  PUP-3074



  Error message "Could not run: failed to allocate memory" is seen when more than 700 vlans is configured on Juniper device (Puppet client) 










Issue Type:

  Bug




Affects Versions:


 3.6.1




Assignee:

 Kylo Ginsberg




Attachments:


 failed_allocate_mem_memory_usage.txt, failed_allocate_mem_puppet_debug_logs.txt, failed_allocate_mem_puppet_verbose_logs.txt, failed_allocate_mem_site.pp




Components:


 Client




Created:


 18/Aug/14 4:42 AM




Environment:


Puppet client is Juniper device with jpuppet package added on it. % ruby -v ruby 1.8.7 (2012-10-12 patchlevel 371) [i386-freebsd6.3] % puppet --version 3.6.1 % facter --version 2.0.1 %




Priority:

  Normal




Reporter:

 Ganesh Nalawade










Error message "Could not run: failed to allocate memory": appear when puppet client is pulling config from pup

Jira (PDB-818) Add select-reports subquery

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-818



  Add select-reports subquery 










Change By:

 Kenneth Barber




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 (PDB-819) Add select-events subquery operator

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-819



  Add select-events subquery operator 










Change By:

 Kenneth Barber




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 (PDB-829) PR (1051): (maint) Add pretty SQL formatting - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-829



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










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 18/Aug/14 6:21 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(maint) Add pretty SQL formatting


Author: Ken Barber 


Company: Puppet Labs Inc.


Github ID: kbarber


Pull Request 1051 Discussion


Pull Request 1051 File Diff


Pull Request Description

This patch converts all SQL code from the query engine into a pretty format so it is easier to read from the debug output.
Signed-off-by: Ken Barber 

(webhooks-id: 62d09a050e64d27b0479d923ddfb034e)

Jira (PUP-3075) Puppet client core dump when trying to configure more than 1005 vlans on Juniper device (Puppet client)

[Ganesh Nalawade (JIRA)]

Title: Message Title










 

 Ganesh Nalawade created an issue











 






 Puppet /  PUP-3075



  Puppet client core dump when trying to configure more than 1005 vlans on Juniper device (Puppet client) 










Issue Type:

  Bug




Affects Versions:


 3.6.1




Assignee:

 Kylo Ginsberg




Attachments:


 core_dump_memory_usage.txt, core_dump_puppet_debug_logs.txt, core_dump_puppet_verbose_logs.txt, core_dump_site.pp




Components:


 Client




Created:


 18/Aug/14 6:48 AM




Environment:


jpuppet package added on Juniper device. % ruby -v ruby 1.8.7 (2012-10-12 patchlevel 371) [i386-freebsd6.3] % puppet --version 3.6.1 % facter --version 2.0.1 %




Priority:

  Normal




Reporter:

 Ganesh Nalawade










Please refer log file for more details Puppet client getting configured when puppet is trying to configure vlans with vlan count greater than 1005 vlans. Pulling the config file from master which is having 100

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

[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




Sprint:

 20140813 to 20140827












   

 Add Comment











 










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




 














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

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

[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




Assignee:

 Kenneth Barber




Story Points:

 1




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

[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/621/












   

 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-1165) Spurious 'trigger changed' messages generated by scheduled task provider

[Rob Reynolds (JIRA)]

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Rob Reynolds




Labels:

 customer  pe_mcollective  redmine windows












   

 Add Comment











 










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




 














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

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

[Rob Reynolds (JIRA)]

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Rob Reynolds




Component/s:

 PE












   

 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-2999) Merge clay-davis branch of FOSS puppet into upstream repository.

[Britt Gresham (JIRA)]

Title: Message Title










 

 Britt Gresham commented on an issue











 






  Re: Merge clay-davis branch of FOSS puppet into upstream repository. 










I am currently running acceptance tests for this.












   

 Add Comment











 













 Puppet /  PUP-2999



  Merge clay-davis branch of FOSS puppet into upstream repository. 







 We need to be pulling acceptance tests directly from FOSS puppet repository and should not be worrying about synchronizing our branch with minimal changes with upstream.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2984) MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec

[Ethan Brown (JIRA)]

Title: Message Title










 

 Ethan Brown assigned an issue to Ethan Brown











 






 Puppet /  PUP-2984



  MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec 










Change By:

 Ethan Brown




Assignee:

 Ethan Brown












   

 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-2349) Deprecate non-string modes on file type

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Deprecate non-string modes on file type 










Merged in 87b0b5d.












   

 Add Comment











 













 Puppet /  PUP-2349



  Deprecate non-string modes on file type 







 The future parser treats literal numbers as actual numbers instead of strings as the old parser did. This makes file resources that use unquoted mode values behave strangely (see PUP-2156).   In order to provide a good experience and still have numbers be numbers in the language, the mode parameter of file resources needs to issue a deprecation warning f...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3000) Could not get fact fqdn/ipaddress

[Naftuli Tzvi Kay (JIRA)]

Title: Message Title










 

 Naftuli Tzvi Kay commented on an issue











 






  Re: Could not get fact fqdn/ipaddress 










There could be some weird configuration inside of Docker which doesn't set the environment variables when user switching occurs. 
However, I think it would be at least a sane default to include the following in config.ru:



if not ENV['PATH']
ENV['PATH'] = "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
end



The nice thing about this fix is that nobody loses as a result of it. If PATH is set, it isn't changed. If not, then it automatically fails over. 












   

 Add Comment











 













 Puppet /  PUP-3000



  Could not get fact fqdn/ipaddress 







 I have a weird issue where the Puppet Master is generating a certificate called ".mydomain.com" (ie: ".$domain").   Looking into the logs, I see the following:   {noformat}  Aug 1 00:01:14 kungfumaster puppet-master[447]: Could not retrieve fact fqdn  Aug 1 00:01:14 kungfumaster puppet-master[447]: Could not retrieve fact ipaddress  {noformat}   In ...















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




 

Jira (PUP-3076) Solaris (10) acceptance tests assume that /opt/csw/bin (opencsw) is in the path (necessary for solaris 10)

[Rahul Gopinath (JIRA)]

Title: Message Title










 

 Rahul Gopinath created an issue











 






 Puppet /  PUP-3076



  Solaris (10) acceptance tests assume that /opt/csw/bin (opencsw) is in the path (necessary for solaris 10) 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 18/Aug/14 9:42 AM




Priority:

  Normal




Reporter:

 Rahul Gopinath










When running puppet acceptance tests against solaris 10, it tries to run pkgutil, gem, git, and ruby from /usr/bin. However, since it uses pkgutil to install packages, all these are installed in /opt/csw/bin, and hence it fails. The patch below explains what is necessary to atleast get the tests running.


diff --git a/acceptance/lib/puppet/acceptance/install_utils.rb b/acceptance/lib/puppet/acceptance/install_utils.rb
index 2888c6c..b986a32 100644
--- a/acceptance/lib/puppet/acceptance/install_utils.rb
+++ b/acceptance/lib/puppet/acceptance/install_utils.rb
@@ -9,7 +9,8 @@ module Puppet
 :redhat=> /fedora|el|centos/,
 :debian=> /debian|ubuntu/,
 :debian_ruby18 => /debian|ubuntu-lucid|ubuntu-precise/,
-:solaris   => /solaris/,
+:solaris_10   => /solaris-10/,
+:solaris_11   => /solaris-11/,
 :windows   => /windows/,
   }.freeze
 
diff --git a/acceptance/setup/git/pre-suite/000_EnvSetup.rb b/acceptance/setup/git/pre-suite/000_EnvSetup.rb
index 5be7495..58d1e65 100644
--- a/acceptance/setup/git/pre-suite/000_EnvSetup.rb
+++ b/acceptance/setup/git/pre-suite/000_EnvSetup.rb
@@ -22,17 +22,36 @@ PACKAGES = {
   :debian_ruby18 => [
 'libjson-ruby',
   ],
-  :solaris => [
+  :solaris_11 => [
 ['git', 'developer/versioning/git'],
 ['ruby', 'runtime/ruby-18'],
 # there isn't a package for json, so it is installed later via gems
   ],
+  :solaris_10 => [
+['git', 'git'],
+['ruby', 'ruby18'],
+['ruby-dev', 'ruby18_dev'],
+['gcc', 'gcc4_core'],
+['ruby18_gcc4', 'ruby18_dev'],
+['ruby-json', 'rb18_json_1_5_3'],
+  ],
   :windows 

Jira (PUP-3077) When puppet agent fails to contact the master, cached catalog is used without regard for the puppet.conf-declared environment

[David Gwilliam (JIRA)]

Title: Message Title










 

 David Gwilliam created an issue











 






 Puppet /  PUP-3077



  When puppet agent fails to contact the master, cached catalog is used without regard for the puppet.conf-declared environment 










Issue Type:

  Bug




Affects Versions:


 3.6.2




Assignee:


 Unassigned




Created:


 18/Aug/14 9:50 AM




Environment:


Linux, CentOS 6.2




Priority:

  Normal




Reporter:

 David Gwilliam










Steps to reproduce:


do not disable pe-puppet service


successfully compile catalog from non-Production environment using puppet agent -t --noop --environment manage_meta, catalog is cached locally


puppet master fails to compile catalog in agent's assigned environment (e.g. because a new class is assigned for testing non-Production code)


agent enforces non-Production state contained in cached catalog in violation of environment = production explicitly declared in puppet.conf
   

Jira (PUP-3077) When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment

[David Gwilliam (JIRA)]

Title: Message Title










 

 David Gwilliam updated an issue











 






 Puppet /  PUP-3077



  When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment 










Change By:

 David Gwilliam









 Steps to reproduce:- do not disable {{pe-puppet}} service- successfully compile catalog from non-Production environment using {{puppet agent -t --noop --environment manage_meta}}, catalog is cached locally- puppet master fails to compile catalog in agent's assigned environment (e.g. because a new class is assigned for testing non-Production code)-  on next scheduled run,  agent enforces non-Production state contained in cached catalog in violation of {{environment = production}} explicitly declared in puppet.conf- This is accompanied by the warning message indicating that the ENC is overriding the agent as authoritative source for environmentObviously, this could have very bad side effects and, while consistent and predictable, falls squarely under the category of undesirable (and unexpected) behavior, in my opinion.












   

 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-3077) When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment

[David Gwilliam (JIRA)]

Title: Message Title










 

 David Gwilliam updated an issue











 






 Puppet /  PUP-3077



  When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment 










Change By:

 David Gwilliam




Summary:

 When puppet agent fails to  contact the  retrieve catalog from  master, cached catalog is used without regard for the puppet.conf-declared environment












   

 Add Comment











 










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




 














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

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

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






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










We've decided to remote *> for now: https://github.com/puppetlabs/puppetdb/pull/1052
In the future we may rethink this.












   

 Add Comment











 













 PuppetDB /  PDB-820



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







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















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




 














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

Jira (PDB-830) The regexp array operator is too greed when .* is used as the last element

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber assigned an issue to Kenneth Barber











 






 PuppetDB /  PDB-830



  The regexp array operator is too greed when .* is used as the last element 










Change By:

 Kenneth Barber




Assignee:

 Kenneth Barber












   

 Add Comment











 










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




 














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

Jira (PDB-830) The regexp array operator is too greed when .* is used as the last element

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-830



  The regexp array operator is too greed when .* is used as the last element 










Change By:

 Kenneth Barber




Sprint:

 20140813 to 20140827












   

 Add Comment











 










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




 














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

Jira (PDB-830) The regexp array operator is too greed when .* is used as the last element

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber created an issue











 






 PuppetDB /  PDB-830



  The regexp array operator is too greed when .* is used as the last element 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 18/Aug/14 10:16 AM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 Kenneth Barber










When you use .* at the end of an array regexp (~>) it is too greedy and grabs multiple elements.



# curl 'http://localhost:8080/v4/fact-nodes?query=\["~>","path",\["networking","eth.*","macaddress.*"\]\]'
[ {
  "certname" : "node-0",
  "path" : [ "networking", "eth0", "macaddresses", 1 ],
  "name" : "networking",
  "value" : "aa:bb:cc:dd:ee:01",
  "environment" : null
}, {
  "certname" : "node-0",
  "path" : [ "networking", "eth0", "macaddresses", 0 ],
  "name" : "networking",
  "value" : "aa:bb:cc:dd:ee:00",
  "environment" : null
} ]%















   

 Add Comment


   

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

[Peter Huene (JIRA)]

Title: Message Title










 

 Peter Huene created an issue











 






 Facter /  FACT-659



  Partitions fact does not correctly parse the filesystem attribute under Linux 










Issue Type:

  Bug




Affects Versions:


 2.1.0




Assignee:

 Peter Huene




Created:


 18/Aug/14 10:39 AM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 Peter Huene













$ 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-bac8-039337606097
  sdb3:
uuid: 796295c7-31fc-4d32-b2f3-be01643e486c
size: '156092559'
mount: /
filesystem: ext4" PARTLABEL="Linux filesystem" PARTUUID="c925ccbf-3ca4-497e-8cd9-0e0dd637ce23
  sdc1:
size: '204800'
filesystem: ntfs" PARTUUID="7b61cd54-01
  sdc2:
size: '499908608'
filesystem: ntfs" PARTUUID="7b61cd54-02

Jira (FACT-614) Create structured operating system fact

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Facter /  FACT-614



  Create structured operating system fact 










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-2924) Puppet searches disk for whit classes

[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-2924) Puppet searches disk for whit classes

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Puppet searches disk for whit classes 










Merged GH-2979 in 69310a8.












   

 Add Comment











 













 Puppet /  PUP-2924



  Puppet searches disk for whit classes 







 Our Puppet instance has been pretty slow lately so we traced a puppet agent run to see what it was doing. In the trace we see a bunch of lines like this:   stat("/opt/local/lib/ruby/site_ruby/2.0.0/puppet/vendor/semantic/lib/puppet/type/completed_stage.rb", 0xFD7FFFDFE4A0) Err#2 ENOENT  stat("/etc/puppet/modules/admin/lib/puppet/type/completed_stage















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




 














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

[Peter Huene (JIRA)]

Title: Message Title










 

 Peter Huene updated an issue











 






 Facter /  FACT-659



  Partitions fact does not correctly parse the filesystem attribute under Linux 










Change By:

 Peter Huene




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

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: simplify/move warn_if_near_expiration 










You can check rack with a puppet-passenger package install on a Debian host.












   

 Add Comment











 













 Puppet /  PUP-3031



  simplify/move warn_if_near_expiration 







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















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




 














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

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

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

Jira (PUP-3032) Setting to cache `load_library` failures

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

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

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

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

[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

[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 (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master

[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 (FACT-614) Create structured operating system fact

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

[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 (PUP-3063) Remove certification expiration check from puppet-4

[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 (PUP-3025) resource_type search can produce errors if storedconfigs is not configured.

[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-3054) Class inheritance behaving incorrectly in the future parser

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

[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 (PDB-829) PR (1051): (maint) Add pretty SQL formatting - kbarber

[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 (PDB-829) PR (1051): (maint) Add pretty SQL formatting - kbarber

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

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

[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 (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.

[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-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.

[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 (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master

[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

[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-3009) PMT download treats error responses as modules

[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 (PUP-2186) Add `puppet module show` action

[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-2186) Add `puppet module show` action

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

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

[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

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

[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-3015) Add acceptance test for PMT search command changes for 3.7

[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-2701) Add acceptance tests for PMT build metadata.json support

[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

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

[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-2301) puppet module list --tree output shows dependencies incorrectly

[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-2301) puppet module list --tree output shows dependencies incorrectly

[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-2300) Prune dead code from PMT

[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-2300) Prune dead code from PMT

[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

[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

[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

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

[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-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release

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

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

[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-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release

[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

[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-2988) PMT dependency resolution happens in a suboptimal order

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

[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

[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

[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-3069) Use a manifest setting in [master] as global manifests

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

[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-410) Complete Implementation of Language based on the EGrammar

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

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

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

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

[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

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

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

[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 (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master

[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

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

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

[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

[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

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

[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 (FACT-458) Implement changes for AIX Memory facts (already commited)

[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 (FACT-458) Implement changes for AIX Memory facts (already commited)

[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)

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