Jira (PDOC-60) Strings skips docs for the log message functions
Title: Message Title William Hopper commented on PDOC-60 Re: Strings skips docs for the log message functions PR is up at https://github.com/puppetlabs/puppet/pull/5299. PUP-6742 is the tracking puppet 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-6742) Add YARD tags for puppet log functions (debug, info, notice, etc)
Title: Message Title William Hopper created an issue Puppet / PUP-6742 Add YARD tags for puppet log functions (debug, info, notice, etc) Issue Type: Improvement Assignee: William Hopper Created: 2016/09/26 4:06 PM Priority: Normal Reporter: William Hopper Currently, the dynamically created log functions (debug, info, notice, etc) can't be documented by puppet-strings, as YARD does not evaluate Ruby code at runtime. YARD has a @!parse directive which is meant for metaprogrammed constructs. We can use it to give YARD hints about what the metaprogrammed classes will be. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1493) Could not retrieve local facts: failed to parse display name of moniker
Title: Message Title Geoff Nichols commented on FACT-1493 Re: Could not retrieve local facts: failed to parse display name of moniker Jeff Sparrow, when you have a chance, could you please include steps to reproduce this issue? If possible, please include the Puppet version, a sample manifest, and the Powershell script that triggers the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1493) Could not retrieve local facts: failed to parse display name of moniker
Title: Message Title Geoff Nichols assigned an issue to Jeff Sparrow Facter / FACT-1493 Could not retrieve local facts: failed to parse display name of moniker Change By: Geoff Nichols Assignee: Jeff Sparrow 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-1493) Could not retrieve local facts: failed to parse display name of moniker
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1493 Could not retrieve local facts: failed to parse display name of moniker Change By: Geoff Nichols Sprint: AP Triage Windows Facter 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-1493) Could not retrieve local facts: failed to parse display name of moniker
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1493 Could not retrieve local facts: failed to parse display name of moniker Change By: Geoff Nichols Labels: needs_repro Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1480) Statically Compile Facter
Title: Message Title Geoff Nichols commented on FACT-1480 Re: Statically Compile Facter Hi Stephen Gelman, if this is still an issue, could you please pose this question on https://ask.puppet.com? 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-1480) Statically Compile Facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1480 Statically Compile Facter Change By: Geoff Nichols Sprint: AP Triage Windows Facter Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1443) FACTERLIB not taken in account on Windows 2012R2
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1443 FACTERLIB not taken in account on Windows 2012R2 Change By: Geoff Nichols Labels: needs_repro Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6705) Add Sensitive type to Puppet Serialization
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6705 Add Sensitive type to Puppet Serialization Change By: Eric Thompson QA Risk Assessment: Low 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-6682) $settings leaks symbols into manifests
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6682 $settings leaks symbols into manifests Change By: Eric Thompson QA Status: Reviewed 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-6682) $settings leaks symbols into manifests
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6682 $settings leaks symbols into manifests Change By: Eric Thompson QA Highest Test Level: Unit 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-6682) $settings leaks symbols into manifests
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6682 $settings leaks symbols into manifests Change By: Eric Thompson QA Risk Assessment: Medium 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-620) windows facter $::osfamily and $::kernel output inconsistent vs other platforms
Title: Message Title
Eric Sorenson commented on FACT-620
Re: windows facter $::osfamily and $::kernel output inconsistent vs other platforms
In fact I would be reluctant to change it at all.
Do the structured fact equivalents work correctly? I think that'd be {{ $facts['os']['family'] }} and {{ $facts['os']['name'] }} - as long as those are correct, that's what people should be using anyway.
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-6705) Add Sensitive type to Puppet Serialization
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6705 Add Sensitive type to Puppet Serialization Change By: Eric Thompson QA Risk Assessment Reason: no user-functionality yet. will be tested in Sensitive data type test, later 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-768) Add the option to re-use existing vbscripts to be used for executable facts.
Title: Message Title Geoff Nichols updated an issue Facter / FACT-768 Add the option to re-use existing _vbscript_s to be used for executable facts. Change By: Geoff Nichols Sprint: AP Triage Windows Facter 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-620) windows facter $::osfamily and $::kernel output inconsistent vs other platforms
Title: Message Title Eric Sorenson commented on FACT-620 Re: windows facter $::osfamily and $::kernel output inconsistent vs other platforms This change unquestionably needs to be happen on a major version boundary. 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-1358) Add GCC 6.1.0 testing to CI, update instructions
Title: Message Title Michael Smith commented on FACT-1358 Re: Add GCC 6.1.0 testing to CI, update instructions The request was GCC 5+. The latest version is optimal. 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-450) DST in France cause puppet to fail (aka 'Could not intern from pson: "\x92" on US-ASCII')
Title: Message Title Geoff Nichols updated an issue Facter / FACT-450 DST in France cause puppet to fail (aka 'Could not intern from pson: "\x92" on US-ASCII') Change By: Geoff Nichols Sprint: AP Triage Windows Facter 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-1358) Add GCC 6.1.0 testing to CI, update instructions
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1358 Add GCC 6.1.0 testing to CI, update instructions Change By: Geoff Nichols Add GCC 6.1.0 testing to AppVeyor and Travis CI (while preserving GCC 4.8) to ensure we don't backslide while preparing to switch packaging to GCC 5.Also update the README to build with GCC 5 6 (particularly Windows instructions). 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-1358) Add GCC 6.1.0 testing to CI, update instructions
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1358 Add GCC 6.1.0 testing to CI, update instructions Change By: Maggie Dreyer Add GCC 6.1.0 testing to AppVeyor and Travis CI (while preserving GCC 4.8) to ensure we don't backslide while preparing to switch packaging to GCC 5 6 .Also update the README to build with GCC 6 (particularly Windows instructions). 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-1358) Add GCC 6.1.0 testing to CI, update instructions
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1358 Add GCC 6.1.0 testing to CI, update instructions Change By: Geoff Nichols Summary: Add GCC 5 6 . 3 1 .0 testing to CI, update instructions 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-1358) Add GCC 5.3.0 testing to CI, update instructions
Title: Message Title Maggie Dreyer commented on FACT-1358 Re: Add GCC 5.3.0 testing to CI, update instructions This is in the GCC 6.1 epic, do we want to add 6.1 instead of 5.3? Or what was the proposed usefulness of adding 5.3? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1358) Add GCC 6.1.0 testing to CI, update instructions
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1358 Add GCC 6.1.0 testing to CI, update instructions Change By: Geoff Nichols Add GCC 5 6 . 3 1 .0 testing to AppVeyor and Travis CI (while preserving GCC 4.8) to ensure we don't backslide while preparing to switch packaging to GCC 5.Also update the README to build with GCC 5 (particularly Windows instructions). 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-6705) Add Sensitive type to Puppet Serialization
Title: Message Title Henrik Lindberg commented on PUP-6705 Re: Add Sensitive type to Puppet Serialization Taken with the "rich data in catalogs" ticket they together makes it possible to alter the Sensitive implementation so that the values are serialized as Sensitive instead of like now being converted to clear text and protected by another special mechanism that was used as a work around. So, no, no user facing functionality at this point. 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-3770) Beaker fails to copy module to guest in certain circumstances
Title: Message Title John Duarte commented on PUP-3770 Re: Beaker fails to copy module to guest in certain circumstances The linked patch to fix this was merged into Beaker on 2014-12-29 https://github.com/puppetlabs/beaker/commit/d868494c9907462d6a629ce65ba2646352ff8620 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-6705) Add Sensitive type to Puppet Serialization
Title: Message Title Eric Thompson commented on PUP-6705 Re: Add Sensitive type to Puppet Serialization does this enable any user-facing features? or is it just enabling it in Pcore? 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-5831) Add a Binary type and runtime object
Title: Message Title Henrik Lindberg commented on PUP-5831 Re: Add a Binary type and runtime object The binary type implementation was a blocker in that it served as a role model for the Sensitive type (what needed to be implemented there). The actual implementation was however not a blocker. Will get back on user stories. 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-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6701 PE Everett fails to install: Unknown function: 'puppetdb_query' Change By: Eric Thompson QA Status: Reviewed 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-6135) change type mismatch errors in past tense to present tense
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Henrik Lindberg Release Notes Summary: The messages about type mismatch errors have been modified to use more consistent wording for different kinds of mismatches. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6701 PE Everett fails to install: Unknown function: 'puppetdb_query' Change By: Eric Thompson QA Risk Assessment: Low 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-5831) Add a Binary type and runtime object
Title: Message Title Eric Thompson commented on PUP-5831 Re: Add a Binary type and runtime object Henrik Lindberg, Lindsey Smith i'm not exactly clear on how this blocks the Sensitive data epic; so i'm not clear how to change that test (i guess to ensure one can use Sensitive data but it's not en-clair in the catalog? but that's a different user story, i'd think.) Can i get an idea on what some user stories for this would be? 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-1446) Improve the windows user check in facter/acceptance/test/facts/windows.rb
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1446 Improve the windows user check in facter/acceptance/test/facts/windows.rb Change By: Maggie Dreyer Summary: Improve the windows user check in facter/acceptance/test/facts/ window windows .rb Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1326) Apply for registered port number with IANA
Title: Message Title Charles Dunbar commented on PUP-1326 Re: Apply for registered port number with IANA Yeah, it was done in OPS-2081 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-60) Strings skips docs for the log message functions
Title: Message Title William Hopper commented on PDOC-60 Re: Strings skips docs for the log message functions Henrik Lindberg ah, good call. I'll investigate using the 4.x API with @!parse. We should be able to do the same thing with it. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6689) Timespan and Timestamp should inherit from Scalar, not from Numeric
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6689 Timespan and Timestamp should inherit from Scalar, not from Numeric Change By: Eric Thompson QA Risk Assessment: Low 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-1326) Apply for registered port number with IANA
Title: Message Title John Duarte commented on PUP-1326 Re: Apply for registered port number with IANA The puppet master service port, 8140, was registered by Charles Dunbar on puppet's behalf on 2014-09-18. http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml#Puppet Charles Dunbar, can this ticket be closed? 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-6689) Timespan and Timestamp should inherit from Scalar, not from Numeric
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6689 Timespan and Timestamp should inherit from Scalar, not from Numeric Change By: Eric Thompson QA Status: Reviewed 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-60) Strings skips docs for the log message functions
Title: Message Title Henrik Lindberg commented on PDOC-60 Re: Strings skips docs for the log message functions Solution 1 has the downside that it is using the 3.x function API as meta-meta here. Eventually we want to retire the 3.x function API. We then have an additional problem to solve. Solution 2 here we risk that functions in the function directory ends up being loaded and ending up in a different loader (by mistakes made in the future). This solution seems harder to maintain as a future change needs to go into all of the files. Here it is also unclear if it will actually work as the dispatcher is fake as the function reimplements the call method. To pursue on this path I think we need to create a new base class that the function inherits from so we can have a minimum of information in it (maintain the functionality in the base class). This seems like a lot of work at higher risk. Would using the 4.x API in the @!parse comments work? That would remove the only objection I had against Solution 1. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Eric Thompson commented on PUP-6135 Re: change type mismatch errors in past tense to present tense i'm not sure if this needs a release notes blurb or not, nor what type it would be... "bug fix"? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6291) Add 'abs' support to Numeric.new
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Eric Thompson QA Risk Assessment: Medium 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-6291) Add 'abs' support to Numeric.new
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Eric Thompson QA Status: Reviewed 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-6291) Add 'abs' support to Numeric.new
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Eric Thompson QA Highest Test Level: Unit 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-6711) Puppet lookup doesn't know about custom facts
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6711 Puppet lookup doesn't know about custom facts Change By: Thomas Hallgren Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6711) Puppet lookup doesn't know about custom facts
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6711 Puppet lookup doesn't know about custom facts Change By: Thomas Hallgren Assignee: Erik Hansen 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-6711) Puppet lookup doesn't know about custom facts
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6711 Puppet lookup doesn't know about custom facts Change By: Thomas Hallgren Sprint: PDS Triage AP 2016-10-05 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-4464) 4.x syntax error in '=>' in hash following another expression
Title: Message Title Henrik Lindberg commented on PUP-4464 Re: 4.x syntax error in '=>' in hash following another _expression_ I am going to close this a a won't fix as there are several ways to work around this problem and the cost (if at all possible) trying to fix this is very high. 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-4464) 4.x syntax error in '=>' in hash following another expression
Title: Message Title
Henrik Lindberg commented on PUP-4464
Re: 4.x syntax error in '=>' in hash following another _expression_
Note that the hint may not work on older versions, as we only recently made it possible for the parser to differentiate parentheses following an _expression_ from being a call from (as in the post above just an _expression_ grouping) when there is a newline between the _expression_ and the opening parenthesis.
The last example can be written:
$result = $rows.map |$row| {
$temp_val = $row['col'] ; # note the semicolon here
{ a=> $temp_val }
}
Where a semicolon separates the expressions and removes the ambiguity.
Here the parentheses should work (cannot be misinterpreted as a call).
({
'if_eth0' => 'if_',
'if_err_eth0' => 'if_err_',
}).each |$plugin, $target| {
Jira (PUP-5834) Handle extended data in the catalog
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5834 Handle extended data in the catalog Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-6693) Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6693 Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on Change By: Eric Thompson QA Highest Test Level: Unit 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-6693) Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6693 Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on Change By: Eric Thompson QA Risk Assessment: Medium 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-6693) Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6693 Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on Change By: Eric Thompson QA Status: Reviewed 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-60) Strings skips docs for the log message functions
Title: Message Title William Hopper commented on PDOC-60 Re: Strings skips docs for the log message functions Henrik Lindberg alright, here are the two approaches we've got. Do you have thoughts on which you prefer? 1) Use the YARD parse directive (http://www.rubydoc.info/gems/yard/file/docs/Tags.md#parse) to give YARD a hint about what the metaprogrammed functions will be: https://gist.github.com/whopper/8c0439e55ccc7c13dbc9ce6a2dd7b482 This is a simple addition of comments, though it is a bit ugly as YARD doesn't have a mechanism to loop over an array of items. Otherwise, we wouldn't have needed to write out each function. 2) Break each of the functions into their own files and eval them in the static loader: https://gist.github.com/whopper/b0966df9e155b8fec12448918ff7e9b2 This requires us to find the proper way to evaluate the new functions in the static loader. For testing, we just used eval on the path to the function. 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-6685) Remove underscore from Timespan/Timestamp milli_seconds, micro_seconds, and nano_seconds
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6685 Remove underscore from Timespan/Timestamp milli_seconds, micro_seconds, and nano_seconds Change By: Eric Thompson QA Status: Reviewed 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-6685) Remove underscore from Timespan/Timestamp milli_seconds, micro_seconds, and nano_seconds
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6685 Remove underscore from Timespan/Timestamp milli_seconds, micro_seconds, and nano_seconds Change By: Eric Thompson QA Risk Assessment: Low 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-6686) Timespan sometimes parses fractions incorrectly.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6686 Timespan sometimes parses fractions incorrectly. Change By: Eric Thompson QA Risk Assessment: Medium 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-6686) Timespan sometimes parses fractions incorrectly.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6686 Timespan sometimes parses fractions incorrectly. Change By: Eric Thompson QA Highest Test Level Reason: covered via Units 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-6686) Timespan sometimes parses fractions incorrectly.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6686 Timespan sometimes parses fractions incorrectly. Change By: Eric Thompson QA Highest Test Level: Unit 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-6686) Timespan sometimes parses fractions incorrectly.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6686 Timespan sometimes parses fractions incorrectly. Change By: Eric Thompson QA Status: Reviewed 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-4464) 4.x syntax error in '=>' in hash following another expression
Title: Message Title
Andrey Galkin commented on PUP-4464
Re: 4.x syntax error in '=>' in hash following another _expression_
Just a hint for anyone running into the problem. Adding round brackets around Hash should help.
Example (not tested).
$result = $rows.map |$row| {
$temp_val = $row['col']
({ a=> $temp_val })
}
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
Jira (PUP-6592) acceptance: Sensitive data
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6592 acceptance: Sensitive data Change By: Eric Thompson Sprint: Language 2016-09-07, PDS 2016-09-21, PDS 2016-10- 19 05 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-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} (other than {{production}}) and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:128:in `run'{code}{panel}This is usually masked by the fact that {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory is missing on the agent. In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated.{panel}{code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -tNotice: /File[/etc/puppetlabs/code/environments/production]/ensure: createdInfo: Caching certificate for caInfo: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yamlInfo: Creating a new SSL certificate request for centos7b.syd.puppet.vm...{code}{panel}*Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.If a {{puppet}} command requries {{environment}}, most commonly {{puppet apply}}, but not {{server}}, it shouldn't matter what {{server}} is set to, but throwing an error for a missing environment directory is appropriate.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER='
Jira (PUP-6711) Puppet lookup doesn't know about custom facts
Title: Message Title Henrik Lindberg assigned an issue to Erik Hansen Puppet / PUP-6711 Puppet lookup doesn't know about custom facts Change By: Henrik Lindberg Assignee: Erik Hansen 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-6711) Puppet lookup doesn't know about custom facts
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6711 Puppet lookup doesn't know about custom facts Ping Thomas Hallgren - can you take a look at this? See if you have anything to add. It is obvious that before we added support to lookup facts for the node automatically in the CLI for lookup, the user would have to capture and feed in the facts to the lookup CLI or it would get no facts at all. Secondly, lookup now will behave differently depending on if a node has checked in or not. Could that be the reason why it appears to work sometimes? Is if for the same node, has that node checked in? (If not, facts must be generated for it and used on the CLI). Change By: Henrik Lindberg Sprint: PDS 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
Jira (PUP-6711) Puppet lookup doesn't know about custom facts
Title: Message Title William Hopper updated an issue Puppet / PUP-6711 Puppet lookup doesn't know about custom facts Change By: William Hopper Team: Puppet Developer Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6740) sshkey: add support for "markers" / SSHCA
Title: Message Title William Hopper updated an issue Puppet / PUP-6740 sshkey: add support for "markers" / SSHCA Change By: William Hopper Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2983) Ensure PDB + Stockpile is HUPable
Title: Message Title Dan Lidral-Porter assigned an issue to Dan Lidral-Porter PuppetDB / PDB-2983 Ensure PDB + Stockpile is HUPable Change By: Dan Lidral-Porter Assignee: Dan Lidral-Porter 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-6714) PCore generation omits information about capability types
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6714 PCore generation omits information about capability types Change By: Henrik Lindberg Release Notes Summary: The opt in feature 'puppet generate types' did not generate the correct information for capability resources used in application orchestration which caused environment catalog compilation for orchestration to fail. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6714) PCore generation omits information about capability types
Title: Message Title Henrik Lindberg commented on PUP-6714 Re: PCore generation omits information about capability types Merged to master at 8a413a6 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-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:128:in `run'{code}{panel}This is usually masked by the fact that {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory is missing on the agent. In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated.{panel}{code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -tNotice: /File[/etc/puppetlabs/code/environments/production]/ensure: createdInfo: Caching certificate for caInfo: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yamlInfo: Creating a new SSL certificate request for centos7b.syd.puppet.vm...{code}{panel}*Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.If a {{puppet}} command requries {{environment}}, most commonly {{puppet apply}}, but not {{server}}, it shouldn't matter what {{server}} is set to, but throwing an error for a missing environment directory is appropriate.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER=''ENVIRONMENT='dev'AGENT_PKG='puppet-agent-1.6.2-1.el7.x86_64.rpm'PLATFORM='el-7-x86_64'# uncomment the
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:128:in `run'{code}{panel}This is usually masked by the fact that {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory is missing on the agent. In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated.{panel}{code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -tNotice: /File[/etc/puppetlabs/code/environments/production]/ensure: createdInfo: Caching certificate for caInfo: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yamlInfo: Creating a new SSL certificate request for centos7b.syd.puppet.vm...{code}{panel}*Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings. An exception is If a command requries {{ puppet apply environment }}, which does care about most commonly {{ environment puppet apply }} , but not {{server}} , it shouldn't matter what {{server}} is set to, but throwing an error for a missing environment directory is appropriate .https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER='
Jira (PUP-6670) Newlines break Puppet tag validation
Title: Message Title Geoff Nichols assigned an issue to Sean McDonald Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Geoff Nichols Assignee: Kylo Ginsberg Sean McDonald Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Adam Bottchen CS Priority: Needs Priority 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-3069) Remove duplicated id and received time from command refs
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3069 Remove duplicated id and received time from command refs Change By: Ryan Senior Sprint: SE 2016-10- 19 05 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-3040) Implement bypassing the queue perf optimization
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3040 Implement bypassing the queue perf optimization Change By: Ryan Senior Sprint: SE 2016-10- 05 19 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-3066) Add a tracer message to the AMQ upgrade code
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3066 Add a tracer message to the AMQ upgrade code Change By: Ryan Senior Sprint: SE 2016-10- 19 05 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-3067) Switch command logging from message id to '-'
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3067 Switch command logging from message id to '-' Change By: Ryan Senior Sprint: SE 2016-10- 19 05 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-3051) Stop using activemq in the benchmark tool
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3051 Stop using activemq in the benchmark tool Change By: Ryan Senior Sprint: SE 2016-10-19 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-3038) Merge mq_listener and command namespaces
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3038 Merge mq_listener and command namespaces Change By: Ryan Senior Sprint: SE 2016-10-19 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-3067) Switch command logging from message id to '-'
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3067 Switch command logging from message id to '-' Change By: Ryan Senior Sprint: SE 2016-10-19 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-3069) Remove duplicated id and received time from command refs
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3069 Remove duplicated id and received time from command refs Change By: Ryan Senior Sprint: SE 2016-10-19 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-3069) Remove duplicated id and received time from command refs
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3069 Remove duplicated id and received time from command refs Issue Type: Task Assignee: Unassigned Created: 2016/09/26 8:22 AM Priority: Normal Reporter: Ryan Senior Before stockpile, the message UUIDs and and receive times were stored in the "annotations" key associated to the message. With command refs, we have them as a top level key in the CommandRef defrecord. Currently this information is duplicated so as to not break the existing command handling code. We should move all references to id/received in the annotations to the top level keys and remove that duplication from the command refs. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-3063) latest_report_noop_pending=null, should be =true
Title: Message Title Wyatt Alt commented on PDB-3063 Re: latest_report_noop_pending=null, should be =true Elof Ofel Thanks – I'd like to verify the change first, just haven't had the time yet. It seems like something that might be worth documenting. 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-6638) Upgrade from ubuntu 3.x packages to PC1 4.x fails
Title: Message Title Kylo Ginsberg commented on PUP-6638 Re: Upgrade from ubuntu 3.x packages to PC1 4.x fails Nikolai R Kristiansen afaik that's not planned at the moment, but it's an idea worth evaluating. I updated the summary to reflect current understanding of the issue. Ping Geoff Nichols and Eric Sorenson for visibility. 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-6638) Upgrade from ubuntu 3.x packages to PC1 4.x fails
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6638 Upgrade from ubuntu 3.x packages to PC1 4.x fails Change By: Kylo Ginsberg Summary: create_resource in v4.6.0 makes puppet Upgrade from ubuntu 3.x agents fail upgrade packages to PC1 4.x fails 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-6638) Upgrade from ubuntu 3.x packages to PC1 4.x fails
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6638 Upgrade from ubuntu 3.x packages to PC1 4.x fails Change By: Kylo Ginsberg Issue Type: Bug New Feature 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-3063) latest_report_noop_pending=null, should be =true
Title: Message Title Elof Ofel commented on PDB-3063 Re: latest_report_noop_pending=null, should be =true This ticket can be closed if you choose to ignore the changed logic, and instead urge users to upgrade and then use the new syntax in their queries. 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-6741) When `recurse => true` is used in a file resource, tags are not applied to all recursive objects.
Title: Message Title
Stefan Pijnappels created an issue
Puppet / PUP-6741
When `recurse => true` is used in a file resource, tags are not applied to all recursive objects.
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/09/26 7:39 AM
Priority:
Normal
Reporter:
Stefan Pijnappels
In the case where `recurse => true' is added to a file resource which is actually a directory with a whole bunch of files in it, it appears that not all these files get tagged with either the default tags for the class/resource or with custom tags specified in the resource declaration.
If these tags are then used later in a puppet run using --tags, the resource is not included.
As an example, the following code will create a number of files in a directory, where the directory is marked as `recurse => true` and the resource is tagged with a tag `sometag`:
``` class abc::component::ao { tag 'sometag' file { '/tmp/somefiles': tag => 'sometag', ensure => directory, source => "puppet:///static/somefiles", recurse => true, purge => true, owner => 'root', group => 'root', }
exec { 'do something': tag => 'sometag', command => '/bin/echo do something', # 20 lines script refreshonly => true, subscribe => [ File['/tmp/somefiles'], ], }
} ```
However, when `puppet agent -t --tags sometag` is run, the following is noted in the output:
``` Notice: /Stage[main]/Abc::Component::Ao/File[/ao/basescripts/su_stop.ksh]/ensure: defined content as ' {md5}
1fd97a2fc03e639946d960ebd13bebd8' Debug: /Stage[main]/Abc::Component::Ao/File[/ao/basescripts/su_stop.ksh]: The container /ao/basescripts will propagate my refresh event Debug: /ao/basescripts: Not tagged with sometag
Jira (PUP-6740) sshkey: add support for "markers" / SSHCA
Title: Message Title Patrick Schoenfeld created an issue Puppet / PUP-6740 sshkey: add support for "markers" / SSHCA Issue Type: New Feature Affects Versions: PUP 4.7.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/09/26 7:16 AM Priority: Normal Reporter: Patrick Schoenfeld OpenSSH has support for so called "SSH Certificates" for both hostkeys as well as user keys. So a host can be verified by validating a certain ssh certificate. The sshkey resource does not yet support managing allowed CAs in ssh_known_hosts, because technically it is realized with markers before the host aliases (similar to options in ssh_authorized_keys). So to realize this feature requestion one would have to add a new property "markers" (how it is called in the sshd manapage) or "options" (which would be consistent with the similar parameter in ssh_authorized_key) and allow the values @cert-authority and @revoked. As it stands now, it's not possible to manage a SSH CA keys with puppe (except managing known_hosts with a file resource).
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:128:in `run'{code}{panel}This is usually masked by the fact that {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory is missing on the agent. In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated.{panel}{code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -t --environment production Notice: /File[/etc/puppetlabs/code/environments/production]/ensure: created Info: Caching certificate for caInfo: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yamlInfo: Creating a new SSL certificate request for centos7b.syd.puppet.vm... {code}{panel}*Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.An exception is {{puppet apply}}, which does care about {{environment}} but not {{server}}.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER=''ENVIRONMENT='dev'AGENT_PKG='puppet-agent-1.6.2-1.el7.x86_64.rpm'PLATFORM='el-7-x86_64'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k -O
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:128:in `run'{code}{panel}This is usually masked by the fact that a {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory exists by default is missing on the agent . In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated. {panel} {code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -t --environment productionNotice: /File[/etc/puppetlabs/code/environments/production]/ensure: created{code}{panel} *Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.An exception is {{puppet apply}}, which does care about {{environment}} but not {{server}}.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER=''ENVIRONMENT='dev'AGENT_PKG='puppet-agent-1.6.2-1.el7.x86_64.rpm'PLATFORM='el-7-x86_64'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k -O https://${MASTER}:8140/packages/current/$PLATFORM/$AGENT_PKGrpm -i ./$AGENT_PKG# switch the order of the next two lines and the error goes awaypuppet config set
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title Jeremy Adams commented on PUP-6739 Re: If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent Paul Anderson You're correct about 'produciton' being special. I'll amend the description. 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-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6739 If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent Change By: Henrik Lindberg Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2769) specify how 4.x function api code can get caller / source location
Title: Message Title Henrik Lindberg commented on PUP-2769 Re: specify how 4.x function api code can get caller / source location Assigned to Jean Bond for review/awareness that this is documented in the specification (link in the release note). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2769) specify how 4.x function api code can get caller / source location
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2769 specify how 4.x function api code can get caller / source location Bringing this into the sprint as the work is already done. Change By: Henrik Lindberg Acceptance Criteria: This is a specification change that documents an already implemented feature - criteria is therefore that the specification shows how an implementor of a function can learn how to get the file and line of the received call including a trace of all functions if one function calls another. Story Points: 3 1 Release Notes Summary: The 4.x Function API now has a mechanism for getting the source file and line location for calls from a manifest.(As shown in the specification https://github.com/puppetlabs/puppet-specifications/blob/master/language/func-api.md#access-to-stacktrace) Sprint: PDS AP 2016-10- 19 05 Release Notes: New Feature Component/s: Server Add Comment
Jira (PUP-2769) specify how 4.x function api code can get caller / source location
Title: Message Title Henrik Lindberg assigned an issue to Jean Bond Puppet / PUP-2769 specify how 4.x function api code can get caller / source location Change By: Henrik Lindberg Assignee: Jean Bond 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-6724) The new strftime function is not compatible with the strftime function in stdlib.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6724 The new strftime function is not compatible with the strftime function in stdlib. Change By: Henrik Lindberg Sprint: AP PDS 2016-10-05 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-5834) Handle extended data in the catalog
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5834 Handle extended data in the catalog Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-6692) Improve access to "master" settings
Title: Message Title Henrik Lindberg commented on PUP-6692 Re: Improve access to "master" settings Kind of agree. Not sure how we will end up with this since the solution preferred by users is a global $settings variable. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6692) Improve access to "master" settings
Title: Message Title Thomas Hallgren commented on PUP-6692 Re: Improve access to "master" settings I think that implementing a function that returns different types based on its parameters is bad practice. How about using two separate functions? One named settings which (as the name suggests) returns all settings, and one named setting that requires an argument? 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.
