Jira (PUP-7318) Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10
Title: Message Title Josh Cooper commented on PUP-7318 Re: Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10 puppet-agent#6c02a348ab passed CI including revert commit, resolving Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3294) Update i18n dev-resources
Title: Message Title Larissa Lane updated an issue PuppetDB / PDB-3294 Update i18n dev-resources Change By: Larissa Lane Labels: i18n maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7362) Puppet lookup in 4.9.4 failed to interpolate Hiera data path
Title: Message Title Henrik Lindberg commented on PUP-7362 Re: Puppet lookup in 4.9.4 failed to interpolate Hiera data path Ping Thomas Hallgren can you take a look? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3359) AST regex queries against parameters have to match the full string
Title: Message Title
Russell Mull commented on PDB-3359
Re: AST regex queries against parameters have to match the full string
The engine.clj code responsible for expanding the query short just looks... wrong.
[[(op :guard #{"=" "~"}) ["parameter" param-name] param-value]]
["in" "resource"
["extract" "res_param_resource"
["select_params"
["and"
[op "res_param_name" param-name]
[op "res_param_value" (su/db-serialize param-value)]
I think that'll actually try to json-encode the regex. Also, somehow if you are using a regex to compare with the param value, you are also getting a regex on the param name whether you like it or not.
Jira (PDB-3359) AST regex queries against parameters have to match the full string
Title: Message Title Ryan Whitehurst created an issue PuppetDB / PDB-3359 AST regex queries against parameters have to match the full string Issue Type: Bug Assignee: Unassigned Created: 2017/03/16 4:56 PM Priority: Normal Reporter: Ryan Whitehurst For example, ["~", "title", "puppet-"] will match a title value of puppet-agent-last_run_time, but ["", ["parameter", "display_name"], "puppet-"] won't match a display_name parameter with the value puppet-agent-last_run_time; however, ["", ["parameter", "display_name"], "puppet-.*"] will. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3285) PQL's ~ operator doesn't work on resource parameters
Title: Message Title Ryan Whitehurst commented on PDB-3285 Re: PQL's ~ operator doesn't work on resource parameters Also, looks like null? fails on parameters in the AST syntax as well [rw@pe-mom1-prod ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=["from", "resources", ["null?", ["parameter", "content"], true]]' Error 500 HTTP ERROR: 500 Problem accessing /pdb/query/v4. Reason: Value does not match schema: (not (map? nil)) Powered by
Jira (PDB-3285) PQL's ~ operator doesn't work on resource parameters
Title: Message Title Ryan Whitehurst commented on PDB-3285 Re: PQL's ~ operator doesn't work on resource parameters The same seems to be true for is null and is not null. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7350) Update minitar to 0.6.1
Title: Message Title Moses Mendoza commented on PUP-7350 Re: Update minitar to 0.6.1 merged to 4.10.x at 490cfad4950b7994b5c18fb638469ef7bd50c239 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7350) Update minitar to 0.6.1
Title: Message Title Moses Mendoza commented on PUP-7350 Re: Update minitar to 0.6.1 merged to master at 8af414bc417feed541d5ffe3dc26477b04c4ade8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-166) Release new version of puppet-strings
Title: Message Title Lindsey Smith created an issue Puppet Strings / PDOC-166 Release new version of puppet-strings Issue Type: Task Affects Versions: PDOC 1.0.0 Assignee: Unassigned Created: 2017/03/16 3:09 PM Priority: Blocker Reporter: Lindsey Smith Build and release a new version of strings, largely to ship PDOC-161 (add a summary tag) Add Comment This message was sent by Atlassian JIRA
Jira (PDOC-166) Release new version of puppet-strings
Title: Message Title Lindsey Smith updated an issue Puppet Strings / PDOC-166 Release new version of puppet-strings Change By: Lindsey Smith Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-165) Release puppet-strings 1.1.0
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-165 Release puppet-strings 1.1.0 Issue Type: Task Assignee: Unassigned Created: 2017/03/16 2:49 PM Priority: Normal Reporter: William Hopper Skipping subtasks in favor or just commenting here. 1. Is the code ready for release? 2. Reconcile git commits and JIRA tickets 3. Is the Jira tidy-up done for this release and prepared for the next one? 4. Prepare long form release notes: 5. Tag the release 6. Build and smoke test gem 7. Push tag to GitHub 8. Send out announcements 9. Close all resolved tickets in JIRA. Add Comment
Jira (PUP-7273) Hiera 5: strange error unless path is defined
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7273 Hiera 5: strange error unless path is defined Change By: Thomas Hallgren Summary: Hiera 5: strange error unless data_hash path is defined Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3358) (maint) Fix doc issue with `JSON` example
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3358 (maint) Fix doc issue with `JSON` example Issue Type: Bug Assignee: Unassigned Created: 2017/03/16 2:30 PM Priority: Normal Reporter: gepetto-bot Without the extra newline the JSON isn't highlighted Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7314) Implied module namespace for PCore objects
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7314 Implied module namespace for PCore objects Change By: Thomas Hallgren Sprint: PDE 2017-03-08 Triage , PDE 2017-03- 29 08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7363) Create acceptance test for PUP-2349
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-7363 Create acceptance test for PUP-2349 Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7350) Update minitar to 0.6.1
Title: Message Title Moses Mendoza commented on PUP-7350 Re: Update minitar to 0.6.1 merged to stable at https://github.com/puppetlabs/puppet/commit/a7179084c733007d4ad256205f403a07aacdcf70 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1453) $ipaddress on openvz container returning 127.0.0.2
Title: Message Title Branan Riley commented on FACT-1453 Re: $ipaddress on openvz container returning 127.0.0.2 Ah, yup. In Facter 3, we pick out the interface to use for the global ipaddress fact based on the default route, which is venet0, not venet0:0. Older versions of Facter would just read through all interfaces in alphabetical order, and ignore any that had loopback addresses. Unfortunately for any non-trivial networking configuration (including OpenVZ's), "what is my IP address?" is actually a pretty hard question, and we may end up needing to add additional detection methods for when the routes-based one fails or returns nonsense like a loopback IP Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3356) Use anti-join when eliminating inactive nodes from queries
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-3356 Use anti-join when eliminating inactive nodes from queries Change By: Wyatt Alt Assignee: Wyatt Alt Sprint: Hopper SE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7356) acceptance: add tests for empty/conflicting clientbucket behavior
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7356 acceptance: add tests for empty/conflicting clientbucket behavior Change By: Josh Cooper Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7364) Parser result no longer contains current method
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7364 Parser result no longer contains current method Change By: Josh Cooper Team: Puppet Developer Experience Component/s: Language Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7362) Puppet lookup in 4.9.4 failed to interpolate Hiera data path
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7362 Puppet lookup in 4.9.4 failed to interpolate Hiera data path Change By: Josh Cooper Summary: Puppet lookup in 4.9. 5 4 failed to interpolate Hiera data path Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7362) Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7362 Puppet lookup in 4.9.5 failed to interpolate Hiera data path Change By: Josh Cooper Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7360) Apparently a Puppet Hiera error message points to a 404
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7360 Apparently a Puppet Hiera error message points to a 404 Change By: Josh Cooper Story Points: 1 Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-563) hiera tests failing on CiscoXR master hardware pipeline
Title: Message Title Geoff Nichols updated an issue Hiera / HI-563 hiera tests failing on CiscoXR master hardware pipeline Change By: Geoff Nichols Issue Type: Task CI Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7353) Capture debug locally on the client
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7353 Capture debug locally on the client Change By: Geoff Nichols Sprint: Agent Accepted Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7353) Capture debug locally on the client
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7353 Capture debug locally on the client Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7353) Capture debug locally on the client
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7353 Capture debug locally on the client Change By: Geoff Nichols Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7353) Capture debug locally on the client
Title: Message Title Geoff Nichols commented on PUP-7353 Re: Capture debug locally on the client Per discussion in Agent triage, Puppet does not currently provide facility to use a different loglevel for different destinations. There are probably a number of design and UX considerations. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7353) Capture debug locally on the client
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7353 Capture debug locally on the client Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-563) hiera tests failing on CiscoXR master hardware pipeline
Title: Message Title Maggie Dreyer commented on HI-563 Re: hiera tests failing on CiscoXR master hardware pipeline This is another incarnation of the Ruby segfault that should be solved by PA-437. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7349) resource type tidy does not honor metaparameter noop
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7349 resource type tidy does not honor metaparameter noop Change By: Geoff Nichols Fix Version/s: PUP 4.9.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7349) resource type tidy does not honor metaparameter noop
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7349 resource type tidy does not honor metaparameter noop Change By: Geoff Nichols Sprint: Agent Triage Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1589) Need to rethink behavior of specifying facter directory's or not allowing facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1589 Need to rethink behavior of specifying facter directory's or not allowing facts Change By: Geoff Nichols Sprint: Agent Triage Accepted Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7343) exec path and environment attributes do not work as documented
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7343 exec path and environment attributes do not work as documented Change By: Geoff Nichols Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7343) exec path and environment attributes do not work as documented
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7343 exec path and environment attributes do not work as documented Change By: Geoff Nichols Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7343) exec path and environment attributes do not work as documented
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7343 exec path and environment attributes do not work as documented Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7307) Tidy should support 'purge' or update file resource
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7307) Tidy should support 'purge' or update file resource
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: Geoff Nichols Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1590) facter built with vanagon on F25 for AArch64 has double free bug
Title: Message Title Richard Henwood commented on FACT-1590 Re: facter built with vanagon on F25 for AArch64 has double free bug I tested a build of facter against the system supplied boost and it didn't have this problem - so your diagnosis sounds about right. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7364) Parser result no longer contains current method
Title: Message Title Corey Osman created an issue Puppet / PUP-7364 Parser result no longer contains current method Issue Type: Bug Affects Versions: PUP 5.0.0 Assignee: Unassigned Created: 2017/03/16 9:59 AM Priority: Normal Reporter: Corey Osman The puppet debugger uses the AST model to get a model object in order to import itself into the known resource types. In order to make this work with puppet 5 I had to refactor my code slightly to account for the missing method. Not a huge deal but this might break other third party code. Previously I was calling parse_result.current to get the model. However, with puppet 5 I actually don't need to do that anymore since the model object is the parsed result. But because puppet-debugger supports puppet 3-5 I had to write the following code to work around the issue. Puppet 5 should add a current method to the parsed_result object that points to itself, thus keeping third party integrations working. Example: # adds backward compatible call so we don't break third party programs.
Jira (PUP-7340) context_spec.rb fails when run in isolation
Title: Message Title Josh Cooper commented on PUP-7340 Re: context_spec.rb fails when run in isolation Merged to stable in 10d295a. I added a commit to touch the file mtime, so we don't need to sleep in the test. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7340) context_spec.rb fails when run in isolation
Title: Message Title Josh Cooper assigned an issue to Thomas Hallgren Puppet / PUP-7340 context_spec.rb fails when run in isolation Change By: Josh Cooper Assignee: Josh Cooper Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7283) Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-7283 Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization Change By: Adrien Thebo Assignee: Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7283) Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization
Title: Message Title Adrien Thebo commented on PUP-7283 Re: Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization Kicking back to in progress to fix the issues that came up in acceptance testing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7363) Create acceptance test for PUP-2349
Title: Message Title Kurt Wall created an issue Puppet / PUP-7363 Create acceptance test for PUP-2349 Issue Type: Bug Assignee: Kurt Wall Components: Types and Providers Created: 2017/03/16 9:29 AM Labels: QA Priority: Normal Reporter: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7363) Create acceptance test for PUP-2349
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7363 Create acceptance test for PUP-2349 Change By: Kurt Wall QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7363) Create acceptance test for PUP-2349
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7363 Create acceptance test for PUP-2349 Change By: Kurt Wall Verify that puppet emits an error if a file resource is declared using a numeric mode attribute. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7342) Create acceptance test for PUP-5058
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-7342 Create acceptance test for PUP-5058 Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6873) functionality for redirecting hiera_xxx calls to lookup, in existing modules
Title: Message Title Eric Thompson commented on PUP-6873 Re: functionality for redirecting hiera_xxx calls to lookup, in existing modules agreed. tons of testing on this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6872) allow global hiera and lookup in different environments
Title: Message Title Henrik Lindberg commented on PUP-6872 Re: allow global hiera and lookup in different environments Do you think the documentation that is now written is not enough? If so, docs ticket is needed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Lindsey Smith commented on PUP-4242 Re: Add deprecation warnings for manifests declaring things in wrong namespace I'm +1 to adding the deprecation in 4.10 and before deciding whether to remove in 5.0 we should listen for complaints. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6872) allow global hiera and lookup in different environments
Title: Message Title Lindsey Smith commented on PUP-6872 Re: allow global hiera and lookup in different environments This was from the discussion of how to incrementally migrate your Hiera 3 usage to Hiera 5 where the user wanted to proceed environment by environment so that they could test/confirm with a smaller surface are. Does that help? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Henrik Lindberg commented on PUP-4242 Re: Add deprecation warnings for manifests declaring things in wrong namespace Autoloaded code in top scope causes strange problems as the order of evaluation is a complete mystery to users. We have a busted flag that is supposed to protect against this, but it has probably never worked. Thus, it is a source of mysterious and sometimes hard to find problems. There isn't really any valid usecases for this. Maybe there was back in 2.7 and where import (now removed) was the in use everywhere. Getting rid if this is mainly a hygiene issue, but it also prevents some code from being more efficient (since top scope may all of a sudden be different), and we have to be aware of this. Turning on the deprecation will help us figure out how much bad code there is out there. henrik Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6874) per environment: turn off global hiera
Title: Message Title Henrik Lindberg commented on PUP-6874 Re: per environment: turn off global hiera Yes henrik Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7341) Regex Lookup isn't working with Puppet 4.9
Title: Message Title Thomas Hallgren commented on PUP-7341 Re: Regex Lookup isn't working with Puppet 4.9 Andreas Ntaflos, this is per design. The regexp must be anchored anyway to ensure that the module name prefix comes first so we decided to use it as the token to differentiate between a regular key and a regexp. Did you notice the workaround mentioned in under the docs tab? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7341) Regex Lookup isn't working with Puppet 4.9
Title: Message Title
Andreas Ntaflos commented on PUP-7341
Re: Regex Lookup isn't working with Puppet 4.9
Just noticed this problem as well. Using a regex with anchors, like "^profile::(.*)::foo$" results in the above error message. Removing the anchors from the regex ("profile::(.*)::foo") seems to turn it into a regular string as far as Puppet and Hiera are concerned and the lookup options for such keys are subsequently ignored (because no lookup key matches profile::(.*)::foo literally). At least that's my interpretation of what I am observing.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7340) context_spec.rb fails when run in isolation
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7340 context_spec.rb fails when run in isolation Change By: Thomas Hallgren Sprint: PDE 2017-03-29 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7182) Do not report errors in Hiera config as errors in Puppet manifest
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7182 Do not report errors in Hiera config as errors in Puppet manifest Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6874) per environment: turn off global hiera
Title: Message Title Lindsey Smith commented on PUP-6874 Re: per environment: turn off global hiera I agree that we shouldn't turn off the global layer. Next step is closed/won't fix this ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Lindsey Smith commented on PUP-4242 Re: Add deprecation warnings for manifests declaring things in wrong namespace What's the impact of forbidding this? I can understand why we wouldn't want to allow declaring things outside the namespace but don't know how many people that will bite or if there are community patterns of usage built on top of something undesirable. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7362) Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Title: Message Title
Jianwen Wei updated an issue
Puppet / PUP-7362
Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Change By:
Jianwen Wei
Hi,This issue was orginaly posted on Pupepet user lsit https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/0Pgxjk5Ru4I/goQU3tz3BQAJ . Being suggested by Eric Thompson and Henrik Lindberg, I file a ticket for PUP here. After upgrading openproductionource opensource Puppet to version 4.9.4, I followed the Hiera guide https://docs.puppet.com/puppet/4.9/hiera_hierarchy.html#most-hierarchies-interpolate-variables to feed some data to it. I found that for some node, 'puppet lookup' failed to interpolate variables in yaml setting, which lead to incorrect lookup results.Steps to reproduce this issue 1. Install Puppet server on puppet.pi.sjtu.edu.cn . 2. Install Puppet agents on puppet.pi.sjtu.edu.cn, slurm1.pi.sjtu.edu.cn and mu05.pi.sjtu.edu.cn. Sign certificates for them. 3. Delete global hiera setting `/etc/puppetlabs/code/hiera.yaml`. # rm -f /etc/puppetlabs/code/hiera.yaml 4. Create an environment named `production`. # mkdir -p /etc/puppetlabs/code/environments/production/{hieradata,maifests,modules} 5. Create the Hiera conf file for the production environment in `/etc/puppetlabs/code/environments/production/hiera.yaml`{code:java}---version: 5defaults: datadir: hieradata data_hash: yaml_datahierarchy: - name: "Per-node data"path: "nodes/%{trusted.certname}.yaml" - name: "common"path: "common.yaml"{code} 6. Add common data in `/etc/puppetlabs/code/environments/production/hieradata/common.yaml`:{code:java}---group: Compute Nodes{code} 7a. Add per-node hiera data for slurm1.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/slurm1.pi.sjtu.edu.cn.yaml`:{code:java}---group: SLURM{code} 7b. Add per-node hiera data for puppet.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml`:{code:java}---group: Puppet Server{code} 8a. Lookup group for puppet.pi.sjtu.edu.cn and successfully get "Puppet Server" stored in `puppet.pi.sjtu.edu.cn.yaml`.{code:java}# puppet lookup group --node puppet.pi.sjtu.edu.cn --explainSearching for "lookup_options" Global Data Provider (hiera configuration version 5)No such key: "lookup_options" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Merge strategy hash Hierarchy entry "Per-node data"Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml" Original path: "nodes/%{trusted.certname}.yaml" No such key: "lookup_options" Hierarchy entry "common"Path "/etc/puppetlabs/code/environments/production/hieradata/common.yaml" Original path: "common.yaml" No such key: "lookup_options"Searching for "group" Global Data Provider (hiera configuration version 5)No such key: "group" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Hierarchy entry "Per-node data" Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml"
Jira (PUP-7362) Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Title: Message Title
Jianwen Wei updated an issue
Puppet / PUP-7362
Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Change By:
Jianwen Wei
Hi,This issue was orginaly posted on Pupepet user lsit https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/0Pgxjk5Ru4I/goQU3tz3BQAJ . Being suggested by Eric Thompson and Henrik Lindberg, I file a ticket for PUP here. After upgrading openproductionource Puppet to version 4.9.4, I followed the Hiera guide https://docs.puppet.com/puppet/4.9/hiera_hierarchy.html#most-hierarchies-interpolate-variables to feed some data to it. I found that for some node, 'puppet lookup' failed to interpolate variables in yaml setting, which lead to incorrect lookup results.Steps to reproduce this issue 1. Install Puppet server on puppet.pi.sjtu.edu.cn . 2. Install Puppet agents on puppet.pi.sjtu.edu.cn, slurm1.pi.sjtu.edu.cn and mu05.pi.sjtu.edu.cn. Sign certificates for them. 3. Delete global hiera setting `/etc/puppetlabs/code/hiera.yaml`. # rm -f /etc/puppetlabs/code/hiera.yaml 4. Create an environment named `production`. # mkdir -p /etc/puppetlabs/code/environments/production/{hieradata,maifests,modules} 5. Create the Hiera conf file for the production environment in `/etc/puppetlabs/code/environments/production/hiera.yaml`{code:java}---version: 5defaults: datadir: hieradata data_hash: yaml_datahierarchy: - name: "Per-node data"path: "nodes/%{trusted.certname}.yaml" - name: "common"path: "common.yaml"{code} 6. Add common data in `/etc/puppetlabs/code/environments/production/hieradata/common.yaml`:{code:java}---group: Compute Nodes{code} 7a. Add per-node hiera data for slurm1.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/slurm1.pi.sjtu.edu.cn.yaml`:{code:java}---group: SLURM{code} 7b. Add per-node hiera data for puppet.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml`:{code:java}---group: Puppet Server{code} 8a. Lookup group for puppet.pi.sjtu.edu.cn and successfully get "Puppet Server" stored in `puppet.pi.sjtu.edu.cn.yaml`.{code:java}# puppet lookup group --node puppet.pi.sjtu.edu.cn --explainSearching for "lookup_options" Global Data Provider (hiera configuration version 5)No such key: "lookup_options" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Merge strategy hash Hierarchy entry "Per-node data"Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml" Original path: "nodes/%{trusted.certname}.yaml" No such key: "lookup_options" Hierarchy entry "common"Path "/etc/puppetlabs/code/environments/production/hieradata/common.yaml" Original path: "common.yaml" No such key: "lookup_options"Searching for "group" Global Data Provider (hiera configuration version 5)No such key: "group" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Hierarchy entry "Per-node data" Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml"Original path:
Jira (PUP-7362) Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Title: Message Title
Jianwen Wei updated an issue
Puppet / PUP-7362
Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Change By:
Jianwen Wei
Hi,This issue was orginaly posted on Pupepet user lsit https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/0Pgxjk5Ru4I/goQU3tz3BQAJ . Being suggested by Eric Thompson and Henrik Lindberg, I file a ticket for PUP here. After upgrading openproductionource Puppet to version 4.9.4, I followed the Hiera guide https://docs.puppet.com/puppet/4.9/hiera_hierarchy.html#most-hierarchies-interpolate-variables to feed some data to it. I found that for some node, 'puppet lookup' failed to interpolate variables in yaml setting, which lead to incorrect lookup results.Steps to reproduce this issue 1. Install Puppet server on puppet.pi.sjtu.edu.cn . 2. Install Puppet agents on puppet.pi.sjtu.edu.cn, slurm1.pi.sjtu.edu.cn and mu05.pi.sjtu.edu.cn. Sign certificates for them. 3. Delete global hiera setting `/etc/puppetlabs/code/hiera.yaml`. # rm -f /etc/puppetlabs/code/hiera.yaml 4. Create an environment named `production`. # mkdir -p /etc/puppetlabs/code/environments/production/{hieradata,maifests,modules} 5. Create the Hiera conf file for the production environment in `/etc/puppetlabs/code/environments/production/hiera.yaml`{code:java}---version: 5defaults: datadir: hieradata data_hash: yaml_datahierarchy: - name: "Per-node data"path: "nodes/%{trusted.certname}.yaml" - name: "common"path: "common.yaml"{code} 6. Add common data in `/etc/puppetlabs/code/environments/production/hieradata/common.yaml`:{code:java}---group: Compute Nodes{code} 7a. Add per-node hiera data for slurm1.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/slurm1.pi.sjtu.edu.cn.yaml`:{code:java}---group: SLURM{code} 7b. Add per-node hiera data for puppet.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml`:{code:java}---group: Puppet Server{code} 8a. Lookup group for puppet.pi.sjtu.edu.cn and successfully get "Puppet Server" stored in `puppet.pi.sjtu.edu.cn.yaml`.{code:java}# puppet lookup group --node puppet.pi.sjtu.edu.cn --explainSearching for "lookup_options" Global Data Provider (hiera configuration version 5)No such key: "lookup_options" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Merge strategy hash Hierarchy entry "Per-node data"Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml" Original path: "nodes/%{trusted.certname}.yaml" No such key: "lookup_options" Hierarchy entry "common"Path "/etc/puppetlabs/code/environments/production/hieradata/common.yaml" Original path: "common.yaml" No such key: "lookup_options"Searching for "group" Global Data Provider (hiera configuration version 5)No such key: "group" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Hierarchy entry "Per-node data" Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml"Original path:
Jira (FACT-1591) Add TestRail comments to connect test cases to the tests
Title: Message Title John Duarte updated an issue Facter / FACT-1591 Add TestRail comments to connect test cases to the tests Change By: John Duarte QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7204 Add support for mapped paths in hiera.yaml version 5 Change By: Craig Gomes Sprint: PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6373) SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6373 SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics Change By: Craig Gomes Sprint: PDE 2017-02-08, PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7102) Insufficient logging when encountering 'permission denied' on environmentpath
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7102 Insufficient logging when encountering 'permission denied' on environmentpath Change By: Craig Gomes Sprint: PDE 2017-02-08, PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7226) Remove vendored Rgen gem
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7226 Remove vendored Rgen gem Change By: Craig Gomes Sprint: PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7314) Implied module namespace for PCore objects
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7314 Implied module namespace for PCore objects Change By: Craig Gomes Sprint: PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7273) Hiera 5: error unless data_hash is defined
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7273 Hiera 5: error unless data_hash is defined Change By: Craig Gomes Sprint: PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7362) Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Title: Message Title
Jianwen Wei updated an issue
Puppet / PUP-7362
Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Change By:
Jianwen Wei
Hi,This issue was orginaly posted on Pupepet user lsit https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/0Pgxjk5Ru4I/goQU3tz3BQAJ . Being suggested by Eric Thompson and Henrik Lindberg, I file a ticket for PUP here. After upgrading openproductionource Puppet to version 4.9.4, I followed the Hiera guide https://docs.puppet.com/puppet/4.9/hiera_hierarchy.html#most-hierarchies-interpolate-variables to feed some data to it. I found that for some node, 'puppet lookup' failed to interpolate variables in yaml setting, which lead to incorrect lookup results.Steps to reproduce this issue 1. Install Puppet server on puppet.pi.sjtu.edu.cn . 2. Install Puppet agents on puppet.pi.sjtu.edu.cn, slurm1.pi.sjtu.edu.cn and mu05.pi.sjtu.edu.cn. Sign certificates for them. 3. Delete global hiera setting `/etc/puppetlabs/code/hiera.yaml`. # rm -f /etc/puppetlabs/code/hiera.yaml 4. Create an environment named `production`. # mkdir -p /etc/puppetlabs/code/environments/production/{hieradata,maifests,modules} 5. Create the Hiera conf file for the production environment in `/etc/puppetlabs/code/environments/production/hiera.yaml`{code:java}---version: 5defaults: datadir: hieradata data_hash: yaml_datahierarchy: - name: "Per-node data"path: "nodes/%{trusted.certname}.yaml" - name: "common"path: "common.yaml"{code} 6. Add common data in `/etc/puppetlabs/code/environments/production/hieradata/common.yaml`:{code:java}---group: Compute Nodes{code} 7a. Add per-node hiera data for slurm1.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/slurm1.pi.sjtu.edu.cn.yaml`:{code:java}---group: SLURM{code} 7b. Add per-node hiera data for puppet.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml`:{code:java}---group: Puppet Server{code} 8a. Lookup group for puppet.pi.sjtu.edu.cn and successfully get "Puppet Server" stored in `puppet.pi.sjtu.edu.cn.yaml`.{code:java}# puppet lookup group --node puppet.pi.sjtu.edu.cn --explainSearching for "lookup_options" Global Data Provider (hiera configuration version 5)No such key: "lookup_options" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Merge strategy hash Hierarchy entry "Per-node data"Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml" Original path: "nodes/%{trusted.certname}.yaml" No such key: "lookup_options" Hierarchy entry "common"Path "/etc/puppetlabs/code/environments/production/hieradata/common.yaml" Original path: "common.yaml" No such key: "lookup_options"Searching for "group" Global Data Provider (hiera configuration version 5)No such key: "group" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Hierarchy entry "Per-node data" Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml"Original path:
Jira (PUP-7225) Remove the Puppet Binder
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7225 Remove the Puppet Binder Change By: Craig Gomes Sprint: PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7237) fix puppet acceptance Rake tasks
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7237 fix puppet acceptance Rake tasks Change By: Craig Gomes Sprint: PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7362) Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Title: Message Title
Jianwen Wei updated an issue
Puppet / PUP-7362
Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Change By:
Jianwen Wei
Hi,This issue was orginaly posted on Pupepet user lsit https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/0Pgxjk5Ru4I/goQU3tz3BQAJ . Being suggested by Eric Thompson and Henrik Lindberg, I file a ticket for PUP here. After upgrading openproductionource Puppet to version 4.9.4, I followed the Hiera guide https://docs.puppet.com/puppet/4.9/hiera_hierarchy.html#most-hierarchies-interpolate-variables to feed some data to it. I found that for some node, 'puppet lookup' failed to interpolate variables in yaml setting, which lead to incorrect lookup results.Steps to reproduce this issue 1. Install Puppet server on puppet.pi.sjtu.edu.cn . 2. Install Puppet agents on puppet.pi.sjtu.edu.cn, slurm1.pi.sjtu.edu.cn and mu05.pi.sjtu.edu.cn. Sign certificates for them. 3. Delete global hiera setting `/etc/puppetlabs/code/hiera.yaml`. # rm -f /etc/puppetlabs/code/hiera.yaml 4. Create an environment named `production`. # mkdir -p /etc/puppetlabs/code/environments/production/{hieradata,maifests,modules} 5. Create the Hiera conf file for the production environment in `/etc/puppetlabs/code/environments/production/hiera.yaml`{code:java}---version: 5defaults: datadir: hieradata data_hash: yaml_datahierarchy: - name: "Per-node data"path: "nodes/%{trusted.certname}.yaml" - name: "common"path: "common.yaml"{code} 6. Add common data in `/etc/puppetlabs/code/environments/production/hieradata/common.yaml`:{code:java}---group: Compute Nodes{code} 7a. Add per-node hiera data for slurm1.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/slurm1.pi.sjtu.edu.cn.yaml`:{code:java}---group: SLURM{code} 7b. Add per-node hiera data for puppet.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml`:{code:java}---group: Puppet Server{code} 8a. Lookup group for puppet.pi.sjtu.edu.cn and successfully get "Puppet Server" stored in `puppet.pi.sjtu.edu.cn.yaml`.{code:java}# puppet lookup group --node puppet.pi.sjtu.edu.cn --explainSearching for "lookup_options" Global Data Provider (hiera configuration version 5)No such key: "lookup_options" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Merge strategy hash Hierarchy entry "Per-node data"Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml" Original path: "nodes/%{trusted.certname}.yaml" No such key: "lookup_options" Hierarchy entry "common"Path "/etc/puppetlabs/code/environments/production/hieradata/common.yaml" Original path: "common.yaml" No such key: "lookup_options"Searching for "group" Global Data Provider (hiera configuration version 5)No such key: "group" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Hierarchy entry "Per-node data" Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml"Original path:
Jira (PUP-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title John Duarte updated an issue Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names Change By: John Duarte QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7362) Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Title: Message Title
Jianwen Wei updated an issue
Puppet / PUP-7362
Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Change By:
Jianwen Wei
Hi,This issue was orginaly posted on Pupepet user lsit https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/0Pgxjk5Ru4I/goQU3tz3BQAJ . Being suggested by Eric Thompson and Henrik Lindberg, I file a ticket for PUP here. After upgrading openproductionource Puppet to version 4.9.4, I followed the Hiera guide https://docs.puppet.com/puppet/4.9/hiera_hierarchy.html#most-hierarchies-interpolate-variables to feed some data to it. I found that for some node, 'puppet lookup' failed to interpolate variables in yaml setting, which lead to incorrect lookup results.Steps to reproduce this issue 1. Install Puppet server on puppet.pi.sjtu.edu.cn . 2. Install Puppet agents on puppet.pi.sjtu.edu.cn, slurm1.pi.sjtu.edu.cn and mu05.pi.sjtu.edu.cn. Sign certificates for them. 3. Delete global hiera setting `/etc/puppetlabs/code/hiera.yaml`. # rm -f /etc/puppetlabs/code/hiera.yaml 4. Create an environment named `production`. # mkdir -p /etc/puppetlabs/code/environments/production/{hieradata,maifests,modules} 5. Create the Hiera conf file for the production environment in `/etc/puppetlabs/code/environments/production/hiera.yaml`{code:java}---version: 5defaults: datadir: hieradata data_hash: yaml_datahierarchy: - name: "Per-node data"path: "nodes/%{trusted.certname}.yaml" - name: "common"path: "common.yaml"{code} 6. Add common data in `/etc/puppetlabs/code/environments/production/hieradata/common.yaml`:{code:java}---group: Compute Nodes{code} 7a. Add per-node hiera data for slurm1.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/slurm1.pi.sjtu.edu.cn.yaml`:{code:java}---group: SLURM{code} 7b. Add per-node hiera data for puppet.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml`:{code:java}---group: Puppet Server{code} 8a. Lookup group for puppet.pi.sjtu.edu.cn and successfully get "Puppet Server" stored in `puppet.pi.sjtu.edu.cn.yaml`.{code:java}# puppet lookup group --node puppet.pi.sjtu.edu.cn --explainSearching for "lookup_options" Global Data Provider (hiera configuration version 5)No such key: "lookup_options" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Merge strategy hash Hierarchy entry "Per-node data"Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml" Original path: "nodes/%{trusted.certname}.yaml" No such key: "lookup_options" Hierarchy entry "common"Path "/etc/puppetlabs/code/environments/production/hieradata/common.yaml" Original path: "common.yaml" No such key: "lookup_options"Searching for "group" Global Data Provider (hiera configuration version 5)No such key: "group" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Hierarchy entry "Per-node data" Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml"Original path:
Jira (PUP-7314) Implied module namespace for PCore objects
Title: Message Title Henrik Lindberg commented on PUP-7314 Re: Implied module namespace for PCore objects After a long talk with Rick Sherman we came to the conclusion that the generated types must have fully qualified names as they are indeed different entities. The UX problem is that we require the use of the fully qualified names. The suggested import will help with shortening the names, but cannot shorten them beyond the most common root used in a .pp file - which still requires quite long names to be used. Shortening the names further is a separate issue - the import is still of value. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7362) Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Title: Message Title
Jianwen Wei updated an issue
Puppet / PUP-7362
Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Change By:
Jianwen Wei
Hi,This issue was orginaly posted on Pupepet user lsit https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/0Pgxjk5Ru4I/goQU3tz3BQAJ . Being suggested by Eric Thompson and Henrik Lindberg, I file a ticket for PUP here. After upgrading openproductionource Puppet to version 4.9.4, I followed the Hiera guide https://docs.puppet.com/puppet/4.9/hiera_hierarchy.html#most-hierarchies-interpolate-variables to feed some data to it. I found that for some node, 'puppet lookup' failed to interpolate variables in yaml setting, which lead to incorrect lookup results.Steps to reproduce this issue 1. Install Puppet server on puppet.pi.sjtu.edu.cn . 2. Install Puppet agents on puppet.pi.sjtu.edu.cn, slurm1.pi.sjtu.edu.cn and mu05.pi.sjtu.edu.cn. Sign certificates for them. 3. Delete global hiera setting `/etc/puppetlabs/code/hiera.yaml`. # rm -f /etc/puppetlabs/code/hiera.yaml 4. Create an environment named `production`. # mkdir -p /etc/puppetlabs/code/environments/production/{hieradata,maifests,modules} 5. Create the Hiera conf file for the production environment in `/etc/puppetlabs/code/environments/production/hiera.yaml`{code:java}---version: 5defaults: datadir: hieradata data_hash: yaml_datahierarchy: - name: "Per-node data"path: "nodes/%{trusted.certname}.yaml" - name: "common"path: "common.yaml"{code} 6. Add common data in `/etc/puppetlabs/code/environments/production/hieradata/common.yaml`:{code:java}---group: Compute Nodes{code} 7a. Add per-node hiera data for slurm1.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/slurm1.pi.sjtu.edu.cn.yaml`:{code:java}---group: SLURM{code} 7b. Add per-node hiera data for puppet.pi.sjtu.edu.cn in `/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml`:{code:java}---group: Puppet Server{code} 8a. Lookup group for puppet.pi.sjtu.edu.cn and successfully get "Puppet Server" stored in `puppet.pi.sjtu.edu.cn.yaml`.{code:java}# puppet lookup group --node puppet.pi.sjtu.edu.cn --explainSearching for "lookup_options" Global Data Provider (hiera configuration version 5)No such key: "lookup_options" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Merge strategy hash Hierarchy entry "Per-node data"Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml" Original path: "nodes/%{trusted.certname}.yaml" No such key: "lookup_options" Hierarchy entry "common"Path "/etc/puppetlabs/code/environments/production/hieradata/common.yaml" Original path: "common.yaml" No such key: "lookup_options"Searching for "group" Global Data Provider (hiera configuration version 5)No such key: "group" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Hierarchy entry "Per-node data" Path "/etc/puppetlabs/code/environments/production/hieradata/nodes/puppet.pi.sjtu.edu.cn.yaml"Original path:
Jira (PUP-7362) Puppet lookup in 4.9.5 failed to interpolate Hiera data path
Title: Message Title Jianwen Wei created an issue Puppet / PUP-7362 Puppet lookup in 4.9.5 failed to interpolate Hiera data path Issue Type: Bug Affects Versions: PUP 4.9.4 Assignee: Unassigned Components: CLI Created: 2017/03/16 7:35 AM Environment: CentOS 7 Priority: Normal Reporter: Jianwen Wei Hi, This issue was orginaly posted on Pupepet user lsit https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/0Pgxjk5Ru4I/goQU3tz3BQAJ . Being suggested by Eric Thompson and Henrik Lindberg, I file a ticket for PUP here. After upgrading openproductionource Puppet to version 4.9.4, I followed the Hiera guide https://docs.puppet.com/puppet/4.9/hiera_hierarchy.html#most-hierarchies-interpolate-variables to feed some data to it. I found that for some node, 'puppet lookup' failed to interpolate variables in yaml setting, which lead to incorrect lookup results.
Jira (PUP-7313) Shorten the time it takes to initialize the compiler and its scope
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7313 Shorten the time it takes to initialize the compiler and its scope Change By: Craig Gomes Sprint: PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7359) hiera5 doesn't interpolate in encrypted eyaml data
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7359 hiera5 doesn't interpolate in encrypted eyaml data Change By: Craig Gomes Sprint: PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7224) Replace the Rgen AST model with one generated from a Pcore model
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7224 Replace the Rgen AST model with one generated from a Pcore model Change By: Craig Gomes Sprint: PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7227) Add "reference" kind to the Pcore Object Attribute
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7227 Add "reference" kind to the Pcore Object Attribute Change By: Craig Gomes Sprint: PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7222) Add a RubyMethod annotation to the Pcore type system
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7222 Add a RubyMethod annotation to the Pcore type system Change By: Craig Gomes Sprint: PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Craig Gomes updated an issue Puppet / PUP-5659 Puppet master does not fail catalog on unexisting resource in resource parameter Change By: Craig Gomes Sprint: PDE 2017-02-08, PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5908) Implement a PCore MsgPack Serializer
Title: Message Title Craig Gomes updated an issue Puppet / PUP-5908 Implement a PCore MsgPack Serializer Change By: Craig Gomes Sprint: Language 2016-06-29, PDS 2016-11-02, PDS 2016-11-16, PDS 2016-11-30, PDE 2016-12-14, PDE 2017-01-11, PDE 2017-01-25, PDE 2017-02-08, PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7212) Implement Pcore Object annotation pattern
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7212 Implement Pcore Object annotation pattern Change By: Craig Gomes Sprint: PDE 2017-02-22, PDE 2017-03-08 , PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7340) context_spec.rb fails when run in isolation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7340 context_spec.rb fails when run in isolation Change By: Henrik Lindberg Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7339) Local spec failure spec/unit/pops/lookup/context_spec.rb
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7339 Local spec failure spec/unit/pops/lookup/context_spec.rb Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7339) Local spec failure spec/unit/pops/lookup/context_spec.rb
Title: Message Title Henrik Lindberg commented on PUP-7339 Re: Local spec failure spec/unit/pops/lookup/context_spec.rb This was also reported in PUP-7340 for which there is a PR. Closing this in favor of PUP-7340 even if this ticket was earlier. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5969) Include built-in resource types in resource profiling
Title: Message Title Henrik Lindberg commented on PUP-5969 Re: Include built-in resource types in resource profiling Matthaus Owens Any new thoughts - can we close this (since there isn't anything to profile for those when compiling). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6867) lookup extensions: data from service requiring long-lived session/connection
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6867 lookup extensions: data from service requiring long-lived session/connection Change By: Henrik Lindberg Sprint: PDE 2017-03-08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6891) Extending lookup: data structures that require transformation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6891 Extending lookup: data structures that require transformation Change By: Henrik Lindberg Sprint: PDE 2017-03-08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6868) lookup extensions: algorithmic data source capability
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6868 lookup extensions: algorithmic data source capability Change By: Henrik Lindberg Sprint: PDE 2017-03-08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6891) Extending lookup: data structures that require transformation
Title: Message Title Henrik Lindberg assigned an issue to Lindsey Smith Ticket needs assessment and made concrete (docs, ux, etc.) Puppet / PUP-6891 Extending lookup: data structures that require transformation Change By: Henrik Lindberg Assignee: Lindsey Smith Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6868) lookup extensions: algorithmic data source capability
Title: Message Title Henrik Lindberg assigned an issue to Lindsey Smith Ticket needs assessment and made concrete (docs, ux, etc.) Puppet / PUP-6868 lookup extensions: algorithmic data source capability Change By: Henrik Lindberg Assignee: Lindsey Smith Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6867) lookup extensions: data from service requiring long-lived session/connection
Title: Message Title Henrik Lindberg assigned an issue to Lindsey Smith Ticket needs assessment and made concrete (docs, ux, etc.) Puppet / PUP-6867 lookup extensions: data from service requiring long-lived session/connection Change By: Henrik Lindberg Assignee: Lindsey Smith Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Henrik Lindberg assigned an issue to Lindsey Smith Puppet / PUP-4242 Add deprecation warnings for manifests declaring things in wrong namespace Change By: Henrik Lindberg Assignee: Lindsey Smith Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Henrik Lindberg commented on PUP-4242 Re: Add deprecation warnings for manifests declaring things in wrong namespace Ha, we are now doing a 4.10.0 - do we want this deprecation warning to go in such that we can forbid this in Puppet 5.0.0 ? Ping Eric Sorenson Lindsey Smith Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
