Jira (PUP-5923) Administration token detection doesn't work in legacy Windows OS (2003/XP)
Title: Message Title Ethan Brown assigned an issue to Ryan Gard Puppet / PUP-5923 Administration token detection doesn't work in legacy Windows OS (2003/XP) Change By: Ethan Brown Assignee: qa Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Matthew Fischer commented on PUP-5661 Re: Stack level too deep issue Henrik, I've spent about 20 hours on this as I find time during my regular work but no progress yet. I've been able to finally dump code that's being parsed but cannot pin any code to the failure. I'm hindered by my lack of understanding on your parser and Ruby in general but still hope to make progress. I've asked someone else on my team who knows a lot more Ruby to also help. Since we filed, we've upgraded to 3.9.5, which did not help. We still have 4.x in plan but it's not just a simple task. We've also done some rework to reduce exported resource usage by 95% (replacing with stencil), although we hoped that this would fix things, it had no effect unfortunately. The EYAML idea is interesting, we use it extensively in hiera and we can't just turn that off but we probably could either look into upgrading it (if available) or decrypting a single environment to see if it goes away. We are somewhat mitigated here (and therefore not spending all our time on this) because our deployment process includes a puppet master restart at the beginning, which will fix this issue for about an hour. If I get anymore useful info or a repro case that's not just "our whole stack", I'll update it here. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5889) Add a --strict flag to Puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5889 Add a --strict flag to Puppet Change By: Henrik Lindberg Sprint: Language 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5901) Type mismatch describer should merge Enum expectations
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5901 Type mismatch describer should merge Enum expectations Change By: Henrik Lindberg Sprint: Language 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5907) Define the PCore Serialization API and Features
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5907 Define the PCore Serialization API and Features Change By: Henrik Lindberg Sprint: Language 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5911) Define the content of an .xpp file
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5911 Define the content of an .xpp file Change By: Henrik Lindberg Sprint: Language 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3992) ensure data binding for class params can produce undef
Title: Message Title Henrik Lindberg commented on PUP-3992 Re: ensure data binding for class params can produce undef PUP-5925 and PUP-5936 deals with the remaining case for undef handling and data binding and will be released in puppet 4.4.0 and 4.3.0 (whichever comes first). Those tickets have more information and the code has been merged. I am going to close this as a diuplicate even if this ticket was logged before those (we simply missed that we already had a ticket for this). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3985) With `storeconfigs = false` there are no warnings or errors about exported resources
Title: Message Title Henrik Lindberg commented on PUP-3985 Re: With `storeconfigs = false` there are no warnings or errors about exported resources Looked at this again and warnings are produced the same way now (4.x) for things like strict_variables and storeconfigs. Is this still a problem on 4.x ? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3973) puppet-mode.el indentation problems with if/else blocks
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3973 puppet-mode.el indentation problems with if/else blocks Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3836) cleanup dns-alt-names setting and CLI option
Title: Message Title Henrik Lindberg commented on PUP-3836 Re: cleanup dns-alt-names setting and CLI option Ping Kylo Ginsberg and Chris Price - this is a golden oldie and was left over in the 4.0.0 code removal. I am not sure where this belongs. As the description says: See PUP-3684 for background. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3170) Cap integer and float sizes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3170 Cap integer and float sizes Change By: Henrik Lindberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-11) Add sad path system test
Title: Message Title Henrik Lindberg updated an issue Puppet Strings / PDOC-11 Add sad path system test Change By: Henrik Lindberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3018) Puppet doesn't like to evaluate 'require => [ [], [] ],'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3018 Puppet doesn't like to evaluate 'require => [ [], [] ],' Change By: Henrik Lindberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2811) Provide method for class masquerading
Title: Message Title Henrik Lindberg commented on PUP-2811 Re: Provide method for class masquerading A lot of things have happened since this ticket was last discussed. Puppet now has a type system, and from Puppet 4.4.0 it is possible to define type aliases. This provides a mechanism by which it is possible to include the alias instead of the actual class (except from one thing which I will come back to). type Auth = Class['sssd'] Unfortunately, this does not work since the include function is a 3.x function and it does not understand what a "data type" is. By changing the include function to be a 4.x function and giving it the ability to resolve type aliases (to discover the actual class it is an alias for we would achieve a simple indirection. Since types are autoloaded and they can be defined at the environment level, adding the alias to /types/auto.pp makes it possible to define what Auth means in that environment. (Alternatively, the type alias can be placed in site.pp). Does that sound like a solution to this issue? (If so, all we need to do is to refactor the include (and related) functions. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving
Jira (PUP-2695) deprecate that defining a class twice "merges" their behaviors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2695 deprecate that defining a class twice "merges" their behaviors Change By: Henrik Lindberg Sprint: Language 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2695) deprecate that defining a class twice "merges" their behaviors
Title: Message Title Henrik Lindberg commented on PUP-2695 Re: deprecate that defining a class twice "merges" their behaviors Add deprecation in 4.x version following 4.4.0 (i.e. 4.4.1 or 4.5.0), and removal ticket for 5.0.0. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2695) deprecate that defining a class twice "merges" their behaviors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2695 deprecate that defining a class twice "merges" their behaviors Change By: Henrik Lindberg Fix Version/s: PUP 4.x Fix Version/s: PUP 4.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5954) Create removal ticket for 5.0.0
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5954 Create removal ticket for 5.0.0 Issue Type: Sub-task Assignee: Unassigned Created: 2016/02/21 4:22 PM Priority: Normal Reporter: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2695) deprecate that defining a class twice "merges" their behaviors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2695 deprecate that defining a class twice "merges" their behaviors Change By: Henrik Lindberg Summary: deprecate that defining a class twice "merges" their behaviors Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2695) deprecate that defining a class twice "merges" their behaviors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2695 deprecate that defining a class twice "merges" their behaviors Change By: Henrik Lindberg Fix Version/s: PUP 4.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2627) Collecting defined types in masterless configuration
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2627 Collecting defined types in masterless configuration Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2211) Confusing ArgumentError exception message when using future parser
Title: Message Title Henrik Lindberg commented on PUP-2211 Re: Confusing ArgumentError exception message when using future parser I am closing this as incomplete as there is no reproducer. Also since this was reported several issues regarding "file and line missing in error" have been fixed. Please file a new ticket if there is a reproducible case for an error where file/line is missing. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1984) unexpected autorequire
Title: Message Title Henrik Lindberg commented on PUP-1984 Re: unexpected autorequire ping Kylo Ginsberg This may be stale - this was floating around the bottom of the backlog... Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1984) unexpected autorequire
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1984 unexpected autorequire Change By: Henrik Lindberg Scrum Team: Language Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1984) unexpected autorequire
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-1984 unexpected autorequire Change By: Henrik Lindberg Assignee: Andrew Parker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1984) unexpected autorequire
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1984 unexpected autorequire Change By: Henrik Lindberg Component/s: Server Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-197) optional bindings does not work for autoloaded bindings
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-197 optional bindings does not work for autoloaded bindings Change By: Henrik Lindberg Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1606) Virtual classes are always realized
Title: Message Title Henrik Lindberg commented on PUP-1606 Re: Virtual classes are always realized Ping Eric Sorenson - this ticket has been around for a while. It needs a decision. Is it meaningful to support the concept of virtual for classes? If not then it should be an error to attempt to create one, and the documentation should state that it is no legal. If it is a valid concept then we have other work to do Since a class is not actually a resource type and we in other similar cases have turned down requests to make classes more like resources I suggest that we specify that it is illegal to specify a class as being virtual. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-509) Specify the Puppet Language query mechanism
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-509 Specify the Puppet Language query mechanism Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1536) Write spec for project Honeydew
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1536 Write spec for project Honeydew Change By: Henrik Lindberg Summary: Write spec for Orchestration project Honeydew Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5451) bizarre error handling with an application resource when I should have been told I forgot a comma inside the manifest
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5451 bizarre error handling with an application resource when I should have been told I forgot a comma inside the manifest Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5451) bizarre error handling with an application resource when I should have been told I forgot a comma inside the manifest
Title: Message Title Henrik Lindberg commented on PUP-5451 Re: bizarre error handling with an application resource when I should have been told I forgot a comma inside the manifest Ping Ryan Coleman - are you still having this problem? Can we close this? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1061) Install multiple package within a single call to the package manager
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1061 Install multiple package within a single call to the package manager Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Henrik Lindberg commented on PUP-5661 Re: Stack level too deep issue Ping Matthew Fischer curions how you are doing. Still having the same issue? We have found and fixed a couple of out of stack problems that were found on Puppet Server. One related to use of Eyaml. While the other problems were in Puppet Ruby (not in server), I cannot know if what is now fixed applies to your case. Since you reported the problem for 3.8.4 and we are now about to release 4.4.0 there is not much we can do as we do not have a reproducer for the problem you are seeing. My only advice is to try with a newer release and possibly see if you are using EYAML hiera provider and if it makes a difference if you disable it (I realize that could be difficult). I am closing this with status "incomplete", if you have new information, please reopen the ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2687) File Names with "?" cause failures with recursive copies
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2687 File Names with "?" cause failures with recursive copies Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4750) Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead)
Title: Message Title Henrik Lindberg commented on PUP-4750 Re: Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead) Closing this as incomplete. Please reopen if there is more information available. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5848) Relationship validation fails when a multi-resource reference is used inside an array
Title: Message Title Henrik Lindberg assigned an issue to Nick Lewis Puppet / PUP-5848 Relationship validation fails when a multi-resource reference is used inside an array Change By: Henrik Lindberg Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5848) Relationship validation fails when a multi-resource reference is used inside an array
Title: Message Title Henrik Lindberg commented on PUP-5848 Re: Relationship validation fails when a multi-resource reference is used inside an array Nick Lewis Can we close this? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5904) Puppet parser validate does not validate puppet functions and type aliases
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5904 Puppet parser validate does not validate puppet functions and type aliases Change By: Henrik Lindberg Sprint: Language Triage 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5924) The default hiera.yaml file does not include the '::' prefix for the environment variable
Title: Message Title Henrik Lindberg commented on PUP-5924 Re: The default hiera.yaml file does not include the '::' prefix for the environment variable ping Thomas Hallgren Can you take a look at this? Is this an issue or not? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5902) Type mismatch describer should expand aliases
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5902 Type mismatch describer should expand aliases Change By: Henrik Lindberg Sprint: Language Triage 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5818) regular expression character class/sets interpreted incorrectly for node
Title: Message Title Henrik Lindberg commented on PUP-5818 Re: regular _expression_ character class/sets interpreted incorrectly for node When we fixed PUP-3167 we concluded that the change would not be backwards compatible and no fix was therefore done for the 3.x series. If you are bit badly by this, you may want to consider applying the PR /patch from PUP-3167 in your own puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5818) regular expression character class/sets interpreted incorrectly for node
Title: Message Title Henrik Lindberg commented on PUP-5818 Re: regular _expression_ character class/sets interpreted incorrectly for node While not a strict duplicate of PUP-3167 , the fix made there will also cure this problem. The fix was released in Puppet 4.0.0. In older versions you have to use regular expressions that the name mangler does not turn into actual names of nodes. Sometimes this is as simple as changing to [1-2] instead of [12], sometimes zero effect regexp parts have to be inserted into the regexp for the sole purpose of making the mangled name different. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5818) regular expression character class/sets interpreted incorrectly for node
Title: Message Title Henrik Lindberg commented on PUP-5818 Re: regular _expression_ character class/sets interpreted incorrectly for node I think I know what is going on here and that the problem is fixed in newer versions of puppet. I cannot reproduce this on 4.x The issue is that older puppets performs name manging on the regular _expression_ and assigns the node to a name that is essentially the regular _expression_ with some punctuation replaced by underscores. Thus the regexp /lb[12]/ becomes "lb12" whereas the /lb[1.2]/ becomes "lb1_2". The insanity continues as it then checks with the node's "names" (which it constructs from things like certname, hostname, domain etc. depending on what is available. (When I run this I get an array ['lb12', 'Henrik2']). Each of those names are matched agains a) the identity/name of the node _expression_ - and surprise, it finds as "lb12" the badly transformed regexp. It accepts this as a match and it never gets to the regexp match (which would indeed fail). Will locate the ticket for this. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5903) 4.x function api should contain way to add type aliases
Title: Message Title Henrik Lindberg commented on PUP-5903 Re: 4.x function api should contain way to add type aliases Using type inside function and type makes them look like local types, and that is odd because they are used before they are defined. Your questions It looks like the types are defined in a global scope and it will be somewhat surprising that they are not. For function (and type) yes, agree. Will try with another proposal. How would you do this if you declare a function in, say, init.pp? We do not really care - that just defines the type/function class etc. This use case is mainly for writing examples, testing, experimenting, debugging etc. Should we have this ability when we declare types as well? Types can consist of other fairly complex types. If we do allow this for types as well, how do we differentiate between the global type and the types local to the type definition? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5937) Parser validator should warn about duplicate keys in hash constructs
Title: Message Title Henrik Lindberg commented on PUP-5937 Re: Parser validator should warn about duplicate keys in hash constructs I have an idea about adding a --strict option to puppet (separate ticket). You can set it to 'warning' 'error' or 'ignore'. We guarantee that we do not make things more strict in .z releases, but we may in an .y (users that used strict=error can then shift to strict=warning until they have fixed their issues). At major release boundary we make everything that is a "strict check" be standard. (Without this we end up with lots of different settings). There is a problem with warnings as well - someone may have the problem in a number of places. They may also have many nodes. This means that they will see the same warning lots of times. Thus when adding warnings, it is good to have a key that allows warnings to be suppressed. That led me down the path to instead doing a 'strict mode'. What I wanted to do with this ticket (and the --strict= ... one, and a few others) was to bring it up for discussion before we acted on them. That was the reason this ticket was floating around in Triage in a state other than "ready for engineering" and marked with a version. (There are 10-20 tickets similar to this one). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5952) Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5952 Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment Ping Thomas Hallgren - can you take a look at this to see what is going on? Change By: Henrik Lindberg Sprint: Language Triage Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5953) Puppetserver 2.2.1 (RC1 release) and gem handling
Title: Message Title Simon Hönscheid created an issue Puppet / PUP-5953 Puppetserver 2.2.1 (RC1 release) and gem handling Issue Type: Bug Assignee: Unassigned Created: 2016/02/21 9:57 AM Environment: Running on Debian Jessie dpkg -l|grep puppet ii puppet-agent 1.3.5-1jessie amd64The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective. ii puppetdb-termini 3.2.3-1puppetlabs1 all Termini for puppetdb ii puppetlabs-release-pc1 0.9.3.3.g91e66b9-1jessieall Release packages for the Puppet Labs PC1 repository ii puppetserver 2.2.1-1puppetlabs1 all Puppet Labs puppetserver
Jira (PDOC-70) Always generate JSON output for Rake task
Title: Message Title Gareth Rushgrove created an issue Puppet Strings / PDOC-70 Always generate JSON output for Rake task Issue Type: Improvement Assignee: Unassigned Created: 2016/02/21 9:12 AM Priority: Normal Reporter: Gareth Rushgrove At the moment it's not possible to generate the JSON output using the rake tasks, without knowing the internals and writing your own rake task. Given how useful that output can be, I think it's a reasonable default to always generate it. I've opened https://github.com/puppetlabs/puppetlabs-strings/pull/72/files with that change. My rationale for that is by always generating it more people will find out about it, and potentially use it to do awesome. A user that really doesn't want that can always add it to .gitignore or similar, or write there own rake task. This could be made configurable later, or split into separate tasks. I'm less bothered about the implementation and more interested in the default. Outputting by default could lead to more visibility/usage of the format, which can only be a good thing. Add Comment
Jira (PUP-5952) Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Title: Message Title Andrey Galkin created an issue Puppet / PUP-5952 Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Unassigned Components: Puppet Server Created: 2016/02/21 6:38 AM Priority: Normal Reporter: Andrey Galkin It seems, this issue has not been reported before. It affects general variable lookup. If merge strategy is first, then environment's data is ignored. If merge strategy is unique then Undef/nil is inserted as first argument That breaks class parameter lookup as well. Steps to reproduce: 1. Global hiera.yaml datadir points to /etc/puppetlabs/code/hieradata/ and only entry "global" in the hierarchy. 2. There is /etc/puppetlabs/code/hieradata/global.yaml ---
Jira (PUP-5937) Parser validator should warn about duplicate keys in hash constructs
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-5937
Parser validator should warn about duplicate keys in hash constructs
Change By:
Thomas Hallgren
The keys in a hash construct are most often literals. As such, they can be validated during parsing so that the parser immediately complains about constructs like this:{code:puppet}$myhash = { key => "some value", other_key => "some other value", key => "some overriding value"}notice( $myhash[key] ){code}Presently, this is ignored and Puppet will notice 'some overriding value'. With a correct validation, it would instead yield an error issue a warning :{code}The key 'key' is declared more than once at /some/path/to/a.pp:3:17{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5937) Parser validator should warn about duplicate keys in hash constructs
Title: Message Title Thomas Hallgren commented on PUP-5937 Re: Parser validator should warn about duplicate keys in hash constructs Yes, of course. It cannot error out on this. I changed the PR so that a warning is printed instead. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5937) Parser validator should warn about duplicate keys in hash constructs
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5937 Parser validator should warn about duplicate keys in hash constructs Change By: Thomas Hallgren Summary: Parser validator should raise errors for warn about duplicate keys in hash constructs Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5903) 4.x function api should contain way to add type aliases
Title: Message Title
Thomas Hallgren commented on PUP-5903
Re: 4.x function api should contain way to add type aliases
The last comment about allowing the same for a puppet function definition. I see some problems with that.
It looks like the types are defined in a global scope and it will be somewhat surprising that they are not.
How would you do this if you declare a function in, say, init.pp?
Should we have this ability when we declare types as well? Types can consist of other fairly complex types.
If we do allow this for types as well, how do we differentiate between the global type and the types local to the type definition? All in all, I think we need to have a syntax to describe the closure where the loader is local and not just say that this closure is implicit since it's contained in a file under the functions directory, i.e.
{
type PartColor = Enum[blue, red, green, mauve, teal, white, pine]
type Part = Enum[cubicle_wall, chair, wall, desk, carpet]
type 'PartToColorMap = Hash[Part, PartColor]
}.definition_closure {
function mymodule::define_colors(MyModule::PartToColorMap $part_color_map) {
Jira (PUP-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Thomas Hallgren commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes I agree on the "totally weird" part. I have no idea what's going on here. A stacktrace or a small example that reproduces the problem would be of great value. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
