Jira (PUP-5643) Test
Title: Message Title Nishanth BS created an issue Puppet / PUP-5643 Test Issue Type: Task Affects Versions: PUP 4.3.1 Assignee: Unassigned Components: DEV Created: 2015/12/29 10:08 PM Fix Versions: PUP 4.3.2 Priority: Normal Reporter: Nishanth BS Add Comment
Jira (PUP-5642) puppet module generate's manifests/init.pp is unusable
Title: Message Title closeparen created an issue Puppet / PUP-5642 puppet module generate's manifests/init.pp is unusable Issue Type: Bug Assignee: Unassigned Created: 2015/12/29 9:48 PM Priority: Normal Reporter: closeparen I want a class named "base" and my username is closeparen. "puppet module generate" requires that I name the module closeparen-base, but generates a class in manifests/site.pp named base. It cannot be imported by either name, which is expected since the class name must match the name of the enclosing folder. If I change the name of the class to closeparen-base it works. Apologies if I am misunderstanding something, but the generated code should probably function out of the box. Add Comment
Jira (FACT-1281) Remove host specific logic from facter acceptance setup steps
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1281 Remove host specific logic from facter acceptance setup steps Change By: Kylo Ginsberg Sprint: Client Platform Additions 2016-01-13 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-5583) Remove host specific logic from puppet acceptance setup steps
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5583 Remove host specific logic from puppet acceptance setup steps Change By: Kylo Ginsberg Sprint: Client Platform Additions 2016-01-13 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-5641) Shepherd beaker-hostgenerator changes through CI for pup/fact/hi
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5641 Shepherd beaker-hostgenerator changes through CI for pup/fact/hi Change By: Kylo Ginsberg 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-5641) Shepherd beaker-hostgenerator changes through CI for pup/fact/hi
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5641 Shepherd beaker-hostgenerator changes through CI for pup/fact/hi Change By: Kylo Ginsberg Story Points: 3 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-5641) Shepherd beaker-hostgenerator changes through CI for pup/fact/hi
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5641 Shepherd beaker-hostgenerator changes through CI for pup/fact/hi Change By: Kylo Ginsberg Sprint: Client 2015-12-30 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-5641) Shepherd beaker-hostgenerator changes through CI for pup/fact/hi
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5641 Shepherd beaker-hostgenerator changes through CI for pup/fact/hi Issue Type: Task Assignee: Kylo Ginsberg Created: 2015/12/29 4:55 PM Priority: Normal Reporter: Kylo Ginsberg There were several tickets created combining both the beaker-hostgenerator change and the beaker install change for different projects: HI-486, FACT-1281, PUP-5583, PCP-198. Since the b-hg changes arrived first, we're actually doing those two tickets in two phases. This ticket (just one, jira fatigue) is for the beaker-hostgenerator change across PUP/FACT/HI which needed to be sync-rolled. The remaining activities can be done separately under their original tickets. Add Comment This message was sent by Atlassian JIRA (v6.4.12#6402
Jira (HI-486) Remove host specific logic from hiera acceptance setup steps
Title: Message Title Kylo Ginsberg updated an issue Hiera / HI-486 Remove host specific logic from hiera acceptance setup steps Change By: Kylo Ginsberg Sprint: Client Platform Additions 2016-01-13 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-3278) Find ways of increasing the puppet master's capacity
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3278 Find ways of increasing the puppet master's capacity Change By: Kylo Ginsberg Epic Status: To Do Done 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-3438) Pass facts from catalog requests directly to node requests.
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-3438 Pass facts from catalog requests directly to node requests. Change By: Kylo Ginsberg 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-3278) Find ways of increasing the puppet master's capacity
Title: Message Title Kylo Ginsberg commented on PUP-3278 Re: Find ways of increasing the puppet master's capacity Some good things happened under the auspices of this epic, but what remains of the epic is bitrotted. I'm punting the one ticket out into the un-epic'ed cold and closing this epic. 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-2951) Add static analysis of ruby code
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2951 Add static analysis of ruby code Change By: Kylo Ginsberg Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1148) Port Facter to OpenBSD
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1148 Port Facter to OpenBSD Change By: Kylo Ginsberg Epic Status: To Do Done 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-4739) Mac OS X 10.11 Changes
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4739 Mac OS X 10.11 Changes Change By: Kylo Ginsberg Epic Status: To Do Done 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-4553) Improve Canary Workflow in NC
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4553 Improve Canary Workflow in NC Change By: Kylo Ginsberg Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-927) Facter 3 Solaris Support
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-927 Facter 3 Solaris Support Change By: Kylo Ginsberg Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-890) Facter 3 AIX Support
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-890 Facter 3 AIX Support Change By: Kylo Ginsberg Epic Status: To Do Done 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-5584) Cached catalogs are loaded using the agent's string locale which can result in corrupted data
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5584 Cached catalogs are loaded using the agent's string locale which can result in corrupted data Change By: Kylo Ginsberg Story Points: 3 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-4619) fstab entries can be written in bad order
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4619 fstab entries can be written in bad order Change By: Kylo Ginsberg Sprint: Client 2015-07-22, Client 2015-12-02, Client 2016-01- 13 27 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-5378) acceptance: backport call all parser functions test to 3.x
Title: Message Title Eric Thompson commented on PUP-5378 Re: acceptance: backport call all parser functions test to 3.x Thomas Hallgren this is ready to go. thanks for the help. i completely forgot about trusted_node_data in 3.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-1072) support HTTP(S) URL as the file 'source'
Title: Message Title Kylo Ginsberg assigned an issue to qa Puppet / PUP-1072 support HTTP(S) URL as the file 'source' Change By: Kylo Ginsberg Status: Ready for CI Test Assignee: Michael Smith qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-959) Incorrect processor counts on Windows
Title: Message Title Kylo Ginsberg assigned an issue to qa Facter / FACT-959 Incorrect processor counts on Windows Change By: Kylo Ginsberg Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1455) Puppet should utilize a faster plist library to read/write plist files
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1455 Puppet should utilize a faster plist library to read/write plist files Change By: Kylo Ginsberg Fix Version/s: PUP 4.x Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5639) meta parameter $name not useable for resource collection
Title: Message Title Henrik Lindberg commented on PUP-5639 Re: meta parameter $name not useable for resource collection I wonder if this is a regression from an earlier puppet version? It is sensitive to change things like this if it is not a regression. 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-5639) meta parameter $name not useable for resource collection
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5639 meta parameter $name not useable for resource collection Change By: Henrik Lindberg Summary: "free" meta parameter $name not useable for resource collection Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2280) Report aggregate data from all envs, for specific views, and for specific data slices over time
Title: Message Title Kurt Wall assigned an issue to Unassigned PuppetDB / PDB-2280 Report aggregate data from all envs, for specific views, and for specific data slices over time Change By: Kurt Wall Assignee: qa-team Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2281) Report transition from managed to unmanaged, when it happened, and the code responsible
Title: Message Title Kurt Wall assigned an issue to Unassigned PuppetDB / PDB-2281 Report transition from managed to unmanaged, when it happened, and the code responsible Change By: Kurt Wall Assignee: qa-team Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2278) Compare current failed catalog with previous good catalog and identify failure
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2278 Compare current failed catalog with previous good catalog and identify failure Change By: Kurt Wall Component/s: QA Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2279) Report historical data on a failed resources and associated actions to converge
Title: Message Title Kurt Wall assigned an issue to Unassigned PuppetDB / PDB-2279 Report historical data on a failed resources and associated actions to converge Change By: Kurt Wall Assignee: qa-team Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2280) Report aggregate data from all envs, for specific views, and for specific data slices over time
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2280 Report aggregate data from all envs, for specific views, and for specific data slices over time Change By: Kurt Wall Summary: Report aggregate data from all environments envs , for specific views, and for specific data slices over time Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2281) Report transition from managed to unmanaged, when it happened, and the code responsible
Title: Message Title Kurt Wall created an issue PuppetDB / PDB-2281 Report transition from managed to unmanaged, when it happened, and the code responsible Issue Type: Bug Assignee: qa-team Components: QA Created: 2015/12/29 2:53 PM Priority: Normal Reporter: Kurt Wall As a sys admin, I want to see if a node went from managed to unmanaged, when it flipped, and the code that caused this to happen. This will allow me to identify if there are issues with some of my deployed code. Add Comment
Jira (PDB-2280) Report aggregate from all environments, for specific views, and for specific data slices over time
Title: Message Title Kurt Wall created an issue PuppetDB / PDB-2280 Report aggregate from all environments, for specific views, and for specific data slices over time Issue Type: Bug Assignee: qa-team Components: QA Created: 2015/12/29 2:52 PM Priority: Normal Reporter: Kurt Wall As a sys admin I want the ability to view aggregated data from all my environments. I want the ability to segregate out views for an admin, or specific data slices for an auditor over time. So that I can have a comprehensive view of my entire puppetized infrastructure. Add Comment
Jira (PDB-2279) Report historical data on a failed resources and associated actions to converge
Title: Message Title Kurt Wall created an issue PuppetDB / PDB-2279 Report historical data on a failed resources and associated actions to converge Issue Type: Bug Assignee: qa-team Components: QA Created: 2015/12/29 2:40 PM Priority: Normal Reporter: Kurt Wall As a sys admin I need to pull a report for my auditor who is requesting the state and associated actions from a failed resource event 6 months prior. So that I can trace how the resource fell out of the expected state, code that caused this, and the code that put the resource back in the expected state, and the expected state for that point in time. Add Comment
Jira (PDB-2278) Compare current failed catalog with previous good catalog and identify failure
Title: Message Title Kurt Wall created an issue PuppetDB / PDB-2278 Compare current failed catalog with previous good catalog and identify failure Issue Type: Bug Assignee: Unassigned Created: 2015/12/29 2:33 PM Priority: Normal Reporter: Kurt Wall As a sys admin I want the ability to do comparisons between the current failed state and the most recent green state of my resource. So that I can see what has changed and identify the offending code associated to the failure. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Thomas Hallgren commented on PUP-5209 Re: call_function and metadata.json: call a function from a different module, very strange behavior Thanks Francois Lafont for an excellent test suite. I can reproduce the two cases you mention. This issue is not resolved just yet. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2276) Remove usage of robert.hooke for tk-config
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-2276 Remove usage of robert.hooke for tk-config Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2276) Remove usage of robert.hooke for tk-config
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2276 Remove usage of robert.hooke for tk-config Change By: Russell Mull Scope Change Category: Adopted Scope Change Reason: Bandwidth Story Points: 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 (PDB-2276) Remove usage of robert.hooke for tk-config
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2276 Remove usage of robert.hooke for tk-config Change By: Russell Mull Sprint: PuppetDB 2015-12-30 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2277) (maint) Improve memory usage in benchmark tool
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-2277 (maint) Improve memory usage in benchmark tool Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2277) (maint) Improve memory usage in benchmark tool
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2277 (maint) Improve memory usage in benchmark tool Change By: Russell Mull Scope Change Category: Adopted Scope Change Reason: Bandwidth Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2262) NullPointerException while executing "extract" query against /pdb/query/v4/events
Title: Message Title Kurt Wall assigned an issue to Unassigned PuppetDB / PDB-2262 NullPointerException while executing "extract" query against /pdb/query/v4/events Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2262) NullPointerException while executing "extract" query against /pdb/query/v4/events
Title: Message Title Kurt Wall commented on PDB-2262 Re: NullPointerException while executing "extract" query against /pdb/query/v4/events From PDB 3.2.1, showing the error: # puppetdb --version puppetdb version: 3.2.1 # curl -XGET localhost:8080/pdb/query/v4/events -d 'query=["extract", ["certname"], ["and", ["=", "resource_type", "User"], ["=", "status", "noop"]], ["group_by", "certname", "resource_title"]]' Error 500 HTTP ERROR: 500 Problem accessi
Jira (PUP-5591) undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-5591 undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class Change By: Glenn Sarti Assignee: Rob Reynolds Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Francois Lafont commented on PUP-5209 Re: call_function and metadata.json: call a function from a different module, very strange behavior Hi, thanks guys for the work. This being said , I think the commit doesn't fix all the cases. Indeed, I have applied the changes in this commit in a testing (and updated) puppetserver and I have restarted the puppetserver. After that I have made some tests: I have called a puppet and ruby function from moda in init.pp, in a puppet function and in a ruby function of modb with the dependency declared and not declared (I think there are 12 tests if I count well). I have uploaded a new version of code in production_v2.zip. In this code, the tests just consist in comment/uncomment lines in modb/init.pp and in add/remove the dependency in modb/metadata.json (and launch a puppet run of course). Here is my conclusion concerning the remaining bugs: 1. modb can call any function of moda when called in modb/init.pp regardless if I add moda as dependency of modb or not. If I have well understood, if moda is not a dependency of modb, modb should not be able to call function of moda. 2. modb can not call any function of moda when called in a puppet function modb/functions/*.pp even if moda is added as dependency of modb in its metadata.json. I think the new production_v2.zip can help to make these tests. Regards. 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Francois Lafont updated an issue Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Change By: Francois Lafont Attachment: production_v2.zip 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Francois Lafont updated an issue Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Change By: Francois Lafont Attachment: production.zip Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2262) NullPointerException while executing "extract" query against /pdb/query/v4/events
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2262 NullPointerException while executing "extract" query against /pdb/query/v4/events Change By: Kurt Wall QA Risk Assessment: High Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2262) NullPointerException while executing "extract" query against /pdb/query/v4/events
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2262 NullPointerException while executing "extract" query against /pdb/query/v4/events Change By: Kurt Wall QA Risk Assessment Reason: No data loss or downtime, but still non-trivial Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2262) NullPointerException while executing "extract" query against /pdb/query/v4/events
Title: Message Title Kurt Wall assigned an issue to Kurt Wall PuppetDB / PDB-2262 NullPointerException while executing "extract" query against /pdb/query/v4/events Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2262) NullPointerException while executing "extract" query against /pdb/query/v4/events
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2262 NullPointerException while executing "extract" query against /pdb/query/v4/events Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2262) NullPointerException while executing "extract" query against /pdb/query/v4/events
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2262 NullPointerException while executing "extract" query against /pdb/query/v4/events Change By: Kurt Wall QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2264) Add setting to PuppetDB config to toggle historical catalog storage
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2264 Add setting to PuppetDB config to toggle historical catalog storage Change By: Kurt Wall QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2264) Add setting to PuppetDB config to toggle historical catalog storage
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2264 Add setting to PuppetDB config to toggle historical catalog storage Change By: Kurt Wall QA Status: Reviewed 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Francois Lafont updated an issue Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior New version with all the tests Change By: Francois Lafont Attachment: production.zip 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-5589) Type without namevar causes failures with no error
Title: Message Title Henrik Lindberg commented on PUP-5589 Re: Type without namevar causes failures with no error Good that there is an error now, and it will probably point user in the right direction. It would be even better if it could point out that there is no namevar whatso ever declared in the type (i.e. since the "set of title patterns" is probably empty ) 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Change By: Henrik Lindberg Release Notes Summary: Functions in a module (A) could not be called from other modules that in meta data expressed the dependency on module A using a dash to separate user and module name. A work around is to change the separator to '/'. Release Notes: Bug Fix 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Merged to stable at: 05f5cf4 Change By: Henrik Lindberg Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5612) Error message for declaring resource without title is confusing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5612 Error message for declaring resource without title is confusing Change By: Henrik Lindberg Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5612) Error message for declaring resource without title is confusing
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5612 Error message for declaring resource without title is confusing Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title
Thomas Hallgren commented on PUP-5209
Re: call_function and metadata.json: call a function from a different module, very strange behavior
I can reproduce the problem using the attached zip file. The problem remains even if I add a metadata.json file to both modules and declare a relationship from modb to moda (necessary for modb::bar to call moda::foo).
During debugging I discovered that my dependency, declared as:
{"name":"flaf-moda","version_requirement":">= 0.1.0"}
didn't have the desired effect on the loader. Why? Because a module name declared in a dependency must be separated by a slash rather than a dash. Changing the dependency to:
{"name":"flaf/moda","version_requirement":">= 0.1.0"}
will do the trick and moda and it's function is loaded and called correctly. This is definitely a bug and it was fixed in the Puppet Forge by
FORGE-52
. Puppet apparently still have issues with this.
Add Comment
Jira (PUP-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Change By: Thomas Hallgren Scope Change Category: Found Scope Change Reason: TODO column of current sprint is empty Story Points: 2 Sprint: Language 2016 2015 - 01 12 - 13 30 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 o
Jira (PUP-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-5061) Always restore full trusted information from store
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5061 Always restore full trusted information from store Change By: Thomas Hallgren Assignee: Sean Griffin Thomas Hallgren 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-5061) Always restore full trusted information from store
Title: Message Title Thomas Hallgren assigned an issue to Kylo Ginsberg Puppet / PUP-5061 Always restore full trusted information from store Change By: Thomas Hallgren Assignee: Thomas Hallgren Kylo Ginsberg 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-5589) Type without namevar causes failures with no error
Title: Message Title Thomas Hallgren commented on PUP-5589 Re: Type without namevar causes failures with no error The problem was that the logging of all errors that occurred during calls to the terminus.filter() method was suppressed. The puppet apply command assumes that all Puppet::Error exceptions has been logged by the compiler (which is correct) but the filter is called after successful compilation and before the Indirection.find method returns. PR-4532 ensures that the error is logged and I think that is enough to fix this issue even if the message doesn't explicitly mention isnamevar or :namevar = true. Instead it says: Error: No set of title patterns matched the title "" Which, from the looks of it, is correct. The isnamevar or :namevar = true are ways to ensure that a title pattern exists, but so will a parameter named :name. The title_patterns method is marked @api_private though, so perhaps it is questionable to expose that concept in an error message. 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-5589) Type without namevar causes failures with no error
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5589 Type without namevar causes failures with no error Change By: Thomas Hallgren Assignee: Thomas Hallgren 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.
