Jira (MCO-184) PR (164): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (164): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug Pull request (mco-166)(packaging) Remove Fedora 18 from the default package builds has been closed. Add Comment MCollective / MCO-184 PR (164): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug h2. (mco-166)(packaging) Remove Fedora 18 from the default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 164 Discussion|https://github.com/puppetlabs/marionette-collective/pull/164] * [Pull Request 164 File Diff|https://github.com/puppetlabs/marionette-collective/pull/164/files] h2. Pull Requ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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 (MCO-185) PR (165): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (165): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug Pull request (mco-166)(packaging) Remove Fedora 18 from the default package builds has been closed. Add Comment MCollective / MCO-185 PR (165): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug h2. (mco-166)(packaging) Remove Fedora 18 from the default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 165 Discussion|https://github.com/puppetlabs/marionette-collective/pull/165] * [Pull Request 165 File Diff|https://github.com/puppetlabs/marionette-collective/pull/165/files] h2. Pull Requ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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 (PDB-343) (packaging) Remove Fedora 18 from default build targets
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-343 (packaging) Remove Fedora 18 from default build targets Change By: Kenneth Barber Sprint: 20140212to20140219 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/groups/opt_out.
Jira (PDB-459) PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-459 PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-460) PR (119): Adding option to disable management of the firewall - nibalizer
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-460 PR (119): Adding option to disable management of the firewall - nibalizer Change By: Kenneth Barber Component/s: Module 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/groups/opt_out.
Jira (PUP-1147) File purge actions should ignore unmanaged files created by File backup actions
Title: Message Title
Jan rnstedt commented on an issue
Re: File purge actions should ignore unmanaged files created by File backup actions
I still think that it is the backup that should ignore backing up backup files.
Add Comment
Puppet / PUP-1147
File purge actions should ignore unmanaged files created by File backup actions
Create this manifest: {code} $backup = '.old' $fragdir = '/tmp/bug' File { backup = $backup } file { $fragdir: ensure = directory, } file { ${fragdir}/fragments: ensure = directory, force = true, purge = true, recurse = true, } file { ${fragdir}/fragments/file.a: ensure = present, content ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-343) (packaging) Remove Fedora 18 from default build targets
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-343 (packaging) Remove Fedora 18 from default build targets Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-459) PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-459 PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior Change By: Kenneth Barber Sprint: 20140212to20140219 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/groups/opt_out.
Jira (PDB-460) PR (119): Adding option to disable management of the firewall - nibalizer
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-460 PR (119): Adding option to disable management of the firewall - nibalizer Change By: Kenneth Barber Sprint: 20140212to20140219 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/groups/opt_out.
Jira (PDB-460) PR (119): Adding option to disable management of the firewall - nibalizer
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-460 PR (119): Adding option to disable management of the firewall - nibalizer Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-449) PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug Pull request (pdb-343)(packaging) Remove Fedora 18 from default package builds has been closed. Add Comment PuppetDB / PDB-449 PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug h2. (pdb-343)(packaging) Remove Fedora 18 from default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 854 Discussion|https://github.com/puppetlabs/puppetdb/pull/854] * [Pull Request 854 File Diff|https://github.com/puppetlabs/puppetdb/pull/854/files] h2. Pull Request Description Fedora 1... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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 (PDB-449) PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug kbarber commented: Needs rebasing against 1.5.x. Add Comment PuppetDB / PDB-449 PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug h2. (pdb-343)(packaging) Remove Fedora 18 from default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 854 Discussion|https://github.com/puppetlabs/puppetdb/pull/854] * [Pull Request 854 File Diff|https://github.com/puppetlabs/puppetdb/pull/854/files] h2. Pull Request Description Fedora 1... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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 (PDB-450) PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug Pull request (pdb-343)(packaging) Remove Fedora 18 from default package builds has been closed. Add Comment PuppetDB / PDB-450 PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug h2. (pdb-343)(packaging) Remove Fedora 18 from default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 855 Discussion|https://github.com/puppetlabs/puppetdb/pull/855] * [Pull Request 855 File Diff|https://github.com/puppetlabs/puppetdb/pull/855/files] h2. Pull Request Description Fedora 1... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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 (PDB-450) PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug kbarber commented: @shrug can both this and the other patch just be rebased against 1.5.x? We'll roll it up from there. Add Comment PuppetDB / PDB-450 PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug h2. (pdb-343)(packaging) Remove Fedora 18 from default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 855 Discussion|https://github.com/puppetlabs/puppetdb/pull/855] * [Pull Request 855 File Diff|https://github.com/puppetlabs/puppetdb/pull/855/files] h2. Pull Request Description Fedora 1... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDB-7) Move puppetdb acceptance testing to use vsphere
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-7 Move puppetdb acceptance testing to use vsphere Change By: Kenneth Barber Thecurrentec2acceptancetestingisbothpronetofailureandcomplicatedtosetup.Movingthepuppetdbacceptanceteststousethelocalvsphereinfrastructurewillallowthes3repostepstoberemovedfromthepipeline,whichwillsimplifytheworkflowandwillallowformorestabilityintesting. Furthertothis:thereisstillsomedecisionstobemadeaboutthefutureofEC2/Vsphere,sountilweunderstandwherethecompanyreallywantstogo,we'renotsurewhattodowiththisticket. 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/groups/opt_out.
Jira (PDB-171) Provide documentation for how to debug a crashed or frozen JVM
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-171 Provide documentation for how to debug a crashed or frozen JVM Change By: Kenneth Barber 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/groups/opt_out.
Jira (PDB-182) Document backup and restoration advice
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-182 Document backup and restoration advice Change By: Kenneth Barber 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/groups/opt_out.
Jira (PDB-215) Improve API documentation and examples for submitting commands
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-215 Improve API documentation and examples for submitting commands Change By: Kenneth Barber 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/groups/opt_out.
Jira (PDB-333) Catalog wire format docs state aliases are required for resources
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-333 Catalog wire format docs state aliases are required for resources Change By: Kenneth Barber 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/groups/opt_out.
Jira (PDB-187) Add formal docs for the CLI tools
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-187 Add formal docs for the CLI tools Change By: Kenneth Barber 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/groups/opt_out.
Jira (PDB-444) Convert to using dynamic postgres instances for unit tests
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-444 Convert to using dynamic postgres instances for unit tests Change By: Kenneth Barber Story Points: 3 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/groups/opt_out.
Jira (PDB-380) /reports/hash
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-380 /reports/hash Change By: Kenneth Barber Summary: / repors reports /hash 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/groups/opt_out.
Jira (PDB-198) storeconfigs error caused by unclear documentation
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-198 storeconfigs error caused by unclear documentation Change By: Kenneth Barber 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/groups/opt_out.
Jira (PDB-271) Retire JDK 1.6. in docs
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-271 Retire JDK 1.6. in docs Change By: Kenneth Barber Affects Version/s: 1.6.0 Fix Version/s: 1.6.x Fix Version/s: 2.0.x Summary: Deprecate Retire JDK1.6.indocs 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/groups/opt_out.
Jira (PDB-234) Create v4 API
Title: Message Title Kenneth Barber commented on an issue Re: Create v4 API Okay, the PR is ready to go again: https://github.com/puppetlabs/puppetdb/pull/848 Add Comment PuppetDB / PDB-234 Create v4 API This involves creating the new /v4 end-point ready for new features and major changes. We should probably consider publishing this as /v4-experimental or /experimental/v4 or something like that, so we have some room to modify v4 before we commit to it as stable. This all depends on timing of course, as we may find v4 is read when we ship. Other ideas: ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-308) Drop 2.7.x support for puppetdb-terminus
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-308 Drop 2.7.x support for puppetdb-terminus 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/groups/opt_out.
Jira (PUP-1204) Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008)
Title: Message Title Christophe Fonteyne commented on an issue Re: Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008) I'm experiencing the same problem, however, my puppet master is 3.4.2 running on CentOS 6.5 with ruby 1.8.7 and the client is running 3.2.2 on windows. I started by installing 3.4.2 on windows as well, but this gave me the ssl handshake error. I downgraded to 3.1.1, this was working fine. I then upgraded the client to 3.2.2 and I got the error again. The error is the exact same one: Error: Failed to apply catalog: SSL_connect SYSCALL returned=5 errno=0 state=SSL v2/v3 read server hello A Add Comment Puppet / PUP-1204 Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008) Hello, I am experiencing this issue. Could not retrieve domain: undefined method `gsub' for nil:NilClass Could not retrieve domain: undefined method `gsub' for nil:NilClass Could not retrieve domain: undefined method `gsub' for nil:NilClass Error: Failed to apply catalog: SSL_connect SYSCALL returned=5 errno=0 state=SSL v2/v3 read server hello A... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-343) (packaging) Remove Fedora 18 from default build targets
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-343 (packaging) Remove Fedora 18 from default build targets Change By: Kenneth Barber Fix Version/s: 1.5.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-778) PR (2086): Initial refactoring of yumrepo. - apenney
Title: Message Title gepetto-bot commented on an issue Re: PR (2086): Initial refactoring of yumrepo. - apenney adrienthebo commented: I agree, I'll go though and do the needful shortly. Add Comment Puppet / PUP-778 PR (2086): Initial refactoring of yumrepo. - apenney h2. Initial refactoring of yumrepo. * Author: Ashley Penney ashley.pen...@puppetlabs.com * Company: Puppetlabs * Github ID: [apenney|https://github.com/apenney] * [Pull Request 2086 Discussion|https://github.com/puppetlabs/puppet/pull/2086] * [Pull Request 2086 File Diff|https://github.com/puppetlabs/puppet/pull/2086/files] h2. Pull Request Descr... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1697) hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
Title: Message Title
Dawn Foster commented on an issue
Re: hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
This ticket was mistakenly filed in the bug tracker for our Ask QA Website, so I've moved it to the Puppet project.
Add Comment
Puppet / PUP-1697
hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
The hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode. If a restart of the puppet agent is triggered, the changes are made. {code} Feb 11 11:17:59 node1 puppet-agent[5806]: Finished catalog run in 0.42 seconds Feb 11 11:20:59 node1 puppet-agent[5993]: Finished catalog run in 0.42 seconds Feb 11...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1697) hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
Title: Message Title Dawn Foster moved an issue Puppet / PUP-1697 hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode Change By: Dawn Foster Key: ASK PUP - 21 1697 Project: AskWebsite Puppet 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/groups/opt_out.
Jira (PUP-1670) PR (2347): A way to validate file content syntax before replacing files
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1670 PR (2347): A way to validate file content syntax before replacing files 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/groups/opt_out.
Jira (PUP-1327) PR (2060) owner of files created by nagios resource types
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1327 PR (2060) owner of files created by nagios resource types 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/groups/opt_out.
Jira (FACT-239) Expose different resolution types in DSL
Title: Message Title Kurt Wall updated an issue Facter / FACT-239 Expose different resolution types in DSL Change By: Kurt Wall Assignee: EricSorenson 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/groups/opt_out.
Jira (PUP-1407) PR (2238): puppet CA generates CRL that does not conform to RFC5280
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1407 PR (2238): puppet CA generates CRL that does not conform to RFC5280 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/groups/opt_out.
Jira (PUP-1029) filter function should accept two parameters
Title: Message Title Henrik Lindberg commented on an issue Re: filter function should accept two parameters Apply prints both what is logged as well as the error directly - I also find it very annoying. Add Comment Puppet / PUP-1029 filter function should accept two parameters The filter function should accept two keys for all LHS types; key/value, or index/value to make it consistent with each and map. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1029) filter function should accept two parameters
Title: Message Title Henrik Lindberg commented on an issue Re: filter function should accept two parameters The reason the error messages are different are that the reduce case just passes on what it got to the lambda, the others do their own checking. And it looks like lambda call gets expected and actual backwards. I will fix this by: improving the error messages of all of them (add arg count to all, and descriptive text to reduce) fix the order, and add the word exepected to make it even easier to parse. Add Comment Puppet / PUP-1029 filter function should accept two parameters The filter function should accept two keys for all LHS types; key/value, or index/value to make it consistent with each and map. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1698) speed up search for type/define by using index
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-1698
speed up search for type/define by using index
Issue Type:
Improvement
Assignee:
Unassigned
Created:
14/Feb/14 10:00 AM
Fix Versions:
3.5.0
Priority:
Normal
Reporter:
Henrik Lindberg
The lookup of types must take place before the lookup of user defined resource types. This wastes lots of CPU cycles (described in PUP-1592), especially on the agent.
An idea for fixing this is to index all of the types at the start of the transaction. This way, the lib search path only needs to be traversed once. All subsequent lookups can quickly determine if there exists a file to load by doing a simple hash lookup.
the structure should be:
{ TYPENAME = [ PATH, PATH] }
(the multiple paths just to be complete - the first will always win, but we get it for free with a simple algorithm like this:
search_directories(env).collect do |dir|
Dir[File.join(dir,'/puppet/type/*.rb')]
end.flatten.reduce({}) do |memo,path|
n = File.basename(path, '.rb')
if memo[n]
memo[n] path
else
memo[n] = [path]
end
memo
end
The work that remains
Jira (PUP-1699) Cache environments
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-1699 Cache environments Issue Type: Improvement Assignee: Unassigned Created: 14/Feb/14 10:08 AM Fix Versions: 3.5.0 Priority: Normal Reporter: Henrik Lindberg Currently environments are not cached - each catalog compilation will start from scratch and reparse all puppet manifests and reload types. This can be solved by caching the result. A naive implementation that never evicts anything proved this to have a positive effect, bringing down the execution time to about 50% of the first compilation - and to a level on par, or slightly better than 3.4.2. The task consists of two things: Make tests run - there are many tests that are written in a way that they rely on side effects / order of execution of settings / application of modulepath etc. This will take quite some time to untangle. Cache eviction - while the naive implementation is on par with what 3.4.3 does (its cache does not evict either), we should at least explore if there is a suitable eviction algorithm that can be used (perhaps if the environment's directory does no longer exist)
Jira (PUP-1700) Update Puppet Package Acceptance tests to make use of the new package_build_url parameter for tracing pipeline errors.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-1700 Update Puppet Package Acceptance tests to make use of the new package_build_url parameter for tracing pipeline errors. Issue Type: Task Assignee: Unassigned Created: 14/Feb/14 10:14 AM Priority: Normal Reporter: Joshua Partlow From Moses: 'If you find it useful, you can now accept PACKAGE_BUILD_URL in the acceptance downstream job for easier failure tracking. A chief complaint about the acceptance pipelines is that while the packaging job on jenkins-release triggers the downstream acceptance job on jenkins-foss with with a status param of success or failure, it is a hassle to trace back a failure because of the cross-jenkins workflow. With this change: https://github.com/puppetlabs/packaging/pull/268, the packaging job also sends a param containing the URL of itself, so that in failure, the acceptance job can say upstream packaging job failed, here's the url to that job!' So by modifying the package acceptance jobs to capture this parameter, we can provide a link back to the pipeline failure, and possibly remove the ci:tag_creator task, and the creator.txt artifact. Add Comment
Jira (PUP-1029) filter function should accept two parameters
Title: Message Title Henrik Lindberg commented on an issue Re: filter function should accept two parameters well, actually, it is not backwards - the lambda is called with 2 arguments (memo, and value) but has declared 3 parameters - so the error is that too few args are passed - it really needs a better error messsage. Add Comment Puppet / PUP-1029 filter function should accept two parameters The filter function should accept two keys for all LHS types; key/value, or index/value to make it consistent with each and map. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-333) PR (638): Fetch and unpack cfpropertylist at build time for apple packages - haus
Title: Message Title gepetto-bot created an issue Facter / FACT-333 PR (638): Fetch and unpack cfpropertylist at build time for apple packages - haus Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 14/Feb/14 10:17 AM Labels: github Priority: Normal Reporter: gepetto-bot Fetch and unpack cfpropertylist at build time for apple packages Author: Matthaus Owens mlitte...@gmail.com Company: Puppet Labs Github ID: haus Pull Request 638 Discussion Pull Request 638 File Diff Pull Request Description
Jira (FACT-333) PR (638): Fetch and unpack cfpropertylist at build time for apple packages - haus
Title: Message Title gepetto-bot commented on an issue Re: PR (638): Fetch and unpack cfpropertylist at build time for apple packages - haus Pull request Fetch and unpack cfpropertylist at build time for apple packages has been closed. Add Comment Facter / FACT-333 PR (638): Fetch and unpack cfpropertylist at build time for apple packages - haus h2. Fetch and unpack cfpropertylist at build time for apple packages * Author: Matthaus Owens mlitte...@gmail.com * Company: Puppet Labs * Github ID: [haus|https://github.com/haus] * [Pull Request 638 Discussion|https://github.com/puppetlabs/facter/pull/638] * [Pull Request 638 File Diff|https://github.com/puppetlabs/facter/pull/638/files] h2. Pu... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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 (PDB-461) PR (858): Remove redmine links - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-461 PR (858): Remove redmine links - kbarber Issue Type: Task Assignee: Unassigned Created: 14/Feb/14 10:23 AM Labels: github Priority: Normal Reporter: gepetto-bot Remove redmine links Author: Ken Barber k...@bob.sh Company: Puppetlabs Inc. Github ID: kbarber Pull Request 858 Discussion Pull Request 858 File Diff Pull Request Description There were still links to the redmine tracker in our documentation. This patch removes them and replaces them with the Jira URL instead. Signed-off-by: Ken Barber k...@bob.sh (webhooks-id: de7ac7e32a9d4e43edf8c8d915755268)
Jira (PDB-459) PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-459 PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior Change By: Kenneth Barber Affects Version/s: 2.0.x Affects Version/s: 1.6.0 Affects Version/s: 1.6.2 Fix Version/s: 1.6.x Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group,
Jira (PDB-459) PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior Pull request The order of (keys m) and (vals m) is not guaranteed to be the same has been closed. Add Comment PuppetDB / PDB-459 PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior h2. The order of (keys m) and (vals m) is not guaranteed to be the same * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 857 Discussion|https://github.com/puppetlabs/puppetdb/pull/857] * [Pull Request 857 File Diff|https://github.com/puppetlabs/puppetdb/pull/857/files] h2. Pul... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-1701) No timeout on puppetmaster connections
Title: Message Title Kal McFate created an issue Puppet / PUP-1701 No timeout on puppetmaster connections Issue Type: Bug Affects Versions: 3.3.0 Assignee: Unassigned Created: 14/Feb/14 10:27 AM Environment: Debian Priority: Normal Reporter: Kal McFate I'm dealing with an environment with some networking limitations (read 'silly firewalls') that when puppet is performing its duties, there is no timeout on the connection to the puppet master. This results in a puppet session that never ends, and never cleans up its lock file, preventing any future puppet runs. root 8913 0.0 1.0 176276 86596 ? S Feb09 0:02 puppet agent: applying configurat root 28065 0.0 0.5 110904 42892 ? Ss Feb02 0:10 /usr/bin/ruby /usr/bin/puppet agent puppet 8913 root 4u IPv4 80859330 0t0 TCP server:55565-puppet-master:8140 (ESTABLISHED) The connection has been idle for days and is gone as far as the puppet-master knows. Granted this is poor behavior of the network in between, it should be accounted for.
Jira (PDB-460) PR (119): Adding option to disable management of the firewall - nibalizer
Title: Message Title gepetto-bot commented on an issue Re: PR (119): Adding option to disable management of the firewall - nibalizer nibalizer commented: Fixed. Add Comment PuppetDB / PDB-460 PR (119): Adding option to disable management of the firewall - nibalizer h2. Adding option to disable management of the firewall * Author: Spencer Krum krum.spencer+git...@gmail.com * Company: UTI Worldwide Inc * Github ID: [nibalizer|https://github.com/nibalizer] * [Pull Request 119 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/119] * [Pull Request 119 File Diff|https://github.com/puppetlabs/puppet... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-461) PR (858): Remove redmine links - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (858): Remove redmine links - kbarber pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/245/ Add Comment PuppetDB / PDB-461 PR (858): Remove redmine links - kbarber h2. Remove redmine links * Author: Ken Barber k...@bob.sh * Company: Puppetlabs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 858 Discussion|https://github.com/puppetlabs/puppetdb/pull/858] * [Pull Request 858 File Diff|https://github.com/puppetlabs/puppetdb/pull/858/files] h2. Pull Request Description There were sti... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options,
Jira (PUP-1704) PR (2358): (maint) Revise docs for evaluator setting - nfagerlund
Title: Message Title gepetto-bot created an issue Puppet / PUP-1704 PR (2358): (maint) Revise docs for evaluator setting - nfagerlund Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 14/Feb/14 11:34 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Revise docs for evaluator setting Author: Nick Fagerlund Company: Github ID: nfagerlund Pull Request 2358 Discussion Pull Request 2358 File Diff Pull Request Description (webhooks-id:
Jira (PUP-1707) Faces help sometimes blows up when descriptions are absent
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-1707 Faces help sometimes blows up when descriptions are absent Issue Type: Bug Assignee: Nicholas Fagerlund Created: 14/Feb/14 12:01 PM Fix Versions: 3.5.0 Priority: Normal Reporter: Nicholas Fagerlund Right now, puppet man config will explode, because there's no description for the --section option. This isn't the intended behavior; it should devolve gracefully to the summary if the description is missing. We're navely doing gsub on a value that might be nil. Add Comment This message was
Jira (FACT-334) PR (640): (maint) Return the empty string on exec error - adrienthebo
Title: Message Title gepetto-bot created an issue Facter / FACT-334 PR (640): (maint) Return the empty string on exec error - adrienthebo Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 14/Feb/14 12:23 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Return the empty string on exec error Author: Adrien Thebo git+git...@somethingsinistral.net Company: Puppet Labs Github ID: adrienthebo Pull Request 640 Discussion Pull Request 640 File Diff Pull Request Description Commit
Jira (FACT-334) PR (640): (maint) Return the empty string on exec error - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (640): (maint) Return the empty string on exec error - adrienthebo Pull request (maint) Return the empty string on exec error has been closed. Add Comment Facter / FACT-334 PR (640): (maint) Return the empty string on exec error - adrienthebo h2. (maint) Return the empty string on exec error * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 640 Discussion|https://github.com/puppetlabs/facter/pull/640] * [Pull Request 640 File Diff|https://github.com/puppetlabs/facter/pull/640/files] ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1200) [meta] please stop arbitrarily changing systemd service unit names
Title: Message Title
John Florian commented on an issue
Re: [meta] please stop arbitrarily changing systemd service unit names
This is most frustrating. Can somebody here please post the specific change points? I unfortunately have to support clients that may not get updated (for change control reasons). This constant, silly renaming is nothing but grief. Historical consistency would have been to never change it and if it did get changed and released to leave the problem alone and not make it worse as was done. These types of things shouldn't be changing without extremely good justification. Every time this sort of thing happens, puppet looses some of its value in reducing burden.
Presently, I'm now operating with the following, but I'm guessing somewhat at the boundaries here:
if versioncmp($puppetversion, '3.1') 0 or
versioncmp($puppetversion, '3.4.0') = 0 {
$client_service_name = 'puppet'
} else {
$client_service_name = 'puppetagent'
}
Add Comment
Puppet / PUP-1200
[meta] please stop arbitrarily changing systemd service unit names
In 3.4, what was previously puppetagent.service is now puppet.service. Now every person who was managing the puppet service and used systemd has to add a case statement based on version. I understand that puppet is a better (and more consistent) name, but the change seems unfounded. Instead of fixing any problem it just introduces yet another complexity i...
Jira (PUP-751) Measure stat() calls
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-751 Measure stat() calls Change By: Henrik Lindberg Assignee: HenrikLindberg 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/groups/opt_out.
Jira (PUP-751) Measure stat() calls
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-751 Measure stat() calls Change By: Henrik Lindberg Assignee: HenrikLindberg AaronArmstrong 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/groups/opt_out.
Jira (PUP-751) Measure stat() calls
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-751 Measure stat() calls Change By: Henrik Lindberg Assignee: AaronArmstrong HenrikLindberg 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/groups/opt_out.
Jira (PUP-751) Measure stat() calls
Title: Message Title Henrik Lindberg commented on an issue Re: Measure stat() calls Merged 731d10a Add Comment Puppet / PUP-751 Measure stat() calls Better understanding of wasted filesystem access This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-751) Measure stat() calls
Title: Message Title Andrew Parker commented on an issue Re: Measure stat() calls Merged PR-2341, which contained all of the changes, into master in 731d10 Add Comment Puppet / PUP-751 Measure stat() calls Better understanding of wasted filesystem access This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1029) filter function should accept two parameters
Title: Message Title
Henrik Lindberg commented on an issue
Re: filter function should accept two parameters
Now the output is:
puppet apply --parser future -e \$foo = [1,2,3]; notice \$foo.each | | { 'yep' }
Error: Evaluation Error: Error while evaluating a Method call, each(): block must define at least one parameter; value. Block has 0. at line 1:28 on node henriks-macbook-pro.local
puppet apply --parser future -e \$foo = [1,2,3]; notice \$foo.each | \$i, \$j, \$k | { 'yep' }
Error: Evaluation Error: Error while evaluating a Method call, each(): block must define at most two parameters; index, value. Block has 3; i, j, k at line 1:28 on
node henriks-macbook-pro.local
puppet apply --parser future -e \$foo = [1,2,3]; notice \$foo.reduce | | { 'yep' }
Error: Evaluation Error: Error while evaluating a Method call, reduce(): block must define 2 parameters; memo, value. Block has 0; at line 1:28 on node henriks-macbook-pro.local
puppet apply --parser future -e \$foo = [1,2,3]; notice \$foo.reduce | \$i, \$j, \$k | { 'yep' }
Error: Evaluation Error: Error while evaluating a Method call, reduce(): block must define 2 parameters; memo, value. Block has 3; i, j, k at line 1:28 on node henriks-macbook-pro.local
Add Comment
Puppet / PUP-1029
filter function should accept two parameters
The filter function should accept two keys for all LHS types; key/value, or index/value to make it consistent with each and map.
Jira (PUP-1704) PR (2358): (maint) Revise docs for evaluator setting - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (2358): (maint) Revise docs for evaluator setting - nfagerlund Pull request (maint) Revise docs for evaluator setting has been closed. Add Comment Puppet / PUP-1704 PR (2358): (maint) Revise docs for evaluator setting - nfagerlund h2. (maint) Revise docs for evaluator setting * Author: Nick Fagerlund * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 2358 Discussion|https://github.com/puppetlabs/puppet/pull/2358] * [Pull Request 2358 File Diff|https://github.com/puppetlabs/puppet/pull/2358/files] h2. Pull Request Description (... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1158) PR (2061) Augeas provider warns on parse errors in other files handled by same lens
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-1158 PR (2061) Augeas provider warns on parse errors in other files handled by same lens Change By: Andrew Parker Assignee: AndrewParker 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/groups/opt_out.
Jira (PUP-648) PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx
Title: Message Title Peter Huene assigned an issue to Unassigned Puppet / PUP-648 PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx Change By: Peter Huene Assignee: PeterHuene 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/groups/opt_out.
Jira (FACT-322) Remove special casing of the empty string
Title: Message Title Peter Huene assigned an issue to Unassigned Facter / FACT-322 Remove special casing of the empty string Change By: Peter Huene Assignee: PeterHuene 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/groups/opt_out.
Jira (PUP-1029) filter function should accept two parameters
Title: Message Title Henrik Lindberg commented on an issue Re: filter function should accept two parameters Since that takes care of the comments that made this fail review, I am moving this to done. Add Comment Puppet / PUP-1029 filter function should accept two parameters The filter function should accept two keys for all LHS types; key/value, or index/value to make it consistent with each and map. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1029) filter function should accept two parameters
Title: Message Title Henrik Lindberg commented on an issue Re: filter function should accept two parameters Merged 502a0c81141aed082818e49c2049f4d3f71e06a0 Add Comment Puppet / PUP-1029 filter function should accept two parameters The filter function should accept two keys for all LHS types; key/value, or index/value to make it consistent with each and map. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-322) Remove special casing of the empty string
Title: Message Title Peter Huene commented on an issue Re: Remove special casing of the empty string Leaving in Ready for CI as there's currently a facter acceptance test failure. Add Comment Facter / FACT-322 Remove special casing of the empty string In Facter 1 the only meaningful data type was the string and empty strings were converted to nil. This behavior was mainly due to the behavior of command execution - it was assumed that if a command didn't return anything on stdout then the value should be considered nil. Since Facter derives a lot of information from commands this use case was optimized ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-322) Remove special casing of the empty string
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-322 Remove special casing of the empty string Change By: Peter Huene Assignee: PeterHuene 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/groups/opt_out.
Jira (PDB-461) PR (858): Remove redmine links - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (858): Remove redmine links - kbarber puppetcla commented: CLA signed by all contributors. Add Comment PuppetDB / PDB-461 PR (858): Remove redmine links - kbarber h2. Remove redmine links * Author: Ken Barber k...@bob.sh * Company: Puppetlabs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 858 Discussion|https://github.com/puppetlabs/puppetdb/pull/858] * [Pull Request 858 File Diff|https://github.com/puppetlabs/puppetdb/pull/858/files] h2. Pull Request Description There were sti... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title
Trevor Vaughan created an issue
Hiera / HI-183
Really need the ability to lookup hashes and arrays from other parts of Hiera.
Issue Type:
Improvement
Affects Versions:
1.3.1
Assignee:
Adrien Thebo
Components:
Community
Created:
14/Feb/14 2:45 PM
Environment:
ALL
Labels:
redmine
Priority:
Normal
Reporter:
Trevor Vaughan
So, back in the old Redmine system, there was feature #23302, which needed to be able to look up hashes and arrays from other parts of Hiera.
I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs.
For instance, consider this scenario:
== hiera.yaml == % {module_name}
Jira (PUP-1708) PR (2361): (maint) Improve Puppet::Util::Docs.scrub's handling of one-liners - nfagerlund
Title: Message Title gepetto-bot created an issue Puppet / PUP-1708 PR (2361): (maint) Improve Puppet::Util::Docs.scrub's handling of one-liners - nfagerlund Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 14/Feb/14 3:53 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Improve Puppet::Util::Docs.scrub's handling of one-liners Author: Nick Fagerlund Company: Github ID: nfagerlund Pull Request 2361 Discussion Pull Request 2361 File Diff Pull Request Description One-liner
Jira (HI-184) Inconsistent handling of fully-qualified facts when called from the command line
Title: Message Title
Justin Holguin created an issue
Hiera / HI-184
Inconsistent handling of fully-qualified facts when called from the command line
Issue Type:
Bug
Affects Versions:
1.3.0
Assignee:
Unassigned
Created:
14/Feb/14 3:59 PM
Priority:
Normal
Reporter:
Justin Holguin
Assuming you have something like this in hiera.yaml:
:hierarchy:
- osfamily/%{::osfamily}
You can call hiera from the command line with ::osfamily=redhat and it will do lookups in osfamily/redhat.yaml, as expected. But nobody wants to give hiera every single fact one at a time, so the docs suggest doing something like this:
sudo facter -y facts.yaml
hiera LOOKUP -y facts.yaml
Understandably, facter's output doesn't include all the leading ::'s, so you can never match %{::fact_name} like this. Since that seems to be the preferred way to refer to facts in hiera, that notation should be able to coexist with using facter's output on the command line.
Jira (PUP-897) package type should accept virtual package for rpm
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP-897 package type should accept virtual package for rpm Change By: Peter Huene Assignee: PeterHuene 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/groups/opt_out.
Jira (FACT-322) Remove special casing of the empty string
Title: Message Title Peter Huene updated an issue Facter / FACT-322 Remove special casing of the empty string Change By: Peter Huene Assignee: PeterHuene 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/groups/opt_out.
Jira (PUP-1282) puppet gem does not include platform specific gem dependencies
Title: Message Title Joshua Cooper commented on an issue Re: puppet gem does not include platform specific gem dependencies To verify this issue, I did the following. I setup a stickler server on my mac: $ gem install stickler Successfully installed stickler-2.4.0 1 gem installed $ stickler config --add --server http://localhost:6789 --upstream https://rubygems.org --debug server : http://localhost:6789 upstream : https://rubygems.org 0 ~/work/puppet (master) $ mkdir ~/stickler 0 ~/work/puppet (master) $ stickler-server start ~/stickler Thin web server (v1.6.1 codename Death Proof) Maximum connections set to 1024 Listening on 0.0.0.0:6789, CTRL+C to stop Then I pushed generic and platform specific puppet gems to it: 0 ~/work/puppet/pkg (master) $ stickler push puppet-3.4.2.862.gem Pushing gem(s) to http://localhost:6789/ ... /Users/josh/work/puppet/pkg/puppet-3.4.2.862.gem - OK http://localhost:6789/gems/puppet-3.4.2.862.gem 0 ~/work/puppet/pkg (master) $ stickler push puppet-3.4.2.862-x86-mingw32.gem Pushing gem(s) to http://localhost:6789/ ... /Users/josh/work/puppet/pkg/puppet-3.4.2.862-x86-mingw32.gem - OK http://localhost:6789/gems/puppet-3.4.2.862-x86-mingw32.gem Then on Windows, I created a module with a Gemfile containing: source http://arcturus.local:6789 source https://rubygems.org gem 'puppet' And did bundle install: C:\work\modules\joshcooper-eventlogbundle install --path .bundle\gems Fetching gem metadata from http://arcturus.local:6789/. Fetching full source index from http://arcturus.local:6789/ Fetching gem metadata from https://rubygems.org/.. Fetching gem metadata from https://rubygems.org/... Installing facter (1.7.5) Installing ffi (1.9.0) Installing json_pure (1.8.1) Installing hiera (1.3.1) Installing minitar (0.5.4) Installing rgen (0.6.6) Installing win32-api (1.4.8) Installing windows-api (0.4.2) Installing windows-pr (1.2.2) Installing win32-security (0.1.4) Installing sys-admin (1.5.6) Installing win32-dir (0.4.6) Installing win32-eventlog (0.5.3) Installing win32-process (0.6.6) Installing win32-service (0.7.2) Installing win32-taskscheduler (0.2.2) Installing win32console (1.3.2) Installing puppet (3.4.2.862) Using bundler (1.2.4) Your bundle is complete! It was installed into ./.bundle/gems And the correct platform dependencies get pulled in: C:\work\modules\joshcooper-eventlogbundle exec gem list *** LOCAL GEMS *** bundler (1.2.4) facter (1.7.5) ffi (1.9.0 x86-mingw32) hiera (1.3.1) json_pure (1.8.1) minitar (0.5.4) puppet (3.4.2.862 x86-mingw32) rgen (0.6.6) sys-admin (1.5.6 x86-mingw32) win32-api
Jira (PUP-1709) The `puppet resource' command doesn't have a man page
Title: Message Title Christopher Nielsen created an issue Puppet / PUP-1709 The `puppet resource' command doesn't have a man page Issue Type: Improvement Affects Versions: 3.4.2 Assignee: Eric Sorenson Components: UX Created: 14/Feb/14 4:37 PM Environment: CentOS installed from the Puppetlabs repo Priority: Normal Reporter: Christopher Nielsen The resource face to the puppet command line tool doesn't seem to have a man page. Example: http://docs.puppetlabs.com/references/latest/man/resource.html It would be pretty nice, if there were some options to use or the syntax were explained a little bit. We know it from memory, but sometimes we look for new options, and a description of how the success or failure will affect the exit code. Thanks very much, -Chris
Jira (PUP-1709) The `puppet resource' command doesn't have a man page
Title: Message Title Christopher Nielsen updated an issue Puppet / PUP-1709 The `puppet resource' command doesn't have a man page Change By: Christopher Nielsen Theresourcefacetothepuppetcommandlinetooldoesn'tseemtohaveamanpage.Example:http://docs.puppetlabs.com/references/latest/man/resource.htmlItwouldbeprettynice,ifthereweresomeoptions touse listed, orthesyntaxwereexplainedalittlebit.Weknowitfrommemory,butsometimeswelookfornewoptions,andadescriptionofhowthesuccessorfailurewillaffecttheexitcode.Thanksverymuch,-Chris 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/groups/opt_out.
Jira (PUP-1158) PR (2061) Augeas provider warns on parse errors in other files handled by same lens
Title: Message Title Andrew Parker assigned an issue to Unassigned Puppet / PUP-1158 PR (2061) Augeas provider warns on parse errors in other files handled by same lens Change By: Andrew Parker Assignee: AndrewParker 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/groups/opt_out.
Jira (PUP-1158) PR (2061) Augeas provider warns on parse errors in other files handled by same lens
Title: Message Title Andrew Parker commented on an issue Re: PR (2061) Augeas provider warns on parse errors in other files handled by same lens Confirmed on Centos6 that if another file handled by the same lens (only seems to happen for the files configured for that lens, not if a lens is set on the resource) causes a spurious warning on 3.4.2. The debug output shows the errors in the file that isn't being managed. The patched code no longer shows the warning when an unmanaged file is unparseable, but it does show the warning, as expected, if the managed file has an error. Add Comment Puppet / PUP-1158 PR (2061) Augeas provider warns on parse errors in other files handled by same lens Greetings, we are evaluating Puppet 3.0. At the moment we are getting errors from the augeas provider: Warning: Augeas[xx](provider=augeas): Loading failed for one or more files, see debug for /augeas//error output $ rpm -qa|grep puppet puppet-server-3.0.1-1.el6.noarch puppet-3.0.1-1.el6.noarch puppetdb-terminus-1.0.2-1.el6.noarch puppet-da... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received
Jira (PUP-1710) PR (2362): (maint) Revise help for puppet config, plus two minor doc commits - nfagerlund
Title: Message Title gepetto-bot created an issue Puppet / PUP-1710 PR (2362): (maint) Revise help for puppet config, plus two minor doc commits - nfagerlund Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 14/Feb/14 5:27 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Revise help for puppet config, plus two minor doc commits Author: Nick Fagerlund Company: Github ID: nfagerlund Pull Request 2362 Discussion Pull Request 2362 File Diff Pull Request Description
Jira (PDB-460) PR (119): Adding option to disable management of the firewall - nibalizer
Title: Message Title gepetto-bot commented on an issue Re: PR (119): Adding option to disable management of the firewall - nibalizer kbarber-jenkins2 commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-460 PR (119): Adding option to disable management of the firewall - nibalizer h2. Adding option to disable management of the firewall * Author: Spencer Krum krum.spencer+git...@gmail.com * Company: UTI Worldwide Inc * Github ID: [nibalizer|https://github.com/nibalizer] * [Pull Request 119 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/119] * [Pull Request 119 File Diff|https://github.com/puppetlabs/puppet... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1699) Cache environments
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1699 Cache environments Change By: Andrew Parker Currently ,thenewdirectory environmentsarenotcached-eachcatalogcompilationwillstartfromscratchandreparseallpuppetmanifestsandreloadtypes.Thiscanbesolvedbycachingtheresult.Anaiveimplementationthatneverevictsanythingprovedthistohaveapositiveeffect,bringingdowntheexecutiontimetoabout50%ofthefirstcompilation-andtoalevelonpar,orslightlybetterthan3.4.2.Thetaskconsistsoftwothings:*Maketestsrun-therearemanyteststhatarewritteninawaythattheyrelyonsideeffects/orderofexecutionofsettings/applicationofmodulepathetc.Thiswilltakequitesometimetountangle.*Cacheeviction-whilethenaiveimplementationisonparwithwhat3.4.3does(itscachedoesnotevicteither),weshouldatleastexploreifthereisasuitableevictionalgorithmthatcanbeused(perhapsiftheenvironment'sdirectorydoesnolongerexist) 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/groups/opt_out.
Jira (PUP-1687) PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1687 PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne Change By: Andrew Parker Fix Version/s: 3.4.3 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/groups/opt_out.
Jira (PUP-1687) PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne
Title: Message Title Andrew Parker commented on an issue Re: PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne Merged into stable in 8e2dfd Add Comment Puppet / PUP-1687 PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne h2. Revert Add initial support for building in a RHEL 7 mock * Author: Melissa * Company: * Github ID: [melissaanne|https://github.com/melissaanne] * [Pull Request 2353 Discussion|https://github.com/puppetlabs/puppet/pull/2353] * [Pull Request 2353 File Diff|https://github.com/puppetlabs/puppet/pull/2353/files] h2. Pull Request Description --... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1684) Mark some facts immutable
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1684 Mark some facts immutable Change By: Andrew Parker Assignee: EricSorenson 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/groups/opt_out.
Jira (PUP-404) Apple fix for half-applied changes possibly due to git pull in the middle of puppet parsing manifests (or looking up hiera).
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-404 Apple fix for half-applied changes possibly due to git pull in the middle of puppet parsing manifests (or looking up hiera). Change By: Andrew Parker Assignee: AndrewParker 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/groups/opt_out.
Jira (PUP-406) Deprecate stringify_fact = true
Title: Message Title Andrew Parker updated an issue Puppet / PUP-406 Deprecate stringify_fact = true Change By: Andrew Parker Assignee: KyloGinsberg 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/groups/opt_out.
Jira (PUP-406) Deprecate stringify_fact = true
Title: Message Title Andrew Parker commented on an issue Re: Deprecate stringify_fact = true Should this be deprecated in 4 or should this happen in 3.6? Since Facter 2 is going out soon, it seems like deprecating this in 3.6 might be something to push forward on structured facts more quickly. Add Comment Puppet / PUP-406 Deprecate stringify_fact = true Erik Dalen's patch that allows turning off the stringification of facts by puppet opens the door to structured facts. In 3.x that settings was to still stringify by default, in 4.0.0 it needs to be changed to *not* stringify by default and to issue a deprecation warning when it is set to stringify. The reason for the deprecation and not complete removal ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-436) httplog and masterhttplog can be created with incorrect permissions when using WEBrick
Title: Message Title Andrew Parker updated an issue Puppet / PUP-436 httplog and masterhttplog can be created with incorrect permissions when using WEBrick Change By: Andrew Parker Assignee: EricSorenson 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/groups/opt_out.
Jira (PUP-142) Using the ENC with multiple environments can load classes that can't be reloaded during a reparse of manifests
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-142 Using the ENC with multiple environments can load classes that can't be reloaded during a reparse of manifests Change By: Andrew Parker Assignee: AndrewParker 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/groups/opt_out.
Jira (PUP-28) Add heredoc support in future parser
Title: Message Title Andrew Parker updated an issue Puppet / PUP-28 Add heredoc support in future parser Change By: Andrew Parker Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-438) reportdir gets permissions of root owner when running puppet apply
Title: Message Title Andrew Parker updated an issue Puppet / PUP-438 reportdir gets permissions of root owner when running puppet apply Change By: Andrew Parker Assignee: EricSorenson 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/groups/opt_out.
Jira (PUP-30) Support Puppet Templates
Title: Message Title Andrew Parker updated an issue Puppet / PUP-30 Support Puppet Templates Change By: Andrew Parker Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-30) Support Puppet Templates
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-30 Support Puppet Templates Change By: Andrew Parker Assignee: EricSorenson AndrewParker 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/groups/opt_out.
Jira (PUP-144) Canonized type names and resource titles can only be looked up by creating a Puppet::Resource
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-144 Canonized type names and resource titles can only be looked up by creating a Puppet::Resource Change By: Andrew Parker Assignee: AndrewParker 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/groups/opt_out.
Jira (PUP-458) Need consistent reporting when experimental features are enabled
Title: Message Title Andrew Parker updated an issue Puppet / PUP-458 Need consistent reporting when experimental features are enabled Change By: Andrew Parker Assignee: EricSorenson 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/groups/opt_out.
Jira (PUP-280) Variables outside of class definition in module does not produce error when running puppet apply
Title: Message Title
Andrew Parker updated an issue
Puppet / PUP-280
Variables outside of class definition in module does not produce error when running puppet apply
Change By:
Andrew Parker
{noformat}$ var1='een' classelvis{ $var1='one' $var2='two' $var3='three' file{'/tmp/ff': ensure=file, content=${::var1}${var2}\n, } } {noformat} thecontentis:two.Sincethisisnotarecommendedplacetodeclareavariableweshouldideallygenerateawarningwhenauseristryingtodothis.
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/groups/opt_out.
Jira (PUP-280) Variables outside of class definition in module does not produce error when running puppet apply
Title: Message Title Andrew Parker updated an issue Puppet / PUP-280 Variables outside of class definition in module does not produce error when running puppet apply Change By: Andrew Parker Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-280) Variables outside of class definition in module does not produce error when running puppet apply
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-280 Variables outside of class definition in module does not produce error when running puppet apply Change By: Andrew Parker Assignee: AndrewParker 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/groups/opt_out.
Jira (PUP-643) Solaris pkg package provider does not handle expiring certificates
Title: Message Title Andrew Parker updated an issue Puppet / PUP-643 Solaris pkg package provider does not handle expiring certificates Change By: Andrew Parker Assignee: KyloGinsberg 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/groups/opt_out.
