Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Joshua Chaitin-Pollak commented on an issue Re: Invalid parameter provider for custom types/providers You didn't tag me, but I can confirm our postmaster has a default configuration of the puppet environment, but is configured to serve one of two different puppet libraries based on parameters of the connected client. In other words, I believe out puppet master executes with a different set of puppet modules than it serves to clients, which I think is what people say causes this situation. Add Comment Puppet / PUP-1515 Invalid parameter provider for custom types/providers In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe
Jira (PUP-1739) Upgrade version of Ruby (some platforms ship 1.8.
Title: Message Title Jose Palafox created an issue Puppet / PUP-1739 Upgrade version of Ruby (some platforms ship 1.8. Issue Type: Improvement Assignee: Unassigned Created: 19/Feb/14 6:34 PM Priority: Normal Reporter: Jose Palafox Some platforms come with Puppet 1.8. This is causing some issues because 1.8 can't interact with F5's REST API. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received th
Jira (HI-194) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages Passed same tests on debian squeeze and wheezy. Add Comment Hiera / HI-194 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1600) puppet node doesn't retrieve the environment params
Title: Message Title
Eric Sorenson commented on an issue
Re: puppet node doesn't retrieve the environment params
Setting $environment as a top-scope parameter does not set the Puppet environment. Setting the Puppet environment is not supported in dashboard, as I understand it. There's a workaround using a module, check out https://projects.puppetlabs.com/issues/21902 for more detail.
Add Comment
Puppet / PUP-1600
puppet node doesn't retrieve the environment params
Hi, According to http://docs.puppetlabs.com/guides/environment.html, I have defined a variable environment in my puppet dashboard. {code} # /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 /usr/share/puppet-dashboard/bin/external_node mynode --- name: mynode parameters: ... environment: beta ... {code} I have configure my master : ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups
Jira (HI-194) Smoke test packages
Title: Message Title Andrew Parker assigned an issue to Joshua Partlow Hiera / HI-194 Smoke test packages Change By: Andrew Parker Assignee: Andrew Parker Joshua Partlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-194) Smoke test packages
Title: Message Title Andrew Parker commented on an issue Re: Smoke test packages Ubuntu 12 looks good. Installed packaged, ran hiera --version, put a global.json and a defaults.yaml data file in /var/lib/hiera (default location), modified /etc/hiera.yaml to include the json backend (changed nothing else). Lookups of both the yaml and json data worked just fine. Add Comment Hiera / HI-194 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-194) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages Testing debian6/7 Add Comment Hiera / HI-194 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-194) Smoke test packages
Title: Message Title Andrew Parker commented on an issue Re: Smoke test packages testing ubuntu 12 Add Comment Hiera / HI-194 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-142) puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS)
Title: Message Title Rob Braden assigned an issue to Rob Braden PuppetDB / PDB-142 puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS) Change By: Rob Braden Assignee: Rob Braden 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-142) puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS)
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-142 puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS) Change By: Kenneth Barber Labels: redmine trivial 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-142) puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS)
Title: Message Title Kenneth Barber commented on an issue Re: puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS) I just noticed PDB-468 actually makes in-roads to fixing this very issue. We probably just need to add JAVA_ARGS to the command line call instead of the templated version once PDB-468 is merged. Add Comment PuppetDB / PDB-142 puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS) A user on IRC reported that when running puppetdb-foreground, it fell back to the default heap size of 192M even though he'd configured the heap to 4G in the puppetdb system defaults. We should verify this, and see how hard it would be to make the script respect the user's settings--it's far less useful of a tool if it doesn't do that. :) This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For mo
Jira (PDB-142) puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS)
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-142 puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS) Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Eric Sorenson commented on an issue Re: Invalid parameter provider for custom types/providers Net Kgk Alejandro Figueroa i am having trouble reproducing this issue. is it true in your case that, as Andy Shinn said on the redmine bug "my default environment for the puppetmaster doesn’t have some new types I am testing in another environment and when testing that environment it is failing." ?? Add Comment Puppet / PUP-1515 Invalid parameter provider for custom types/providers In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send emai
Jira (PUP-1656) Merge into pe branch
Title: Message Title Melissa Stone commented on an issue Re: Merge into pe branch Since this is such a big merge, I figured I'd make it into a PR, just to make sure nothing is getting in that shouldn't Add Comment Puppet / PUP-1656 Merge into pe branch This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1656) Merge into pe branch
Title: Message Title Melissa Stone commented on an issue Re: Merge into pe branch as per Dom, I'm going ahead and merging this tag into the pe-hiera 3.3.x branch Add Comment Puppet / PUP-1656 Merge into pe branch This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Felix Frank commented on an issue Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments +1 about the gem topic being a thread of its own. As far as I'm concerned, the meat of this here ticket is summerized in this comment: http://projects.puppetlabs.com/issues/12173#note-8 Add Comment Puppet / PUP-731 Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Quoted from a previous ticket, #4409 The key problem is that a master can’t reliably distinguish between two versions of the same native type that are used in different environments (or between an environment which uses a native type and an environment which doesn’t). This is due to the fact that native types are defined using ruby code, which the mast... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsu
Jira (PUP-1270) PR (2200) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1270 PR (2200) 'pkg' package provider does not understand IPS package versions properly Change By: Michelle Johansen Sprint: Week 2014-1-29 to 2014-2-05, Week 2014-2-5 to 2014-2-12 , Week 2014-2-19 to 2014-2-26 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-847) Manage security descriptor owner & group
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-847 Manage security descriptor owner & group Change By: Michelle Johansen Sprint: Week 2014-2-19 to 2014-2-26 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-1656) Merge into pe branch
Title: Message Title Melissa Stone commented on an issue Re: Merge into pe branch Dominic Maraglia, Andrew Parker, Joshua Cooper, the 3.4.3 tag looks like it shouldn't get merged into pe-puppet 3.2.x, since Josh already merged stable. Should I still merge this release into the pe-puppet 3.3.x branch? Add Comment Puppet / PUP-1656 Merge into pe branch This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-848) Manage security descriptor protected field
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-848 Manage security descriptor protected field Change By: Michelle Johansen Sprint: Week 2014-2-19 to 2014-2-26 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 Kurt Wall updated an issue Facter / FACT-322 Remove special casing of the empty string Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-465) Add Trusty (Ubuntu 14.04) Support
Title: Message Title Kenneth Barber commented on an issue Re: Add Trusty (Ubuntu 14.04) Support We'll need an Ubuntu 14.04 image for EC2 before this can be done. Melissa Stone, I presume this ticket tracks the packaging work, do we need another to track this image creation and acceptance test work? Add Comment PuppetDB / PDB-465 Add Trusty (Ubuntu 14.04) Support This involves adding/updating spen and acceptance tests for trusty, and making sure the build_defaults has been updated accordingly This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-466) Scope 2.0 epics Round 3 - Reporting and Structured Facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-466 Scope 2.0 epics Round 3 - Reporting and Structured Facts Change By: Kenneth Barber Spend time scoping and creating tickets for the epics 'Reporting' and 'Structured Facts'. 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-136) Support for Oracle backend
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-136 Support for Oracle backend Change By: Kenneth Barber Story Points: 30 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-130) Provide human-friendly message if the infile specified to import/anonymzie doesn't exist
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-130 Provide human-friendly message if the infile specified to import/anonymzie doesn't exist Change By: Kenneth Barber Story Points: 1 Affects Version/s: 1.5.0 Affects Version/s: 1.6.2 Labels: redmine trivial 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-130) Provide human-friendly message if the infile specified to import/anonymzie doesn't exist
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-130 Provide human-friendly message if the infile specified to import/anonymzie doesn't exist Change By: Kenneth Barber Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1571) Checksumfile /var/lib/puppet/state/state.yaml is corrupt
Title: Message Title
Eric Sorenson commented on an issue
Re: Checksumfile /var/lib/puppet/state/state.yaml is corrupt
Daniel – if you delete the corrupted file, does it get re-created successfully? I have heard of problems writing state if something interrupts the process or puppet runs into a disk-full condition.
Add Comment
Puppet / PUP-1571
Checksumfile /var/lib/puppet/state/state.yaml is corrupt
I am doing a simple puppet agent run using: {{puppet agent --test}} on a Debian Wheezy with puppet packages coming from puppetlabs apt repositories. Every time I run puppet it yields me the following error: {noformat} Error: Checksumfile /var/lib/puppet/state/state.yaml is corrupt ((/var/lib/puppet/state/state.yaml): could not find expected ':' while s...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet
Jira (PUP-1571) Checksumfile /var/lib/puppet/state/state.yaml is corrupt
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1571 Checksumfile /var/lib/puppet/state/state.yaml is corrupt Change By: Eric Sorenson Assignee: Eric Sorenson Daniel Taschik 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-852) Create acl defined type
Title: Message Title Rob Reynolds commented on an issue Re: Create acl defined type Joshua Cooper do you think we can just close this one as it was a hold over when the type was a bit more complicated? Add Comment Puppet / PUP-852 Create acl defined type We will likely want to create a defined type to manage the collection of security related settings. Not entirely sure this is necessary, but it seemed helpful in the case of the registry, and that was of similar complexity. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1652) Go/no-go meeting
Title: Message Title Melissa Stone commented on an issue Re: Go/no-go meeting (thumbsup) from Joshua Cooper, Eric Sorenson, Andrew Parker, and Kylo Ginsberg Add Comment Puppet / PUP-1652 Go/no-go meeting This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1737) Manage acl permissions on Windows
Title: Message Title Rob Reynolds created an issue Puppet / PUP-1737 Manage acl permissions on Windows Issue Type: New Feature Assignee: Rob Reynolds Created: 19/Feb/14 11:59 AM Fix Versions: M Labels: windows Priority: Normal Reporter: Rob Reynolds Manage setting permissions against a resource Add Comment
Jira (PUP-852) Create acl defined type
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-852 Create acl defined type Change By: Rob Reynolds Summary: Manage permissions Create acl defined type 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-852) Manage permissions
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-852 Manage permissions Change By: Rob Reynolds Summary: Create acl defined type Manage permissions 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 (HI-196) Docs pushed
Title: Message Title Justin Holguin assigned an issue to Justin Holguin Hiera / HI-196 Docs pushed Change By: Justin Holguin Assignee: Justin Holguin 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-844) Create basic acl type
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-844 Create basic acl type Change By: Rob Reynolds Create an acl type. It should support basic functionality for describing the desired state of a file/dir in terms of what users are allowed access to the resource. More complex cases should be handled later (protected vs not, inheritance, etc). Type also does autorequire of files and users 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-468) Update scripts to leverage JAVA_BIN
Title: Message Title Rob Braden assigned an issue to Rob Braden PuppetDB / PDB-468 Update scripts to leverage JAVA_BIN Change By: Rob Braden Assignee: Rob Braden 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-845) Create a windows provider
Title: Message Title Rob Reynolds commented on an issue Re: Create a windows provider The above issue has been resolved. I was missing FILE_ALL_ACCESS as a check for full permissions. Add Comment Puppet / PUP-845 Create a windows provider Create a basic (empty) windows provider that is only suitable on windows. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1668) Redmine Pages need pointers to JIRA
Title: Message Title Eric Sorenson commented on an issue Re: Redmine Pages need pointers to JIRA I feel like the top-line banner is probably better because there's no telling which page Google will direct people to. We can/should also clean up the dead projects but I see that as a separate and less important problem than causing people to click around on search, wiki, etc until they land somewhere with a jira banner. Add Comment Puppet / PUP-1668 Redmine Pages need pointers to JIRA Given that most people solve problems via Google, and the current first hits for google with the search 'puppet bug report' goto the old Redmine site, it would be very helpful if the redmine site could have a notation somewhere ( header perhaps ) that lets users know the site is depreciated and please go use the new Jira site. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send e
Jira (PUP-1651) Smoke test packages
Title: Message Title Joshua Cooper commented on an issue Re: Smoke test packages 2008r2 passed windows 8 passed Add Comment Puppet / PUP-1651 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1736) Add encoding information to debug output
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-1736 Add encoding information to debug output Issue Type: Improvement Assignee: Charlie Sharpsteen Created: 19/Feb/14 11:12 AM Priority: Normal Reporter: Charlie Sharpsteen Lots of Puppet encoding issues are sensitive to the locale settings that the Ruby process happens to be using. Investigating encoding issues frequently involves patching Puppet so that encoding info is printed out. This info should be added to the standard --debug output — preferably somewhere prominent. Printing out the value of Encoding.default_external after startup should be sufficient. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1735) Puppet::Node::Environment.current should reroute with deprecation warning
Title: Message Title Dominic Cleal created an issue Puppet / PUP-1735 Puppet::Node::Environment.current should reroute with deprecation warning Issue Type: Bug Affects Versions: 3.5.0 Assignee: Dominic Cleal Created: 19/Feb/14 11:05 AM Priority: Normal Reporter: Dominic Cleal PUP-1118 in commit ecb317b removed Puppet::Node::Environment.current, which I've seen used in two places: kafo fancy template headers (e.g. https://github.com/theforeman/puppet-puppet/blob/master/templates/_header.erb) I'm worried that there might be other users of this, so would suggest it's rerouted to the `Puppet.lookup(:current_environment)` call and prints a deprecation warning to this ticket.
Jira (PUP-1722) Yumrepo doesn't permit HTTPS URLs
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1722 Yumrepo doesn't permit HTTPS URLs Change By: Kylo Ginsberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1722) Yumrepo doesn't permit HTTPS URLs
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1722 Yumrepo doesn't permit HTTPS URLs Change By: Kylo Ginsberg Sprint: Week 2014-2-19 to 2014-2-26 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-1041) naginator not parsing blank parameters
Title: Message Title
Joshua Cooper commented on an issue
Re: naginator not parsing blank parameters
Reopening this issue, thanks to Erik Dalén for explaining the use case. It should be possible to specify a blank parameter, but this is not currently possible.
The fix for PUP-652 just ensures that if an exception is raised, for whatever reason, that we only call #file=, if the exception (subclass) implements it.
Add Comment
Puppet / PUP-1041
naginator not parsing blank parameters
Even though it wrote it, and is valid nagios syntax, The Naginator can not parse this: {code} define host { host_name gib-proxytest parents hostgroups gib use linux-server address 10.3.100.72 ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http:/
Jira (PUP-1722) Yumrepo doesn't permit HTTPS URLs
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1722 Yumrepo doesn't permit HTTPS URLs Change By: Henrik Lindberg Fix Version/s: 3.5.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-1041) naginator not parsing blank parameters
Title: Message Title
Joshua Cooper updated an issue
Puppet / PUP-1041
naginator not parsing blank parameters
Change By:
Joshua Cooper
Even though it wrote it, and is valid nagios syntax, The Naginator can not parse this: {code} define host {host_name gib-proxytestparentshostgroups gibuselinux-serveraddress10.3.100.72alias proxytest} {code} Where the parents value is blank. It borks with: {code} err: Could not prefetch nagios_host provider 'naginator': Could not parse configuration for nagios_host: line 62: syntax error at '' in /etc/nagios/nagios_host.cfg {code} And then rebuilds the file from scratch every time.
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-652) PR (2026): #19422: Deal with invalid arguments to nagios types - yath
Title: Message Title
Joshua Cooper commented on an issue
Re: PR (2026): #19422: Deal with invalid arguments to nagios types - yath
After PR review, we are going to pull in 189dde723 into 3.5.0. This simply only calls the #file= method if the exception subclass implements it.
There is a separate issue where you want to specify a blank value, so that the default value will be used:
define host {
host_name gib-proxytest
parents
hostgroups gib
uselinux-server
address10.3.100.72
alias proxytest
}
However, puppet will raise an error. Thanks to Erik Dalén for explaining this. I will reopen
PUP-1041
for this issue.
Add Comment
Puppet / PUP-652
PR (2026): #19422: Deal with invalid arguments to nagios types - yath
h2. #19422: Deal with invalid arguments to nagios types * Author: Sebastian Schmidt * Company: * Github ID: [yath|https://github.com/yath] * [Pull Request 2026 Discussion|https://github.com/puppetlabs/puppet/pull/2026] * [Pull Request 2026 File Diff|https://github.com/puppetlabs/puppet/pull/2026/files] h2. Pull Request Description -...
Jira (HI-127) Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Title: Message Title
Simon commented on an issue
Re: Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
I think a backslash is also already used by yaml in normal "" strings.. so I would avoid that
Interpolation function does not look nice and if this cannot handle everything ..
I would like to have %%.. but I understand, that this will break stuff from others..
Add Comment
Hiera / HI-127
Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
I have some data that contains Apache variables (such as %{SERVER_NAME}, %{QUERY_STRING}, etc ) in a Hiera file (Yaml backend). However, when I retrieve the value, the string is replaced with empty value. For instance, for: myserver: http://%{SERVER_NAME} I got the value "http//" I found out that during the lookup in the YAML backend, the answ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-900) noop => true is ignored when resource is triggered by other resource
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-900 noop => true is ignored when resource is triggered by other resource Change By: Charlie Sharpsteen Assignee: Eric Sorenson Charlie Sharpsteen 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-1220) dynamic variable lookup works in templates
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1220 dynamic variable lookup works in templates Change By: Andrew Parker Component/s: DSL 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 (PDB-221) puppetdb-export/import doesn't contain node facts
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-221 puppetdb-export/import doesn't contain node facts Change By: Ryan Senior Sprint: 20140219 to 20140226 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-1677) Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1677 Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet Change By: Andrew Parker Sprint: Week 2014-2- 12 19 to 2014-2- 19 26 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 (HI-186) Hiera 1.3.2-rc2 Release
Title: Message Title Andrew Parker updated an issue Hiera / HI-186 Hiera 1.3.2-rc2 Release Change By: Andrew Parker Sprint: Week 2014-2- 19 12 to 2014-2- 26 19 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-110) Switch PuppetDB to use streams from the incoming command requests
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-110 Switch PuppetDB to use streams from the incoming command requests 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-111) Switch message publishing from Strings to bytes
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-111 Switch message publishing from Strings to bytes Change By: Kenneth Barber Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-378) Empty query on reports results in http 500
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-378 Empty query on reports results in http 500 Change By: Kenneth Barber Labels: trivial 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-221) puppetdb-export/import doesn't contain node facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-221 puppetdb-export/import doesn't contain node facts Change By: Kenneth Barber Story Points: 5 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-468) Update scripts to leverage JAVA_BIN
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-468 Update scripts to leverage JAVA_BIN Change By: Ryan Senior Sprint: 20140219 to 20140226 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-468) Update scripts to leverage JAVA_BIN
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-468 Update scripts to leverage JAVA_BIN Issue Type: Bug Affects Versions: 1.6.2 Assignee: Unassigned Created: 19/Feb/14 8:44 AM Fix Versions: 1.6.x Priority: Normal Reporter: Ryan Senior Not all of the scripts currently have the defaults (in puppetdb_default.erb) sourced. We have the issue now where the user could have both the JDK 1.6 packages and the JDK 1.7 packages installed and our scripts will just use /usr/bin/java (which could be 1.6). We need code like below in each of these scripts, to make sure we're getting the right JDK: if [ -r "/etc/default/<%= @name -%>" ] ; then . /etc/default/<%= @name %> elif [ -r "/etc/sysconfig/<%= @name -%>" ] ; then . /etc/sysconfig/<%= @name -%> else JAVA_BIN = "/usr/bin/java" fi
Jira (PDB-221) puppetdb-export/import doesn't contain node facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-221 puppetdb-export/import doesn't contain node facts Change By: Kenneth Barber It would be good if puppetdb-export & import contained the facts of the nodes as well as the catalog and reports. A change to anonymize will probably have to occur as well, unless we can see a way for skipping it for now. 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-467) Merge versioning tests for http testing into non-versioned files
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-467 Merge versioning tests for http testing into non-versioned files 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-467) Merge versioning tests for http testing into non-versioned files
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-467 Merge versioning tests for http testing into non-versioned files Issue Type: Improvement Assignee: Unassigned Created: 19/Feb/14 8:42 AM Fix Versions: 1.6.x Priority: Normal Reporter: Kenneth Barber We have done some work in merging the testing between versioning into single files but there is still some cleanup work to go on remaining end-points. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1584) Puppet module tool should work with new directory environments
Title: Message Title Kurt Wall commented on an issue Re: Puppet module tool should work with new directory environments Joshua Partlow I'd like to formalize the testing I've done for dir envs so far. I would like to write a full-on test plan for the directory environments work, so we should sit down to talk about use cases. I'll schedule a meeting... Add Comment Puppet / PUP-1584 Puppet module tool should work with new directory environments Given two environments, a legacy environment 'legacyenv' defined in puppet.conf and a 'direnv' directory in the established $environmentdir, `puppet module install --environment ` will respect the legacy environment but not the directory environment. This probably needs to be fixed for all the module functions, but I haven't tested everything yet. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://
Jira (PDB-335) Scope 2.0 epics Round 2 - HA
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-335 Scope 2.0 epics Round 2 - HA Change By: Kenneth Barber Fix Version/s: 2.0.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 (PDB-466) Scope 2.0 epics Round 3 - Reporting and Structured Facts
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-466 Scope 2.0 epics Round 3 - Reporting and Structured Facts Change By: Michelle Johansen Sprint: 20140305 20140226 to 20140312 20140305 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-335) Scope 2.0 epics Round 2 - HA
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-335 Scope 2.0 epics Round 2 - HA Change By: Michelle Johansen Sprint: 20140226 20140219 to 20140305 20140226 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-88) Remove JDK 1.6 Support
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-88 Remove JDK 1.6 Support Change By: Michelle Johansen Sprint: 20131218 to 20140101, 20140108 to 20140115, 20140212 to 20140219 , 20140219 to 20140226 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-466) Scope 2.0 epics Round 3 - Reporting and Structured Facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-466 Scope 2.0 epics Round 3 - Reporting and Structured Facts 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-401) PR (826): Port to trapperkeeper 0.3.0 - cprice404
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-401 PR (826): Port to trapperkeeper 0.3.0 - cprice404 Change By: Michelle Johansen Sprint: 20140129 to 20140205, 20140205 to 20140212, 20140212 to 20140219 , 20140219 to 20140226 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-466) Scope 2.0 epics Round 3 - Reporting and Structured Facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-466 Scope 2.0 epics Round 3 - Reporting and Structured Facts Change By: Kenneth Barber Summary: Scope 2.0 epics Round 3 - Reporting and Structured Facts 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-466) Scope 2.0 Round 3 - Reporting and Structured Facts
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-466 Scope 2.0 Round 3 - Reporting and Structured Facts Issue Type: Task Assignee: Unassigned Created: 19/Feb/14 8:19 AM Priority: Normal Reporter: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-466) Scope 2.0 Round 3 - Reporting and Structured Facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-466 Scope 2.0 Round 3 - Reporting and Structured Facts Change By: Kenneth Barber Sprint: 20140305 to 20140312 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-335) Scope 2.0 epics Round 2 - HA
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-335 Scope 2.0 epics Round 2 - HA Change By: Kenneth Barber Summary: Scope 2.0 epics Round 2 - HA 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-330) Scope 2.0 epics Round 1 - Environments
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-330 Scope 2.0 epics Round 1 - Environments Change By: Kenneth Barber Summary: Scope 2.0 epics Round 1 - Environments 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-401) PR (826): Port to trapperkeeper 0.3.0 - cprice404
Title: Message Title Kenneth Barber commented on an issue Re: PR (826): Port to trapperkeeper 0.3.0 - cprice404 Seems PDB-88 is blocking this also, Ryan Senior and delivery have been working on this. Sorry Christopher Price. Add Comment PuppetDB / PDB-401 PR (826): Port to trapperkeeper 0.3.0 - cprice404 h2. Port to trapperkeeper 0.3.0 * Author: Chris Price <> * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 826 Discussion|https://github.com/puppetlabs/puppetdb/pull/826] * [Pull Request 826 File Diff|https://github.com/puppetlabs/puppetdb/pull/826/files] h2. Pull Request Description This commit updates PuppetD... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-88) Remove JDK 1.6 Support
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-88 Remove JDK 1.6 Support Change By: Michelle Johansen Assignee: Ryan Senior 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-88) Remove JDK 1.6 Support
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-88 Remove JDK 1.6 Support Change By: Michelle Johansen Component/s: RE 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-844) Create basic acl type
Title: Message Title Rob Reynolds commented on an issue Re: Create basic acl type Ethan Brown - I guess I was not watching this issue for some reason, I missed this. I think symlinks becomes an edge case or to put it in better terms a JIRA issue. Things won't be perfect out of the gate. This ticket is focused on the type. IMHO something like symlinks is getting more into the provider (where the work actually happens). Add Comment Puppet / PUP-844 Create basic acl type Create an acl type. It should support basic functionality for describing the desired state of a file/dir in terms of what users are allowed access to the resource. More complex cases should be handled later (protected vs not, inheritance, etc). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-
Jira (PUP-751) Measure stat() calls
Title: Message Title Henrik Lindberg commented on an issue Re: Measure stat() calls Brice Figureau, we are aware of that, we decided to delay that work somewhat because it proved to be difficult to introduce in 3.4.3 and 3.5 in a safe and timely manner. Loading and performance is very much on the agenda for Puppet 4.0 and 3.6 may receive the same features - detailed planning for those releases is just about to begin. 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 Kenn Hussey updated an issue Puppet / PUP-751 Measure stat() calls Change By: Kenn Hussey Flagged: Impediment 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 Kenn Hussey updated an issue Puppet / PUP-751 Measure stat() calls Change By: Kenn Hussey Flagged: Impediment 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-232) Create database migration size estimates and fail with insufficient disk space
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-232 Create database migration size estimates and fail with insufficient disk space Change By: Kenneth Barber Story Points: 8 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-232) Create database migration size estimates and fail with insufficient disk space
Title: Message Title Kenneth Barber commented on an issue Re: Create database migration size estimates and fail with insufficient disk space I think this is non-trivial, so marking it as an 8. More because I can't see an extremely clean/efficient way of doing this without some effort. Add Comment PuppetDB / PDB-232 Create database migration size estimates and fail with insufficient disk space Some of our database migrations can require significant changes to disk usage, such as copying the contents of a large table to a new table that has additional columns or other structural changes. It would be nice to have something that estimates the potential impact of an upgrade and ensure that the user meets those guidelines before performing the upgr... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For
Jira (PDB-220) Titles containing numbers returned from functions will throw exceptions during report storage
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-220 Titles containing numbers returned from functions will throw exceptions during report storage Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-220) Titles containing numbers returned from functions will throw exceptions during report storage
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-220 Titles containing numbers returned from functions will throw exceptions during report storage Change By: Kenneth Barber Labels: redmine trivial 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-220) Titles containing numbers returned from functions will throw exceptions during report storage
Title: Message Title
Kenneth Barber updated an issue
PuppetDB / PDB-220
Titles containing numbers returned from functions will throw exceptions during report storage
Change By:
Kenneth Barber
During some testing, I saw this error: {code} 2013-06-07 17:30:53,124 ERROR [command-proc-45] [puppetdb.command] [97b7fe3f-775e-4ced-833c-6a031758aa47] [store report] Fatal error on attempt 0java.lang.IllegalArgumentException: ResourceEvent key :resource-title should be String, got 1459 at com.puppetlabs.validation$validate_against_model_BANG_.invoke(validation.clj:82) at com.puppetlabs.puppetdb.report$validate_BANG_.invoke(report.clj:42) at com.puppetlabs.puppetdb.command$eval3849$fn__3852$fn__3855.invoke(command.clj:363) at com.puppetlabs.puppetdb.command$eval3849$fn__3852.invoke(command.clj:362) at clojure.lang.MultiFn.invoke(MultiFn.java:167) at com.puppetlabs.puppetdb.command$produce_message_handler$fn__3944.invoke(command.clj:582) at com.puppetlabs.puppetdb.command$wrap_with_discard$fn__3895$fn__3898.invoke(command.clj:490) at com.puppetlabs.puppetdb.command.proxy$java.lang.Object$Callable$f8c5758f.call(Unknown Source) at com.yammer.metrics.core.Timer.time(Timer.java:91) at com.puppetlabs.puppetdb.command$wrap_with_discard$fn__3895.invoke(command.clj:489) at com.puppetlabs.puppetdb.command$wrap_with_exception_handling$fn__3880$fn__3881.invoke(command.clj:443) at com.puppetlabs.puppetdb.command.proxy$java.lang.Object$Callable$f8c5758f.call(Unknown Source) at com.yammer.metrics.core.Timer.time(Timer.java:91) at com.puppetlabs.puppetdb.command$wrap_with_exception_handling$fn__3880.invoke(command.clj:442) at com.puppetlabs.puppetdb.command$wrap_with_command_parser$fn__3890.invoke(command.clj:465) at com.puppetlabs.puppetdb.command$wrap_with_meter$fn__3871.invoke(command.clj:403) at com.puppetlabs.puppetdb.command$wrap_with_thread_name$fn__3903.invoke(command.clj:505) at clamq.jms$jms_consumer$fn__3141.invoke(jms.clj:38) at clamq.jms.proxy$java.lang.Object$MessageListener$ce893c05.onMessage(Unknown Source) at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560) at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498) at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467) at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325) at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947) at java.lang.Thread.run(Thread.java:722) {code} I was using notify during a load test, the code to replicate is simple: {code} $a = range('1','2') notify { $a: } {code} Even confirmed in future pa
Jira (PDB-239) After a change causing a service to not restart, it takes two puppet run for Puppetdb's events API to get the proper status
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-239 After a change causing a service to not restart, it takes two puppet run for Puppetdb's events API to get the proper status 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-378) Empty query on reports results in http 500
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-378 Empty query on reports results in http 500 Change By: Kenneth Barber Story Points: 2 Assignee: Deepak Giridharagopal 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-379) /nodes//reports
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-379 /nodes//reports Change By: Kenneth Barber Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1719) package/apt provider needs to allow holding and ensuring a particular version at the same time
Title: Message Title Jo Rhett commented on an issue Re: package/apt provider needs to allow holding and ensuring a particular version at the same time FreeBSD's new pkg is another one with that feature. Add Comment Puppet / PUP-1719 package/apt provider needs to allow holding and ensuring a particular version at the same time The package provider needs to be able to ensure a particular version of a package while also being able to set a hold status simultaneously. Currently, I'm forced to use an exec to install the package and then have the package provider ensure it being held. I can do it the other way around, but then I get change notices about the package version changing ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1719) package/apt provider needs to allow holding and ensuring a particular version at the same time
Title: Message Title Lauri Tirkkonen commented on an issue Re: package/apt provider needs to allow holding and ensuring a particular version at the same time I don't think this is apt specific, but instead applies to all package providers which implement 'holdable'. Add Comment Puppet / PUP-1719 package/apt provider needs to allow holding and ensuring a particular version at the same time The package provider needs to be able to ensure a particular version of a package while also being able to set a hold status simultaneously. Currently, I'm forced to use an exec to install the package and then have the package provider ensure it being held. I can do it the other way around, but then I get change notices about the package version changing ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For mo
Jira (PUP-1733) Wrong exit code after failed mount
Title: Message Title
Stepan Cenek created an issue
Puppet / PUP-1733
Wrong exit code after failed mount
Issue Type:
Bug
Affects Versions:
3.4.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
19/Feb/14 2:10 AM
Environment:
RHEL 6.4
Priority:
Normal
Reporter:
Stepan Cenek
Puppet apply with incomplete/wrong mount reports success even it failed.
Example:
$ puppet apply -v -d -e "mount { '/tmp/test': ensure => mounted, device => '/dev/test' }"; echo $?
...
Error: /Stage[main]/Main/Mount[/tmp/test]: Could not evaluate: Execution of '/bin/mount /tmp/test' returned 32: mount: mount point /tmp/test does not exist
...
Notice: Finished catalog run in 0.72 seconds
0
puppet apply -v -d -e "mount { '/tmp/test': ensure =>
Jira (PUP-751) Measure stat() calls
Title: Message Title Brice Figureau commented on an issue Re: Measure stat() calls This bug is marked fixed, but to me as discussed on the puppet-dev mailing list (https://groups.google.com/d/msg/puppet-dev/xL2MpRDqufY/j865QCgnAs0J) the excessive stat() calls won't be fixed until Henrik Lindberg introduces his changes to the Puppet Type manager. Those commits listed above only put back the master/stable performance on par with the performance of 3.4.2 (which is great, don't get me wrong), but don't fix the original issue (as described in PUP-1592). 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
Jira (PUP-744) Pool HTTPS connections
Title: Message Title Denis Boulas commented on an issue Re: Pool HTTPS connections Yep. Actually it looks like it will never happen. Release date has been postponed many times already. Now it looks like that functionality only will appear in puppet 4.0 (or maybe 5.0). From my POV there are no any complexity to add keep-alive support on puppet agent side. However if there are any blockers in communication protocol/API they should be fixed on puppet master side, thus at least configurations different from basic WeBrick will be able to manage it well. For eg.: Mongrel (puppet master) <- plain http / no keep-alive > nginx < https / keep-alive -> puppet agent Also there are no discussions at all, no reports about development problems/blockers. I'm just curious why Add Comment Puppet / PUP-744 Pool HTTPS connections Reduce network traffic and latency This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this mess
