Jira (PUP-3060) Remove Warning on Ruby 2.0 / Windows about DL is deprecated, please use Fiddle
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3060 Remove Warning on Ruby 2.0 / Windows about DL is deprecated, please use Fiddle Change By: Josh Cooper Assignee: JoshCooper 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-3079) latest atrribute for vcsrepo svn provider does not work if latest revision has more digits that current one
Title: Message Title Ronny M created an issue Puppet / PUP-3079 latest atrribute for vcsrepo svn provider does not work if latest revision has more digits that current one Issue Type: Bug Affects Versions: 2.7.25 Assignee: Andy Parker Components: Modules Created: 19/Aug/14 12:20 AM Labels: puppetlabs-vcsrepo Priority: Normal Reporter: Ronny M puppetlabs/vcsrepo 2.0 and 1.1 (svn provider) do not update to the latest revision if latest revision has more digits that current revision. 9 = 22 (fails) 10 = 22 (succeeds) 9500 = 1010 (fails) 1001 = 1010 (succeeds)
Jira (PUP-3080) vcsrepo (force = true) attribute for svn provider generates puppet error
Title: Message Title Ronny M created an issue Puppet / PUP-3080 vcsrepo (force = true) attribute for svn provider generates puppet error Issue Type: Bug Affects Versions: 2.7.25 Assignee: Andy Parker Components: Modules Created: 19/Aug/14 1:10 AM Labels: puppetlabs-vcsrepo Priority: Normal Reporter: Ronny M It seems that the force option is also added to the svn info (-rHEAD) command for checking current and latest revision by the vcsrepo resource. svn Info hasn't a force option so this generates a puppet run error. notice: /Vcsrepo[/root/scripts]/ensure: Deleting current repository before recloning notice: /Vcsrepo[/root/scripts]/ensure: Create repository from latest err: /Vcsrepo[/root/scripts]: Could not evaluate: Execution of '/usr/bin/svn - non-interactive --username svn_tsslx --password fxipzvK1sScktKA --no-auth-cache --force info' returned 1: Subcommand 'info' doesn't accept option ' -force' Type 'svn help info' for usage.
Jira (PUP-3080) vcsrepo (force = true) attribute for svn provider generates puppet error
Title: Message Title Ronny M updated an issue Puppet / PUP-3080 vcsrepo (force = true) attribute for svn provider generates puppet error Change By: Ronny M vcsrepo2.0and1.1 Itseemsthattheforceoptionisalsoaddedtothesvninfo(-rHEAD)commandforcheckingcurrentandlatestrevisionbythevcsreporesource.svnInfohasn'taforceoptionsothisgeneratesapuppetrunerror.notice:/Vcsrepo[/root/scripts]/ensure:Deletingcurrentrepositorybeforerecloningnotice:/Vcsrepo[/root/scripts]/ensure:Createrepositoryfromlatesterr:/Vcsrepo[/root/scripts]:Couldnotevaluate:Executionof'/usr/bin/svn--non-interactive--usernamesvn_tsslx--passwordfxipzvK1sScktKA--no-auth-cache--forceinfo'returned1:Subcommand'info'doesn'tacceptoption'--force'Type'svnhelpinfo'forusage. 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-3080) vcsrepo (force = true) attribute for svn provider generates puppet error
Title: Message Title Ronny M updated an issue Puppet / PUP-3080 vcsrepo (force = true) attribute for svn provider generates puppet error Change By: Ronny M vcsrepo2.0and1.1Itseemsthattheforceoptionisalsoaddedtothesvninfo(-rHEAD)commandforcheckingcurrentandlatestrevisionbythevcsreporesource.svnInfohasn'taforceoptionsothisgeneratesapuppetrunerror.notice:/Vcsrepo[/root/scripts]/ensure:Deletingcurrentrepositorybeforerecloningnotice:/Vcsrepo[/root/scripts]/ensure:Createrepositoryfromlatesterr:/Vcsrepo[/root/scripts]:Couldnotevaluate:Executionof'/usr/bin/svn--non-interactive--username svn_tsslx svn --password fxipzvK1sScktKA x --no-auth-cache--forceinfo'returned1:Subcommand'info'doesn'tacceptoption'--force'Type'svnhelpinfo'forusage. 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-3079) latest atrribute for vcsrepo svn provider does not work if latest revision has more digits that current one
Title: Message Title Ronny M commented on an issue Re: latest atrribute for vcsrepo svn provider does not work if latest revision has more digits that current one This can be solved I think by changing the following line in lib/puppet/provider/vcsrepo/svn.rb: (self.revision = self.latest) and (@resource.value(:source) == self.sourceurl) to: (self.revision == self.latest) and (@resource.value(:source) == self.sourceurl) Add Comment Puppet / PUP-3079 latest atrribute for vcsrepo svn provider does not work if latest revision has more digits that current one puppetlabs/vcsrepo 2.0 and 1.1 (svn provider) do not update to the latest revision if latest revision has more digits that current revision. 9 = 22 (fails) 10 = 22 (succeeds) 9500 = 1010 (fails) 1001 = 1010 (succeeds) This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-2889) Upgrade win32-eventlog
Title: Message Title Rob Reynolds commented on an issue Re: Upgrade win32-eventlog I believe the MSI will contain the correct behavior, because the vendored eventlog also contains a patch to not load the library that is not available on Windows 2003. This was in Puppet-Win32-Ruby 8b064f4. Add Comment Puppet / PUP-2889 Upgrade win32-eventlog We need to either upgrade or replace the use of win32-eventlog. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3056) Restore constants / deprecated call sites changed during x64 upgrade that impact ACL module
Title: Message Title
Ethan Brown commented on an issue
Re: Restore constants / deprecated call sites changed during x64 upgrade that impact ACL module
Does not require FR.
For constants used in the ACL module, we ultimately ended up going a different route and re-defining all the constants local to the module. That way, we're insulated from their moving around within Puppet.
Add Comment
Puppet / PUP-3056
Restore constants / deprecated call sites changed during x64 upgrade that impact ACL module
When {{Puppet::Util::Windows::File}} and {{Puppet::Util::Windows::Security}} were refactored, mixins from older versions of the {{windows-pr]} gem were removed. At the time, we didn't check downstream modules to see if they were consuming any of the mixed in methods or constants. A scan through the ACL module has revealed that some methods were not ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-829) PR (1051): (maint) Add pretty SQL formatting - kbarber
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/636/ Add Comment PuppetDB / PDB-829 PR (1051): (maint) Add pretty SQL formatting - kbarber h2. (maint) Add pretty SQL formatting * Author: Ken Barber k...@bob.sh * 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
Jira (PUP-3047) Validate Puppet -x64-mingw32 gem dependencies on x64
Title: Message Title Ethan Brown commented on an issue Re: Validate Puppet -x64-mingw32 gem dependencies on x64 I guess our hand is forced on the win32-eventlog upgrade Had to update from the old 0.5.3 eventlog gem (as part of PUP-2889 ) since it was not FFI'd Even though the 0.6.1 gem has a bug in it that doesn't appear in the gem per https://jira.puppetlabs.com/browse/PUP-3061 Rob Reynolds and I caught the eventlog thing last week, but he decided to pause on merging it because of the missing patch. I also wasn't sure what the ultimate result was on 2003. I got the impression that 0.6.1 didn't work properly on 2003, which is obviously a bigger issue if that's the case. 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)
Jira (PUP-3081) reported catalog run time is wildly inaccurate
Title: Message Title Ward Vandewege created an issue Puppet / PUP-3081 reported catalog run time is wildly inaccurate Issue Type: Bug Affects Versions: 3.4.3 Assignee: Kylo Ginsberg Components: Client Created: 19/Aug/14 8:07 AM Environment: Debian Wheezy Priority: Normal Reporter: Ward Vandewege The puppet client clearly does not actually use wallclock time to calculate how long a puppet run takes. Here are a few examples of puppet runs with the time command: time puppet agent -t Notice: Finished catalog run in 131.19 seconds real 3m32.015s user 1m48.207s sys 0m18.101s time puppet agent -t
Jira (PUP-2889) Upgrade win32-eventlog
Title: Message Title Ethan Brown commented on an issue Re: Upgrade win32-eventlog FYI Josh Cooper we had started to go forward on this last week, but held off since the 0.6.1 gem still doesn't have the patch necessary to fix eventlog on 2003. Unfortunately a new gem still hasn't been released that incorporates your patch. So some Windows specs for eventlog are broken as a result. https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/job/Puppet-Specs-Windows-master/nodes=win2003r2/2457/#showFailuresLink We're in a bad spot on this one given we wanted to upgrade eventlog for the sake of PUP-3047 , but the new gem isn't ready yet. I believe our only option is to temporarily skip the failing tests on 2003 and add some additional detail to PUP-3061 to make sure to remove those guards. Add Comment Puppet / PUP-2889 Upgrade win32-eventlog We need to either upgrade or replace the use of win32-eventlog. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3047) Validate Puppet -x64-mingw32 gem dependencies on x64
Title: Message Title Ethan Brown commented on an issue Re: Validate Puppet -x64-mingw32 gem dependencies on x64 Yes, verified that the gem has broken 17 specs on Windows 2003. Our only option is to skip those tests on 2003 for now, and add some notes to PUP-3061 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 (PDB-831) PR (1054): (maint) Remove more dead code from facts.clj - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-831 PR (1054): (maint) Remove more dead code from facts.clj - kbarber Issue Type: Task Assignee: Unassigned Created: 19/Aug/14 8:46 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Remove more dead code from facts.clj Author: Ken Barber k...@bob.sh Company: Puppet Labs Inc. Github ID: kbarber Pull Request 1054 Discussion Pull Request 1054 File Diff Pull Request Description This removes some older facts flattening code that is no longer used. Signed-off-by: Ken Barber k...@bob.sh (webhooks-id: d0d0275c5ef6df780a4c17eb906ca597)
Jira (PDB-831) PR (1054): (maint) Remove more dead code from facts.clj - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-831 PR (1054): (maint) Remove more dead code from facts.clj - kbarber Change By: Kenneth Barber Sprint: 20140813to20140827 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-831) PR (1054): (maint) Remove more dead code from facts.clj - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-831 PR (1054): (maint) Remove more dead code from facts.clj - kbarber Change By: Kenneth Barber Assignee: KennethBarber Story Points: 0 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 (PUP-2889) Upgrade win32-eventlog
Title: Message Title Ethan Brown commented on an issue Re: Upgrade win32-eventlog Added a PR to mark related specs as pending on 2003 so that we can clear CI. In the logging_spec.rb, there are more tests marked pending than necessary, but I didn't think it was worth the effort of refactoring the tests to the bar minimum at this time, given we should be expecting a new gem soon. Add Comment Puppet / PUP-2889 Upgrade win32-eventlog We need to either upgrade or replace the use of win32-eventlog. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3061) Upgrade win32-eventlog to 0.6.2+ once it is released
Title: Message Title Ethan Brown commented on an issue Re: Upgrade win32-eventlog to 0.6.2+ once it is released A new PR is pending for PUP-2889 that marks specific tests as pending on 2003 until we can get an upgraded gem. https://github.com/puppetlabs/puppet/pull/2991 PUP-2889 has been put back into the ready for merge state, and should be updating after the PR is reviewed + merged. Add Comment Puppet / PUP-3061 Upgrade win32-eventlog to 0.6.2+ once it is released This will incorporate https://github.com/djberg96/win32-eventlog/pull/10 fix that we need to upgrade the gems locally in puppet. Following that up we'll need to remove the patches from the puppet-win32-ruby repository. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-2924 Puppet searches disk for whit classes Change By: Eric Thompson Assignee: EricThompson 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)
Title: Message Title Kylo Ginsberg commented on an issue Re: Implement changes for AIX Memory facts (already commited) William Hopper I'm not sure why the SHAs in the description above are referenced But I looked in facter/master history for the merge commit associated with that redmine ticket and found cbbb6de, which does seem to have some payload not in current facter/master: [4] facter git:(master) git cherry-pick -m1 cbbb6de error: could not apply cbbb6de... Merge pull request #554 from haus/ticket/stable/fix-aix-memory-facts hint: after resolving the conflicts, mark the corrected paths hint: with 'git add paths' or 'git rm paths' hint: and commit the result with 'git commit' But honestly I haven't studied the code so I could easily be missing something and the fix is already in. So yeah, your question is an excellent one, and I don't honestly know if/how this is working on AIX. Since the history here is a bit muddy maybe we should grab an AIX LPAR and try it out. 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...
Jira (PUP-3082) Error in puppet module skeleton
Title: Message Title
Sebastian Otaegui created an issue
Puppet / PUP-3082
Error in puppet module skeleton
Issue Type:
Bug
Affects Versions:
3.7.0
Assignee:
Unassigned
Components:
PMT
Created:
19/Aug/14 9:24 AM
Labels:
moduletool
Priority:
Normal
Reporter:
Sebastian Otaegui
The puppet module skeleton specifies a Gemfile with the following line:
puppetversion = ENV.key?('PUPPET_VERSION') ? = # {ENV['PUPPET_VERSION']} : ['= 3.3'] if you define an env var as PUPPET_VERSION=~ 3.6.0 as most people do when testing with travis, bundler will complain stating it cannot meet the requirements. Changing the line to: puppetversion = ENV.key?('PUPPET_VERSION') ? #{ENV['PUPPET_VERSION']}
: ['= 3.3']
Fixes the issue.
Jira (PUP-3031) simplify/move warn_if_near_expiration
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3031 simplify/move warn_if_near_expiration Change By: Josh Cooper Assignee: JoshCooper 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-3061) Upgrade win32-eventlog to 0.6.2+ once it is released
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3061 Upgrade win32-eventlog to 0.6.2+ once it is released Change By: Rob Reynolds Thiswillincorporatehttps://github.com/djberg96/win32-eventlog/pull/10fixthatweneedtoupgradethegemslocallyinpuppet.Followingthatupwe'llneedtoremovethepatchesfromthepuppet-win32-rubyrepository. Removetheguardsputinwithhttps://github.com/puppetlabs/puppet/pull/2991 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
Title: Message Title Josh Cooper updated an issue Puppet / PUP-744 Pool HTTPS connections Change By: Josh Cooper Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-744) Persistent HTTP(S) connections
Title: Message Title Josh Cooper updated an issue Puppet / PUP-744 Persistent HTTP(S) connections Change By: Josh Cooper Summary: PoolHTTPS PersistentHTTP(S) connections 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-810) Analyze new structured fact schema and indexing under load
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-810 Analyze new structured fact schema and indexing under load Change By: Wyatt Alt Assignee: WyattAlt 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-3084) --detailed-exitcodes not honoured for errors with puppet agent
Title: Message Title Alan Hodgson created an issue Puppet / PUP-3084 --detailed-exitcodes not honoured for errors with puppet agent Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Components: Client Created: 19/Aug/14 9:45 AM Environment: Linux x86_64 Ruby 1.9.3p545 (a rebuild of a fedora package running on CentOS 6) Puppet 3.6.2 client and server Priority: Minor Reporter: Alan Hodgson When puppet agent --detailed-exitcodes encounters an error, it exits with status 1. The docs suggest that should be either a 4 or a 6, depending on whether changes also occurred. Example: [root@server tmp]# /usr/bin/puppet agent -v --detailed-exitcodes --ignorecache --no-usecacheonfailure --no-daemonize --onetime --server puppetmaster --environment=dev --waitforcert 60 Info: Retrieving pluginfacts Info: Retrieving plugin Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find template 'puppet/run-puppet.tpl' at /puppet/environments/dev/modules/puppet/manifests/init.pp:15 on node
Jira (PUP-2889) Upgrade win32-eventlog
Title: Message Title Rob Reynolds commented on an issue Re: Upgrade win32-eventlog Merged into master at 6fdea01. Merged into puppet-4 at 84d91df. Add Comment Puppet / PUP-2889 Upgrade win32-eventlog We need to either upgrade or replace the use of win32-eventlog. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3083) Problem with parsing regular expressions.
Title: Message Title
Dominik Zyla created an issue
Puppet / PUP-3083
Problem with parsing regular expressions.
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Andy Parker
Components:
DSL
Created:
19/Aug/14 9:45 AM
Environment:
Occurs on AWS on Amazon Linux distribution.
Priority:
Normal
Reporter:
Dominik Zyla
It seems the way regular expressions are now parsed has been changed and I presume it wasn't on purpose.
Here's how it used to work before and what I consider as expected:
On 3.4.3
[ec2-user@instance-CN5L5XeZKd ~]$ cat test.pp
$test = 1
case $test {
/^\d+$/: {
fail('MATCH')
}
default: {
fail(Not MATCH)
}
}
[ec2-user@instance-CN5L5XeZKd ~]$ puppet apply test.pp
Error: MATCH at /home/ec2-user/test.pp:5 on node instance-cn5l5xezkd.us-west-1.compute.internal
Error: MATCH at
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2349 Deprecate non-string modes on file type Change By: Kurt Wall Assignee: KurtWall 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-2889) Upgrade win32-eventlog
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2889 Upgrade win32-eventlog Change By: Rob Reynolds Sprint: Week2014-6-25to2014-7-9 ,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 (PDB-831) PR (1054): (maint) Remove more dead code from facts.clj - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1054): (maint) Remove more dead code from facts.clj - kbarber pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/637/ Add Comment PuppetDB / PDB-831 PR (1054): (maint) Remove more dead code from facts.clj - kbarber h2. (maint) Remove more dead code from facts.clj * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1054 Discussion|https://github.com/puppetlabs/puppetdb/pull/1054] * [Pull Request 1054 File Diff|https://github.com/puppetlabs/puppetdb/pull/1054/files] h2. Pull Request Des... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2349 Deprecate non-string modes on file type Change By: Kurt Wall Assignee: KurtWall 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-2987) Puppet service hangs when attempting to stop on Windows
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2987 Puppet service hangs when attempting to stop on Windows Change By: Kurt Wall Assignee: KurtWall 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)
Title: Message Title William Hopper commented on an issue Re: Implement changes for AIX Memory facts (already commited) This was already fixed, so no changes needed! Add Comment Facter / FACT-458 Implement changes for AIX Memory facts (already commited) We are running facter 1.7.3 on AIX systems and they are not reporting memorysize and memoryfree facts. This has already been implemented on May 31st 2013 according to the git history: Commit: 183b2ba4035cd0e532a7bfcb90047c816a4dfd4d (#20994) fix incorrect memoryfree fact on AIX (was set to 0) Commit: b739a96626a5bbc48ffa99a5b5f3fb9ce5f8bf83 (#2099... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-831) PR (1054): (maint) Remove more dead code from facts.clj - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1054): (maint) Remove more dead code from facts.clj - kbarber Pull request (maint) Remove more dead code from facts.clj has been closed. Add Comment PuppetDB / PDB-831 PR (1054): (maint) Remove more dead code from facts.clj - kbarber h2. (maint) Remove more dead code from facts.clj * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1054 Discussion|https://github.com/puppetlabs/puppetdb/pull/1054] * [Pull Request 1054 File Diff|https://github.com/puppetlabs/puppetdb/pull/1054/files] h2. Pull Request Des... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.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
Title: Message Title
Bob Rasey commented on an issue
Re: PMT upgrade command returns an error when trying to upgrade a module with only one release
I see this at our site. We're updating modules via r10k/Puppetfile, but here's what the failure looks like here:
puppet module --modulepath '/etc/puppetlabs/puppet/environments/production/modules' upgrade --ignore-dependencies example42/perl Notice: Preparing to upgrade 'example42-perl' ... Notice: Found 'example42-perl' (v2.0.17) in /etc/puppetlabs/puppet/environments/production/modules ... Error: Could not upgrade module 'example42-perl' (v2.0.17 - latest) Installed module has had changes made locally Use `puppet module upgrade --force` to upgrade this module anyway
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)
Jira (PUP-3032) Setting to cache `load_library` failures
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3032 Setting to cache `load_library` failures Change By: Joshua Partlow Assignee: JoshuaPartlow 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
Title: Message Title Joshua Partlow commented on an issue Re: Resolve Tempfile handling issues Merged to master in d5585e Add Comment Puppet / PUP-3030 Resolve Tempfile handling issues See linked PE ticket; I will add a more precise description of the work needed here once we've gotten a bit further in investigating our options, but just wanted to get a 3.7.0 ticket in place because I do think some change will be needed before then. The gist of the issue is that the `Tempfile` class may not behave well in long-running JRuby processes... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-629) ec2 facts should ignore proxy
Title: Message Title
William Hopper commented on an issue
Re: ec2 facts should ignore proxy
The ec2 facts now contain a `reachable?` method to determine suitability. This commit didn't add the default value of nil for :proxy in the initial connection to the baseurl, and thus `http_proxy=http://nonexistent.invalid/ facter ec2_mac` still fails as described above.
A fix for this should be up in a PR in the next few minutes.
Add Comment
Facter / FACT-629
ec2 facts should ignore proxy
On an ec2 instance: {code}aj:~$ facter ec2_mac 06:6e:3c:a0:6d:78 aj:~$ http_proxy=http://nonexistent.invalid/ facter ec2_macaj:~${code} A change like the following should be made: https://github.com/alexjurkiewicz/facter/commit/902529ea32fecb0c45ea8628443d8f809695bf44#diff-5d468eb8d8ea9574dd2a2e00b3064cf7R81
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to
Jira (FACT-467) Puppet 3 uninstallable on Debian ARM
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-467 Puppet 3 uninstallable on Debian ARM Change By: Kylo Ginsberg 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 (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3021 User resource on AIX returns a non-working structure or 'attributes' Change By: Steve Barlow Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3032) Setting to cache `load_library` failures
Title: Message Title Joshua Partlow commented on an issue Re: Setting to cache `load_library` failures Melissa Stone There is a new setting in this patch, :always_cache_features, which defaults to false, preserving old behavior and is the desired behavior on agents. But masters probably want always_cache_features set true. This might be a good addition to puppet.conf in our foss packages? Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3069 Use a manifest setting in [master] as global manifests Change By: Steve Barlow Sprint: 2014-09-03 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-3085) possible Directory Environments bug
Title: Message Title TJ Walker created an issue Puppet / PUP-3085 possible Directory Environments bug Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Attachments: puppet.conf, puppet_httpd_error_log.txt, puppetlogs.txt Created: 19/Aug/14 10:42 AM Environment: production, development Labels: support Priority: Normal Reporter: TJ Walker I attempted to update puppet.conf to move from config-file environments to directory environments but puppet master wouldn't start. I have reverted the changes but puppet master still wont start. I have attached my current puppet.conf, puppet logs and httpd logs.
Jira (PUP-3032) Setting to cache `load_library` failures
Title: Message Title Joshua Partlow commented on an issue Re: Setting to cache `load_library` failures Merged to master in a704036; will be going out in 3.7.0 Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3032 Setting to cache `load_library` failures Change By: Joshua Partlow Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3086) Add spec tests for puppet strings
Title: Message Title Hailee Kenney created an issue Puppet / PUP-3086 Add spec tests for puppet strings Issue Type: Improvement Assignee: Unassigned Created: 19/Aug/14 10:55 AM Priority: Normal Reporter: Hailee Kenney Original Estimate: 1 week Remaining Estimate: 1 week Since the puppet strings feature was originally a prototype, it currently does not have any tests written. Some spec tests need to be added to ensure that the project is sustainable. https://github.com/puppetlabs/puppetlabs-strings Add Comment
Jira (PUP-3086) Add spec tests for puppet strings
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-3086 Add spec tests for puppet strings Change By: Hailee Kenney Assignee: HaileeKenney 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
Title: Message Title John Duarte updated an issue Puppet / PUP-3031 simplify/move warn_if_near_expiration Change By: John Duarte QA Contact: EricThompson QA Status: Reviewed 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-1044) FileBucket should not keep files in memory
Title: Message Title Henrik Lindberg commented on an issue Re: FileBucket should not keep files in memory PR merged to master. Follow up fix also made in a22bdca780ee8874fb868ff32c0f4a09e44fbd5b (file mode for creating a stream was r instead of the required rb for binary mode). Add Comment Puppet / PUP-1044 FileBucket should not keep files in memory It should not be necessary to load entire files into memory to checksum them. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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
Title: Message Title Steve Barlow updated an issue Puppet / PUP-2914 Update packages to use RGen 0.7.0 Change By: Steve Barlow Sprint: 2014-09-03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3050) Fix cfacter integration to match recent cfacter changes
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3050 Fix cfacter integration to match recent cfacter changes Change By: Kurt Wall QA Contact: ErikDasher KurtWall QA Status: Reviewed 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
Title: Message Title Melissa Stone commented on an issue Re: Setting to cache `load_library` failures Joshua Partlow yeah, if there are significant performance improvements, it might not be a bad idea to think about. Would that be something you'd like to see in puppet 4? Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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
Title: Message Title
William Hopper updated an issue
Facter / FACT-614
Create structured operating system fact
Change By:
William Hopper
Currently,thereareseveralfactsrelatedtooperatingsystembaseddata,including:{noformat}operatingsystemoperatingsystemmajreleaseoperatingsystemreleaseosfamily{noformat}Also,thereareahandfuloflsb*factsforLinuxsystems,including:{noformat}lsbdistcodenamelsbdistdescriptionlsbdistidlsbdistreleaselsbmajdistrelease lsbminordistrelease lsbrelease{noformat}Thesecombinedareagoodcandidateforastructuredfact.Outputforthisfactcouldappearasfollows(onaLinuxsystem):{noformat}{osfamily=Debian,operatingsystem=Debian,release={major= 1 ,minor= 2 , patch=3 ,full=1.2.3},lsb={distid=Debian,distcodename=wheezy,distdescription=DebianGNU/Linux7.4(wheezy),distrelease=1.2.3,majdistrelease=1 ,minordistrelease=2 }}{noformat}Backwardscompatibilitywithexistingflatfactsshouldbemaintained.Thenamingofthisstructuredfactisalsounderconsideration.
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.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2999 Merge clay-davis branch of FOSS puppet into upstream repository. Change By: Joshua Partlow 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-2924) Puppet searches disk for whit classes
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2924 Puppet searches disk for whit classes Change By: Eric Thompson QA Status: Reviewed 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
Title: Message Title Christopher Price commented on an issue Re: Setting to cache `load_library` failures Melissa Stone for PE we are going to want to set that setting on the master for PE 3.4. That probably doesn't have any bearing on what you decide to do for OSS, but just FYI. I linked in a PE ticket that is about making sure we get that setting turned on for PE. Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-744) Persistent HTTP(S) connections
Title: Message Title Eric Thompson updated an issue Puppet / PUP-744 Persistent HTTP(S) connections Change By: Eric Thompson QA Contact: EricThompson QA Status: Reviewed 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
Title: Message Title Melissa Stone commented on an issue Re: Setting to cache `load_library` failures Christopher Price, since this is getting into PE 3.4, then we might want to think about making this update in Puppet 3.7, since that's the puppet version getting into PE 3.4. However, 3.7 is slated for release next week. Kylo Ginsberg do you have any thoughts on this? Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-3008) Already initialized constant warning when running puppet
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3008 Already initialized constant warning when running puppet Change By: Josh Cooper Assignee: JoshCooper 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-3085) possible Directory Environments bug
Title: Message Title TJ Walker updated an issue Puppet / PUP-3085 possible Directory Environments bug Change By: TJ Walker Issue Type: Bug Story 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-3087) PMT upgrade should let you specify the path to your modules
Title: Message Title garrett honeycutt created an issue Puppet / PUP-3087 PMT upgrade should let you specify the path to your modules Issue Type: Bug Assignee: Unassigned Created: 19/Aug/14 12:14 PM Priority: Normal Reporter: garrett honeycutt `puppet module install` supports specify the target directory with --target-dir DIR | -i DIR. `puppet module upgrade` should also support these flags so you can upgrade modules in a specified directory. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3087) PMT upgrade should let you specify the path to your modules
Title: Message Title garrett honeycutt updated an issue Puppet / PUP-3087 PMT upgrade should let you specify the path to your modules Change By: garrett honeycutt Assignee: RyanColeman 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-3008) Already initialized constant warning when running puppet
Title: Message Title Josh Cooper commented on an issue Re: Already initialized constant warning when running puppet 2.0.0-x64, before change: C:\work\puppet [master +12 ~0 -0 !] .\ext\envpuppet puppet agent -t c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/2.0.0/gems/win32-eventlog-0.6.1/lib/win32/windows/constants.rb:26: warning: already initialized constant Windows::Constants::ERROR_INSUFFICIENT_BUFFER c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/2.0.0/gems/win32-service-0.8.5/lib/win32/windows/constants.rb:136: warning: previous definition of ERROR_INSUFFICIENT_BUFFER was here c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/2.0.0/gems/win32-eventlog-0.6.1/lib/win32/windows/constants.rb:31: warning: already initialized constant Windows::Constants::INFINITE c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/2.0.0/gems/win32-service-0.8.5/lib/win32/windows/constants.rb:120: warning: previous definition of INFINITE was here c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/2.0.0/gems/win32-eventlog-0.6.1/lib/win32/windows/constants.rb:32: warning: already initialized constant Windows::Constants::WAIT_FAILED c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/2.0.0/gems/win32-service-0.8.5/lib/win32/windows/constants.rb:141: warning: previous definition of WAIT_FAILED was here c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/2.0.0/gems/win32-eventlog-0.6.1/lib/win32/windows/constants.rb:52: warning: already initialized constant Windows::Constants::FORMAT_MESSAGE_IGNORE_INSERTS c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/2.0.0/gems/win32-service-0.8.5/lib/win32/windows/constants.rb:126: warning: previous definition of FORMAT_MESSAGE_IGNORE_INSERTS was here 2.0.0-x64, with change, merged in 18eaa515 C:\work\puppet [master +12 ~0 -0 !] .\ext\envpuppet puppet agent -t Info: Retrieving pluginfacts 1.9.3-x86, before change: C:\work\puppet [master +12 ~0 -0 !] .\ext\envpuppet puppet agent -t c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/windows/constants.rb:26: warning: already initialized constant ERROR_INSUFFICIENT_BUFFER c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/windows/constants.rb:31: warning: already initialized constant INFINITE c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/windows/constants.rb:32: warning: already initialized constant WAIT_FAILED c:/work/puppet-win32-ruby/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/windows/constants.rb:52: warning: already initialized constant FORMAT_MESSAGE_IGNORE_INSERTS 1.9.3-x86, with change, merged in 7329dd9a C:\work\puppet [master +12 ~0 -0 !] .\ext\envpuppet puppet agent -t Info: Retrieving pluginfacts
Jira (PDB-769) Deprecate pre 9.3 PostgreSQL
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-769 Deprecate pre 9.3 PostgreSQL Change By: Kenneth Barber Assignee: KennethBarber 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
Title: Message Title Joshua Partlow commented on an issue Re: Setting to cache `load_library` failures Melissa Stone Yes, 4.0 sounds right for a package change. Nicholas Fagerlund Yes, I think we'd recommend this always to be set true in the [master] section of a master installation. I believe setting it in main could have an impact on agent runs on the master itself. Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-3008) Already initialized constant warning when running puppet
Title: Message Title
Josh Cooper commented on an issue
Re: Already initialized constant warning when running puppet
For review:
install puppet x86 from: http://jenkins-release.delivery.puppetlabs.net/view/Windows%20Builds/job/Windows%20On%20Demand/8/ARCH=x86,label=win-build/artifact/pkg/puppet-3.6.2-1040-g58401f3.msi
Run puppet agent -t and verify there are no already initialized constant messages.
Repeat with puppet x64 from: http://jenkins-release.delivery.puppetlabs.net/view/Windows%20Builds/job/Windows%20On%20Demand/ARCH=x64,label=win-build/8/artifact/pkg/puppet-3.6.2-1040-g58401f3-x64.msi
Add Comment
Puppet / PUP-3008
Already initialized constant warning when running puppet
{noformat} C:\Windows\system32puppet agent -t C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/windows/constants.rb:26: warning: already initialized constant ERROR_INSUFFICIENT_BUFFER C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/wind...
Jira (PUP-3088) The debug logging method can't be used by providers with a path property
Title: Message Title
Charlie Sharpsteen created an issue
Puppet / PUP-3088
The debug logging method can't be used by providers with a path property
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Unassigned
Created:
19/Aug/14 12:59 PM
Labels:
logging
Priority:
Normal
Reporter:
Charlie Sharpsteen
The definition of the `debug` logging method contains some very bad assumptions. In particular, logging at the debug level will attempt to set a source line for the message (location in ruby file, puppet manifest, etc.). Unfortunately, the method which sets the source line assumes that if the object which emitted the log message responds to the path method, then it also responds to tags, file and line.
This assumption is disastrous when a class using debug logging defines a path method purely by coincidence. The original reproduction case for this is the Solaris Zone provider which has a path property and emits log messages at debug level:
test_zone.pp
zone { 'test_zone':
ensure = 'running',
path = '/zones/test_zone',
# This part is required, it adds un-modeled configuration to the zone
Jira (PUP-3088) The debug logging method can't be used by providers with a path method
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3088 The debug logging method can't be used by providers with a path method Change By: Charlie Sharpsteen Summary: Thedebugloggingmethodcan'tbeusedbyproviderswithapath property method 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-3088) The debug logging messages can't be used by providers with a path method
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3088 The debug logging messages can't be used by providers with a path method Change By: Charlie Sharpsteen Summary: Thedebuglogging method messages can'tbeusedbyproviderswithapathmethod 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-3088) Debug logging messages can't be used by providers with a path method
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3088 Debug logging messages can't be used by providers with a path method Change By: Charlie Sharpsteen Summary: Thedebug Debug loggingmessagescan'tbeusedbyproviderswithapathmethod 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
Title: Message Title Christopher Price commented on an issue Re: Setting to cache `load_library` failures Melissa Stone we could always do the config change in PE packaging only, if we want. I don't have an opinion on that; will defer to you, Matthaus Owens and co. Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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
Title: Message Title Joshua Partlow commented on an issue Re: Setting to cache `load_library` failures Melissa Stone For FOSS I think it's safer to leave it for 4.0 since it is technically a behavior change. Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3088) Debug logging messages can't be used by providers with a path method
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3088 Debug logging messages can't be used by providers with a path method Change By: Charlie Sharpsteen Thedefinitionofthe`debug`loggingmethodcontainssomeverybadassumptions.Inparticular,loggingatthedebuglevelwillattempttosetasourcelineforthemessage(locationinrubyfile,puppetmanifest,etc.).Unfortunately,themethodwhichsetsthesourceline[assumes|https://github.com/puppetlabs/puppet/blob/ master 3.6.2 /lib/puppet/util/log.rb# L319 L317
Jira (PUP-3032) Setting to cache `load_library` failures
Title: Message Title Melissa Stone commented on an issue Re: Setting to cache `load_library` failures Awesome, let's do that then. It should be fine to get this into PE 3.4 only now, and then Puppet 4 later, unless there are any other concerns that I'm not aware of. Are there tickets for this work yet (for both PE and FOSS)? Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For
Jira (PUP-3032) Setting to cache `load_library` failures
Title: Message Title Christopher Price commented on an issue Re: Setting to cache `load_library` failures I linked the relevant PE ticket. It may need to move to a different Jira project and/or change owners, but it's created anyway Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-660) Facter on Solaris 11.2+ should report what zones types are support/active
Title: Message Title
Kristina Tripp created an issue
Facter / FACT-660
Facter on Solaris 11.2+ should report what zones types are support/active
Issue Type:
Improvement
Assignee:
Eric Sorenson
Created:
19/Aug/14 2:16 PM
Environment:
Solaris 11.2+ Sparc/X86
Priority:
Normal
Reporter:
Kristina Tripp
The virtinfo command introduced in Solaris 11.2 allows the user to see what types of zones are supported on the hardware.
When run on a x86 system that supports kernel zones $ virtinfo NAME CLASS non-global-zone supported kernel-zone supported
When run on a x86 kernel zone $ virtinfo NAME CLASS kernel-zone current non-global-zone supported
When run on a x86 system that doesn't support kernel zones $ virtinfo NAME CLASS non-global-zone supported
When run a sparc system that doesn't support kernel zones $ virtinfo NAME CLASS logical-domain current non-global-zone supported
When run on a sparc system that supports kernel zones $ virtinfo NAME CLASS non-global-zone supported kernel-zone supported
The solaris_zones.rb file should be expanded to include the following attributes — facter-2.1.0/lib/facter/util/solaris_zones.rb.orig 2014-08-19 13:49:14.721574641 -0600 +++ facter-2.1.0/lib/facter/util/solaris_zones.rb 2014-08-19 13:50:03.475818042 -0600 @@ -156,3 +156,29 @@ end end end + +Facter.add(kernel_zone) do + confine :operatingsystem = :Solaris + setcode do + virtinfo = %x {/sbin/virtinfo list -H -o class kernel-zone 2/dev/null}
+ case virtinfo.chomp! + when supported, current, parent + virtinfo
Jira (FACT-660) Facter on Solaris 11.2+ should report what zones types are support/active
Title: Message Title Kristina Tripp assigned an issue to Kristina Tripp Facter / FACT-660 Facter on Solaris 11.2+ should report what zones types are support/active Change By: Kristina Tripp Assignee: EricSorenson KristinaTripp 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-660) Facter on Solaris 11.2+ should report if zones are supported
Title: Message Title Kristina Tripp updated an issue Facter / FACT-660 Facter on Solaris 11.2+ should report if zones are supported Change By: Kristina Tripp Summary: FacteronSolaris11.2+shouldreport what if zones types are support/active supported 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-2174) Returned data from PMT actions should be better specified
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2174 Returned data from PMT actions should be better specified Change By: Anderson Mills Assignee: PietervandeBruggen AndersonMills 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
Title: Message Title Anderson Mills updated an issue Puppet / PUP-1046 puppet module generate should produce a skeleton spec test Change By: Anderson Mills Assignee: PietervandeBruggen AndersonMills 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-2513) puppet module install fails when url includes basic auth
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2513 puppet module install fails when url includes basic auth Change By: Anderson Mills Assignee: PietervandeBruggen AndersonMills 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-2431) PMT doesn't follow http redirects
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2431 PMT doesn't follow http redirects Change By: Anderson Mills Assignee: PietervandeBruggen AndersonMills 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-2304) Implement requirements support for the PMT
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2304 Implement requirements support for the PMT Change By: Anderson Mills Assignee: PietervandeBruggen AndersonMills 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
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2301 puppet module list --tree output shows dependencies incorrectly Change By: Anderson Mills Assignee: PietervandeBruggen AndersonMills 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
Title: Message Title Joshua Partlow commented on an issue Re: Setting to cache `load_library` failures Melissa Stone I just added PUP-3090 Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3090) Packaging for puppet master's should include always_cache_features set to true.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-3090 Packaging for puppet master's should include always_cache_features set to true. Issue Type: Improvement Assignee: Unassigned Components: RE Created: 19/Aug/14 2:46 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Joshua Partlow PUP-3032 introduced the always_cache_features settings which will cache feature state regardless of whether the feature test was successful or not (relevant for features tested by lib lookups). This is false by default, and needs to be so for agents/apply so that features effectively enabled part way through a puppet run can be made use of (gem installation is an example). For master's it should default to false however, and we should update our master packaging scripts such that their puppet.conf's have this setting set to false in their [master] section (setting it in [main] would impact agent/apply on the master).
Jira (PUP-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2628 Ability to add a member to a group, instead of specifying the complete list Change By: Rob Reynolds Component/s: Client 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-3067) Windows Package provider should verify DisplayName after install
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3067 Windows Package provider should verify DisplayName after install Change By: Rob Reynolds Component/s: Client 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
Title: Message Title Joshua Partlow commented on an issue Re: Resolve Tempfile handling issues And merged the test fix in 30e4fe Add Comment Puppet / PUP-3030 Resolve Tempfile handling issues See linked PE ticket; I will add a more precise description of the work needed here once we've gotten a bit further in investigating our options, but just wanted to get a 3.7.0 ticket in place because I do think some change will be needed before then. The gist of the issue is that the `Tempfile` class may not behave well in long-running JRuby processes... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2016) Invalid Characters Allowed in Windows Paths for Puppet Resource Type 'file'
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2016 Invalid Characters Allowed in Windows Paths for Puppet Resource Type 'file' Change By: Rob Reynolds Component/s: Client 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-2647) Windows user provider reports that the password is created instead of changed
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2647 Windows user provider reports that the password is created instead of changed Change By: Rob Reynolds Component/s: Client 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-1918) FileUtils.mv is unreliable on Windows
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1918 FileUtils.mv is unreliable on Windows Change By: Rob Reynolds Component/s: Client 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-2919) Remove conditional pending tests on windows x64
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2919 Remove conditional pending tests on windows x64 Change By: Rob Reynolds Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2964) Ruby 2.0 x64 fails on win2003
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2964 Ruby 2.0 x64 fails on win2003 Change By: Rob Reynolds Component/s: Client 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-2982) Reconfigure Jenkins jobs for Puppet Windows acceptance on stable for Ruby 2
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2982 Reconfigure Jenkins jobs for Puppet Windows acceptance on stable for Ruby 2 Change By: Rob Reynolds Component/s: Client 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-2964) Ruby 2.0 x64 fails on win2003
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2964 Ruby 2.0 x64 fails on win2003 Change By: Rob Reynolds Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2982) Reconfigure Jenkins jobs for Puppet Windows acceptance on stable for Ruby 2
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2982 Reconfigure Jenkins jobs for Puppet Windows acceptance on stable for Ruby 2 Change By: Rob Reynolds Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3008) Already initialized constant warning when running puppet
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3008 Already initialized constant warning when running puppet Change By: Rob Reynolds Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
