Jira (PUP-5994) Puppet module install fails when modules have long path names
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5994 Puppet module install fails when modules have long path names Change By: Ethan Brown Flagged: Impediment 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-5768) Fix problematic usage of ENV for Windows
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5768 Fix problematic usage of ENV for Windows Change By: Ethan Brown Flagged: Impediment 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-5879) Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5879 Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8 Change By: Ethan Brown Flagged: Impediment 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-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-5995 Stray UTF-8 character in manifest corrupts parsed parameters Change By: Jeremy Barlow Summary: Stray UTF-8 character in comment manifest corrupts parsed parameters 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-5995) Stray UTF-8 character in comment corrupts parsed parameters
Title: Message Title
Jeremy Barlow commented on PUP-5995
Re: Stray UTF-8 character in comment corrupts parsed parameters
Also, I tested a variation of the 'parse.pp' only with the types removed - String and Integer - since Puppet v3 did not support type specification:
class myclass (
$a_string = "this is a Ѐ string",
$an_integer = 3,
) {}
For a resource_types query, the result appeared to be correct:
{
"kind": "class",
"line": 1,
"name": "myclass",
"parameters": {
Jira (PUP-5995) Stray UTF-8 character in comment corrupts parsed parameters
Title: Message Title Jeremy Barlow commented on PUP-5995 Re: Stray UTF-8 character in comment corrupts parsed parameters I realized later on that the multibyte UTF-8 character didn't need to be in a comment in order for it to cause parsing problems. It was sufficient to have the character in the body of a string for a default parameter value, for example. I updated the description to reflect this scenario as it seems to be even more problematic. 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-5995) Stray UTF-8 character in comment corrupts parsed parameters
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-5995 Stray UTF-8 character in comment corrupts parsed parameters Change By: Jeremy Barlow Attachment: parse.pp 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-5995) Stray UTF-8 character in comment corrupts parsed parameters
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-5995 Stray UTF-8 character in comment corrupts parsed parameters Change By: Jeremy Barlow Attachment: parse.pp 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-5995) Stray UTF-8 character in comment corrupts parsed parameters
Title: Message Title
Jeremy Barlow updated an issue
Puppet / PUP-5995
Stray UTF-8 character in comment corrupts parsed parameters
Change By:
Jeremy Barlow
Summary:
Stray UTF-8 character in manifest comment corrupts parsed parameters
If I have the {{Puppet::InfoService::ClassInformationService}} or {{resource_types}} endpoint parse a manifest which includes a special UTF-8 character in a comment , the resulting default values parsed for parameters appear to be corrupted.Here is the manifest file I used for this test, also attached as "parse.pp":{code:puppet} # Ѐ class myclass ( String $a_string = "this is a Ѐ string", Integer $an_integer = 3,) {}{code}Note that the character at the end of the comment line is a Cyrillic Capital letter Ye with grave, Unicode code point of U+4000, hex representation of 0xD080 in UTF-8 in the file. Running the following code...{code:ruby}require 'puppet'require 'puppet/info_service'files_to_parse = { "production" => [ "./parse.pp" ] }puts Puppet::InfoService::ClassInformationService.new.classes_per_environment(files_to_parse){code}... produces the following output:{noformat}{"production"=>{"./parse.pp"=>{:classes=>[{:name=>"myclass", :params=>[{:name=>"a_string", :type=>"String", :default_literal=>"this is a Ѐ string", :default_source=>" \" this is a Ѐ string\","}, {:name=>"an_integer", :type=>"Integer", :default_literal=>3, :default_source=>","}]}]}}}{noformat}The `:default_literal` values for each parameter appear to be correct but the `:default_source` values do not. Instead of " \" this is a Ѐ string\",", I would have expected "\"this is a Ѐ string\"". Instead of ",", I would have expected "3".This problem does not appear to be unique to the {{ClassInformationService}}. I get the same error when I use the "resource_types" endpoint to query for this data. For a query to "https://localhost:8140/puppet/v3/resource_types/*?kind=class=production" where the "parse.pp" file is stored under the "/environments/production/modules/mymodule/manifests" directory, I get the following response (pretty-printed for display):{noformat}[{"kind": "class","line": 2,"name": "myclass","parameters": {"a_string": " \" this is a Ѐ string\",","an_integer": ","}}]{noformat}
Add Comment
Jira (PUP-5526) (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content.
Title: Message Title Erik Dasher commented on PUP-5526 Re: (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content. I think maybe the testing for this is covered in PUP-5122 . Will sync up with Sean Griffin tomorrow about this ticket... 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-5526) (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content.
Title: Message Title Erik Dasher assigned an issue to Sean Griffin Puppet / PUP-5526 (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content. Change By: Erik Dasher Assignee: Sean Griffin 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-5526) (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content.
Title: Message Title Erik Dasher commented on PUP-5526 Re: (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content. Meanwhile, test: For each case in ( file resource with content attribute file resource with source attribute set to puppet:/// file resource with source attribute set to file:/// Check in a test manifest and test module Run puppet agent -t Validate that the test file exists and has the expected content Modify the test file, cause it to drift. Run puppet agent -t --use_cached_catalog Validate that the test file exists and has the expected content. 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-5526) (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content.
Title: Message Title Erik Dasher commented on PUP-5526 Re: (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content. I think we have an agent that can do this for us; We need to clear up Item #3 in the description. Steve Barlow Do we have information that answers this question? "Is it possible to still use older "source" parameters on nodes with direct puppet enabled? What should happen?" 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-5535) (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5535 (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog Change By: Erik Dasher Scope Change Category: Adopted Scope Change Reason: Because I had time. Sub-team: Jade Story Points: 1 Sprint: Server Jade 2016-03-09 Scrum Team: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5535) (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog
Title: Message Title Erik Dasher assigned an issue to Erik Dasher Puppet / PUP-5535 (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog Change By: Erik Dasher Assignee: qa Erik Dasher 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-5535) (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog
Title: Message Title Erik Dasher assigned an issue to qa Puppet / PUP-5535 (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog Change By: Erik Dasher Status: Accepted Ready for Test Assignee: qa 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-5535) (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog
Title: Message Title Erik Dasher commented on PUP-5535 Re: (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog Validated against: puppetserver version: 2016.1.1014.SNAPSHOT.2016.02.29T1654 puppet --version 4.3.2 pe_build = 2016.1.0-rc2-406-g339593c CentOS release 6.5 (Final) Validation Steps: Checked in (via File Sync) a very small test manifest that defined a file resource Performed a puppet agent -t. Observed the puppetserver logs while the puppet agent -t command was running. Started a puppet agent -t --use_cached_catalog in a "while true" loop. VALIDATED that while puppet agent -t --use_cached_catalog was running, the only messages that came into the puppet server log indicated reports being sent, not catalogs being compiled. 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-5971) Define evaluation should be evaluated depth-first, not breadth-first
Title: Message Title Henrik Lindberg commented on PUP-5971 Re: Define evaluation should be evaluated depth-first, not breadth-first Keeping lazy evalutation pointers on defined() functions such that it is neither depth nor breadth evaluation sounds like a ball of spaghetti to me, but I'd love for you to prove me wrong. Indeed - but I am not suggesting that should be done. The defined function would simply look at what is (completely) defined, just like now. The point I made was just that what is already defined at any given point would change somewhat. Maybe we should start a branch where puppet has depth-first behavior to see how much breakage there 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-5997) acceptance: parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5997 acceptance: parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config Change By: Sean Griffin Assignee: Eric Sorenson Sean Griffin 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-5971) Define evaluation should be evaluated depth-first, not breadth-first
Title: Message Title Hunter Haugen commented on PUP-5971 Re: Define evaluation should be evaluated depth-first, not breadth-first Keeping lazy evalutation pointers on defined() functions such that it is neither depth nor breadth evalutaion sounds like a ball of spaghetti to me, but I'd love for you to prove me wrong. In the mean time, I'll keep my eye open for sub defines that would assume the parent would be fully evaluated. 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-5997) acceptance: parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config
Title: Message Title Chris Price commented on PUP-5997 Re: acceptance: parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config ping Sean Griffin] Kylo Ginsberg this is a semi-blocker for us getting some final OSS Puppet Server changes into PE before the integration freeze date; we have something we're supposed to get in by Thursday the 3rd. 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-5996) acceptance: language/exported_resources.rb test fails when agent on master is run
Title: Message Title Chris Price commented on PUP-5996 Re: acceptance: language/exported_resources.rb test fails when agent on master is run ping Eric Thompson Kylo Ginsberg this is a semi-blocker for us getting some final OSS Puppet Server changes into PE before the integration freeze date; we have something we're supposed to get in by Thursday the 3rd. 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-5863) Static catalog (manual) acceptance: Old agents function as before, no static catalog, Story PUP-5532, PUP-5536
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-5863 Static catalog (manual) acceptance: Old agents function as before, no static catalog, Story PUP-5532, PUP-5536 Change By: Sean Griffin Assignee: Sean Griffin 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-5863) Static catalog (manual) acceptance: Old agents function as before, no static catalog, Story PUP-5532, PUP-5536
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5863 Static catalog (manual) acceptance: Old agents function as before, no static catalog, Story PUP-5532, PUP-5536 Change By: Sean Griffin Attachment: pup-5863-manifest 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-5535) (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5535 (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog Change By: Erik Dasher QA Risk Assessment: High Medium 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-5535) (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog
Title: Message Title Erik Dasher commented on PUP-5535 Re: (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog Discussed with Sean Griffin; We view the risk on this story as "Medium." 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-5863) Static catalog (manual) acceptance: Old agents function as before, no static catalog, Story PUP-5532, PUP-5536
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5863 Static catalog (manual) acceptance: Old agents function as before, no static catalog, Story PUP-5532, PUP-5536 Change By: Sean Griffin Release Notes Summary: Not necessary 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 (FACT-1355) Fix build isolation for generated files
Title: Message Title Michael Smith created an issue Facter / FACT-1355 Fix build isolation for generated files Issue Type: Task Assignee: Unassigned Created: 2016/03/01 4:14 PM Priority: Normal Reporter: Michael Smith Currently generated files are put into the source tree. This makes it impossible to have multiple project directories at once. We should put them all in the project bin directory. Also, the way we handle rspec is messy and requires manual setup. This causes packaging to fail if trying to do a local packaging build. We should do bundle setup in the project bin directory as part of make test, and use it to run specs. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Henrik Lindberg commented on PUP-5849 Re: Newline is not sufficient to avoid parsing as a function call Daniel Parks Believe me, if this was easy we would have made the error better already . The detection of the situation and giving a better error may be just as much work as making it work ok in the first place. The Ruby implementation does not have support for showing error in context like Peter showed for the native parser that is in the works. That is a major undertaking to do for the Ruby parser (although it has information about lines, positions and lengths of tokens). The error message is however correctly pointing out where the element is that the parser thinks you intended to be the function name - the line and position on line. It is the fact that whitespace is insignificant that is baffling here. We cannot just include that in this error (it would need to be included in a bunch of other errors as well) and it would probably be irritating in a "clippy" kind of irritating way as most problems are bona fide typos. Therefore I think a better course of action is to add the rule that "for an LPAR to be considered to signal a call, it must be on the same line as the preceding token". Ruby has taken this a step further where even a single space may break the meaning. (That is actually easier to implement) - ie. foo() # this is a call foo () # this is not call Add Comment This message was sent by Atlassian JIRA
Jira (PUP-5997) acceptance: parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5997 acceptance: parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config Change By: Henrik Lindberg Summary: acceptance: parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config 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-5996) acceptance: language/exported_resources.rb test fails when agent on master is run
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5996 acceptance: language/exported_resources.rb test fails when agent on master is run Change By: Henrik Lindberg Summary: acceptance: language/exported_resources.rb test fails when agent on master is run 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-5994) Puppet module install fails when modules have long path names
Title: Message Title Glenn Sarti commented on PUP-5994 Re: Puppet module install fails when modules have long path names First introduced 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-5994) Puppet module install fails when modules have long path names
Title: Message Title Glenn Sarti commented on PUP-5994 Re: Puppet module install fails when modules have long path names Pending QE/QA review 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-5994) Puppet module install fails when modules have long path names
Title: Message Title Glenn Sarti assigned an issue to Ethan Brown Puppet / PUP-5994 Puppet module install fails when modules have long path names Change By: Glenn Sarti Assignee: Ethan Brown 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-5994) Puppet module install fails when modules have long path names
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-5994
Puppet module install fails when modules have long path names
Change By:
Glenn Sarti
Running {code}puppet module install puppetlabs-dsc{code} silently fails to install ALL some of the files in tar.gz in the module from from the forge. tarball {code}PS C:\ProgramData\PuppetLabs\code\environments\production\modules\dsc> ls *.psm1 -rec |measureCount: 28{code}There should be over 240 PSM1 files
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-5994) Puppet module install fails when modules have long path names
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5994 Puppet module install fails when modules have long path names Change By: Glenn Sarti Environment: Puppet Agent 4.3.2 and 3.8.6 Windows 2012 R2 and MacOS X Darwin Production ForgeDSC Module 1.0.0 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-5994) Puppet module install fails when modules have long path names
Title: Message Title
Glenn Sarti commented on PUP-5994
Re: Puppet module install fails when modules have long path names
Repro steps -
Git clone the puppet repo Checkout the appropriate branch Bundle install
Using this script
@ECHO OFF
RD C:\ProgramData\PuppetLabs\code\environments\production\modules\dsc /s/q > NUL
RD C:\ProgramData\PuppetLabs\puppet\etc\modules\dsc /s/q > NUL
call Bundle exec puppet module install puppetlabs-dsc
powershell "& { ls 'C:\ProgramData\PuppetLabs\code\environments\production\modules\dsc\*.psm1' -rec -ErrorAction 'SilentlyContinue' | measure }"
powershell "& { ls 'C:\ProgramData\PuppetLabs\puppet\etc\modules\dsc\*.psm1' -rec -ErrorAction 'SilentlyContinue' | measure }"
Jira (PUP-5994) Puppet module install fails when modules have long path names
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-5994
Puppet module install fails when modules have long path names
Change By:
Glenn Sarti
Running {code}puppet module install puppetlabs-dsc{code} silently fails to install ALL of the files in tar.gz in the module from from the forge.{code}PS C:\ProgramData\PuppetLabs\code\environments\production\modules\dsc> ls *.psm1 -rec |measureCount: 28{code}There should be over 250 240 PSM1 files
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-5994) Puppet module install fails when modules have long path names
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-5994
Puppet module install fails when modules have long path names
Change By:
Glenn Sarti
Running {code}puppet module install puppetlabs-dsc{code} silently fails to install ALL of the files in tar.gz in the module from from the forge. {code}PS C:\ProgramData\PuppetLabs\code\environments\production\modules\dsc> ls *.psm1 -rec |measureCount: 28{code}
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-5994) Puppet module install fails when modules have long path names
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-5994
Puppet module install fails when modules have long path names
Change By:
Glenn Sarti
Running {code}puppet module install puppetlabs-dsc{code} silently fails to install ALL of the files in tar.gz in the module from from the forge.{code}PS C:\ProgramData\PuppetLabs\code\environments\production\modules\dsc> ls *.psm1 -rec |measureCount: 28{code} There should be over 250 PSM1 files
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-5994) Puppet module install fails when modules have long path names
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5994 Puppet module install fails when modules have long path names Major change as it can impact any module in the forge Change By: Glenn Sarti Scope Change Category: Found Scope Change Reason: Found during testing of the DSC module for the Windows Wednesday Blog 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-5994) Puppet module install fails when modules have long path names
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-5994
Puppet module install fails when modules have long path names
Change By:
Glenn Sarti
Running {code}puppet module install puppetlabs-dsc{code} silently fails to install ALL of the files in tar.gz in the module from from the forge.
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-5994) Puppet module install fails when modules have long path names
Title: Message Title Glenn Sarti commented on PUP-5994 Re: Puppet module install fails when modules have long path names The standard TAR header only uses a 100 byte field for filename. The UStar format supersedes this and adds the ability to add a 155 filename prefix to the header, effectively making the the max pathname 255 chars. Using the default standard tar command on Mac OSX (Darwin), when it encounters the long name it shortens the filename and adds a prefix. This can be seen in an extract of the name parameter in the DSC module. puppetlabs-dsc-1.0.0/tests/acceptance/tests/basic_dsc_resources/user/user_valid_password.rb puppetlabs-dsc-1.0.0/tests/acceptance/tests/basic_dsc_resources/user/user_valid_unicode.rb tests/acceptance/tests/basic_dsc_resources/user/negative/user_invalid_password.rb tests/acceptance/tests/basic_dsc_resources/user/negative/user_invalid_passwordneverexpires.rb tests/acceptance/tests/basic_dsc_resources/user/negative/user_invalid_username.rb puppetlabs-dsc-1.0.0/tests/acceptance/tests/basic_dsc_resources/service/negative/ puppetlabs-dsc-1.0.0/tests/acceptance/tests/basic_dsc_resources/service/service_remove.rb tests/acceptance/tests/basic_dsc_resources/service/service_valid_name_startuptype_state.rb
Jira (PUP-5994) Puppet module install fails when modules have long path names
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5994 Puppet module install fails when modules have long path names Change By: Glenn Sarti Fix Version/s: PUP 4.3.3 Fix Version/s: PUP 3.8.7 Fix Version/s: PUP 4.4.0 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-5997) parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config
Title: Message Title
Jeremy Barlow updated an issue
Puppet / PUP-5997
parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config
Change By:
Jeremy Barlow
The parser_functions/puppet_lookup_cmd.rb test fails when run in the Puppet Server CI pipeline :https://jenkins . puppetlabs.com/view/puppet-server/view/all/job/platform_puppet-server_integration-system_no-conditional_full-master/139/LAYOUT=redhat7-64ma-windows2008r2-64a,LDAP_TYPE=default,PLATFORM=default,label=beaker/testReport/junit/%28root%29/ruby_puppet_acceptance_tests_parser_functions/puppet_lookup_cmd_rb/ The root cause of the failure appears to be that the test was written to only work when a single `agent` is in the CI/beaker configuration:This line...https://github.com/puppetlabs/puppet/blob/92fa18efefa40fa8ef0b6a44d6d900f9e522c45a/acceptance/tests/parser_functions/puppet_lookup_cmd.rb#L14...has:{code:ruby}@agentname = on(agent, facter('fqdn')).stdout.chomp{code}I think the test needs to be reworked to iterate through each agent the configuration with an {{agents.each}} and do the appropriate steps.
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
Jira (PUP-5997) parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config
Title: Message Title Jeremy Barlow commented on PUP-5997 Re: parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config Sean Griffin - as I think this may be in your area, could you look into this test issue? 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-5997) parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config
Title: Message Title
Jeremy Barlow created an issue
Puppet / PUP-5997
parser_functions/puppet_lookup_cmd.rb test fails when multiple agents in beaker config
Issue Type:
Bug
Assignee:
Eric Sorenson
Components:
QA
Created:
2016/03/01 2:40 PM
Priority:
Normal
Reporter:
Jeremy Barlow
The parser_functions/puppet_lookup_cmd.rb test fails when run in the Puppet Server CI pipeline. The root cause of the failure appears to be that the test was written to only work when a single `agent` is in the CI/beaker configuration:
This line...
https://github.com/puppetlabs/puppet/blob/92fa18efefa40fa8ef0b6a44d6d900f9e522c45a/acceptance/tests/parser_functions/puppet_lookup_cmd.rb#L14
...has:
@agentname = on(agent, facter('fqdn')).stdout.chomp
I think the test needs to be reworked to iterate through each agent the configuration with an agents.each and do the
Jira (PUP-5996) language/exported_resources.rb test fails when agent on master is run
Title: Message Title Jeremy Barlow commented on PUP-5996 Re: language/exported_resources.rb test fails when agent on master is run Eric Thompson - would it make sense to have someone on your team look into 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-5996) language/exported_resources.rb test fails when agent on master is run
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-5996 language/exported_resources.rb test fails when agent on master is run Issue Type: Bug Assignee: Eric Sorenson Components: QA Created: 2016/03/01 2:31 PM Priority: Normal Reporter: Jeremy Barlow The language/exported_resources.rb test fails when run in the Puppet Server CI pipeline, specifically when the agent on the master is run: https://jenkins.puppetlabs.com/view/puppet-server/view/all/job/platform_puppet-server_integration-system_no-conditional_full-master/139/LAYOUT=ubuntu1404-64ma-64a,LDAP_TYPE=default,PLATFORM=default,label=beaker/testReport/junit/%28root%29/ruby_puppet_acceptance_tests_language/exported_resources_rb/ This problem presumably has not come up in puppet-agent pipeline testing because it is not done with the agent on master configuration. The test makes an assertion that a puppet agent returns an exit code of 2, indicating that some resources have changed. For cases where an agent not on the master is run, a "User" resource would be collected into the catalog during the agent run. When the agent is run on the master, however, no "User" resource is collected: From https://github.com/puppetlabs/puppet/blob/92fa18efefa40fa8ef0b6a44d6d900f9e522c45a/acceptance/tests/language/exported_resources.rb#L132-L138:
Jira (PUP-5608) Add initial ruby 2.3 support
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5608 Add initial ruby 2.3 support Change By: Kylo Ginsberg Release Notes Summary: This adds initial Ruby 2.3 support . However , but only at the spec test level note that using puppet with ruby 2 . 3.0 is not recommended yet. 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-5608) Add initial ruby 2.3 support
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5608 Add initial ruby 2.3 support Change By: Kylo Ginsberg Summary: Add initial ruby 2.3 support 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-5995) Stray UTF-8 character in manifest comment corrupts parsed parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5995 Stray UTF-8 character in manifest comment corrupts parsed parameters Change By: Henrik Lindberg Priority: Normal Major 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-5995) Stray UTF-8 character in manifest comment corrupts parsed parameters
Title: Message Title Henrik Lindberg commented on PUP-5995 Re: Stray UTF-8 character in manifest comment corrupts parsed parameters If that goes wrong (multibyte unicode in comment) then other multibyte unicode characters elsewhere will also result in problems as the offsets will be wrong. 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-5995) Stray UTF-8 character in manifest comment corrupts parsed parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5995 Stray UTF-8 character in manifest comment corrupts parsed parameters First we need to establish is this is a Ruby thing or not. We should take the example and turn it into a unit test. The implementation is different depending on which Ruby is in use (byte oriented or character oriented) - we did this since Ruby 1.8 and 1.9 were quit different in their support for byte vs. character positions when using a string scanner. It also turned out that the char based APIs were much slower. Anyway, we need to start with a reproducer. Change By: Henrik Lindberg Story Points: 2 Sprint: Language Triage 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
Jira (PUP-1072) support HTTP(S) URL as the file 'source'
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-1072
support HTTP(S) URL as the file 'source'
Change By:
Josh Cooper
Release Notes Summary:
This adds support for 'http' and 'https' URLS as source attributes to the file resource.Since the checksum metadata is not available from the URL, applying a file resource with an http/s source will always be detected as a content change. This can be avoided by specifying the {{checksum}} and {{checksum_value}} explicitly, or using {{mtime}} as the checksum.
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 (PDOC-28) Make puppet strings available as a gem
Title: Message Title Trevor Vaughan commented on PDOC-28 Re: Make puppet strings available as a gem Jan Vansteenkiste How large is the codebase that you're trying to run on? I didn't have any issues running, but you may be having weird issues on large codebases per PDOC-71. You may also be having issues depending on what version of Puppet you're using per PDOC-72. I'm not sure if there are any other breaking combinations. 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 (PDOC-28) Make puppet strings available as a gem
Title: Message Title Kylo Ginsberg commented on PDOC-28 Re: Make puppet strings available as a gem Thanks for trying it out Jan Vansteenkiste! I just tried to reproduce that with master of puppetlabs-strings (678ba735e8d62ff59339b04644fc335ba20799e8); I used the puppetlabs-apache module as a sample module to run strings on. That didn't fail. Can you share more info about your setup? 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-5620) Puppet should log the results of running an autosign script
Title: Message Title Jeremy Barlow commented on PUP-5620 Re: Puppet should log the results of running an autosign script This should come up in the Puppet Server scrum team's backlog grooming this week since it has the "Puppet Server" scrum team on it. We can talk in that meeting about what project would be most appropriate for this ticket to be under. 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-5994) Puppet module install fails when modules have long path names
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5994 Puppet module install fails when modules have long path names Change By: Glenn Sarti Summary: Installing the Puppetlabs DSC Puppet module install fails to expand all of the files when modules have long path names 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-5994) Installing the Puppetlabs DSC module fails to expand all of the files
Title: Message Title Glenn Sarti commented on PUP-5994 Re: Installing the Puppetlabs DSC module fails to expand all of the files Found the issue in the module installer (mini.rb) with long paths 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-5994) Installing the Puppetlabs DSC module fails to expand all of the files
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-5994 Installing the Puppetlabs DSC module fails to expand all of the files Change By: Glenn Sarti Assignee: Glenn Sarti 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-5862) Static catalog acceptance: Request file content only when drift detected, Story PUP-5531
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-5862 Static catalog acceptance: Request file content only when drift detected, Story PUP-5531 Change By: Josh Cooper Assignee: Josh Cooper 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-5989) connection timeout / performance issues with ruby 2.1
Title: Message Title Josh Cooper commented on PUP-5989 Re: connection timeout / performance issues with ruby 2.1 Could you check what your server's http keepalive timeout is set to (either webrick, passenger, load-balancer), e.g. https://httpd.apache.org/docs/2.4/mod/core.html#keepalivetimeout? I'm guessing the server's http keepalive timeout is shorter than the client's (which defaults to 4 seconds). And so the server will close the idle connection (either gracefully by sending FIN, or ungracefully with RST). Also could you include the part of the trace between plugin_hook and with_connection? 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-5099) Include code_id in environment catalog
Title: Message Title Nick Lewis updated an issue Puppet / PUP-5099 Include code_id in environment catalog Change By: Nick Lewis Sprint: AM 2015-10-21 , AO 2016-03-09 (Burn CF) 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-5341) Tag fields in reports accidentally changed to Puppet::Util::TagSet objects
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5341 Tag fields in reports accidentally changed to Puppet::Util::TagSet objects Change By: Josh Cooper Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.0 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-5862) Static catalog acceptance: Request file content only when drift detected, Story PUP-5531
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5862 Static catalog acceptance: Request file content only when drift detected, Story PUP-5531 Change By: Josh Cooper Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.0 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-5867) Static catalog acceptance: Why cached catalog is applied, Story PUP-5706
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5867 Static catalog acceptance: Why cached catalog is applied, Story PUP-5706 Change By: Josh Cooper Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.0 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-5872) Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5872 Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533 Change By: Josh Cooper Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.0 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-5959) Add test that static catalog metadata defaults match File type
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5959 Add test that static catalog metadata defaults match File type Change By: Josh Cooper Summary: Derive Add test that static catalog metadata lookup defaults from match File type 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-5959) Derive static catalog metadata lookup defaults from File type
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5959 Derive static catalog metadata lookup defaults from File type Change By: Josh Cooper Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.0 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-5866) Static catalog acceptance: Per environment control of static catalog, Story PUP-5705
Title: Message Title Michael Smith updated an issue Puppet / PUP-5866 Static catalog acceptance: Per environment control of static catalog, Story PUP-5705 Change By: Michael Smith Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.0 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-5866) Static catalog acceptance: Per environment control of static catalog, Story PUP-5705
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-5866 Static catalog acceptance: Per environment control of static catalog, Story PUP-5705 Change By: Michael Smith Assignee: 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5995) Stray UTF-8 character in manifest comment corrupts parsed parameters
Title: Message Title Chris Price commented on PUP-5995 Re: Stray UTF-8 character in manifest comment corrupts parsed parameters It doesn't seem like a blocker but does seem like a bug. 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 (FACT-1354) Facter ec2_userdata handles binary data incorrectly
Title: Message Title Michael Smith created an issue Facter / FACT-1354 Facter ec2_userdata handles binary data incorrectly Issue Type: Bug Affects Versions: FACT 3.1.4, FACT 3.0.0 Assignee: Unassigned Created: 2016/03/01 10:51 AM Priority: Normal Reporter: Michael Smith On an ec2 instance with binary userdata specified (as in gzipped data), facter ec2_userdata emits extra bytes at the end. This means you can't pipe the data to gunzip and unzip it. For comparison, try curl http://169.254.169.254/latest/user-data/ | gunzip. Add Comment
Jira (PUP-5995) Stray UTF-8 character in manifest comment corrupts parsed parameters
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-5995 Stray UTF-8 character in manifest comment corrupts parsed parameters Change By: Jeremy Barlow Affects Version/s: PUP 4.3.2 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-5995) Stray UTF-8 character in manifest comment corrupts parsed parameters
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-5995 Stray UTF-8 character in manifest comment corrupts parsed parameters Issue Type: Bug Assignee: Unassigned Attachments: parse.pp Created: 2016/03/01 10:38 AM Priority: Normal Reporter: Jeremy Barlow If I have the Puppet::InfoService::ClassInformationService or resource_types endpoint parse a manifest which includes a special UTF-8 character in a comment, the resulting default values parsed for parameters appear to be corrupted. Here is the manifest file I used for this test, also attached as "parse.pp": # Ѐ class myclass ( String $a_string = "this is a string",
Jira (PUP-5993) Possible intermittent test failure in registry_spec.rb
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-5993
Possible intermittent test failure in registry_spec.rb
Change By:
Ethan Brown
During a different PR (PUP-5991) the registry_spec test failed but then passed when the CI test was started again.The registry code was changed a while ago to guard against memory buffer overruns but perhaps not all of the code was corrected. Test Failure;{code}[00:37:29] Failures:[00:37:29] [00:37:29] 1) Puppet::Util::Windows::Registry#values when reading values should return REG_MULTI_SZ values[00:37:29] Failure/Error: expect(written).to eq(pair[:value])[00:37:29] [00:37:29]expected: ["string1", "string2"][00:37:29] got: ["string1", "string2", "\u6E00"][00:37:29] [00:37:29](compared using ==)[00:37:29] # ./spec/integration/util/windows/registry_spec.rb:222:in `block (6 levels) in '[00:37:29] # ./spec/integration/util/windows/registry_spec.rb:213:in `block (5 levels) in '[00:37:29] {code} The failing code in question can be found at https://github.com/puppetlabs/puppet/blob/dae071984dd25025498bbf273cffa0e3e5b6ca43/spec/integration/util/windows/registry_spec.rb#L199-L226Particularly, round-tripping the following values through {{reg.write}} triggered a read of extraneous data:{code:ruby}{:name => 'REG_MULTI_SZ', :type => Win32::Registry::REG_MULTI_SZ, :value => ['string1', 'string2']}{code}The Unicode character http://www.fileformat.info/info/unicode/char/6e00/index.htm is not present in any of the strings, so this looks like an improperly terminated string / memory corruption issue.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5993) Possible intermittent test failure in registry_spec.rb
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5993 Possible intermittent test failure in registry_spec.rb Change By: Ethan Brown Sprint: Windows 2016-03-23 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-5993) Possible intermittent test failure in registry_spec.rb
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5993 Possible intermittent test failure in registry_spec.rb Change By: Ethan Brown Story Points: 1 2 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-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Peter Huene commented on PUP-5849 Re: Newline is not sufficient to avoid parsing as a function call Sure enough, if you change $a = [] to $a = foo, the native parser, like the ruby one, ignores the whitespace and treats it like the expected function call. Sadly, that can be a little confusing since it only shows one line of context: $ puppetcpp compile foo.pp Notice: compiling for node 'peterhu-osx' with environment 'production'. Error: foo.pp:1:6: node 'peterhu-osx': unknown function 'foo'. $a = foo ^~~ Notice: compilation failed with 1 error and 0 warnings. Add Comment
Jira (PUP-5994) Installing the Puppetlabs DSC module fails to expand all of the files
Title: Message Title Glenn Sarti created an issue Puppet / PUP-5994 Installing the Puppetlabs DSC module fails to expand all of the files Issue Type: Bug Assignee: Unassigned Created: 2016/03/01 10:27 AM Environment: Puppet Agent 4.3.2 Production Forge DSC Module 1.0.0 Priority: Major Reporter: Glenn Sarti Running puppet module install puppetlabs-dsc fails to install of the files in tar.gz from from the forge.
Jira (PUP-5989) connection timeout / performance issues with ruby 2.1
Title: Message Title Suny Kim commented on PUP-5989 Re: connection timeout / performance issues with ruby 2.1 This seems to be it. I tried 3 times each and consistently got these results: A. With http_keepalive_timeout=0 in the client session of the node's puppet.conf, the runs get through in the normal time ( 14 - 20 secs). B. Without the http_keepalive_timeout setting, we get ESC[0;36mDebug: Failed to load library 'msgpack' for feature 'msgpack'ESC[0m ESC[0;36mDebug: Puppet::Network::Format[msgpack]: feature msgpack is missingESC[0m ESC[0;36mDebug: catalog supports formats: pson b64_zlib_yaml yaml dot rawESC[0m ESC[0;36mDebug: Using cached connection for https://infrastructure-puppet.muc.domeus.com:8140ESC[0m ESC[0;36mDebug: Closing connection for https://infrastructure-puppet.muc.domeus.com:8140ESC[0m ESC[1;31mError: Could not retrieve catalog from remote server: execution expired /usr/lib/ruby/2.1.0/net/http.rb:920:in `connect' /usr/lib/ruby/2.1.0/net/http.rb:920:in `block in connect'
Jira (PUP-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Daniel Parks commented on PUP-5849 Re: Newline is not sufficient to avoid parsing as a function call Rad. Again, I care less about this being an error, then having a clear error message. I keep running into it, since `[$arr1 + $arr2].each …` is a pattern I use in other languages. I haven't thought of a better error message, though. Perhaps adding output that shows the error in context, and identifies the function call. I will think on it more. 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-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Peter Huene commented on PUP-5849 Re: Newline is not sufficient to avoid parsing as a function call $ puppetcpp parse foo.pp statements: - kind: binary first: kind: variable begin: offset: 0 line: 1 end: offset: 2 line: 1
Jira (PUP-5993) Possible intermittent test failure in registry_spec.rb
Title: Message Title Glenn Sarti created an issue Puppet / PUP-5993 Possible intermittent test failure in registry_spec.rb Issue Type: Bug Assignee: Unassigned Created: 2016/03/01 9:29 AM Priority: Trivial Reporter: Glenn Sarti During a different PR (PUP-5991) the registry_spec test failed but then passed when the CI test was started again. The registry code was changed a while ago to guard against memory buffer overruns but perhaps not all of the code was corrected. Test Failure; [00:37:29] Failures: [00:37:29] [00:37:29] 1) Puppet::Util::Windows::Registry#values when reading values should return REG_MULTI_SZ values [00:37:29] Failure/Error: expect(written).to
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-2487
Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Change By:
Nick Walker
Currently we store report-ttl days of events in the resource_events table in the puppetdb database. Some customer customers have performance issues using the API endpoints that read from resource_events that could be mitigated or resolved by reducing the number of days of events that are stored in that table. In cases where customers would like to store more reports like 30-60 days of reports they may not desire storing that many days of events as events tend to be more useful for watching things that changed recently. I would be good to have an option to seperate these concerns and allow customers to tune in production for their own preferences. Side note: I'm not tied to the name "resource-events-ttl" I just figured people would know what I meant by reading that. {code}DELETE FROM resource_events WHERE timestamp < NOW() - INTERVAL '4 days';{code}
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-2488) Don't accept trailing garbage in query string
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2488 Don't accept trailing garbage in query string Issue Type: Bug Assignee: Unassigned Created: 2016/03/01 9:20 AM Priority: Normal Reporter: Rob Browning Right now, this will succeed, returning all facts, and it shouldn't: curl -X GET http://localhost:8080/pdb/query/v4?pretty=true --data-urlencode 'query=["from","facts"] ["not" ["=", "certname", "security-sensitive-host"]]' Add Comment
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-2487
Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Change By:
Nick Walker
Currently we store report-ttl days of events in the resource_events table in the puppetdb database. Some customer have performance issues using the API endpoints that read from resource_events that could be mitigated or resolved by reducing the number of days of events that are stored in that table. In cases where customers would like to store more reports like 30-60 days of reports they may not desire storing that many days of events as events tend to be more useful for watching things that changed recently. I would be good to have an option to seperate these concerns and allow customers to tune in production for their own preferences. Side note: I'm not tied to the name "resource-events-ttl" I just figured people would know what I meant by reading that. {code}DELETE FROM resource_events WHERE timestamp < NOW() - INTERVAL '4 days';{code}
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-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Nick Walker created an issue PuppetDB / PDB-2487 Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Issue Type: Improvement Affects Versions: PDB 4.0.0 Assignee: Unassigned Created: 2016/03/01 9:12 AM Labels: tcse Priority: Normal Reporter: Nick Walker Currently we store report-ttl days of events in the resource_events table in the puppetdb database. Some customer have performance issues using the API endpoints that read from resource_events that could be mitigated or resolved by reducing the number of days of events that are stored in that table. In cases where customers would like to store more reports like 30-60 days of reports they may not desire storing that many days of events as events tend to be more useful for watching things that changed recently. I would be good to have an option to seperate these concerns and allow customers to tune in production for their own preferences. Side note: I'm not tied to the name "resource-events-ttl" I just figured people would know what I meant by reading that.
Jira (PDB-2486) PuppetDB crashes during startup migration with namespaced trgm indices
Title: Message Title Russell Mull commented on PDB-2486 Re: PuppetDB crashes during startup migration with namespaced trgm indices Hi Nick Moriarty, Can you tell us a more about your PostgreSQL setup? How are you getting PuppetDB to run outside the 'public' schema? Did you (or whoever is running the DB) set search_path for your user to '$user,public' or something similar? Russ 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-2477) Refactor GC processes to avoid cascades
Title: Message Title Nick Walker commented on PDB-2477 Re: Refactor GC processes to avoid cascades Ryan Senior I added a gist of some different options. I implemented a temp table version and a CTE version of the report-ttl and node-purge-ttl GC queries. Then I noodled over if they could be combined and I made a version of that at the end of the gist that puts the certnames being deleted into a temp table during node-purge-ttl and then uses it during report-ttl as well. If node-purge-ttl is not enabled then an empty temp table is created so that the code is compatible in both use cases. https://gist.github.com/npwalker/4ea81e5c1eba01535967 I'd like to make an attempt at performance testing the options but I would need some guidance on what would be a good way to test and provide data on the options. I have to assume the CTE versions are faster because they don't need to perform an upfront select to find out what rows to delete and instead delete the rows and return the results for use in other queries but you never 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2477) Refactor GC processes to avoid cascades
Title: Message Title Nick Walker assigned an issue to Nick Walker PuppetDB / PDB-2477 Refactor GC processes to avoid cascades Change By: Nick Walker Assignee: Nick Walker 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-5863) Static catalog (manual) acceptance: Old agents function as before, no static catalog, Story PUP-5532, PUP-5536
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5863 Static catalog (manual) acceptance: Old agents function as before, no static catalog, Story PUP-5532, PUP-5536 Change By: Sean Griffin Assignee: Sean Griffin 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-2486) PuppetDB crashes during startup migration with namespaced trgm indices
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2486 PuppetDB crashes during startup migration with namespaced trgm indices Change By: Ryan Senior Sprint: PuppetDB 2016-03-23 Scrum Team: 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 (PDB-2486) PuppetDB crashes during startup migration with namespaced trgm indices
Title: Message Title Nick Moriarty created an issue PuppetDB / PDB-2486 PuppetDB crashes during startup migration with namespaced trgm indices Issue Type: Bug Affects Versions: PDB 2.3.8 Assignee: Unassigned Created: 2016/03/01 6:43 AM Environment: PuppetDB 2.3.8-1puppetlabs1 on Ubuntu 14.04 Running against PostgreSQL 9.5 Priority: Normal Reporter: Nick Moriarty Our PuppetDB instance runs against a managed PostgreSQL service hosting multiple databases. This means that indices end up being created under the 'puppetdb' namespace rather than the 'public' one. With pg_trgm indices enabled, PuppetDB crashes at startup as it tries to create duplicate indices during the migration operation. This is because it ends up looking in the 'public' namespace by default. In storage-utils, the default namespace for testing whether an index exists is 'public', which is not necessarily correct for a given deployment. The result is a BatchUpdateException, which kills the PuppetDB application straight away.
Jira (PUP-5969) Include built-in resource types in resource profiling
Title: Message Title Henrik Lindberg assigned an issue to Matthaus Owens Puppet / PUP-5969 Include built-in resource types in resource profiling Change By: Henrik Lindberg Assignee: Matthaus Owens 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-5969) Include built-in resource types in resource profiling
Title: Message Title Henrik Lindberg commented on PUP-5969 Re: Include built-in resource types in resource profiling Matthaus Owens Is there an example of when this would have been of value? The difference between ruby defined resources and user defined is that the former does not really have a body that gets evaluated. Therefore there is not much to profile. What remains is possibly some munging or validation. (I may also be wrong, and that you can write code that indeed takes time when compiling). I can imagine that in aggregate the information would be of interest - i.e. the number of resources, it is very likely that all ruby resource types take an equal amount of time. 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-2695) deprecate that defining a class twice "merges" their behaviors
Title: Message Title Henrik Lindberg commented on PUP-2695 Re: deprecate that defining a class twice "merges" their behaviors PUP-5954 is the removal ticket (i.e. change to always bee an error), targeted at puppet 5.0.0 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-5954) Change deprecation from PUP-2695 (merge class) to error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5954 Change deprecation from PUP-2695 (merge class) to error Change By: Henrik Lindberg Component/s: 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-5954) Change deprecation from PUP-2695 (merge class) to error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5954 Change deprecation from PUP-2695 (merge class) to error Change By: Henrik Lindberg Summary: Create removal ticket for 5.0.0 Change deprecation from PUP-2695 (merge class) to error 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.
