Jira (PUP-7382) Ensure current values are YAML serializable
Title: Message Title Josh Cooper commented on PUP-7382 Re: Ensure current values are YAML serializable Also note this problem could have happened in Ruby 2.1 if the ACL module had return Array subclasses instead of Hash subclasses. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7382) Ensure current values are YAML serializable
Title: Message Title Josh Cooper created an issue Puppet / PUP-7382 Ensure current values are YAML serializable Issue Type: Bug Assignee: Unassigned Created: 2017/03/21 10:30 PM Priority: Normal Reporter: Josh Cooper As described in MODULES-4275, a provider may return arbitrary objects as the current value. This value is written (as YAML) in the corrective change file and in the report (if there is a change). The assumption has always been that the current value is primitive (string, integer, etc), but the ACL module returns Hash subclasses. Since we rely on to_yaml_properties for report serialization (see PUP-7381), Ruby 2.3 will serialize instance variables of our subclasses, which causes puppet to try to serialize the provider instance. This wasn't a problem previously, because Ruby 2.2 and below just serialize the hash key/value pairs. Puppet needs to be more defensive about how current values are handled. Presumably this could be done by always writing out the to_s version of the object. /cc Geoff Nichols, Ethan Brown, Henrik Lindberg Add Comment
Jira (PUP-7134) Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding for SSL files
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7134 Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding for SSL files Change By: Geoff Nichols Sprint: Puppet 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7381) Consistently use encode_with for YAML serialization
Title: Message Title Josh Cooper created an issue Puppet / PUP-7381 Consistently use encode_with for YAML serialization Issue Type: Bug Assignee: Unassigned Created: 2017/03/21 10:20 PM Priority: Normal Reporter: Josh Cooper Puppet serializes objects to YAML using both to_yaml_properties: lib/puppet/graph/simple_graph.rb lib/puppet/parser/yaml_trimmer.rb lib/puppet/resource/status.rb lib/puppet/resource.rb
Jira (PUP-7381) Consistently use encode_with for YAML serialization
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7381 Consistently use encode_with for YAML serialization Change By: Josh Cooper Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7334) add a default hierarchy to module hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-7334 Re: add a default hierarchy to module hiera.yaml I see several problems with this: 1. The ambiguity doesn't stop at finding a lookup_option for a key. What if there is a pattern in the regular lookup_options that matches the key and then an explicit key in the default_options that matches the same key? Or would a pattern in the regular lookup_options that matches all keys in a module effectively rule out the use of the default_hierarchy by "intention to override with not found"? 2. The merge strategy used is determined by first looking at what was given as a parameter, then what has been declared as a lookup_option for the given key. Once this has been determined, the source of the merge strategy is forgotten and the lookup proceeds. Now, let's assume that the value isn't found and the default_hierarchy is consulted. If the merge strategy then was given as a parameter, it should not be replaced by a lookup_option found in the default_hierarchy. If it originates from the regular hierarchy some other rule (which one depends on answer to #1) apply. I'm not saying that values in the default_hierarchy should not be merged. What I don't get is why they need a special lookup_options entry that is governed by special rules. Why isn't it enough to declare the lookup_options in the regular hierarchy and be done with it? I'm also questioning how our users in general will understand this and use it correctly when I can't make heads or tails of how it's supposed to work. It would be far simpler if we just stated that lookup_options in the default hierarchy are ignored and that the lookup_options declared in the regular hierarchy will be applied in the default_hierarchy as well. Easy to explain, no ambiguity, no "intentions", no remembering source of the options, no extra resource consuming lookup. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are
Jira (PUP-7258) Ensure JSON on Agents defaults to native implementation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7258 Ensure JSON on Agents defaults to native implementation Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7261) Add/Honor charset parameter in Content-Type header
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7261 Add/Honor charset parameter in Content-Type header Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5973) Remove Symbol monkey patch
Title: Message Title Josh Cooper commented on PUP-5973 Re: Remove Symbol monkey patch We had to revert that because it caused problems in Puppetserver/JRuby. We'll need to re-do the removal for 5.0. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5974) Remove IO#binwrite monkey patch
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5974 Remove IO#binwrite monkey patch Change By: Geoff Nichols Sprint: Agent Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5974) Remove IO#binwrite monkey patch
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5974 Remove IO#binwrite monkey patch Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5975) Remove Range#intersection monkey patch
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5975 Remove Range#intersection monkey patch Change By: Geoff Nichols Sprint: Agent Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6250) Remove static compiler terminus
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6250 Remove static compiler terminus Change By: Geoff Nichols Sprint: Agent Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6250) Remove static compiler terminus
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6250 Remove static compiler terminus Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5975) Remove Range#intersection monkey patch
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5975 Remove Range#intersection monkey patch Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7133) Remove always_cache_features setting
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7133 Remove always_cache_features setting Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5973) Remove Symbol monkey patch
Title: Message Title Geoff Nichols commented on PUP-5973 Re: Remove Symbol monkey patch On Feb 14, this was merged to puppet#master at https://github.com/puppetlabs/puppet/commit/eba2bcdae2200b4ea706cde43e4ff769878dada6. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5973) Remove Symbol monkey patch
Title: Message Title Geoff Nichols assigned an issue to qa Puppet / PUP-5973 Remove Symbol monkey patch Change By: Geoff Nichols Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5830) Remove crazy symlink behavior
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5830 Remove crazy symlink behavior Change By: Geoff Nichols Sprint: Agent Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7265) Remove file face
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7265 Remove file face Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7265) Remove file face
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7265 Remove file face Change By: Geoff Nichols Acceptance Criteria: Puppet's file face and accompanying man pages, help files and tests have been removed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6762) (SPIKE) How and when do we get PO files from Transifex?
Title: Message Title Geoff Nichols assigned an issue to Maggie Dreyer Puppet / PUP-6762 (SPIKE) How and when do we get PO files from Transifex? Change By: Geoff Nichols Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6764) Add PO files with translated strings to Puppet repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Add PO files with translated strings to Puppet repo Change By: Geoff Nichols Sprint: Agent Puppet 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6762) (SPIKE) How and when do we get PO files from Transifex?
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6762 (SPIKE) How and when do we get PO files from Transifex? Change By: Geoff Nichols Sprint: AP 2016-11-16, Agent Puppet 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7108) Create pseudo-localized PO file for CI
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7108 Create pseudo-localized PO file for CI Change By: Geoff Nichols Sprint: Agent Puppet 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6979) Puppet Module List fails in code page 65001 on ja-JP windows
Title: Message Title Geoff Nichols commented on PUP-6979 Re: Puppet Module List fails in code page 65001 on ja-JP windows Any chance this could be related to https://bugs.ruby-lang.org/issues/7758 ? /cc Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3478) Remove extlookup2hiera
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3478 Remove extlookup2hiera Change By: Geoff Nichols Sprint: Puppet 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3478) Remove extlookup2hiera
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3478 Remove extlookup2hiera Change By: Geoff Nichols Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3478) Remove extlookup2hiera
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3478 Remove extlookup2hiera Change By: Geoff Nichols 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-3478) Remove extlookup2hiera
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3478 Remove extlookup2hiera Change By: Geoff Nichols Acceptance Criteria: - Both bin/extlookup2hiera and man/man8/extlookup2hiera.8 are removed- Deprecation warning in Puppet 4.10 docs Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Geoff Nichols Sprint: Agent Puppet 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7063) Handle incompatible encodings in Puppet::Util::Log when rendering to console
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7063 Handle incompatible encodings in Puppet::Util::Log when rendering to console Change By: Geoff Nichols Sprint: Agent 2017-04-05 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7042) Mark non-debug messages for externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7042 Mark non-debug messages for externalization Change By: Geoff Nichols Sprint: AP 2017-01-11, AP 2017-01-25, AP 2017-02-08, AP 2017-03-08, Agent 2017-04-05 Puppet 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3312) Dashboard does not work when postgres is unavailable
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3312 Dashboard does not work when postgres is unavailable Change By: Russell Mull Sprint: Son of Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3102) Use internal rubygems mirror
Title: Message Title Russell Mull commented on PDB-3102 Re: Use internal rubygems mirror we may get this for free / easy when our stuff starts running on vmpooler; re-evaluate once that goes in. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1592) Networking key/value pair for Interface Speed and Duplex State
Title: Message Title Joseph Oaks created an issue Facter / FACT-1592 Networking key/value pair for Interface Speed and Duplex State Issue Type: Improvement Assignee: Unassigned Created: 2017/03/21 4:45 PM Priority: Normal Reporter: Joseph Oaks Having these 2 values would be a benefit giving customers the ability to search for specific interfaces that meet a specific speed or duplex state. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3224) Add the ability to stop processing different types of commands via API
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API Change By: Russell Mull Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3212) Vacuum reports after GC
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3212 Vacuum reports after GC Change By: Russell Mull Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7380) Acceptance: Cisco eXR 6.1.3 VM fails to run augeus test successfully
Title: Message Title Stan Duffy created an issue Puppet / PUP-7380 Acceptance: Cisco eXR 6.1.3 VM fails to run augeus test successfully Issue Type: Bug Assignee: Stan Duffy Created: 2017/03/21 4:41 PM Environment: Cisco eXR 6.1.3. VM Priority: Normal Reporter: Stan Duffy The new Cisco eXR VM is significantly faster that the previous version due to it no longer emulating the backplane. This "Control Plane only" version provides a significant improvement to test execution time and a nice reduction to VMpooler CPU resource usage. Testing has shown that we have one issue with this VM. While running puppet acceptance, one of augeus test fails. We have decided it's worth skipping this test to take advantage of the performance increase. Add Comment
Jira (PDB-3102) Use internal rubygems mirror
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3102 Use internal rubygems mirror Change By: Russell Mull Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2950) Bump required postgres to 9.6
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2950 Bump required postgres to 9.6 Change By: Russell Mull Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2994) PuppetDB becomes unreachable after agent node catalog update
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2994 PuppetDB becomes unreachable after agent node catalog update Change By: Russell Mull Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2959) document batch querying for metrics
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2959 document batch querying for metrics Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7334) add a default hierarchy to module hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-7334 Re: add a default hierarchy to module hiera.yaml I think you are overcomplicating this. The premises is that a module author wants to be able to have full control over the design of the module's hiera data for the default values without imposing those decisions onto a user of the module. From the user's perspective there is simply a non merging default value for a particular key. That is, the author does not want the key/values that are to be default values to be merged with any data that a user may specify - the module author does also not want to impose that certain parameter values should be merged if the user decides to override the defaults. (That would be the effect if the module author decided that some key in the module should have deep merge and sets that in the regular hierarchy for that lookup key). ANOTHER case is that the module author decides that it makes most sense to merge the default value, and that users should use deep merge. This is what you can achieve as hiera 5 is now (without a default hierarchy in the module). When the module author designs the data for the module - the construction of that may come from several files in a hierarchy. The user wants to compose those using a hiera deep merge. Hence - what I proposed earlier: If there is a miss in the regular hierarchy (and only then) the default hierarchy will be consulted before signalling a not found when consulting the default hierarchy, the default hierarchy's lookup_options for that key is used (if set) the corner case of having a lookup_options for a key in the regular hierarchy but the result is not_found (in regular hierarchy) creates an ambiguity - it can be resolved by either taking the entry in the regular hierarchy's lookup_options for that key (without a bound value) to be an "intention to override with not found" - there is then no confusion over if lookup_options comes from regular hierarchy or from module's default hierarchy. The alternatives are far more complicated merging of regular and default lookup_options for the key? That goes against the purpose of having the default hierarchy in the first place the default hierarchy's lookup_options wins over the regular hierarchy's? That goes against the base rule (only lookup in defaults if missing in regular) the regular hierarchy's lookup_options wins over the default hierarchy's? This option makes some sense - and I could possibly be persuaded to use this instead (if there is a good argument for it), but it goes against the idea that the default hierarchy and its result is opaque from the user of the module.
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 I've updated the docs to provide a bit more info. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3085) Cannot start Puppet DB because of filerights
Title: Message Title Wyatt Alt commented on PDB-3085 Re: Cannot start Puppet DB because of filerights Closing, can't reproduce. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3158) puppet query gives rust error when piped to a program that doesn't read its output
Title: Message Title Ryan Senior commented on PDB-3158 Re: puppet query gives rust error when piped to a program that doesn't read its output AJ Roetker What should we do with this ticket? Can we close it? Looks like it's in ready for merge now. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3177) Dead links in the PuppetDB Documentation pages
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3177 Dead links in the PuppetDB Documentation pages Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3369) (maint) use a common set of certname-based implicit relations
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3369 (maint) use a common set of certname-based implicit relations Issue Type: Bug Assignee: Unassigned Created: 2017/03/21 3:56 PM Priority: Normal Reporter: gepetto-bot Centralize definition of certname-based implicit relationships. This will make us less likely to leave them out or create inconsistencies in the future. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7365) Make puppet agent and puppet server first check for a clock skew
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7365 Make puppet agent and puppet server first check for a clock skew Change By: Karen Van der Veer Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3312) Dashboard does not work when postgres is unavailable
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3312 Dashboard does not work when postgres is unavailable Change By: Ryan Senior Sprint: Son of Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3312) Dashboard does not work when postgres is unavailable
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3312 Dashboard does not work when postgres is unavailable Change By: Ryan Senior Fix Version/s: PDB 4.4.x Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3312) Dashboard does not work when postgres is unavailable
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3312 Dashboard does not work when postgres is unavailable Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3318) Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days )
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3318 Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days ) Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3359) AST regex queries against parameters have to match the full string
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3359 AST regex queries against parameters have to match the full string Change By: Ryan Senior Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3322) PuppetDB fails to update catalogs when sensitive parameters are added
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3322 PuppetDB fails to update catalogs when sensitive parameters are added Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3359) AST regex queries against parameters have to match the full string
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3359 AST regex queries against parameters have to match the full string Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3362) (maint) Don't test against puppetserver master for now
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3362 (maint) Don't test against puppetserver master for now Change By: Ryan Senior Sprint: PuppetDB 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3363) (MAINT) Consolodated report integration tests
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3363 (MAINT) Consolodated report integration tests Change By: Ryan Senior Sprint: PuppetDB 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3363) (MAINT) Consolodated report integration tests
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3363 (MAINT) Consolodated report integration tests Change By: Ryan Senior Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3362) (maint) Don't test against puppetserver master for now
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3362 (maint) Don't test against puppetserver master for now Change By: Ryan Senior Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3368) (maint) add package inventory benchmark data
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3368 (maint) add package inventory benchmark data Change By: Ryan Senior Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3365) (maint) fix facts migration test
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3365 (maint) fix facts migration test Change By: Ryan Senior Sprint: PuppetDB 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3365) (maint) fix facts migration test
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3365 (maint) fix facts migration test Change By: Ryan Senior Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3368) (maint) add package inventory benchmark data
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3368 (maint) add package inventory benchmark data Change By: Ryan Senior Sprint: PuppetDB 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7379) acceptance: rake: preserved hosts modes don't work with other test types
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7379 acceptance: rake: preserved hosts modes don't work with other test types Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7379) acceptance: rake: preserved hosts modes don't work with other test types
Title: Message Title Eric Thompson created an issue Puppet / PUP-7379 acceptance: rake: preserved hosts modes don't work with other test types Issue Type: Improvement Assignee: Unassigned Created: 2017/03/21 3:36 PM Priority: Normal Reporter: Eric Thompson from related ticket: ci:test_and_preserve and ci:test_against_preserved_hosts don't work with git style testing, only packages. Seems like the preserve/no-provision logic should be a parameter that the other types of tasks ci:test:git, ci:test:aio, etc use to either provision & preserve hosts or run against already provisioned hosts Add Comment
Jira (PUP-7237) fix puppet acceptance Rake tasks
Title: Message Title Eric Thompson commented on PUP-7237 Re: fix puppet acceptance Rake tasks Josh Cooper totally agree on #3 we don't often parameterize tasks around here and defer a bit to ENV for config. this is probably bad for this type of interface. we could always do both if we wanted as well. opened PUP-7379 to capture Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7378) acceptance rake: ci:list_hosts shows hosts that have been previously killed
Title: Message Title Eric Thompson created an issue Puppet / PUP-7378 acceptance rake: ci:list_hosts shows hosts that have been previously killed Issue Type: Bug Assignee: Eric Sorenson Components: QA Created: 2017/03/21 3:32 PM Priority: Normal Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to
Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Susan McNerney commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error Approved for PDB 4.3.2.1 / PE 2016.4.4 by davis leads. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7334) add a default hierarchy to module hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-7334 Re: add a default hierarchy to module hiera.yaml I still don't understand this. As a module author, I would create a normal hierarchy where every key is prefixed with the module name (it has to be). The only time I would create a default_hierarchy is for the special use-case that maps to the current params.pp scenario, i.e. I want to provide some default in case nothing "above" have declared the value. A real world use-case would be helpful. What's stopping the user from declaring lookup_options in the normal hierarchy that is then applied overall? It becomes mind boggling very fast if the lookup_options declared in the above layer does not apply do the default_hierarchy, or vice versa, if lookup_options declared in the defaults doesn't affect other layers. Either way, we end up with special rules for lookup_options in combination with default that neither applies to normal values of to values found in the defaults. Today, the lookup for lookup_options is performed as a completely separate lookup that caches the found hash. We can of course do a special variant of that with a separate cache for for the defaults in each module but that will slow things down another notch. I guess I just don't see a clean solution that is relatively easy to understand from a functional standpoint. I therefore doubt it will be considered very useful. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Adam Bottchen assigned an issue to Unassigned Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Adam Bottchen Assignee: Adam Bottchen Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3368) (maint) add package inventory benchmark data
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3368 (maint) add package inventory benchmark data Issue Type: Bug Assignee: Unassigned Created: 2017/03/21 1:19 PM Priority: Normal Reporter: gepetto-bot This includes two package sets from a barebones PE master and one from my laptop. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7266) SPIKE: Master and Agent should not share a libdir
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7266 SPIKE: Master and Agent should not share a libdir Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4885) Master and Agent should not share libdir
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-4885 Master and Agent should not share libdir Change By: Geoff Nichols Team/s: Agent, Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7237) fix puppet acceptance Rake tasks
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7237 fix puppet acceptance Rake tasks Change By: Josh Cooper Fix Version/s: PUP 4.10.0 Fix Version/s: PUP 4.9.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7237) fix puppet acceptance Rake tasks
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7237 fix puppet acceptance Rake tasks Change By: Josh Cooper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7237) fix puppet acceptance Rake tasks
Title: Message Title Josh Cooper commented on PUP-7237 Re: fix puppet acceptance Rake tasks There are a few remaining issues: 1. ci:test:git is still broken on windows: PUP-7009 2. ci:list_hosts shows hosts that have been previously killed 3. ci:test_and_preserve and ci:test_against_preserved_hosts don't work with git style testing, only packages. Seems like the preserve/no-provision logic should be a parameter that the other types of tasks ci:test:git, ci:test:aio, etc use to either provision & preserve hosts or run against already provisioned hosts. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-51) Implement the return statement
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-51 Implement the return statement Issue Type: New Feature Assignee: Peter Huene Created: 2017/03/21 12:19 PM Priority: Normal Reporter: Peter Huene Implement the return statement in the parser. Implement the return statement in the _expression_ evaluator (without exception handling). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (NPUP-50) Implement the next statement
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-50 Implement the next statement Issue Type: New Feature Assignee: Peter Huene Created: 2017/03/21 12:16 PM Priority: Normal Reporter: Peter Huene Implement the next statement in the parser Implement the next statement in the evaluator (without using exception handling). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (NPUP-49) Implement the break statement
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-49 Implement the break statement Issue Type: Bug Assignee: Peter Huene Created: 2017/03/21 12:10 PM Priority: Normal Reporter: Peter Huene Implement the break statement in the parser. Implement the break statement in the _expression_ evaluator without using exception handling. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (NPUP-49) Implement the break statement
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-49 Implement the break statement Change By: Peter Huene 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 (NPUP-49) Implement the break statement
Title: Message Title Peter Huene assigned an issue to Unassigned Native Puppet / NPUP-49 Implement the break statement Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7334) add a default hierarchy to module hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-7334 Re: add a default hierarchy to module hiera.yaml You would have complicated logic in your params.pp that did that - with merges being function calls. Many users would rather do the same with a hierarchy. The motivation why this is separate is that it is default values merged and handled per the decision(s) of the module author. If a user of the module wants to do something different they should be able to state a value that completely overrides the default - they should not have to be concerned with the decisions made by the module author wrt. merges. As an example, the module author may want to merge within the defaults - but should not affect if that key is a merged key or not - the user of the module may not want to do merges. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7330) Puppet::LookupKey and Puppet::LookupValue types are unavailable to Hiera backend functions
Title: Message Title Josh Cooper commented on PUP-7330 Re: Puppet::LookupKey and Puppet::LookupValue types are unavailable to Hiera backend functions This is causing failures in CI: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent%20suite%20pipelines/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-stable/31/ It appears this failure didn't happen in the per-commit pipeline because the test that is failing above has been modified in more than 2 weeks, so it is excluded from the per-commit. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7129) Use systemd service provider for Debian 9 (Stretch)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7129 Use systemd service provider for Debian 9 (Stretch) Change By: Geoff Nichols 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-7129) Use systemd service provider for Debian 9 (Stretch)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7129 Use systemd service provider for Debian 9 (Stretch) Change By: Geoff Nichols Sprint: Agent Grooming On 2017 - Deck 03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7129) Use systemd service provider for Debian 9 (Stretch)
Title: Message Title Geoff Nichols commented on PUP-7129 Re: Use systemd service provider for Debian 9 (Stretch) Passing CI run at https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent%20suite%20pipelines/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-1.10.x/13/. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3332) Implement querying support for package inventory
Title: Message Title Rob Browning assigned an issue to Unassigned PuppetDB / PDB-3332 Implement querying support for package inventory Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7334) add a default hierarchy to module hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-7334 Re: add a default hierarchy to module hiera.yaml Also, if you have a complex setup with merges and all, why put that in default_hierarchy? I don't understand the motivation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7334) add a default hierarchy to module hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-7334 Re: add a default hierarchy to module hiera.yaml How did you do that with params.pp? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7129) Use systemd service provider for Debian 9 (Stretch)
Title: Message Title Geoff Nichols commented on PUP-7129 Re: Use systemd service provider for Debian 9 (Stretch) Kenn Hussey possibly, it was originally merged to puppet#master on Feb 8 and backported to puppet#4.10 this sprint. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7334) add a default hierarchy to module hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-7334 Re: add a default hierarchy to module hiera.yaml Merges of defaults makes absolute sense; you may have multiple entries - like a common entry, and one or more on top for different operating systems etc. You definitively need the ability to merge them - but they are all within the default hierarchy. In comparison to a default hash - it works like an array of default hashes... (kind of). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7334) add a default hierarchy to module hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-7334 Re: add a default hierarchy to module hiera.yaml A third alternative would be to say that the default data is handled just like the default hash that you can pass as an option to the lookup command. I.e. not subject to merges and hence, not subject to lookup_options. I see two advantages with that: The handling of default values is consistent regardless of source for the default. It's very easy to document and to explain (just an extension of the given parameter). I have difficulties finding a use-case where merges of default values would make sense. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7129) Use systemd service provider for Debian 9 (Stretch)
Title: Message Title Kenn Hussey commented on PUP-7129 Re: Use systemd service provider for Debian 9 (Stretch) Geoff Nichols if this is ready for CI should it be added to the current sprint? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7009) Git acceptance broken on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7009 Git acceptance broken on Windows Change By: Josh Cooper Story Points: 2 Team: Agent Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5008) Add support for the user type's forcelocal attribute on Solaris
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-5008 Add support for the user type's forcelocal attribute on Solaris Change By: Eric Sorenson Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5008) Add support for the user type's forcelocal attribute on Solaris
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-5008 Add support for the user type's forcelocal attribute on Solaris Change By: Eric Sorenson Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7377) "undefined method 'version'" when running puppet agent --configprint confdir
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7377 "undefined method 'version'" when running puppet agent --configprint confdir Change By: Eric Delaney Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7377) "undefined method 'version'" when running puppet agent --configprint confdir
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7377 "undefined method 'version'" when running puppet agent --configprint confdir Change By: Eric Delaney Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
