Jira (PUP-7554) Puppet runs fail when hiera.yaml version 3 detected in a module
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7554 Puppet runs fail when hiera.yaml version 3 detected in a module Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-1800) Ruby downcase does not handle all unicode letters
Title: Message Title Henrik Lindberg commented on PUP-1800 Re: Ruby downcase does not handle all unicode letters Here is an article about the Unicode support in Ruby 2.4 http://www.sw.it.aoyama.ac.jp/2016/pub/IUC40-Ruby2.4/ I found that it follows Unicode 9.0.0 recommendations for handling of special characters in German, Turkish, etc. by making compromises. That is better than having to rely on Locale and having different behavior depending on it. This means that up/down-case operations work - but that the operation in reverse (upcase.downcase or downcase.upcase) is not guaranteed to produce the same result. This is good enough since Puppet is not a typesetting system I have yet to try out sorting and comparisons (<=>, <, >, etc) and operations like casecmp. (Article did not talk much about that) 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-7577) augeas does not error if no suitable lens found
Title: Message Title Steve Traylen created an issue Puppet / PUP-7577 augeas does not error if no suitable lens found Issue Type: Bug Affects Versions: PUP 4.8.1 Assignee: Unassigned Created: 2017/05/19 12:59 AM Environment: puppet-agent-1.8.2.10.g44e8319-1.ai7.x86_64 Labels: augeas Priority: Normal Reporter: Steve Traylen There are various similar reports but I could not find an existing bug. Running an augeas type when a suitable lens cannot be found results in no augeas change and so no puppet notification. Running pupept apply with augeas { 'testi
Jira (PUP-1800) Ruby downcase does not handle all unicode letters
Title: Message Title Henrik Lindberg commented on PUP-1800 Re: Ruby downcase does not handle all unicode letters Oh, the implementation is naturally filled with gotchas - see this article: http://blog.honeybadger.io/ruby-s-unicode-support/ Read through the list of tests in that post and cry... We may have to normalize all strings everywhere and that will have a huge performance impact. (Every JSON and YAML read for example). If we do nothing we get the new behavior and we will probably be seeing bug after bug in relation to use of unicode characters and non normalized strings. 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Henrik Lindberg commented on PUP-7431 Re: Upgrade vendored version of SemanticPuppet Thomas Hallgren regarding "release note" for an upgraded dependency - if the upgrade does not add any new features it almost certainly contains bugfixes. If it neither brings new features nor fixes any bugs visible to puppet users then it is probably not release note worthy. 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-7574) Introduce structured compare support for Hash Resource Properties
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7574 Introduce structured compare support for Hash Resource Properties Change By: Henrik Lindberg Summary: Introduce proper structured compare support for Hash properties Resource Properties 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Thomas Hallgren commented on PUP-7431 Re: Upgrade vendored version of SemanticPuppet Henrik Lindberg, that works for a monolith but doesn't scale very well. We need to be able to say that we've upgrade a dependency and reference the release notes for the appointed component. 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-7574) Introduce structured compare support for Hash Resource Properties
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7574 Introduce structured compare support for Hash Resource Properties Change By: Henrik Lindberg Component/s: DEV Component/s: Types and Providers 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-7574) Introduce structured compare support for Hash Resource Properties
Title: Message Title Henrik Lindberg commented on PUP-7574 Re: Introduce structured compare support for Hash Resource Properties While very interesting and worth having as a feature I don't think we should add this as a subclass to Parameter (as the PR for this does). The reason is that we want to be able to compare/diff any data type and that it is the data type or kind of wanted comparison that determines how it is done. All such cannot be determined a priori and can therefore not be implemented directly in 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-7578) parser settings per modulepath
Title: Message Title Christian S created an issue Puppet / PUP-7578 parser settings per modulepath Issue Type: New Feature Assignee: Unassigned Components: Compiler Created: 2017/05/19 1:38 AM Labels: strict_variables parser Priority: Normal Reporter: Christian S When developing puppet i would like to enforce strictness settings for my own modules. Since we use some modules from puppetforge this is not possible, because they sometimes fail the requirements. Therefore i have to disallow the setting for my own modules as well. Since we already have separate modulepaths for own and third party modules it would be great if i could just put relaxed strict settings on the third-party modulepath and use strict as the default.
Jira (PUP-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Henrik Lindberg commented on PUP-7431 Re: Upgrade vendored version of SemanticPuppet Sure, put the link in the release note? Include/highlight an important fix or important new feature that we show in our release note. 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-7578) parser settings per modulepath
Title: Message Title Henrik Lindberg commented on PUP-7578 Re: parser settings per modulepath Sorry, that is not possible as it would require us to track where every value during evaluation originated from (every integer, string, etc.). This because "strict" does not just apply to the language parsing/validation. 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-6977) Add variable for path of current module instance
Title: Message Title Henrik Lindberg commented on PUP-6977 Re: Add variable for path of current module instance If you do - make it a 4.x function, and include error handling for when a module is not found. 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Thomas Hallgren commented on PUP-7431 Re: Upgrade vendored version of SemanticPuppet Yep. I can do that. The original question still remains though. What type of release note is it? 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-7471) misleading error message with classname errors
Title: Message Title David Schmitt commented on PUP-7471 Re: misleading error message with classname errors Henrik Lindberg pushed https://github.com/puppetlabs/puppet/pull/5892 with a possible solution 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-7574) Introduce structured compare support for Hash Resource Properties
Title: Message Title Jairo Junior commented on PUP-7574 Re: Introduce structured compare support for Hash Resource Properties Thanks for your feedback. I figured that it could be used the same way as Puppet::Property::KeyValue (e.g. https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/group.rb#L150). But I did not payed attention to the fact that Property is a subclass of Parameter as you pointed out. One alternative - and less intrusive - approach would be to transform DeepHash in a module and include it in the property declaration: ``` newproperty(:state) do include DeepHash end ``` Regarding: The reason is that we want to be able to compare/diff any data type and that it is the data type or kind of wanted comparison that determines how it is done. I am not sure if I get it, cause after all I'm relying in Hash comparison, just need to determine what is managed before hand. 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-7471) misleading error message with classname errors
Title: Message Title Henrik Lindberg commented on PUP-7471 Re: misleading error message with classname errors That works, but needs a tweak to the error message (as noted in the review of the PR). 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-7471) misleading error message with classname errors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7471 misleading error message with classname errors Change By: Henrik Lindberg Fix Version/s: PUP 5.0.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-7471) misleading error message with classname errors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7471 misleading error message with classname errors Change By: Henrik Lindberg Release Notes Summary: handling of corner case - not release note worthy Release Notes: Not Needed 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-7471) misleading error message with classname errors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7471 misleading error message with classname errors Change By: Henrik Lindberg Component/s: Language 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-7471) misleading error message with classname errors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7471 misleading error message with classname errors Change By: Henrik Lindberg Story Points: 1 Team: Agent Puppet Developer Experience Sprint: PDE 2017-05-31 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-7471) misleading error message with classname errors
Title: Message Title Henrik Lindberg assigned an issue to David Schmitt Puppet / PUP-7471 misleading error message with classname errors Change By: Henrik Lindberg Assignee: David Schmitt 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-7574) Introduce structured compare support for Hash Resource Properties
Title: Message Title Henrik Lindberg commented on PUP-7574 Re: Introduce structured compare support for Hash Resource Properties If done as an inclusion this does not have to be in Puppet. We are currently working on trying to simplify the API of Resource types - this proposal goes in the other direction I am afraid. We need to be able compare two values in different context. When it is only known by the implementation you are forced to load the Ruby code that implements the type (or a particular provider for that type). That is not doable say in a user interface or other locations where it would mean executing arbitrary Ruby code. What is needed is instead a declarative approach where the data type of a value is defined and the rule for how instances of that data type compare is also declarative. As an example, we cannot differentiate on types in a catalog - it is not possible to see if "foo" is of the DeepMerging kind or not. To be able to do that you would need to embed the type of the parameter in the Catalog (and that does not work as things are now). We also have ongoing work similar to what you want to achieve - where the content consists of large XML structures modeled using our experimental support for rich data. We have not quite arrived at how to deal with deltas of structures and reporting, so not yet possible to explain how we think this should work. Right now we are busy with the Puppet 5.0.0 release, and will return to this after the 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Henrik Lindberg commented on PUP-7431 Re: Upgrade vendored version of SemanticPuppet As I understand it, the upgrade does not really bring new features to users, so use "bugfix". 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-6978) Distinguish errors in ClassInformationService response for class located in improper manifest file
Title: Message Title Henrik Lindberg commented on PUP-6978 Re: Distinguish errors in ClassInformationService response for class located in improper manifest file I believe we have a ticket in the "5.y Validation" epic about not accepting classes that are defined where they are forbidden (main focus on top scope). Details not worked out. When we have that, the things discussed here would be solved by that ticket since there would be errors from regular validation. It is however complex as users want to be able to validate a file out of context, and want to be able to experiment with snippets in a simple .pp file and use apply to figure out how things work. In any case, "5.y Validation" is a suitable epic - so I added this there. 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-170) exported resources with single element arrays aren't arrays on the collected side
Title: Message Title Rolf commented on PDB-170 Re: exported resources with single element arrays aren't arrays on the collected side We worked around it with puppetdb query. Fine to close it, can we update the docs to reflect this limitation? 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-6978) Distinguish errors in ClassInformationService response for class located in improper manifest file
Title: Message Title Henrik Lindberg commented on PUP-6978 Re: Distinguish errors in ClassInformationService response for class located in improper manifest file An option for the use cases here would be to include information if the class is autoloadable or not. Only those where there is a mapping from name to file can be autoloaded. (But the rules are more complex than a 1:1 name <=> file, as there is a search). 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-7574) Introduce structured compare support for Hash Resource Properties
Title: Message Title Jairo Junior commented on PUP-7574 Re: Introduce structured compare support for Hash Resource Properties OK. I'll try to follow the discussion of the new type system and check how it may help me. 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-3813) Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique
Title: Message Title Henrik Lindberg commented on PUP-3813 Re: Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique Don't know - the recent work on alias would if anything make it worse since it was about finding things that have aliases where it used to not find them. 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-3813) Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3813 Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique Change By: Henrik Lindberg Labels: needs_repro 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-3813) Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique
Title: Message Title Henrik Lindberg commented on PUP-3813 Re: Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique Needs to be reproduced on 4.x to see if there is still a problem (guess that it probably 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-3813) Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-3813 Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-3966) Short paths for source and template()
Title: Message Title Henrik Lindberg commented on PUP-3966 Re: Short paths for source and template() It needs to be backwards compatible. This means we cannot take a relative name to mean something other than what it used to mean. The functions makes a URI out of the given "path" and interprets "puppet:", then it either accepts an absolute file name or a relative. The relative must start with the a path segment that is the module name. For the references that are resolved via functions (for example 'template' and 'epp') we could accept a filename $f = "template.erb" (no path separators) to be resolved to the same as if $f = "$module_name/template.erb". For source it is more complicated as that happens much later when there is no $module_name variable to use. I could imagine using different URI schemes, a "self:template.erb" could resolve to "this module", a "module::foo::template.erb" to a template in module foo, etc. 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-4078) puppet resource tool output contains incorrect quoting
Title: Message Title Henrik Lindberg commented on PUP-4078 Re: puppet resource tool output contains incorrect quoting Ping Thomas Hallgren wonder if your recent work using string converter may have effect on this ticket as well ?? 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-3819) parser validate
Title: Message Title Henrik Lindberg commented on PUP-3819 Re: parser validate The input is a correct puppet language string. The interpolation is valid because a $varname interpolates that variable name and it stops at the right curly brace. The language can not know if this was intentional or not. Closing this as "Won't Do". 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-6517) undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6517 undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source Change By: Ethan Brown Sprint: Agent 2017-05-31 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-3800) hiera function reacts different based on order of loaded resources
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3800 hiera function reacts different based on order of loaded resources Change By: Henrik Lindberg Component/s: Platform Component/s: Hiera & Lookup 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-3800) hiera function reacts different based on order of loaded resources
Title: Message Title Henrik Lindberg commented on PUP-3800 Re: hiera function reacts different based on order of loaded resources The module_data module module is not part of puppet and should not be used as it has several 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-3394) Built-in variable referring to the path of the current environment
Title: Message Title Henrik Lindberg commented on PUP-3394 Re: Built-in variable referring to the path of the current environment IIRC this is a duplicate because I remember commenting on suggestions what the variable name should be... (Someone interested in this ticket can search in Jira and link it here). 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-3995) Prevent node resource names from potentially overlapping with other resources
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3995 Prevent node resource names from potentially overlapping with other resources Change By: Henrik Lindberg Labels: help_wanted needs_repro 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-3995) Prevent node resource names from potentially overlapping with other resources
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3995 Prevent node resource names from potentially overlapping with other resources Change By: Henrik Lindberg Component/s: Server Component/s: Compiler 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-3995) Prevent node resource names from potentially overlapping with other resources
Title: Message Title Henrik Lindberg commented on PUP-3995 Re: Prevent node resource names from potentially overlapping with other resources It would be great if someone could help write a unit test that shows a failure of a node named foo and a class foo. 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-7554) Puppet runs fail when hiera.yaml version 3 detected in a module
Title: Message Title Geoff Nichols commented on PUP-7554 Re: Puppet runs fail when hiera.yaml version 3 detected in a module PR #5887 was merged to puppet#stable at https://github.com/puppetlabs/puppet/commit/93ac4dca91b510cc6f76a83111308f813ec111cf. 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-5975) Remove Range#intersection monkey patch
Title: Message Title John Duarte updated an issue Puppet / PUP-5975 Remove Range#intersection monkey patch Change By: John Duarte QA Risk Assessment: No Action 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-6692) Improve access to "master" settings
Title: Message Title John Duarte updated an issue Puppet / PUP-6692 Improve access to "master" settings Change By: John Duarte QA Risk Assessment: No Action 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-5635) accessing facts via another scope
Title: Message Title John Duarte updated an issue Puppet / PUP-5635 accessing facts via another scope Change By: John Duarte QA Risk Assessment: No Action 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-7471) misleading error message with classname errors
Title: Message Title John Duarte updated an issue Puppet / PUP-7471 misleading error message with classname errors Change By: John Duarte QA Risk Assessment: Needs Assessment Manual 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-509) Specify the Puppet Language query mechanism
Title: Message Title Henrik Lindberg commented on PUP-509 Re: Specify the Puppet Language query mechanism Not relevant given PQL and PUP-7541. 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-5615) Deprecate unused options for Puppet::Resource::Catalog.apply
Title: Message Title John Duarte updated an issue Puppet / PUP-5615 Deprecate unused options for Puppet::Resource::Catalog.apply Change By: John Duarte QA Risk Assessment: No Action 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-1795) Issue warning for numeric coercion
Title: Message Title John Duarte updated an issue Puppet / PUP-1795 Issue warning for numeric coercion Change By: John Duarte QA Risk Assessment: Manual 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-1606) put warn/error for attempt to instantiate virtual class under --strict control
Title: Message Title John Duarte updated an issue Puppet / PUP-1606 put warn/error for attempt to instantiate virtual class under --strict control Change By: John Duarte QA Risk Assessment: No Action 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-7508) Failing mapped_paths don't get explained by lookup --explain
Title: Message Title John Duarte updated an issue Puppet / PUP-7508 Failing mapped_paths don't get explained by lookup --explain Change By: John Duarte QA Risk Assessment: Needs Assessment Manual 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-7155) PCore resource output improperly quoted
Title: Message Title John Duarte updated an issue Puppet / PUP-7155 PCore resource output improperly quoted Change By: John Duarte QA Risk Assessment: Needs Assessment Automate 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-3743) Parser should report invalid operand types when possible
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3743 Parser should report invalid operand types when possible If someone wants to have a crack at this and make a PR against the checker4_0.rb validator and that is not too slow then we would accept this. It is not as easy as it seems to implement - for example: $x = 1 + if $something { 2 } else { Booh } I don't see us doing this on our own given that there is a runtime error for the error in the manifest. 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-6658) Support puppet-REST integration
Title: Message Title James Shewey updated an issue Puppet / PUP-6658 Support puppet-REST integration Change By: James Shewey Acceptance Criteria: A scheduler would need to be used to do one URL very every 60 seconds or so over a 90 minute window. If all the URLs were called at once, this could overload the CPU of an a web site or device. 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-3743) Parser should report invalid operand types when possible
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3743 Parser should report invalid operand types when possible Change By: Henrik Lindberg Component/s: Language 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-3743) Parser should report invalid operand types when possible
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3743 Parser should report invalid operand types when possible Change By: Henrik Lindberg Labels: help_wanted 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-7558) Remove outdated editor extensions from the Puppet repo
Title: Message Title John Duarte updated an issue Puppet / PUP-7558 Remove outdated editor extensions from the Puppet repo Change By: John Duarte QA Risk Assessment: Needs Assessment No Action 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-7383) Puppet with openssl 1.1 fails
Title: Message Title John Duarte updated an issue Puppet / PUP-7383 Puppet with openssl 1.1 fails Change By: John Duarte QA Risk Assessment: Needs Assessment Manual 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-5975) Remove Range#intersection monkey patch
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5975 Remove Range#intersection monkey patch Change By: Henrik Lindberg Release Notes Summary: The monkey patch of Range#intersection to handle SemVer range matches have now been removed. This only affects those that have written version compare logic in Ruby. Release Notes: Deprecation 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-7576) Minor error in arity error in face_base.rb
Title: Message Title John Duarte updated an issue Puppet / PUP-7576 Minor error in arity error in face_base.rb Change By: John Duarte QA Risk Assessment: Needs Assessment 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-6566) Face based application help should say (c) Puppet Inc. not Puppet Labs.
Title: Message Title John Duarte updated an issue Puppet / PUP-6566 Face based application help should say (c) Puppet Inc. not Puppet Labs. Change By: John Duarte QA Risk Assessment: No Action 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-1723) Yumrepo logs info messages without context
Title: Message Title John Duarte updated an issue Puppet / PUP-1723 Yumrepo logs info messages without context Change By: John Duarte QA Risk Assessment: Manual 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-7554) Puppet runs fail when hiera.yaml version 3 detected in a module
Title: Message Title John Duarte updated an issue Puppet / PUP-7554 Puppet runs fail when hiera.yaml version 3 detected in a module Change By: John Duarte Labels: regression 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-7554) Puppet runs fail when hiera.yaml version 3 detected in a module
Title: Message Title John Duarte updated an issue Puppet / PUP-7554 Puppet runs fail when hiera.yaml version 3 detected in a module Change By: John Duarte QA Risk Assessment: Needs Assessment Automate 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-7528) Add Ruby 2.4 builds to puppet-win32-ruby to support ci:test:git workflows
Title: Message Title John Duarte updated an issue Puppet / PUP-7528 Add Ruby 2.4 builds to puppet-win32-ruby to support ci:test:git workflows Change By: John Duarte QA Risk Assessment: Needs Assessment Manual 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-3744) Function to dig out allowed values for an attribute of a type
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3744 Function to dig out allowed values for an attribute of a type Change By: Henrik Lindberg Fix Version/s: None 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-3744) Function to dig out allowed values for an attribute of a type
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3744 Function to dig out allowed values for an attribute of a type Change By: Henrik Lindberg Fix Version/s: None 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-7576) Minor error in arity error in face_base.rb
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7576 Minor error in arity error in face_base.rb Change By: Eric Delaney QA Risk Assessment: No Action QA Contact: Eric Delaney 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-3744) Function to dig out allowed values for an attribute of a type
Title: Message Title Henrik Lindberg commented on PUP-3744 Re: Function to dig out allowed values for an attribute of a type This ticket says it was fixed in PUP 4.5.0 - that is not correct. 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-1443) FACTERLIB not taken in account on Windows 2012R2
Title: Message Title John Duarte updated an issue Facter / FACT-1443 FACTERLIB not taken in account on Windows 2012R2 Change By: John Duarte QA Risk Assessment: Automate 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-1443) FACTERLIB not taken in account on Windows 2012R2
Title: Message Title Eric Delaney updated an issue Facter / FACT-1443 FACTERLIB not taken in account on Windows 2012R2 Change By: Eric Delaney QA Risk Assessment Reason: Need to check if this is a problem and if its already being tested QA Contact: Eric Delaney 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-3744) Function to dig out allowed values for an attribute of a type
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3744 Function to dig out allowed values for an attribute of a type Change By: Henrik Lindberg Fix Version/s: None 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-7481) Update Language Spec wrt changed "Data" data type
Title: Message Title John Duarte updated an issue Puppet / PUP-7481 Update Language Spec wrt changed "Data" data type Change By: John Duarte QA Risk Assessment: Needs Assessment No Action 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Eric Delaney updated an issue Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: Eric Delaney QA Risk Assessment Reason: We should add a test for this if we don't have one. QA Risk Assessment: Automate 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-7571) Add ability to relax VersionRange constraints so that they include pre-releases
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7571 Add ability to relax VersionRange constraints so that they include pre-releases Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Delaney 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-6517) undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source
Title: Message Title John Duarte updated an issue Puppet / PUP-6517 undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source Change By: John Duarte QA Risk Assessment: Manual 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-6517) undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source
Title: Message Title Eric Delaney updated an issue Puppet / PUP-6517 undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source Change By: Eric Delaney QA Risk Assessment Reason: This should be a manual test QA Contact: Eric Delaney 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-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Eric Delaney updated an issue Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Eric Delaney QA Risk Assessment Reason: We could write a test for this. QA Risk Assessment: Automate QA Contact: Erik Dasher Eric Delaney 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-7381) Consistently use encode_with for YAML serialization
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7381 Consistently use encode_with for YAML serialization Change By: Eric Delaney QA Risk Assessment Reason: covered by our existing automation QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Delaney 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-7382) Ensure current values are YAML serializable
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7382 Ensure current values are YAML serializable Change By: Eric Delaney QA Risk Assessment Reason: Does this cause test changes? QA Risk Assessment: Needs Assessment Automate QA Contact: Eric Delaney 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-6734) foo
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6734 foo Change By: Moses Mendoza Epic Name: Type/Provider Improvements - Package Management Phase 1 bar 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-6734) foo
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6734 foo Change By: Moses Mendoza Summary: Type/Provider Improvements - Package Management Phase 1 foo 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-7383) Puppet with openssl 1.1 fails
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7383 Puppet with openssl 1.1 fails Change By: Josh Cooper Release Notes Summary: All puppet commands would fail when running puppet as a gem or from source with system ruby 2.4 or greater. Release Notes: Bug Fix 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-7383) Puppet with openssl 1.1 fails
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7383 Puppet with openssl 1.1 fails Change By: Josh Cooper Release Notes Summary: All puppet commands would fail when running puppet as a gem or from source with system ruby 2.4 or greater + and openssl 1 . 1.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-2239) logical operations in ?{}
Title: Message Title Henrik Lindberg commented on PUP-2239 Re: logical operations in ?{} Also note that what is requested here already works in puppet 4. 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-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Joe Pinsonault commented on PUP-6639 Re: Yumrepo can't work with files using spaces in their INI format Ah, I'm sorry, I totally misread your description. We spent 3 days going through the PUP project cleaning up tickets and I was very tired by the time I read this. You're right, this is definitely something that needs to be looked at/fixed. Reopening 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-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Joe Pinsonault updated an issue Puppet / PUP-6639 Yumrepo can't work with files using spaces in their INI format Change By: Joe Pinsonault Team: Agent 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-5357) PMT - Allow Installation of Latest Pre-release Modules
Title: Message Title Ethan Brown commented on PUP-5357 Re: PMT - Allow Installation of Latest Pre-release Modules Ping David Schmitt on this feature request for PMT. 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-5068) Windows - Allow logging to a different event log
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5068 Windows - Allow logging to a different event log Change By: Ethan Brown Sprint: Agent N+2 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-2510) Overrides and definitions don't mix
Title: Message Title Henrik Lindberg commented on PUP-2510 Re: Overrides and definitions don't mix This is a known problem - you can only override parameters of a user defined type until it has been evaluated. After that, only the parameter itself is changed, but the body of the user defined type is not reevaluated. We have another ticket for this that should be linked here. The operation that is attempted here should at least produce a warning "override of parameters of evaluated user defined resource type has no effect" The only reason it works (when it works) is because the resource has not yet been evaluated. Closing this as a duplicate. 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-2318) Ruby open classes functionality breaks when used in ERB templates
Title: Message Title Henrik Lindberg commented on PUP-2318 Re: Ruby open classes functionality breaks when used in ERB templates Don't use the workaround!! Don't open Ruby classes and put stuff in them unless you are a system tool - it is as bad as monkeypatching! 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-3517) legacy query engine does not support null?
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3517 legacy query engine does not support null? Change By: Russell Mull Fix Version/s: PDB 5.1.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-3230) Exported resource collectors don't support standard puppet expression set
Title: Message Title Henrik Lindberg commented on PUP-3230 Re: Exported resource collectors don't support standard puppet _expression_ set The operators allowed are specified by a terminus API where it is possible to plug in a provider of exported resources. This is implemented by PDB. Since the backing store for exported resources is most likely a database there are constraints in how queries can be formulated and the operators' expressive power. A subset of expressions where therefore selected to be used in Puppet. I don't think it is even possible to achieve the goal of supporting the "puppet _expression_ set", but it may be possible to add some missing operators, but then they would not be exactly the same (POSIX regular expressions in PostgreSQL are not identical to the regular expressions in Puppet). The design is also done so that the syntax and semantics of VirtualCollector and ExportedCollector are the same. If we were only dealing with VirtualCollector, there would be no problem supporting the entire language. For ExportedCollector we strongly recommend the PQL API over the collector operator. Given that it is not really possible to achieve the goal stated "support standard puppet _expression_ set" for ExportedCollector - I am going to close this as a Won't Do. If someone comes up with support for a new operator in PDB and maps that to the puppet language - Great! But there is going to be the need to discuss each such operator in detail and PR separately. Don't see the value of keeping this ticket open. 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-6517) undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6517 undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source Change By: Josh Cooper Story Points: 1 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-7523) Can't gem install puppet with some versions of bundler and ruby 1.9.3
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7523 Can't gem install puppet with some versions of bundler and ruby 1.9.3 Change By: Ethan Brown Release Notes Summary: In Puppet 4.10.1 a change was made that may prevent the Puppet gem (or Puppet run from source) from being able to load and run on Ruby 1.9.3 due to a bug in Bundler. This issue would not have impacted Puppet installed from packages. 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-7523) Can't gem install puppet with some versions of bundler and ruby 1.9.3
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7523 Can't gem install puppet with some versions of bundler and ruby 1.9.3 Change By: Ethan Brown Release Notes: Bug Fix 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-3286) Add job_id to reports and catalogs
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3286 Add job_id to reports and catalogs Change By: Russell Mull Fix Version/s: PDB 5.0.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 (PDB-3520) (maint) Use a real scope object for terminus testing
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3520 (maint) Use a real scope object for terminus testing Change By: Russell Mull Fix Version/s: PDB 4.2.3.3 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-1619) Memory fact fails on Solaris SPARC 11.3 patch level 17.0.3.0
Title: Message Title Maggie Dreyer commented on FACT-1619 Re: Memory fact fails on Solaris SPARC 11.3 patch level 17.0.3.0 John Duarte or Branan Riley Do we have any way to get ahold of a Solaris 11 SPARC box/image with their patch level on it? I assume ours is different and that's why this doesn't show up. Without being able repro it's going to be very hard to track down the exact code path leading to this bug, and we may have to go with a less fine-grained approach. 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.