Jira (PUP-6893) Remove Ruby 1.9.3 support
Title: Message Title Henrik Lindberg commented on PUP-6893 Re: Remove Ruby 1.9.3 support Since puppet is also used as a gem this cannot be done until a major release. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6894) Remove Ruby 1.9.3 related pinning of addressable gem in Puppets Gemfile
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6894 Remove Ruby 1.9.3 related pinning of addressable gem in Puppets Gemfile Change By: Ethan Brown Summary: Remove Ruby 1.9.3 related pinning of addressable gem in Puppets Gemfile Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6894) Remove Ruby 1.9.3 related pinning of
Title: Message Title Ethan Brown created an issue Puppet / PUP-6894 Remove Ruby 1.9.3 related pinning of Issue Type: Task Affects Versions: PUP 4.8.0 Assignee: Unassigned Created: 2016/11/04 4:47 PM Priority: Normal Reporter: Ethan Brown https://github.com/puppetlabs/puppet/pull/5362 was performed to fix issues running on Ruby 1.9.3 caused by the addressable gem. When 1.9.3 support is removed from Puppet, the addressable pin can be removed. Add Comment
Jira (PUP-6893) Remove Ruby 1.9.3 support
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6893 Remove Ruby 1.9.3 support Change By: Ethan Brown Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6893) Remove Ruby 1.9.3 support
Title: Message Title Ethan Brown created an issue Puppet / PUP-6893 Remove Ruby 1.9.3 support Issue Type: Epic Assignee: Unassigned Created: 2016/11/04 4:44 PM Priority: Normal Reporter: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6892) Extending lookup: JSON/YAML/HOCON files
Title: Message Title Lindsey Smith created an issue Puppet / PUP-6892 Extending lookup: JSON/YAML/HOCON files Issue Type: Story Assignee: Unassigned Created: 2016/11/04 4:32 PM Priority: Normal Reporter: Lindsey Smith As the maintainer of non-hiera data stored in YAML/JSON/HOCON files, I want to be able to extend lookup to understand my data files so that my information can used by puppet in a manner consistent with everyday hiera usage. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6884) Lookup default data syntax and usage for module authors
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-6884 Lookup default data syntax and usage for module authors Change By: Lindsey Smith Summary: Lookup default data syntax and usage for module authors Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6891) Extending lookup: data structures that require transformation
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-6891 Extending lookup: data structures that require transformation Change By: Lindsey Smith As the owner of an external data source, I want to be able to extend lookup to fetch structured data from my source and process or transform it so that my information can used by puppet in a manner consistent with everyday hiera usage. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6891) Extending lookup: data structures that require transformation
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-6891 Extending lookup: data structures that require transformation Change By: Lindsey Smith Summary: Extending lookup: data structures that require transformation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6891) Extending lookup: data structures
Title: Message Title Lindsey Smith created an issue Puppet / PUP-6891 Extending lookup: data structures Issue Type: Story Assignee: Unassigned Created: 2016/11/04 4:21 PM Priority: Normal Reporter: Lindsey Smith As the owner of an external data source, I want to be able to extend lookup to fetch structured data from my source so that my information can used by puppet in a manner consistent with everyday hiera usage. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6890) Extending lookup: key/value data
Title: Message Title Lindsey Smith created an issue Puppet / PUP-6890 Extending lookup: key/value data Issue Type: Story Assignee: Unassigned Created: 2016/11/04 4:20 PM Priority: Normal Reporter: Lindsey Smith As the owner of an external data source, I want to be able to extend lookup to fetch key/value pairs from my source so that my information can used by puppet in a manner consistent with everyday hiera usage. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6889) Expressing params.pp as lookup static data
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-6889 Expressing params.pp as lookup static data Change By: Lindsey Smith As a module author currently using the params.pp pattern, I want to use a lookup data provider instead so that not all keys/values have to be computed even if not used so I can make my module perform better. Three key/value function types are supported for data that needs computation: * Data files that directly represents a data structure in json/yaml/hocon* An external service (see also PUP-6867)* Algorithmical (PUP=6868)* Note:* need an example of doing this with an existing module. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6889) Expressing params.pp as lookup static data
Title: Message Title Lindsey Smith created an issue Puppet / PUP-6889 Expressing params.pp as lookup static data Issue Type: Story Assignee: Unassigned Created: 2016/11/04 4:14 PM Priority: Normal Reporter: Lindsey Smith As a module author currently using the params.pp pattern, I want to use a lookup data provider instead so that not all keys/values have to be computed even if not used so I can make my module perform better. Note: need an example of doing this with an existing module. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6889) Expressing params.pp as lookup static data
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-6889 Expressing params.pp as lookup static data Change By: Lindsey Smith Team: Puppet Developer Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6474) Incorporate gettext_setup gem into puppet
Title: Message Title Branan Riley commented on PUP-6474 Re: Incorporate gettext_setup gem into puppet Glenn Sarti I am focused on 1.8.x regressions and on support escalations right now. Since this is realistically an agent 1.9 or 2.0 feature, It's fallen down my priority ladder. If somebody else on the team wants to take it up I will happily assist in hand-off. If not, it is probably stalled until I can look at it again. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6474) Incorporate gettext_setup gem into puppet
Title: Message Title Maggie Dreyer commented on PUP-6474 Re: Incorporate gettext_setup gem into puppet I'd be happy to try to take it up if you can tell me what still needs to be done. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6871) spec/unit/transaction/persistence_spec.rb includes a spec test that fails on non-US English Windows platforms
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-6871 spec/unit/transaction/persistence_spec.rb includes a spec test that fails on non-US English Windows platforms Change By: Glenn Sarti Assignee: Ethan Brown Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6474) Incorporate gettext_setup gem into puppet
Title: Message Title Glenn Sarti commented on PUP-6474 Re: Incorporate gettext_setup gem into puppet Have we had any traction on this? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6862) Lookup doesn't interpolate values into hash keys
Title: Message Title Thomas Hallgren commented on PUP-6862 Re: Lookup doesn't interpolate values into hash keys This is per design. Interpolating keys would require eager interpolation of all keys at initialization time. Lookup uses lazy interpolation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 Ethan Brown updated an issue Puppet / PUP-5995 Stray UTF-8 character in manifest corrupts parsed parameters Change By: Ethan Brown Labels: utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6883) Unlisted module dependency in metadata.json results in weird errors
Title: Message Title
Rune Juhl Jacobsen updated an issue
Puppet / PUP-6883
Unlisted module dependency in metadata.json results in weird errors
Change By:
Rune Juhl Jacobsen
Changing our modules to use Hiera instead of params.pp meant that some of our modules got a metadata.json file which had been missing before. As dependencies seem to be enforced religiously when a module has a metadata.json file, this has been the cause of some weird errors.Without metadata.json dependencies would be resolved just fine. With a metadata.json with a unlisted dependency on a module providing a function we got errors like the following:{noformat}Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error:Error while evaluating a Function Call, Scope variable name false is a FalseClass, not a string at /etc/puppetlabs/code/envs/rune/modules/enableit/profile/manifests/storage/nas.pp:32:3 at /etc/puppetlabs/code/envs/rune/modules/enableit/profile/manifests/storage/nas.pp:19 on node testnode1.enableit{noformat}The cause of this is a bit weird. During our transition to Puppet 4 we ended up having two Ruby functions with the same name, one with a Puppet 3.x autoloader format path ({{lib/puppet/parser/functions/confine.rb}}) and the other with a Puppet 4.x autoloader format path ({{lib/puppet/functions/confine.rb}}). The autoloader format can be seen here: https://github.com/puppetlabs/puppet-specifications/blob/master/language/func-api.md#autoloading .* With both autoloader functions in place and missing a metadata.json, everything would work* With both functions and a metadata.json missing a dependency on the module containing the functions, we would get errors like the above* With both functions and a proper metadata.json, everything would work* With both functions missing and a proper metadata.json, we'd get an "Unknown function" error, as expectedWe probably hit an edge case, but the weird error message meant that it took quite a while to figure out what went wrong. The error did point to the correct line, but since we've used the function both before and after Puppet 4.x it wasn't obvious why we got an error, and especially why the error complained about types.I'm not sure how this should be resolved either. Perhaps look for duplicate function declarations in modules that have a metadata.json file? R
Add Comment
Jira (PUP-6888) HOCON backend for puppet lookup
Title: Message Title Lindsey Smith created an issue Puppet / PUP-6888 HOCON backend for puppet lookup Issue Type: Story Assignee: Unassigned Created: 2016/11/04 2:35 PM Priority: Normal Reporter: Lindsey Smith As puppet lookup user, I would like to capture my hiera data in HOCON format so that I can work in a file format consistent with the rest of Puppet while also taking advantage of HOCON for things like ability to add comments. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6888) HOCON backend for puppet lookup
Title: Message Title Lindsey Smith assigned an issue to Lindsey Smith Puppet / PUP-6888 HOCON backend for puppet lookup Change By: Lindsey Smith Assignee: Lindsey Smith Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6823) Puppet filebucket command does not pick up proper server address from server_list config property
Title: Message Title Branan Riley commented on PUP-6823 Re: Puppet filebucket command does not pick up proper server address from server_list config property Mateusz Gozdek We might end up un-deprecating server. The host selection in various layers of Puppet's network code isn't always as clean as we'd like, and it is at this point probably not possible to totally unset server. In addition, the work we are doing for HA in Puppet Enterprise isn't going to want to unset server when we set server_list, and we don't want to warn users all the time when both are set. See PUP-6885 for details on how I view the situation. This is an ongoing internal discussion, put for now I would say that ignoring the deprecation warning might be reasonable. It may go away soon. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6887) Compatibility with hiera 3 YAML files
Title: Message Title Lindsey Smith created an issue Puppet / PUP-6887 Compatibility with hiera 3 YAML files Issue Type: Story Assignee: Unassigned Created: 2016/11/04 2:22 PM Priority: Normal Reporter: Lindsey Smith As a hiera v3 user with YAML data files, I want to get the same results from lookup as I do witih classic hiera without modifying my YAML data files so that I can begin adopting lookup without having to worry about modifying my hiera data first. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6886) Compatibility with hiera 3 JSON files
Title: Message Title Lindsey Smith created an issue Puppet / PUP-6886 Compatibility with hiera 3 JSON files Issue Type: Story Assignee: Unassigned Created: 2016/11/04 2:22 PM Priority: Normal Reporter: Lindsey Smith As a hiera v3 user with JSON data files, I want to get the same results from lookup as I do witih classic hiera without modifying my JSON data files so that I can begin adopting lookup without having to worry about modifying my hiera data first. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6885) Remove warning about server_list and server conflicting
Title: Message Title Branan Riley created an issue Puppet / PUP-6885 Remove warning about server_list and server conflicting Issue Type: Improvement Assignee: Unassigned Created: 2016/11/04 2:21 PM Fix Versions: PUP 4.8.1 Priority: Normal Reporter: Branan Riley When we added server_list, it was under the idea that it was a path to deprecating the server setting. Currently, a warning is printed at Puppet startup when both settings are set. In addition, for non-agent commands, we will use one of an edpoint-specific setting, the first entry of server_list, or the server setting, depending on the particular command and how it interacts with the netcode. All of this is super complicated, and makes things bad for users for a number of reasons. The big ones are: Our netcode is incredibly complex, and in many ways smeared across several layers of abstraction. This makes it very hard to understand all the ways that the server setting could sneak in In the PE HA world, the server_list setting will be managed by puppet, but because we have not previously managed the server setting, we can't safely remove that old setting (since that might conflict with a user's resource that manages server). My
Jira (PUP-6884) Lookup syntax and usage for module authors
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-6884 Lookup syntax and usage for module authors Change By: Lindsey Smith As a module author, I want to specify class parameter defaults so that consumers of my module only have to override the parameters that they need to be different. *Note:* my assumption is that this ticket is about the validation and documentation for class parameter default values because the implementation is covered elsewhere. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6884) Lookup syntax and usage for module authors
Title: Message Title Lindsey Smith created an issue Puppet / PUP-6884 Lookup syntax and usage for module authors Issue Type: Story Assignee: Unassigned Created: 2016/11/04 2:16 PM Priority: Normal Reporter: Lindsey Smith As a module author, I want to specify class parameter defaults so that consumers of my module only have to override the parameters that they need to be different. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6808) Global defaults do not override `undef` parameters
Title: Message Title Michael Smith updated an issue Puppet / PUP-6808 Global defaults do not override `undef` parameters Change By: Michael Smith Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6813) module face: `install` should report back on which dependencies were not satisfiable
Title: Message Title Michael Smith assigned an issue to Hailee Kenney Puppet / PUP-6813 module face: `install` should report back on which dependencies were not satisfiable Change By: Michael Smith Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6813) module face: `install` should report back on which dependencies were not satisfiable
Title: Message Title Michael Smith updated an issue Puppet / PUP-6813 module face: `install` should report back on which dependencies were not satisfiable Change By: Michael Smith Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6814) Filebucket fails with recursive backup
Title: Message Title Michael Smith updated an issue Puppet / PUP-6814 Filebucket fails with recursive backup Change By: Michael Smith Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6815) Reserved characters in class/type parameters are not enforced
Title: Message Title Michael Smith updated an issue Puppet / PUP-6815 Reserved characters in class/type parameters are not enforced Change By: Michael Smith Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6815) Reserved characters in class/type parameters are not enforced
Title: Message Title Michael Smith updated an issue Puppet / PUP-6815 Reserved characters in class/type parameters are not enforced Change By: Michael Smith Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6822) Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist
Title: Message Title Michael Smith updated an issue Puppet / PUP-6822 Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist Change By: Michael Smith Acceptance Criteria: Linux says nothing happens, Windows and OS X will error. Not clear what which is the consistent cross-platform behavior would be better approach , needs investigation but it should be consistent . Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6822) Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist
Title: Message Title Michael Smith updated an issue Puppet / PUP-6822 Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist Change By: Michael Smith Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6809) http report processor does not show error messages from remote server
Title: Message Title Josh Cooper commented on PUP-6809 Re: http report processor does not show error messages from remote server Closing per last comment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6822) Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist
Title: Message Title Michael Smith updated an issue Puppet / PUP-6822 Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist Change By: Michael Smith Acceptance Criteria: Not clear what the consistent cross-platform behavior would be, needs investigation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6823) Puppet filebucket command does not pick up proper server address from server_list config property
Title: Message Title Michael Smith updated an issue Puppet / PUP-6823 Puppet filebucket command does not pick up proper server address from server_list config property Change By: Michael Smith Sprint: Puppet Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6823) Puppet filebucket command does not pick up proper server address from server_list config property
Title: Message Title Michael Smith assigned an issue to Josh Cooper Puppet / PUP-6823 Puppet filebucket command does not pick up proper server address from server_list config property Change By: Michael Smith Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6188) Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8
Title: Message Title Ethan Brown commented on PUP-6188 Re: Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8 Some initial notes after discussing with Josh: SSL related files are already encoded in an ASCII 7-bit compatible format when written to disk, so specifying UTF-8 for those files shouldn't be necessary - instead use ASCII inside Ruby when reading / writing these files Changing the process of reading / writing system files like crontab should likely not be forced to UTF-8, and should continue to remain in the systems current encoding, which is the default for how Ruby reads files (i.e. Encoding.default_external). There is a difference between managing Puppet data files, which should always be UTF-8, and system data files which are often subject to the encoding specified on the system. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6865) puppet 4.8.0 breaks code that uses strftime()
Title: Message Title Michael Smith commented on PUP-6865 Re: puppet 4.8.0 breaks code that uses strftime() Thomas Hallgren this looks like something that might've been broken by your work on time. Can you take a look? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6865) puppet 4.8.0 breaks code that uses strftime()
Title: Message Title Michael Smith assigned an issue to Thomas Hallgren Puppet / PUP-6865 puppet 4.8.0 breaks code that uses strftime() Change By: Michael Smith Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6865) puppet 4.8.0 breaks code that uses strftime()
Title: Message Title Michael Smith updated an issue Puppet / PUP-6865 puppet 4.8.0 breaks code that uses strftime() Change By: Michael Smith Team: Puppet Developer Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1479) Occasional stack overflow triggered by Facter::EC2::Base
Title: Message Title Maggie Dreyer commented on FACT-1479 Re: Occasional stack overflow triggered by Facter::EC2::Base The PR for this ticket was merged back in August and appears to have passed CI since then. Closing this as fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1478) EC2 facts intermittently unavailable due to overly optimistic timeouts
Title: Message Title Maggie Dreyer commented on FACT-1478 Re: EC2 facts intermittently unavailable due to overly optimistic timeouts The PR for this was merged back in August and appears to have passed CI since then. Closing as fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6846) Obscure error messages caused by error in metadata.json of a module.
Title: Message Title Michael Smith updated an issue Puppet / PUP-6846 Obscure error messages caused by error in metadata.json of a module. Change By: Michael Smith Acceptance Criteria: Facter should not fail because of errors in metadata.json of some module that has no relation with facter. The error messages should be more explicit ; specifically that metadata . json in a module does not match an expected format/schema. This is not related to Facter (though from the output you can be mislead into believing it is). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6846) Obscure error messages caused by error in metadata.json of a module.
Title: Message Title Michael Smith updated an issue Puppet / PUP-6846 Obscure error messages caused by error in metadata.json of a module. Change By: Michael Smith Sprint: Puppet Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3158) puppet query gives rust error when piped to a program that doesn't read its output
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-3158 puppet query gives rust error when piped to a program that doesn't read its output Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2987) i18n PuppetDB dependencies (stockpile and structured logging)
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2987 i18n PuppetDB dependencies (stockpile and structured logging) Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3172) Fix GC API JIRA ticket
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3172 Fix GC API JIRA ticket Issue Type: Bug Assignee: Unassigned Created: 2016/11/04 1:12 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-129) 4.x function overload tags not parsed if the overload is missing a docstring
Title: Message Title
William Hopper updated an issue
Puppet Strings / PDOC-129
4.x function overload tags not parsed if the overload is missing a docstring
Change By:
William Hopper
Acceptance Criteria:
Given the following 4.x function, both overloads in the JSON output should include a parameter and return tag:{code}# Subtracts two things.Puppet::Functions.create_function(:subtract) do # @param x The first integer. # @param y The second integer. # @return [Integer] Returns x - y. # @example Subtracting two integers. # subtract(5, 1) => 4 dispatch :subtract_ints doparam 'Integer', :xparam 'Integer', :y end # Here is a docstring # @param x The first array. # @param y The second array. # @return [Array] Returns x - y. # @example Subtracting two arrays. # subtract([3, 2, 1], [1]) => [3, 2] dispatch :subtract_arrays doparam 'Array', :xparam 'Array', :y end def subtract_ints(x, y)x - y end def subtract_arrays(x, y)x - y endend{code}
Story Points:
1
Sprint:
PDS 2016-11-16
Fix Version/s:
PDOC 1.0.0
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-129) 4.x function overload tags not parsed if the overload is missing a docstring
Title: Message Title William Hopper assigned an issue to William Hopper Puppet Strings / PDOC-129 4.x function overload tags not parsed if the overload is missing a docstring Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6860) puppet on solaris 11 should support exists? for services
Title: Message Title
Shawn Ferry commented on PUP-6860
Re: puppet on solaris 11 should support exists? for services
I think PR 5322 will eventually be associated here automatically.
With that change you will be able to check that it is absent but you will not be able to enforce that it is absent. Service doesn't have the capability of managing the existence of services that is more the realm of pkg and maybe svccfg.
puppet resource service svc:/network/talk:bogus ensure=absent
service { 'svc:/network/talk:bogus':
ensure => 'absent',
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc
Title: Message Title Garrett Guillotte commented on FACT-1441 Re: Add "virtualization" fact that identifies AWS, Azure, etc For cloud platforms/providers, we don't use platform or provider as core fact names, but I imagine those would be at least as likely to collide with custom facts. We also don't use stack, which Azure and AWS both use to describe broad collections of tools and infrastructure that comprise a cloud service, though not in a consistent way (for instance, the more specific use of stack w/r/t OpsWorks, or Microsoft's "Azure Stack" on-premises product that's distinct from Azure as a cloud service). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6860) puppet on solaris 11 should support exists? for services
Title: Message Title Shawn Ferry updated an issue Puppet / PUP-6860 puppet on solaris 11 should support exists? for services Change By: Shawn Ferry Summary: puppet on solaris 11 cannot distinguish between non-existent and stopped should support exists? for services Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-44) Puppet strings crashes when documenting Puppet's regsubst.rb
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-44 Puppet strings crashes when documenting Puppet's regsubst.rb Change By: William Hopper Summary: Puppet strings crashes when documenting Puppet's egsubst regsubst .rb Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1472) Ensure the collection has enough information about exeternal facts to cache them.
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1472 Ensure the collection has enough information about exeternal facts to cache them. Change By: Maggie Dreyer Currently only caching of core facts is supported. Since this is done based on resolvers, the internal process for caching external facts might look quite different. This ticket is intended to track the investigation of what work would be needed to allow the caching of external facts by name, analogous to the UX of caching by group name for core facts. That work also includes updating the command line option which lists cachable facts to include external facts. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1470) Add the ability for the Collection to cache the output of resolvers
Title: Message Title Maggie Dreyer commented on FACT-1470 Re: Add the ability for the Collection to cache the output of resolvers Closing this as a duplicate of FACT-348 , which implemented fact caching and was released as part of the configurable Facter work in Facter 3.5.0. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1441) Add "virtualization" fact that identifies AWS, Azure, etc
Title: Message Title
Gareth Rushgrove commented on FACT-1441
Re: Add "virtualization" fact that identifies AWS, Azure, etc
So, naming is hard.
This issues goes from a specific need "We should add a fact that determines whether or not a VM is running in Azure" to a general solution:
"virtualization": {
"hypervisor": "kvm",
"cloud": {
"provider": "azure",
"metadata": ...
}
But I think their is an assumption in the proposed structure which isn't explicit, and which I think is wrong. It assumes that a cloud provider is providing virtual machines running on top of a hypervisor. That's not 100% true of, for instance, Packet or Softlayer or Oracle Cloud. For instance the following would not make sense, because Packet isn't using virtualization.
"virtualization": {
"cloud": {
Jira (FACT-1471) Ensure the Collection has enough information about Ruby facts to cache their output
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1471 Ensure the Collection has enough information about Ruby facts to cache their output Change By: Maggie Dreyer Currently only caching of core facts is supported. Since this is done based on resolvers, the internal process for caching Ruby facts might look quite different. This ticket is intended to track the investigation of what work would be needed to allow the caching of Ruby facts by name, analogous to the UX of caching by group name for core facts. This includes updating the command line option which lists cachable facts to include Ruby facts. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1471) Ensure the Collection has enough information about Ruby facts to cache their output
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1471 Ensure the Collection has enough information about Ruby facts to cache their output Change By: Maggie Dreyer Currently only caching of core facts is supported. Since this is done based on resolvers, the internal process for caching Ruby facts might look quite different. This ticket is intended to track the investigation of what work would be needed to allow the caching of Ruby facts by name, analogous to the UX of caching by group name for core facts. This That work also includes updating the command line option which lists cachable facts to include Ruby facts. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1473) Add CLI flags to interact with the fact cache
Title: Message Title Maggie Dreyer commented on FACT-1473 Re: Add CLI flags to interact with the fact cache Closing this as a duplicate of FACT-1509 and FACT-1511 . Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6860) puppet on solaris 11 cannot distinguish between non-existent and stopped services
Title: Message Title Shawn Ferry assigned an issue to Shawn Ferry Puppet / PUP-6860 puppet on solaris 11 cannot distinguish between non-existent and stopped services Change By: Shawn Ferry Assignee: Shawn Ferry Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-518) Document how to make hiera_xxx functions delegate to lookup()
Title: Message Title Nicholas Fagerlund commented on HI-518 Re: Document how to make hiera_xxx functions delegate to lookup() Reid Vandewiele and Nick Walker Okay, just to be clear: what the docs are going to say about this is something like the following: To fully enable Puppet lookup: Put a lookup.yaml file in any environment that contains hiera data. Put a lookup.yaml file in $confdir. Download this manifest file (enable_lookup.pp) and put it in the manifests directory of each environment. (You can skip this step, but if you do, the classic hiera, hiera_array, hiera_hash, and hiera_include functions cannot use lookup's advanced features.) In other words, we're going to frame it as just a normal part of enabling lookup in an environment, and we'll have the file available for download. Does that allay your concerns? I think switching the hiera functions is super important, but I also think it MUST be opt-in as part of switching to lookup, unless we're going to cut a new major version. The workflow here (add a lookup.conf file, add a file to the manifests dir) seems lightweight enough to not block adoption. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving
Jira (PUP-6880) Initial migration from hiera v3 to v5
Title: Message Title Henrik Lindberg commented on PUP-6880 Re: Initial migration from hiera v3 to v5 Here I think it is important to consider the user having a mix of classic hiera use in some environments, and modern v5 lookup in some. With a mix, there is a risk that data files ends up being used both by classic hiera / global and in lookup with the effect that the hiera implementation will win - when doing deep merges this may produce strange effects in addition to being slower. We need to show the correct way of converting env by env. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources One thing that has changed is that create_resources now uses the exact same evaluation order as if the corresponding resources were created in a manifest. This can have an effect on the order in which the resources are applied, but is primarily only an evaluation order difference. Earlier, all resources created with create_resources where fully evaluated and placed in the catalog at the time the create_resources call finishes. Now they are placed on the lazy resource evaluation queue just like resources created in manifests. If you happen to have logic that depends on resources being in the catalog, then it may produce something different after the change. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3171 query compilation is very slow for queries with giant arrays Issue Type: Bug Assignee: Unassigned Attachments: query.json Created: 2016/11/04 10:07 AM Priority: Normal Reporter: Wyatt Alt Nick Lewis alerted me that queries like the attached take a long time (30s+) to compile. I did some crude sampling of stack dumps and it looks like (unsurprisingly) we're spending most of that time in pre-order-visit. We should do some targeted optimization of query compilation – even with 10k nodes in the array, 30s seems way excessive. The problem occurs with large numbers of "or" clauses as well, so there's no particular reason to think this issue is array-specific. Add Comment
Jira (PUP-5402) systemd: Puppet agent starts before network-online.target is reached
Title: Message Title Rene Rinco updated an issue Puppet / PUP-5402 systemd: Puppet agent starts before network-online.target is reached Change By: Rene Rinco Affects Version/s: PUP 4.8.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5402) systemd: Puppet agent starts before network-online.target is reached
Title: Message Title Rene Rinco commented on PUP-5402 Re: systemd: Puppet agent starts before network-online.target is reached The same here in RHEL7 with 4.8.0: [root@xl-ifr28 system]# rpm -qf /usr/lib/systemd/system/puppet.service puppet-agent-1.8.0-1.el7.x86_64 [root@xl-ifr28 system]# cat /usr/lib/systemd/system/puppet.service # Local settings can be configured without being overwritten by package upgrades, for example if you want to increase puppet open-files-limit to 1, you need to increase systemd's LimitNOFILE setting, so create a file named "/etc/systemd/system/puppet.service.d/limits.conf" containing: [Service] LimitNOFILE=1 You can confirm it worked by running systemctl daemon-reload then running systemctl show puppet | grep LimitNOFILE # [Unit] Description=Puppet agent Wants=basic.target After=basic.target network.target [Service] EnvironmentFile=-/etc/sysconfig/puppetagent EnvironmentFile=-/etc/sysconfig/puppet EnvironmentFile=-/etc/default/puppet ExecStart=/opt/puppetlabs/puppet/bin/puppet agent $PUPPET_EXTRA_OPTS --no-daemonize ExecReload=/bin/kill -HUP $MAINPID KillMode=process [Install] WantedBy=multi-user.target [root@xl-ifr28 system]# Add Comment
Jira (PDB-3170) Release a version of structured-logging with the i18n-related changes
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3170 Release a version of structured-logging with the i18n-related changes Issue Type: Improvement Assignee: Rob Browning Created: 2016/11/04 8:47 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDB-3138) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.3.0)
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3138 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.3.0) Change By: Rob Browning Assignee: Wyatt Alt Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3142) Go/no-go meeting (before noon PST) (PDB 4.3.0)
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3142 Go/no-go meeting (before noon PST) (PDB 4.3.0) Change By: Rob Browning Assignee: Wyatt Alt Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Andrew Grimberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources I'll have to do some testing for the catalogs but here's the answer for the other questions: All nodes are in the same environment IIRC this issues seems to only affect nagios exported resources. My environment uses exported resources liberally for setting up databases, webserver and haproxy proxy frontends, as well as backups, nfs, etc. When I get a chance today (maybe tomorrow if I have to) I'll try and run some scenarios in my test lab so I can answer that in more depth. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources Can you compare the catalog from a successful run with one that is failing? (eliminate compiler) Are the exporting and importing nodes in the same environment? (eliminate finding old export made in importing env). Is the problem specific to one type of resource - does a test with an export of something like a notify or file work? (eliminate configuration problems) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6883) Unlisted module dependency in metadata.json results in weird errors
Title: Message Title Henrik Lindberg commented on PUP-6883 Re: Unlisted module dependency in metadata.json results in weird errors Also, this error message is off "Scope variable name false is a FalseClass, not a string" - it looks like there is an attempt to find a variable using a Boolean false value instead of a String value for the variable name. That error is raised when calling Scope#setvar or Scope::lookupvar. That makes me suspect that there is faulty custom ruby code somewhere - the stack trace should tell where it is coming from (it could be from puppet). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Andrew Grimberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources I've given a trace from the client side as well. I'll point out that this only happens if the puppetserver is running on puppet-agent > 1.5.3. I have no issues with the recent puppet-agent against a puppet server that is configured with puppet-agent <= 1.5.3 So scenarios I've run: Server 1.5.3 Server 1.6.0 Server 1.7.0 Server 1.8.0 Remote Client 1.5.3 No issues Not tested Not tested Not tested Remote Client 1.6.0 No Issues Fails Fails Fails Remote Client 1.7.0
Jira (PUP-6883) Unlisted module dependency in metadata.json results in weird errors
Title: Message Title Henrik Lindberg commented on PUP-6883 Re: Unlisted module dependency in metadata.json results in weird errors Rune Juhl Jacobsen Can you supply the full stack trace from the error on the server for this? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources The earlier gist indicates that the problem is on the agent: Error: Puppet::Util::FileType::FileTypeFlat could not write /etc/nagios/conf.d/host_puppet.home.bardicgrove.org_puppet.home.bardicgrove.org.cfg: No such file or directory @ rb_sysopen - /etc/nagios/conf.d/host_puppet.home.bardicgrove.org_p uppet.home.bardicgrove.org.cfg This is when it is applying the catalog. I don't think there is anything wrong with the compiling side (i.e. the call to create_resources is not to blame). The problem seems to be in nagios. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-3169) command-test failures 11/4/2016 edition
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3169 command-test failures 11/4/2016 edition Issue Type: Bug Assignee: Unassigned Created: 2016/11/04 6:06 AM Labels: maintenance Priority: Normal Reporter: Ryan Senior Log snippet of the failures 00:15:26 lein test puppetlabs.puppetdb.command-test 00:15:45 The [database] classname setting has been retired and will be ignored. 00:15:45 The [database] subprotocol setting has been retired and will be ignored.
Jira (PUP-6883) Unlisted module dependency in metadata.json results in weird errors
Title: Message Title Rune Juhl Jacobsen created an issue Puppet / PUP-6883 Unlisted module dependency in metadata.json results in weird errors Issue Type: Bug Affects Versions: PUP 4.7.0 Assignee: Unassigned Created: 2016/11/04 5:58 AM Labels: metadata Priority: Normal Reporter: Rune Juhl Jacobsen Changing our modules to use Hiera instead of params.pp meant that some of our modules got a metadata.json file which had been missing before. As dependencies seem to be enforced religiously when a module has a metadata.json file, this has been the cause of some weird errors. Without metadata.json dependencies would be resolved just fine. With a metadata.json with a unlisted dependency on a module providing a function we got errors like the following: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error:
Jira (PUP-6862) Lookup doesn't interpolate values into hash keys
Title: Message Title Matteo Cerutti commented on PUP-6862 Re: Lookup doesn't interpolate values into hash keys I'm using 4.7, and I see the same issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6882) Incorrect handling of escape sequence precedence
Title: Message Title
Arnout Boks created an issue
Puppet / PUP-6882
Incorrect handling of escape sequence precedence
Issue Type:
Bug
Assignee:
Unassigned
Components:
Language
Created:
2016/11/04 12:48 AM
Priority:
Normal
Reporter:
Arnout Boks
Since Puppet 4 one can use Unicode escape sequences, which work fine:
$ puppet apply -e 'notify { "\u": }'
Notice: Compiled catalog for example.com in environment production in 0.11 seconds
Notice: �
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Angel L. Mateo commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources Small note, in your sample the construct @@omd_nagios_service should be quoted when given as an argument to create_resources - is it a typo in the ticket, or is that what you actually tried? It's a typo in the ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6861) [regression] Mount options not idempotent
Title: Message Title Thomas Kornack commented on PUP-6861 Re: [regression] Mount options not idempotent As Branan Riley suggested in his answer to PUP-6457 I'll gladly add some examples where the puppet agent remounts a share at every run and where fstab options and output of mount differ. All the cases did not occur prior to the update to puppet agent v1.8.0: 1st Example: (2 Hosts) Distro: Ubuntu 12.04.05 LTS FS type, issue: nfs, remout with every agent run fstab: some.ip.add.ress:/home/some.user /home/some.user nfs _netdev,vers=3,bg,soft,intr,retry=5 0 0 mtab: some.ip.add.ress:/home/some.user /home/some.user nfs rw,vers=3,bg,soft,intr,retry=5 0 0 2nd example: Distro: Ubuntu 14.04.05 LTS FS type, issue: tmpfs, remout with every agent run fstab: /dev/shm /var/lib/amavis/tmp tmpfs defaults,size=250m,mode=770,uid=amavis,gid=amavis 0 0 mtab:
Jira (PUP-6457) Mount resources could handle invalid options better
Title: Message Title Thomas Kornack commented on PUP-6457 Re: Mount resources could handle invalid options better As Branan Riley suggested in his answer to PUP-6457 I'll gladly add some examples where the puppet agent remounts a share at every run and where fstab options and output of mount differ. All the cases did not occur prior to the update to puppet agent v1.8.0: 1st Example: (2 Hosts) Distro: Ubuntu 12.04.05 LTS FS type, issue: nfs, remout with every agent run fstab: some.ip.add.ress:/home/some.user /home/some.user nfs _netdev,vers=3,bg,soft,intr,retry=5 0 0 mtab: some.ip.add.ress:/home/some.user /home/some.user nfs rw,vers=3,bg,soft,intr,retry=5 0 0 2nd example: Distro: Ubuntu 14.04.05 LTS FS type, issue: tmpfs, remout with every agent run fstab: /dev/shm /var/lib/amavis/tmp tmpfs defaults,size=250m,mode=770,uid=amavis,gid=amavis 0 0 mtab:
