Jira (PUP-5121) Add profiling for file inlining
Title: Message Title Christopher Price commented on PUP-5121 Re: Add profiling for file inlining Josh Cooper yes, planning to do so, but was waiting until we could have a meeting with the server devs to try to finalize our metrics gameplan. Waiting for Kevin Corcoran to tell me that we're getting close to picking up that work. Best guesses for now (will update after our meeting): All of the compiler metrics that we get from puppet today have ':compiler' as the first entry in their metric id, e.g. https://github.com/puppetlabs/puppet/blob/f069143cd086735fc88d22d5d76c2a279f0b020c/lib/puppet/parser/environment_compiler.rb#L28 , so it makes some sense to me to try to use a metric id in that namespace for these new metrics. But, it actually doesn't matter that much as long as we know what the metric ids for the DP metrics are, because in all likelihood we'll be surfacing these in some kind of new "direct puppet metrics" section of our status JSON output, and we'll be surgically plucking your DP metrics and combining them with ours. For some of these metrics, all we really need are the counts, not the timing data... but on our end, we can get either counts or timing data or both from any metric id that you have a profile block on, so, when you see me mention counts for individual metrics below, it still boils down to just calls to 'profile' on your end. It seems like the most valuable metrics we can gather are going to be things that tell us a) how much extra time we're spending in the compiler, and b) how often we are avoiding subsequent filemeta requests as a result. To that end, the things that seem like they'd be the most useful would be: number of catalogs compiled w/o DP number of catalogs compiled w/DP time spent in DP static catalog post-processing bonus points for breaking this into phases, e.g. at least differentiating the time spent doing the file checksums from the rest of the post-processing number of file resources in DP catalogs that we inlined the metadata for number of file resources in DP catalogs that we didn't inline the metadata for
Jira (PUP-5857) custom_trusted_oid_mapping does not work
Title: Message Title Christopher Price updated an issue Puppet / PUP-5857 custom_trusted_oid_mapping does not work Change By: Christopher Price Sprint: Server Emerald 2016-03-09 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title Christopher Price commented on PUP-5905 Re: transient test failures in common_package_name_in_different_providers.rb test It looks like these are failing due to a connection error w/rubygems.org. Michael Smith pointed me to PUP-4929 , which was closed as "cannot repro". Michael Smith do you have any thoughts on what to do for now? I can just re-run these jobs and ignore the issue if it doesn't continue to come up, or I can re-open PUP-4929 , or we can use this ticket as a replacement for PUP-4929 ... any thoughts? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title
Christopher Price updated an issue
Puppet / PUP-5905
transient test failures in common_package_name_in_different_providers.rb test
Change By:
Christopher Price
We have recently experienced what appear to be transient failures in the acceptance test {{common_package_name_in_different_providers.rb}}. These seem to come up occasionally, usually (perhaps always) on redhat systems, but not usually on more than one or two cells in a given run. We're seeing these on both our {{stable}} and {{master}} branches.Not yet sure where this ticket should go; for now I'm trying to tease out whether or not other teams have seen these before, or whether there's an SME on this. If it appears to be specific to Puppet Server then we can move this ticket to SERVER and dig in further.A few recent failures:https://jenkins.puppetlabs.com/view/puppet-server/view/all/job/platform_puppet-server_integration-system_no-conditional_full-master/LAYOUT=redhat7-64ma-64a,LDAP_TYPE=default,PLATFORM=default,label=beaker/114/consoleFull https://jenkins.puppetlabs.com/job/platform_puppet-server_integration-system_no-conditional_full-stable/77/
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options,
Jira (PUP-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title Christopher Price commented on PUP-5905 Re: transient test failures in common_package_name_in_different_providers.rb test ping Michael Smith for visibility since he appears to know at least some things about this test Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title
Christopher Price updated an issue
Puppet / PUP-5905
transient test failures in common_package_name_in_different_providers.rb test
Change By:
Christopher Price
We have recently experienced what appear to be transient failures in the acceptance test {{common_package_name_in_different_providers.rb}}. These seem to come up occasionally, usually (perhaps always) on redhat systems, but not usually on more than one or two cells in a given run. We're seeing these on both our {{stable}} and {{master}} branches.Not yet sure where this ticket should go; for now I'm trying to tease out whether or not other teams have seen these before, or whether there's an SME on this. If it appears to be specific to Puppet Server then we can move this ticket to SERVER and dig in further.A few recent failures: https://jenkins.puppetlabs.com/view/puppet-server/view/all/job/platform_puppet-server_integration-system_no-conditional_full-master/LAYOUT=redhat7-64ma-64a,LDAP_TYPE=default,PLATFORM=default,label=beaker/114/consoleFull
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title
Christopher Price updated an issue
Puppet / PUP-5905
transient test failures in common_package_name_in_different_providers.rb test
Change By:
Christopher Price
We have recently experienced what appear to be transient failures in the acceptance test {{common_package_name_in_different_providers.rb}}. These seem to come up occasionally, usually (perhaps always) on redhat systems, but not usually on more than one or two cells in a given run. We're seeing these on both our {{stable}} and {{master}} branches.Not yet sure where this ticket should go; for now I'm trying to tease out whether or not other teams have seen these before, or whether there's an SME on this. If it appears to be specific to Puppet Server then we can move this ticket to SERVER and dig in further. A few recent failures:
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title Christopher Price created an issue Puppet / PUP-5905 transient test failures in common_package_name_in_different_providers.rb test Issue Type: Bug Assignee: Unassigned Created: 2016/02/16 11:55 AM Priority: Normal Reporter: Christopher Price We have recently experienced what appear to be transient failures in the acceptance test common_package_name_in_different_providers.rb. These seem to come up occasionally, usually (perhaps always) on redhat systems, but not usually on more than one or two cells in a given run. We're seeing these on both our stable and master branches. Not yet sure where this ticket should go; for now I'm trying to tease out whether or not other teams have seen these before, or whether there's an SME on this. If it appears to be specific to Puppet Server then we can move this ticket to SERVER and dig in further. Add Comment
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Christopher Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server I created an epic for this and will probably break this down into multiple tickets when we get closer to working on it. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5857) custom_trusted_oid_mapping does not work
Title: Message Title Christopher Price commented on PUP-5857 Re: custom_trusted_oid_mapping does not work Josh Cooper that sounds like a solid theory. I think that's enough input to say that this ticket needs to come into a Puppet Server sprint. Also, is there anything we can do to try to prevent changes like that from being merged in the future w/o taking Puppet Server into consideration? I almost wonder if we should put a git commit hook in that looks for anything that touches master.rb and fire off a warning or something Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5857) custom_trusted_oid_mapping does not work
Title: Message Title Christopher Price commented on PUP-5857 Re: custom_trusted_oid_mapping does not work Kylo Ginsberg OK, in this case it seems like nobody has any significant understanding of how this works and someone is going to need to dig into it. Any ideas how we decide which team to do the initial spelunking? reauchambeau? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5857) custom_trusted_oid_mapping does not work
Title: Message Title Christopher Price commented on PUP-5857 Re: custom_trusted_oid_mapping does not work Henrik Lindberg it looks like you were involved in the original PR review / merge, any ideas on this? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5857) custom_trusted_oid_mapping does not work
Title: Message Title Christopher Price commented on PUP-5857 Re: custom_trusted_oid_mapping does not work Kylo Ginsberg Josh Cooper do either of you know who might be an SME on trusted_oid mappings? This came up during our triage this morning, but we aren't familiar with it and have a few questions to ask before we know whether this is something in the Puppet Server code or not. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5818) regular expression character class/sets interpreted incorrectly
Title: Message Title Christopher Price commented on PUP-5818 Re: regular _expression_ character class/sets interpreted incorrectly ╭─cprice@cosmicshame ~ ‹system› (office-workstation ✘)✹ ╰─➤ rbenv shell 1.9.3-p5511:37:47 PM ╭─cprice@cosmicshame ~ ‹1.9.3-p551› (office-workstation ✘)✹ ╰─➤ irb 4:45:59 PM irb(main):001:0> 'lb12.test.local' =~ /lb[1-2].test.local/ => nil irb(main):002:0> 'lb1.test.local' =~ /lb[1-2].test.local/ => 0 irb(main):003:0>
Jira (PUP-5818) regular expression character class/sets interpreted incorrectly
Title: Message Title Christopher Price commented on PUP-5818 Re: regular _expression_ character class/sets interpreted incorrectly ╭─cprice@cosmicshame ~ ‹system› (office-workstation ✘)✹ ╰─➤ rbenv shell 1.9.3-p5511:32:38 PM ╭─cprice@cosmicshame ~ ‹1.9.3-p551› (office-workstation ✘)✹ ╰─➤ irb 1:32:51 PM irb(main):001:0> 'lb12.test.local' =~ /lb[12].test.local/ => nil irb(main):002:0> 'lb1.test.local' =~ /lb[12].test.local/ => 0 irb(main):003:0>
Jira (PUP-5818) regular expression character class/sets interpreted incorrectly
Title: Message Title Christopher Price commented on PUP-5818 Re: regular _expression_ character class/sets interpreted incorrectly Henrik Lindberg nope, no special handling of nodes on Puppet Server. The Java regexp vs. Ruby regexp is entirely possible, though. I found this: https://github.com/jruby/jruby/wiki/DifferencesBetweenMriAndJruby#regular-expressions But not sure how recent that is. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5818) regular expression character class/sets interpreted incorrectly
Title: Message Title Christopher Price commented on PUP-5818 Re: regular _expression_ character class/sets interpreted incorrectly Henrik Lindberg AFAIK JRuby strives for compatibility with the upstream Ruby version that it is emulating, and I'd be a little surprised if there were differences in the regex behavior, but it's not impossible. One point that may be relevant is that Puppet Server's current JRuby strives for compatibility with MRI Ruby 1.9.3, so if Ruby itself made any semantic changes related to regexes between 1.9.x and 2.x, those might not be reflected in Puppet Server until we upgrade to a JRuby that provides MRI 2.x compatibility. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Christopher Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server Henrik Lindberg thanks, will do. Not sure exactly how soon this might be happening, but knowing the next steps is a good start! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Christopher Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server Kylo Ginsberg we already ship the hocon gem with puppet-agent, right? Henrik Lindberg assuming that ^^ is true, then it sounds like the next steps here would be: PR against hiera that adds this backend and some tests PR against puppet that defines the HoconDataProvider, registers it, and adds tests? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Christopher Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server Henrik Lindberg what would you think about me filing a PR against hiera with this in it: https://github.com/cprice404/hiera-hocon Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5807) ClassInformationService.classes_per_environment call for non-existent file does not return errors
Title: Message Title Christopher Price commented on PUP-5807 Re: ClassInformationService.classes_per_environment call for non-existent file does not return errors If you two are satisfied, I'm satisfied. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5747) puppet/PuppetBoard 2.7.3 not running with puppetdb 2.3.8
Title: Message Title Christopher Price updated an issue Puppet / PUP-5747 puppet/PuppetBoard 2.7.3 not running with puppetdb 2.3.8 Change By: Christopher Price Component/s: Puppet Server Component/s: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5720) FileMetadata replace wrong content to file when master die
Title: Message Title Christopher Price updated an issue Puppet / PUP-5720 FileMetadata replace wrong content to file when master die Change By: Christopher Price Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5720) FileMetadata replace wrong content to file when master die
Title: Message Title Christopher Price updated an issue Puppet / PUP-5720 FileMetadata replace wrong content to file when master die Change By: Christopher Price Scrum Team: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2272) Support namespaced configuration for database and vardir settings
Title: Message Title Christopher Price commented on PDB-2272 Re: Support namespaced configuration for database and vardir settings Ryan Senior this is a wish list / nice-to-have thing that I came across when working on PE-AIO. Would be curious to hear your thoughts. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2270) Update to more recent dropwizard metrics version
Title: Message Title Christopher Price commented on PDB-2270 Re: Update to more recent dropwizard metrics version This seems like a dupe of Andrew Roetker's recent work now, right? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-491) PSON error when hiera hash contains 'document_type' as a key
Title: Message Title Christopher Price commented on HI-491 Re: PSON error when hiera hash contains 'document_type' as a key ping Kylo Ginsberg this was routed to us and came up during our triage; it sounds like a hiera thing, so I re-routed it... let me know if that was not the right decision! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-491) PSON error when hiera hash contains 'document_type' as a key
Title: Message Title Christopher Price updated an issue Hiera / HI-491 PSON error when hiera hash contains 'document_type' as a key Change By: Christopher Price Scrum Team: Puppet Server Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-491) PSON error when hiera hash contains 'document_type' as a key
Title: Message Title Christopher Price moved an issue Hiera / HI-491 PSON error when hiera hash contains 'document_type' as a key Change By: Christopher Price Affects Version/s: SERVER 2.1.1 Component/s: Puppet Server Key: SERVER HI - 1085 491 Project: Puppet Server Hiera Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Christopher Price commented on PUP-5661 Re: Stack level too deep issue Also Failed to load msgpack is logged in almost all installations, it's probably not anything to worry about. It seems like all of his errors always follow the Info: Caching node for foo-node.foo.net line, which reminds me of that YAML serialization issue we ran into with node caching a while back in PUP-4775 ... but since this one seems intermittent, I'm not sure. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Christopher Price commented on PUP-5661 Re: Stack level too deep issue Henrik FWIW this is a Passenger setup, so no Puppet Server. I'm not sure if there's a setting to change the stack size on MRI? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Christopher Price commented on PUP-5661 Re: Stack level too deep issue ping Henrik Lindberg Thomas Hallgren any ideas? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2272) Support namespaced configuration for database and vardir settings
Title: Message Title
Christopher Price created an issue
PuppetDB / PDB-2272
Support namespaced configuration for database and vardir settings
Issue Type:
Task
Assignee:
Unassigned
Created:
2015/12/22 9:03 AM
Priority:
Normal
Reporter:
Christopher Price
In recent explorations around the possibility of running multiple components of the PE stack in the same JVM process together, one issue that came up several times is namespacing for configuration settings.
Since all of the Clojure apps use a conf.d style configuration pattern, where config settings can appear in any file in the conf.d directory, there is a risk of collisions between configuration sections or setting names.
For example, PuppetDB has a setting called 'vardir' that lives in a section called 'global'. In a multi-service deployment, this setting looks confusing because it is not at all clear that it is specific to PuppetDB.
PuppetDB also has a configuration section that is just called 'database'. In a multi-service deployment, when there are other databases being configured as well, this is confusing at best and might actually cause incompatibilities at worst.
Fortunately so far the services I've tried running in the same container with PuppetDB have namespaced their own database config settings, e.g.:
classifier: {
Jira (PDB-2271) Support relative path to vardir
Title: Message Title Christopher Price created an issue PuppetDB / PDB-2271 Support relative path to vardir Issue Type: Task Assignee: Unassigned Created: 2015/12/22 8:13 AM Priority: Normal Reporter: Christopher Price In order to be compatible with a PE-AIO development environment, PuppetDB needs to tolerate a relative path being configured for vardir. This commit illustrates one possible implementation: https://github.com/puppetlabs/puppetdb/commit/1f8742f80f4fc3ab3284488d601cc6be3b88e370 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2270) Update to more recent dropwizard metrics version
Title: Message Title Christopher Price created an issue PuppetDB / PDB-2270 Update to more recent dropwizard metrics version Issue Type: Task Assignee: Unassigned Created: 2015/12/22 8:09 AM Priority: Normal Reporter: Christopher Price In order to be compatible with PE-AIO, PuppetDB needs to be updated to be compatible with a more recent version of the dropwizard metrics library. AJ has a branch that resolves the issue: https://github.com/puppetlabs/puppetdb/pull/1775 Though it may need cleanup and consideration w/rt backward compatibility with the metrics endpoint. Add Comment This message was
Jira (PUP-5622) Enable use of client certificate dNSName for client authentication
Title: Message Title Christopher Price commented on PUP-5622 Re: Enable use of client certificate dNSName for client authentication Jeremy Barlow yep Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2256) Regression/Performance Issue introduced by PDB-135
Title: Message Title Christopher Price commented on PDB-2256 Re: Regression/Performance Issue introduced by PDB-135 Ryan Senior no, but I do think it would probably be worthwhile to write a simple reproducer, all in ruby, that can be run from the CLI to compare MRI/JRuby. We have seen some cases where e.g. the Puppet code lexer was slower in JRuby, and that's the easiest way to tease out where the issue might be. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5596) Puppet agent freezes
Title: Message Title Christopher Price commented on PUP-5596 Re: Puppet agent freezes Josh Cooper Kylo Ginsberg this came up in IRC today and sounded like it was causing a lot of pain, but I don't have any ideas. Do either of you, or do you know who might be a good SME? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Christopher Price commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Jo Rhett did you mean to reference PUP-5392 instead of PUP-5326 in your latest comment? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Christopher Price commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Puppet Server doesn't support a master-bucket-dir setting, it's a very very limited list of things that we allow you to override in our config. vardir is one, though. In general if you have a different setting for vardir in [master] of puppet.conf than what you have for master-var-dir in your puppetserver.conf, lots of bad/weird things are likely to happen. It's an unfortunate situation that we hope to improve dramatically in Puppet 5 by removing most or all of the master settings from puppet.conf, but that doesn't help you much now. (Sorry. ) Another thing we need to do for Puppet 5 is have a reckoning for the CLI commands; my expectation / hope is that we will end up with fewer CLI tools that try to span both client-side and server-side tasks. In that world, there might be an entirely different command for interacting with the server filebucket, and that would simplify some of the configuration stuff. I believe we are packaging the HOCON gem with puppet-agent now, and if that's the case, it would be trivial to read Puppet Server's vardir setting programmatically, but to implement that today you'd have to have some way to detect whether the master was Puppet Server or webrick/passenger, and I think that would be tricky or impossible. I think we have some docs somewhere that talk about the importance of keeping the vardir setting consistent between puppet.conf and puppetserver.conf. My best suggestion for now would be to just continue to highlight that as a best practice until we can improve things in Puppet 5, and then, assuming folks are adhering to that policy, you can just use the master vardir setting from Puppet's normal settings accessors. I know that none of what I've stated above provides any outstanding short-term solutions to the issues at hand, but, hopefully maybe it at least clarifies the situation? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Christopher Price commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Sorry, Jo Rhett, I didn't mean to imply that we don't need anyone at PL as a whole to look at this; I only meant to suggest that if we need someone specifically from the Puppet Server team to get involved then I will try to get that sorted. If the main issue is with the filebucket command then that doesn't seem like a server issue, necessarily, unless I'm missing something. And I presume that there is someone from the client team already poking at that side of the issue... is that accurate, Michael Smith? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Christopher Price commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Michael Smith I don't really have much experience with filebucket, so I don't know if I have enough context to help at the moment. On the surface Jo Rhett's suggestion sounds reasonable to me, though. And if we need to assign someone to spend some time poking at this a bit let me know. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Christopher Price commented on PUP-4450 Re: Cannot load 'provider/network_route/routes.rb' There is an alternate workaround described in SERVER-571. It's easier, but is subject to the leakage problem that Josh Cooper mentioned, and probably not an ideal long-term solution. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Christopher Price commented on PDB-2097 Re: Disable dujour checkins for Puppet Server during CI runs Hooray! So, this went into all of the branches that you guys have active CI pipelines for? Thanks a ton for getting this taken care of. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Christopher Price commented on PDB-2097 Re: Disable dujour checkins for Puppet Server during CI runs Yay! Thanks a ton for getting this in. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Christopher Price commented on PDB-2097 Re: Disable dujour checkins for Puppet Server during CI runs Did this just get moved back by a month? If so, please let me know, because once my team gets through with Ankeny stuff we might try to do this ourselves if you haven't done it yet. It's really hurting us. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5061) Add support for --trusted in 'puppet lookup' command
Title: Message Title Christopher Price commented on PUP-5061 Re: Add support for --trusted in 'puppet lookup' command Oh and also /cc Patrick Carlisle - NMS has a node terminus, right? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5061) Add support for --trusted in 'puppet lookup' command
Title: Message Title Christopher Price commented on PUP-5061 Re: Add support for --trusted in 'puppet lookup' command I'm not aware of any obvious issues that would come out of that, but I suspect Kenneth Barber probably has put more thought into this particular puzzle than I have. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5442) Error: Could not request certificate: execution expired
Title: Message Title Christopher Price assigned an issue to Ramkumar Nagaraj Puppet / PUP-5442 Error: Could not request certificate: execution expired Change By: Christopher Price Assignee: Ramkumar Nagaraj Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5442) Error: Could not request certificate: execution expired
Title: Message Title Christopher Price commented on PUP-5442 Re: Error: Could not request certificate: execution expired Ramkumar Nagaraj This looks like your requests are not making it all the way through to the master. Are you able to do something like a `telnet` from the agent to port 8140 on the master? Perhaps there is a firewall blocking the traffic? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5349) only the ca server is veryfing puppet client certificates
Title: Message Title Christopher Price assigned an issue to cristi falcas Puppet / PUP-5349 only the ca server is veryfing puppet client certificates Change By: Christopher Price Assignee: cristi falcas Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Christopher Price commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection Reading up on stopTimeout, it sounds like it just affects how long the server waits to forcefully kill threads during a shutdown. So, that sounds like a long shot, unfortunately. What version of the JDK are you using? And remind me what version of Puppet Server? There are some newer builds of Jetty out there; we're currently using 9.2.10, and they are up to 9.2.13 in the 9.2.x series, and 9.3.5 on the new 9.3.x series. I could pretty easily put a build together for you that included 9.3.5, but it looks like it has a minimum JDK version of 8. It also might be useful to get some JMX metrics out of your Jetty setup when it's under high load. At some point I could put a script together to try to collect those for you, but TBH it'll probably be a few weeks before we have bandwidth for that because we have a big release date coming up. Usually when we've seen those WritePending it's been because (from the perspective of the server) the client closed the connection. So if you're seeing that happen on multiple agents at the same time, I'd be suspicious of a load balancer or a router severing the connection; perhaps temporarily, and perhaps in a way that Apache is more patient about waiting for a recovery from. If you are interested in testing a build with a newer Jetty, let us know. Or if you are able to narrow down what other things might be going on in your environment so that we can set up a repro case over here. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group a
Jira (PDB-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Christopher Price commented on PDB-2097 Re: Disable dujour checkins for Puppet Server during CI runs It would definitely need to happen before Puppet Server was started. We haven't 100% confirmed that the seemingly inflated Puppet Server numbers on dujour are coming from this, but it's the best guess we have at the moment, and if Puppet Server is being started before that pre-suite step then it would seem likely that this was what was going on. Thanks for looking into it! Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Christopher Price created an issue PuppetDB / PDB-2097 Disable dujour checkins for Puppet Server during CI runs Issue Type: Bug Assignee: Unassigned Created: 2015/10/22 10:42 AM Priority: Major Reporter: Christopher Price Analyzing the dujour data for Puppet Server, we are starting to suspect that it is being artificially inflated by checkins from PuppetDB CI tests in AWS. In various CI jobs we've solved this in the beaker pre-suites by either setting a bunk entry for the dujour hostname in /etc/hosts, or by configuring the TK dujour client with a bunk server hostname. I believe that other teams that are using Puppet Server in their CI already have something like this in their pre-suites, but it's less of an issue for the other projects anyway because their tests run on our internal hardware, meaning that the dujour checkins would all share a small number of remote IP addresses and those are easy to filter out if some accidentally slip through. It's a much bigger problem with PuppetDB since the CI jobs are running in AWS; we have no way of differentiating between "real" AWS checkins and PuppetDB CI checkins. Add Comment
Jira (PUP-5389) PID race condition allows two puppet instances, which can result in failure to request certificate
Title: Message Title Christopher Price updated an issue Puppet / PUP-5389 PID race condition allows two puppet instances, which can result in failure to request certificate Change By: Christopher Price Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5389) PID race condition allows two puppet instances, which can result in failure to request certificate
Title: Message Title Christopher Price commented on PUP-5389 Re: PID race condition allows two puppet instances, which can result in failure to request certificate Kylo Ginsberg this landed on our triage list; seems like you will need to route it somewhere? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5389) PID race condition allows two puppet instances, which can result in failure to request certificate
Title: Message Title Christopher Price updated an issue Puppet / PUP-5389 PID race condition allows two puppet instances, which can result in failure to request certificate Change By: Christopher Price Scrum Team: Puppet Server Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5385) could not retrieve catalog in puppet agent
Title: Message Title Christopher Price commented on PUP-5385 Re: could not retrieve catalog in puppet agent These error messages read like your certificate was revoked and added to the CRL, in which case this would be the expected behavior. Can you confirm whether or not the certificate was revoked? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Christopher Price commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection OK, thanks. Keep us posted; we're definitely interested in fixing it if we find something we can sink our teeth into. If you're interested you could skim the Jetty configuration docs and see if anything jumps out at you. We have a mechanism that we could use to help you test out any of the settings listed there if you were inclined to do so: http://www.eclipse.org/jetty/documentation/current/configuring-connectors.html Another thing we could try at some point is to help you build a jar that contains a newer version of Jetty than the one we currently ship, and see if that changes anything. We had a few weird network issues pop up under thundering herd situations about a year ago and a Jetty upgrade resolved them, but they didn't look exactly like this so it's hard to say whether it would help or not. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Christopher Price commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection Adam Winberg yeah. I'd be surprised if there wasn't some Jetty setting, or something related to Jetty, that would get it sorted. If we can come up with a reliable repro case, we would be happy to investigate it further on our end. The fact that both of your agents timed out at the same time makes it seem like some kind of network hiccup or something. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Christopher Price commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection Adam Winberg unfortunately I don't have any immediate guesses as to what timeout settings from our code could be at play here. Are your agents connecting through a load balancer? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2007) munging catalog fails with :undef tags
Title: Message Title Christopher Price commented on PDB-2007 Re: munging catalog fails with :undef tags As best as I can tell from reading the "ask" link that Daniel Dreier posted, it seems like that user was experiencing the issue on Passenger-based master. Not sure how to reconcile that with Wyatt Alt's experience Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2007) munging catalog fails with :undef tags
Title: Message Title Christopher Price commented on PDB-2007 Re: munging catalog fails with :undef tags I can't imagine a reason why this would behave differently under puppetserver vs. webrick, assuming the same version of core puppet. Not clear on priority / urgency / ownership of this ATM; we're pretty slammed with Ankeny but we can probably help look at this in a week or two if it's not sorted. Maybe sooner if it's extremely urgent. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title Christopher Price commented on PUP-5380 Re: Slow catalog run after updating to puppet 3.7.5 Henrik Lindberg not sure about that; mostly what I know is that there have been a rash of support issues for people upgrading from PE 3.3 to PE 3.8 and complaining of drastically increased catalog compilation times. In some ways I'm kind of hoping that this is the culprit, because I don't have any other strong leads at the moment (other than the possibility that environment_timeout is not working in some versions of Puppet, but we haven't really nailed that down yet and Nick Walker has reported very mixed results about people's experiences with modifying that setting). Adam Winberg would you be willing to apply a patch that printed out some debug information so that we could try to narrow down exactly where the expensive calls are coming from? In exchange, we can give you some accreditation in our release notes when we get the fix in place Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title
Christopher Price commented on PUP-5380
Re: Slow catalog run after updating to puppet 3.7.5
Adam Winberg I don't think it's just you by any stretch We've had a bunch of reports of similar issues but mostly they've been coming from Puppet Enterprise customers, who often aren't as able to help us debug things by doing crazy things like running from source and doing {{git bisect}}s So, the debugging process has been taking a while. So thanks again, a ton, for your help.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title Christopher Price commented on PUP-5380 Re: Slow catalog run after updating to puppet 3.7.5 Adam Winberg thanks a ton for testing that out. Super helpful. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title Christopher Price commented on PUP-5380 Re: Slow catalog run after updating to puppet 3.7.5 Assuming that, with the same number of JRubies, there is a noticeable performance difference between 3.7.4 and 3.7.5, then I think that pinning to a specific number of JRubies and not altering that variable, and using the git bisect approach would probably be very illustrative in terms of helping us figure out what to focus on. So, my recommendation would be to pick a number of JRubies that works well for you with 3.7.4 and then let's go with that as a starting point. From there, what you'd need to do would be: clone the puppet repo to some location on the master: git clone g...@github.com:puppetlabs/puppet.git check out the 3.7.4 tag: git checkout 3.7.4 stop puppet server In your puppetserver conf.d directory, there should be a file called 'os-settings.conf'. It should contain a setting called ruby-load-path, which points to some directory in site-ruby as the place to load the puppet ruby code. uninstall the puppet package and verify that the puppet ruby code no longer exists in the directory that you found from the ruby-load-path setting. Modify the os-settings.conf file to add the path to the lib directory from inside of your git clone. (You'll want to also leave the site-ruby path in the value of the setting, so that it can still find facter, etc., from that path.) Restart puppet server At this point if you do a quick run of your perf testing, hopefully you'll see exactly the same kinds of results that you've been seeing with the packaged version of Puppet 3.7.4. Assuming that all goes well then you can start the git bisect. That should look roughly like this: git bisect start git bisect good # 3.7.4 is good
Jira (PUP-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title Christopher Price commented on PUP-5380 Re: Slow catalog run after updating to puppet 3.7.5 One thing we could try is checking out the Puppet 3.7.5 source code and then doing a `git bisect` between 3.7.4 and 3.7.5... it'd be tedious but theoretically it should show us the exact commit where the behavior changed. Adam Winberg if you are interested in that and need help getting it set up, let us know. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title Christopher Price commented on PUP-5380 Re: Slow catalog run after updating to puppet 3.7.5 Since the performance change seems to be coupled to the Puppet version as opposed to the Puppet Server version, moving this ticket over to the PUP project and assigning to the language team. Thanks Thomas Hallgren! Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title Christopher Price assigned an issue to Thomas Hallgren Puppet / PUP-5380 Slow catalog run after updating to puppet 3.7.5 Change By: Christopher Price Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title Christopher Price moved an issue Puppet / PUP-5380 Slow catalog run after updating to puppet 3.7.5 Change By: Christopher Price Affects Version/s: SERVER 1.1.1 Component/s: Performance Component/s: Performance Key: SERVER PUP - 976 5380 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop rec
Jira (PUP-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title Christopher Price updated an issue Puppet / PUP-5380 Slow catalog run after updating to puppet 3.7.5 Change By: Christopher Price Scrum Team: Puppet Server Language Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5349) only the ca server is veryfing puppet client certificates
Title: Message Title Christopher Price commented on PUP-5349 Re: only the ca server is veryfing puppet client certificates Did you restart the server after copying over the new CRL? Also, what path did you copy the CRL file to? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title Christopher Price commented on PUP-3309 Re: puppet master --compile should be able to source facts from master inventory service Kenneth Barber agree that it's different from PDB-949 for exactly the reasons you state. Just linking that in because there was a lot of related discussion there. And I also agree with the conclusions you were getting at on that ticket about that being an indication of a bug in the agent use case. This isn't blocking anything for us for now. User had an easy workaround. I do think that this will maybe become an issue around the time we remove webrick support, so, would be good to have a plan in place before then... but that's a ways out. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title Christopher Price commented on PUP-3309 Re: puppet master --compile should be able to source facts from master inventory service This came up in IRC today. A very reasonable use case: User wants to stand up a new puppetserver instance, to try to migrate from passenger User wants to run some test compilations so that they can validate that their code works OK with puppetserver New puppetserver node does not have any cached facts from any previous agent runs, so puppet master --compile fails. When we get around to re-working some of the CLI tools (such as puppet master), would be good to consider ways that we could make this work (e.g. providing first-class support for using PuppetDB as a facts terminus). /cc Jeremy Barlow Eric Sorenson Archana Sridhar Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title Christopher Price commented on PUP-3309 Re: puppet master --compile should be able to source facts from master inventory service /cc Ben Ford Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title Christopher Price updated an issue Puppet / PUP-3309 puppet master --compile should be able to source facts from master inventory service Change By: Christopher Price Scrum Team: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Christopher Price commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection Josh Cooper does this seem like what you are asking about?: https://github.com/puppetlabs/trapperkeeper-webserver-jetty9/blob/master/doc/jetty-config.md#idle-timeout-milliseconds If so, I'm not sure if we've decided how to get those docs into the official PL docs yet. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5234) Puppet should be able to change a role's shell
Title: Message Title Christopher Price commented on PUP-5234 Re: Puppet should be able to change a role's shell Kylo Ginsberg just a heads up; this got erroneously assigned to our scrum team, during triage we moved it to your team. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5234) Puppet should be able to change a role's shell
Title: Message Title Christopher Price updated an issue Puppet / PUP-5234 Puppet should be able to change a role's shell Change By: Christopher Price Scrum Team: Puppet Server Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5234) Puppet should be able to change a role's shell
Title: Message Title Christopher Price updated an issue Puppet / PUP-5234 Puppet should be able to change a role's shell Change By: Christopher Price Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4536) Investigate and document differences between Ruby 1.9 and 2.1
Title: Message Title Christopher Price commented on PUP-4536 Re: Investigate and document differences between Ruby 1.9 and 2.1 Sounds like we can just file a PR against Puppet Server repo. We should target this at the 1.x branch and merge up from there. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4536) Investigate and document differences between Ruby 1.9 and 2.1
Title: Message Title Christopher Price commented on PUP-4536 Re: Investigate and document differences between Ruby 1.9 and 2.1 Eric Sorenson is going to try to run down where we should put this in the docs. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4536) Investigate and document differences between Ruby 1.9 and 2.1
Title: Message Title Christopher Price assigned an issue to Eric Sorenson Puppet / PUP-4536 Investigate and document differences between Ruby 1.9 and 2.1 Change By: Christopher Price Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5013) Improve the code for profiling resource evaluation?
Title: Message Title Christopher Price commented on PUP-5013 Re: Improve the code for profiling resource evaluation? Kylo Ginsberg thanks. Do we have a protocol for this sort of thing? I'd have no problem with bringing it into my team's sprint and running it through to the end of the board, but if it's in "ready for test" and is going to get some QA review at this point, it might make more sense for it to be reviewed by PUP QA rather than SERVER QA? I'm happy to do it whichever way you think is best. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Christopher Price commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments Yes, the API would just give us the current values of all of the settings from the environment.conf file, presumably including the full modulepath. Then the autoloader logic for determining which files to consider as candidates for parsing would be duplicated in Clojure and give us much more control over how we interact with the Ruby APIs. I agree with Henrik Lindberg's suggestion that a prereq for this would be to document a specification for defining which files are parsed, but assuming we had that, and that it wasn't insanely complex? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Christopher Price commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments Jeremy Barlow maybe (tomorrow) you can weigh in and let us know what you think about this proposed approach? (tomorrow ) Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Christopher Price commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments Thanks, Henrik Lindberg. Then I think the crux of the issue here is "how insane would it be to duplicate the auto-loader's path expansion logic in Clojure". Which boils down to a couple of slightly smaller questions: "How complex is that logic?", "How likely are we to get it right?", "Is there any chance it will change in the future?", and "Would the duplication be a maintenance headache?" Depending on the answers to those questions, I pretty much agree with all of your points. Do you have any thoughts? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5013) Improve the code for profiling resource evaluation?
Title: Message Title Christopher Price commented on PUP-5013 Re: Improve the code for profiling resource evaluation? Pushed up a cleaner PR. Kylo Ginsberg You'd asked about what version of 3.8.x to target; I don't have a specific release in mind, I just wanted it to be in the 3.x branch in case there is another PE release in the 3.8.x series that I can get this and some other related Puppet Server stuff rolled into. I'll ping you if that happens, if you guys haven't already done a maintenance 3.x release before then. What's your process for merge-ups these days? Should I follow this up with some PRs to merge commits up to stable/master? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5013) Improve the code for profiling resource evaluation?
Title: Message Title Christopher Price commented on PUP-5013 Re: Improve the code for profiling resource evaluation? Done, and the PR should be linked to the ticket now via the magical jira github plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5052) Gatling: Add gatling-jenkins plugin for graphing
Title: Message Title Christopher Price updated an issue Puppet / PUP-5052 Gatling: Add gatling-jenkins plugin for graphing Change By: Christopher Price Sprint: On Deck - Tier 1 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5013) Improve the code for profiling resource evaluation?
Title: Message Title Christopher Price commented on PUP-5013 Re: Improve the code for profiling resource evaluation? Henrik Lindberg could you elaborate a bit? Why would that cause a problem if the profiling block was executed on the agent? IIRC the default configuration for the profilers is just to have an empty list of them, and in that case the 'profile' block is effectively a no-op? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5013) Improve the code for profiling resource evaluation?
Title: Message Title Christopher Price commented on PUP-5013 Re: Improve the code for profiling resource evaluation? Kylo Ginsberg Henrik Lindberg Josh Cooper does anyone have any additional thoughts on this? I've done a lot of experimenting in my local branches where I'm surfacing the metrics data through an HTTP status endpoint, and I'm definitely convinced that we'll get more valuable data by moving that profiling block into Resource#evaluate. I'd like to file a PR on this but am sort of waiting to make sure no one has any major concerns... Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5052) Gatling: Add gatling-jenkins plugin for graphing
Title: Message Title Christopher Price commented on PUP-5052 Re: Gatling: Add gatling-jenkins plugin for graphing Thanks, Nate Wolfe, I think you have it all pretty much right. I think the "normal" gatling jenkins plugin could be a reasonable first step, and then we can advance from there to a custom plugin with more business logic later. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Christopher Price commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments Henrik Lindberg does the getClassesForEnvironment do any validation on the file paths that are passed into it before parsing the files? e.g. if Jeremy Barlow used a simple glob approach to get a list of all the *.pp files to pass into getClassesForEnvironment, and one of the paths that he passed in was /etc/puppetlabs/code/modules/my-bad-module/manifests/init.pp (which, as he pointed out, is invalid because of the dashes in the directory name), would that method still parse the file and return class information? Or would it reject it ? If the current implementation would simply parse it without validating the file path, how difficult would it be to modify that implementation to make it do the validation? Jeremy Barlow re: the interop stuff, it's not necessarily that I think it would not be feasible to pass a giant list of strings across, it's just that I'd rather avoid it if possible and I thought that we could probably get away with out it. I also think it'd be good to avoid the hundreds and hundreds of filesystem reads that the ruby code would have to do in order to build up that list. But your point about not wanting to parse files that weren't in valid modules is a good one, and I hadn't thought of that. I don't really have a strong opinion about what the API should look like, so whatever you are able to work out with Henrik Lindberg and Thomas Hallgren is fine w/me... I definitely agree that not populating our cache with class information for classes that don't actually exist or aren't usable is a requirement, so we will have to reconcile the file path validation issue somehow. If it was possible to make that validation happen from inside of the ClassInformationService.classes_per_environment call, though, that seems like it might be a win. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Christopher Price commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments Jeremy Barlow can you please confirm that what I described above would be sufficient so that we can unblock the language team from estimating the work? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Christopher Price commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments FWIW, this is not necessarily what I was expecting that we were going to be asking for in this ticket. In working on the 'classes-per-environment' feature, we ended up merging this code: https://github.com/puppetlabs/puppet-server/blob/13abb5a957cde4280ca120c7b91ec320e9e56d1c/src/ruby/puppet-server-lib/puppet/server/master.rb#L70-L81 Which makes calls to Puppet.settings.clear_environment_settings, and also makes a call to Puppet.lookup(:environments) and holds a long-lived reference to the result of that call, from within Puppet Server's ruby extensions. My gut feeling is that those are low-level implementation methods that are risky for us to depend on as an API contract. I believe that Jeremy Barlow wrote the code that way because he needed a way to get the latest configuration info for a directory environment (parsed from environments.conf), ensuring that the data he retrieved wasn't cached. So, IMO, the minimum requirements for this ticket would actually just be "provide some Puppet API to request the latest configuration information for a given environment". I could see us taking it one step further from there and also including some file glob patterns in the result seems like it would be a win. Asking the Puppet ruby code to walk the file system and return a complete list of files to us across language interop boundaries seems excessive and expensive at first glance and I'm not sure that I feel like we actually need to take this that far. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bu
Jira (PUP-5013) Improve the code for profiling resource evaluation?
Title: Message Title
Christopher Price created an issue
Puppet / PUP-5013
Improve the code for profiling resource evaluation?
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2015/08/10 4:55 AM
Priority:
Normal
Reporter:
Christopher Price
When doing some experimental work around improving metrics in Puppet Server, I noticed that one of the more interesting metrics (about how long is spent evaluating each resource type during a catalog compilation) was not always showing up. After some poking through the code, I discovered this:
https://github.com/puppetlabs/puppet/blob/2667053d0438d650c909158c79ce85cfaee8019a/lib/puppet/parser/compiler.rb#L385-L388
def evaluate_definitions
exceptwrap do
Puppet::Util::Profiler.profile("Evaluated definitions", [:compiler, :evaluate_definitions]) do
Jira (PUP-5013) Improve the code for profiling resource evaluation?
Title: Message Title Christopher Price commented on PUP-5013 Re: Improve the code for profiling resource evaluation? Henrik Lindberg Josh Cooper Kylo Ginsberg I would be interested to hear if any of you guys have any thoughts on this. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-531) {{puppet cert generate}} should accept {{--allow-dns-alt-names}}
Title: Message Title
Christopher Price assigned an issue to Unassigned
Puppet / PUP-531
{{puppet cert generate}} should accept {{--allow-dns-alt-names}}
Change By:
Christopher Price
Assignee:
Christopher Price
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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.
