Jira (PUP-3336) Puppet defaults.rb doesn't split :libdir if multiple paths provided
Title: Message Title Josh Cooper commented on PUP-3336 Re: Puppet defaults.rb doesn't split :libdir if multiple paths provided The ability to specify multiple directories in :libdir was added in f9e05a80, but I don't believe it ever worked correctly. First, in that version of puppet, it would infer the type of setting based on its value. Anything looking like a file path was assumed to be a FileSetting. And any FileSetting whose value starts with '/' was assumed to be a directory. If you ever attempted to "use" that setting (in the Puppet sense), it would create the directory by applying the settings catalog. If the libdir contained multiple directories, then it would fail: Error: Cannot create /Users/josh/work/modules/a/lib:~/work/modules/b/lib; parent directory /Users/josh/work/modules/a/lib:~/work/modules/b does not exist This is the same error reported in http://projects.puppetlabs.com/issues/3094, which was supposed to be fixed by f9e05a80. Also the puppet-dev discussion points out the problems with allowing libdir to contain multiple values. https://groups.google.com/d/topic/puppet-dev/_nMvueR3ESc/discussion. Basically, it's trying to load code from multiple directories, but we need to be able to pluginsync code into one of those directories, so which one do we pick? This is also discussed in http://projects.puppetlabs.com/issues/3464#note-2 We have a couple different options. We could allow :libdir to contain multiple directories. The setting type would need to be changed from :directory to :path. Note that puppet will create directory settings, but not path settings. This might break code that assumes the libdir exists. We would also need to fix the code in puppet that assumes its a single directory, e.g. augeas. We would also have to update the plugindest setting, since it would need to default to one component of the :libdir. We could continue enforcing the requirement that libdir is a single directory. The fact that the autoloader accepts multiple directories is something that only works in testing, but not when actually running puppet. To allow modules to load code from other modules during testing, we could modify puppet's test helper (lib/puppet/test/helper.rb) to modify the LOAD_PATH using something like Puppet::Node::Environment#each_plugin_directory. I would prefer to keep that logic in puppet and not puppetlabs_spec_helper so that we don't have versioning issues between puppet and puppetlabs_spec_helper. I would prefer to go with option 2. /cc Henrik LindbergJoshua Partlow
Jira (PUP-3388) Issue Creating Multiple Mirrors in Zpool Resource
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3388 Issue Creating Multiple Mirrors in Zpool Resource Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1029) PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1029 Re: PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen kbarber commented: @fpringvaldsen this will need a stable branch target. Feel free to fix these comments from @cprice404 first before rebasing. Can I ask you both a question, what does this hierarchy that is a metric_id mean? And what is its goal? In the Ruby puppet profiler, it has this capability to enumerate where in the stack tree the profile is being called from, looking at this new one: https://github.com/puppetlabs/puppet-server/blob/f833bf81498400517c7e1fa1eea1d7161b6c03cb/src/java/com/puppetlabs/puppetserver/LoggingPuppetProfiler.java, I can't see how it does it here. I guess what I'm trying to say is, are we still showing the stack level in the profile? Your request.key thing made me think about hierarchy thats all, but the previous system kind of did that automatically. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1029) PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title Kenneth Barber assigned an issue to Preben Ingvaldsen PuppetDB / PDB-1029 PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen Change By: Kenneth Barber Assignee: Preben Ingvaldsen Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1029) PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1029 PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen Change By: Kenneth Barber Sprint: PuppetDB 2014-11-19 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1029) PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1029 PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen Change By: Kenneth Barber Affects Version/s: 2.2.2 Story Points: 0 Fix Version/s: 2.2.x Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-916) Retire: Retire puppet < 3.7.3 support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-916 Retire: Retire puppet < 3.7.3 support Change By: Kenneth Barber Summary: Retire: Retire puppet < 3.7. 2 3 support Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-916) Retire: Retire puppet < 3.7.3 support
Title: Message Title Kenneth Barber commented on PDB-916 Re: Retire: Retire puppet < 3.7.3 support Might be able to fix this as part of PDB-663, I already have it pinned to 3.7.3 in my patch: https://github.com/kbarber/puppetdb/tree/pdb-663-ezbake Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-916) Retire: Retire puppet < 3.7.3 support
Title: Message Title Kenneth Barber commented on PDB-916 Re: Retire: Retire puppet < 3.7.3 support In particular, this file defines the pinning: https://github.com/kbarber/puppetdb/blob/pdb-663-ezbake/resources/ext/ezbake.conf Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3673) type validation ignores tags when catalog is being converted to RAL format
Title: Message Title Lee Lowder created an issue Puppet / PUP-3673 type validation ignores tags when catalog is being converted to RAL format Issue Type: Bug Affects Versions: PUP 3.4.3 Assignee: Unassigned Created: 2014/11/14 6:15 AM Labels: support Priority: Normal Reporter: Lee Lowder Type validations are being executed during the conversion of the catalog to RAL format during the prepare_and_retrieve_catalog phase. This conversion to RAL is not being filtered by tags in any way Add Comment
Jira (PUP-3673) type validation ignores tags when catalog is being converted to RAL format
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3673 type validation ignores tags when catalog is being converted to RAL format Change By: Henrik Lindberg Component/s: Types and Providers Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3668) Chaining arrows not working as expected
Title: Message Title Henrik Lindberg commented on PUP-3668 Re: Chaining arrows not working as expected A lot of people are bitten by this behavior, but it is by design. The content of a class is not automatically "contained" in that class wrt. ordering. To get the effect you want you can use the contain function (see https://docs.puppetlabs.com/puppet/latest/reference/lang_containment.html). There is also some background information here http://projects.puppetlabs.com/projects/puppet/wiki/Anchor_Pattern regarding the anchor pattern and why it (and the contain function) is needed. If you need help designing your manifests to achieve the wanted ordering please ask for help on the puppet user google group. Closing this as a won't fix since it works as intended. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Jeff Palmer commented on PUP-1035 Re: Default setting for pluginsource problematic for deployments using SRV records Submitted a pull request for this. https://github.com/puppetlabs/puppet/pull/3311 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3672) Installation on EC2 results in non-functioning 'puppet master'
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3672 Installation on EC2 results in non-functioning 'puppet master' Change By: Kylo Ginsberg Assignee: Kylo Ginsberg jon yeargers Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3672) Installation on EC2 results in non-functioning 'puppet master'
Title: Message Title Kylo Ginsberg commented on PUP-3672 Re: Installation on EC2 results in non-functioning 'puppet master' This looks like it might be a dup of PUP-2132 . Please double check if this is an Amazon Linux AMI. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3336) Puppet defaults.rb doesn't split :libdir if multiple paths provided
Title: Message Title Josh Cooper commented on PUP-3336 Re: Puppet defaults.rb doesn't split :libdir if multiple paths provided Actually, I think option 2 should be implemented in the same way that CommandLine appends to the $LOAD_PATH: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/command_line.rb#L116-L120. This is in keeping with the philosophy that puppet should be a library, and any $LOAD_PATH manipulation should be done by the application (CommandLine, test/helper.rb, etc) that loads the puppet library. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1035 Default setting for pluginsource problematic for deployments using SRV records Change By: Josh Cooper Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-1035 Default setting for pluginsource problematic for deployments using SRV records Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Josh Cooper commented on PUP-1035 Re: Default setting for pluginsource problematic for deployments using SRV records Merged in https://github.com/puppetlabs/puppet/commit/e9797ea to be released in 4.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1035 Default setting for pluginsource problematic for deployments using SRV records Change By: Josh Cooper Fix Version/s: PUP 4.x Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Jeff Palmer commented on PUP-1035 Re: Default setting for pluginsource problematic for deployments using SRV records Josh Cooper based on the comment above from Eric Sorenson do we still think this needs to wait until 4.0? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Josh Cooper commented on PUP-1035 Re: Default setting for pluginsource problematic for deployments using SRV records Jeff Palmer I agree that this change is non-breaking if we only consider the puppet code base and users not using SRV records. But it would represent a change in behavior for SRV records, and we don't know what other code, e.g. modules might be using the setting, so I don't think we can say it's absolutely non-breaking. Also given that there is an easy work around (just override the defaults), I am not in favor of 3.7.x. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3269) Remove network access to the Resource indirection
Title: Message Title William Hopper commented on PUP-3269 Re: Remove network access to the Resource indirection It looks like this was already taken care of by Adrien Thebo in commit da2eed61 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3269) Remove network access to the Resource indirection
Title: Message Title William Hopper updated an issue Puppet / PUP-3269 Remove network access to the Resource indirection Change By: William Hopper Sprint: Platform Client 2014-11-26 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Jeff Palmer commented on PUP-1035 Re: Default setting for pluginsource problematic for deployments using SRV records Josh Cooper That makes sense. Thank you for your help/effort. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3378) False positives in Puppet acceptance testing - should_not_change_the_system.rb
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3378 False positives in Puppet acceptance testing - should_not_change_the_system.rb Change By: Josh Cooper Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3378) False positives in Puppet acceptance testing - should_not_change_the_system.rb
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3378 False positives in Puppet acceptance testing - should_not_change_the_system.rb Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1029) PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1029 Re: PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen fpringvaldsen commented: @cprice404 I've addressed your comments. @kbarber I'll go ahead and rebase this onto stable now that I've addressed @cprice404's feedback. In terms of the metric ID, from what I understand it's used for grouping metrics together, and is sort of like a namespace. I'm not sure if we're still showing the stack level in the profile, but I think @cprice404 would be able to answer that. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1029) PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1029 Re: PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen cprice404 commented: @kbarber this doesn't change the logging behavior you're used to seeing in the Puppet ruby profiler code. The logging profiler in Puppet Server probably needs to be updated a bit to follow that same pattern; have been planning to do that but haven't gotten to it yet. Where this stuff really adds value is in PE when you are exporting the metrics to graphite; the new API allows us to provide hierarchy info to graphite and track counts/timing information at each level of the hierarchy. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1030) PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1030 PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen Issue Type: Task Assignee: Unassigned Created: 2014/11/14 11:42 AM Labels: github Priority: Normal Reporter: gepetto-bot (PUP-3512) Use new Profiler API Author: Preben Ingvaldsen Company: Puppet Labs Github ID: fpringvaldsen Pull Request 1157 Discussion Pull Request 1157 File Diff Pull Request Description Change the `profile` function in PuppetDB to use the new Puppet Profiler API in preparation for removing the old API from Puppet. Modify all calls to the `profile` function in PuppetDB to pass in a metric ID.
Jira (PDB-1029) PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1029 Re: PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen fpringvaldsen commented: I'm closing this in favor of https://github.com/puppetlabs/puppetdb/pull/1157, which is rebased on top of and targeted at stable. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1029) PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1029 Re: PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen Pull request (PUP-3512) Use new Profiler API has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1029) PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1029 Re: PR (1156): (PUP-3512) Use new Profiler API - fpringvaldsen pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/200/ Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1030) PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1030 Re: PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/202/ Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3336) Puppet defaults.rb doesn't split :libdir if multiple paths provided
Title: Message Title Joshua Partlow commented on PUP-3336 Re: Puppet defaults.rb doesn't split :libdir if multiple paths provided I prefer option #2 as well. But I'm not sure how we are determining what paths to add in TestHelper? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3672) Installation on EC2 results in non-functioning 'puppet master'
Title: Message Title jon yeargers commented on PUP-3672 Re: Installation on EC2 results in non-functioning 'puppet master' Yes this looks to be a duplicate. It's AMI. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-84) Disable unnecessary termini, Puppet::Resource::Ral should never be enabled in the puppet master application
Title: Message Title William Hopper commented on PUP-84 Re: Disable unnecessary termini, Puppet::Resource::Ral should never be enabled in the puppet master application It looks like this was also taken care of by Adrien Thebo in commit da2eed61 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3269) Remove network access to the Resource indirection
Title: Message Title William Hopper updated an issue Puppet / PUP-3269 Remove network access to the Resource indirection Change By: William Hopper Sprint: Platform Client 2014- 11 12 - 26 10 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-84) Disable unnecessary termini, Puppet::Resource::Ral should never be enabled in the puppet master application
Title: Message Title William Hopper updated an issue Puppet / PUP-84 Disable unnecessary termini, Puppet::Resource::Ral should never be enabled in the puppet master application Change By: William Hopper Sprint: Platform Client 2014-11-26 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3388) Issue Creating Multiple Mirrors in Zpool Resource
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3388 Issue Creating Multiple Mirrors in Zpool Resource Change By: Josh Cooper Component/s: Breaking Change Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3269) Remove network access to the Resource indirection
Title: Message Title William Hopper updated an issue Puppet / PUP-3269 Remove network access to the Resource indirection Change By: William Hopper Sprint: Platform Client 2014- 12 11 - 10 26 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3511) Refactor Application.run() for external reuse
Title: Message Title Wayne Warren commented on PUP-3511 Re: Refactor Application.run() for external reuse Kevin Corcoran Christopher Price This won't hit puppet-server CI until the submodule is updated, should we leave this ticket in Ready for CI until then? Or should I simply verify that this commit has made it into the MRI puppet FOSS pipeline? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3512) Add deprecation warning for old profiler API in Puppet
Title: Message Title Wayne Warren commented on PUP-3512 Re: Add deprecation warning for old profiler API in Puppet Christopher Price Preben Ingvaldsen This won't hit puppet-server CI until the submodule is updated, do you want to leave it in Ready for CI until then? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1030) PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1030 Re: PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen senior commented: Looks good to me, @cprice404 are you ok with it? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1020) PuppetDB terminus contains `puts` statement that causes duplicate error messages in daemon.log file
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1020 PuppetDB terminus contains `puts` statement that causes duplicate error messages in daemon.log file Change By: Ryan Senior Assignee: Christopher Price Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1020) PuppetDB terminus contains `puts` statement that causes duplicate error messages in daemon.log file
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1020 PuppetDB terminus contains `puts` statement that causes duplicate error messages in daemon.log file Change By: Ryan Senior Sprint: SERVER next next candidates PuppetDB 2014-11-19 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1635) "current thread not owner" after Puppet Agent receives USR1 signal
Title: Message Title Chris Kuehl updated an issue Puppet / PUP-1635 "current thread not owner" after Puppet Agent receives USR1 signal Change By: Chris Kuehl Environment: Ubuntu 12.04.2 LTSRuby 2.0.0 (patchlevel 353) ORRuby 2.1.0 (patchlevel 0)CentOS 7Ruby 2.0.0 (patchlevel 353) ORDebian jessie (2014-11-14)Ruby 2.1.4p265puppet 3.7.2-1 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1635) "current thread not owner" after Puppet Agent receives USR1 signal
Title: Message Title Chris Kuehl commented on PUP-1635 Re: "current thread not owner" after Puppet Agent receives USR1 signal This also occurs on Debian jessie as of 2014-11-14 (ruby 2.1.4p265, puppet 3.7.2-1); I've also filed a Debian bug for it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769621 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.