Jira (PDB-4806) package / service files need updated for newest systemd
Title: Message Title Lee Lowder created an issue PuppetDB / PDB-4806 package / service files need updated for newest systemd Issue Type: Bug Affects Versions: PDB 6.11.0, PDB 6.9.1 Assignee: Unassigned Components: PuppetDB Created: 2020/07/08 11:35 AM Priority: Normal Reporter: Lee Lowder The service file created by the package need to be updated to better match current systemd Specifically, the use of /var/run vs /run, and the use of .include. Possibly other items as well. Add Comment
Jira (PUP-6645) Remove the hiera_xxx functions
Title: Message Title Lee Lowder commented on PUP-6645 Re: Remove the hiera_xxx functions One feature present in the hiera functions that are missing from lookup() is hiera's little known third argument - an alternate lookup path to used that overrides the lookup path defined in hiera.yaml. This allowed us to, for example, override the lookup path on our pgpool nodes to pull some data specified in a yaml file specific to a given postgresql cluster. With the new method, we were told this is not possible, we have to restructure our hierarchy and use some sort of shared file. This, however, requires considerable effort to execute properly as have have to find a way to have a file that is shared across two different roles, but still confined to a given group, lifecyle, and cluster (these are fact based layers or pieces to our current hierarchy) so that we can not have to enter the same data over and over but also not have the data leak into places it shouldn't be (i.e. a different PG cluster). We face a similar issue with keepalived/haproxy/apache/tomcat type application stacks with pieces of configuration that need to be shared between them in a DRY manner. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.148538.1471963467000.81410.1591643220025%40Atlassian.JIRA.
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title Lee Lowder commented on PUP-7197 Re: make type aliases from modules available on the agent Another area where having type aliases (and puppet language functions) plugin sync are in the use of deferred functions and deferred templates. Say I have an epp template that takes two parameters - a String for the password, and an Stdlib::Absolutepath for some config file or a binary. If I use Deferred on the template so I can have the password come out of vault or some other secret management tool, then because type aliases are not pluginsnced, when the template is rendered on the agent side, I get an error about unknown type Stdlib::Absolutepath. The same sort of thing happens if I try to deferr a puppet language based function - something that the docs have been pushing people very hard to start using over the last few years and versions. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.174775.1486632721000.49037.1588094640026%40Atlassian.JIRA.
Jira (FACT-2587) Puppet facts missing on facter 3.10.0 with OSP 6.13.0
Title: Message Title Lee Lowder created an issue Facter / FACT-2587 Puppet facts missing on facter 3.10.0 with OSP 6.13.0 Issue Type: Bug Affects Versions: FACT 3.10.0 Assignee: Unassigned Created: 2020/04/28 9:58 AM Priority: Normal Reporter: Lee Lowder When running `facter -p` (with or without sudo) the following warning is mentioned: WARN puppetlabs.facter - Could not load puppet; some facts may be unavailable: cannot load such file – puppet This is happening with open source puppet 6.13.0 on Ubuntu 18.04 systems. Add Comment
Jira (PUP-10211) 'puppet module install --module_repository' never finishes
Title: Message Title Lee Lowder commented on PUP-10211 Re: 'puppet module install --module_repository' never finishes Apologies for the delay - I had been pulled into other things. The URL is correct, I copied and pasted it out of my Artifactory "set me up" section. For the logs, I have a set now, that I have suitably sanitized, I just need to figure out how to get them off the system, as it is fairly restricted access. Other than this master I am building, the only one I have availble to test on is running 4.5.3 - and I haven't set up the reverse prxy thing that 4.9.x and older needs, so I can't test there Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340717.1577458334000.24744.1579104360162%40Atlassian.JIRA.
Jira (PUP-10211) 'puppet module install --module_repository' never finishes
Title: Message Title Lee Lowder commented on PUP-10211 Re: 'puppet module install --module_repository' never finishes So, I let the command run for 5 minutes, with the trace, debug, and http debug options. Wound up with no modules and a 193 mb log file. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340717.1577458334000.9857.1577726400119%40Atlassian.JIRA.
Jira (PUP-10211) 'puppet module install --module_repository' never finishes
Title: Message Title Lee Lowder commented on PUP-10211 Re: 'puppet module install --module_repository' never finishes It's version 6.10.4, and that is what it said to use in the "set me up" section after I added the repo. I'm unable to copy out the json, due to how the work network is setup and company policies, but when I captured it to a file, it looked like some sort of listing of a bunch of modules that had stdlib as a requirement. - metadata of the module, the readme. Looks to be multiple versions of about 20 modules. I'll have to wait till Monday to do any further digging though, it's well past my bed time, let alone the end of my work day. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340717.1577458334000.9747.1577510820131%40Atlassian.JIRA.
Jira (PUP-10211) 'puppet module install --module_repository' never finishes
Title: Message Title Lee Lowder commented on PUP-10211 Re: 'puppet module install --module_repository' never finishes Garrett Guillotte We are configured to use straight https (443). That's what r10k uses, and it gives me a wall of json when I curl the correct URL directly. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340717.1577458334000.9727.1577494560103%40Atlassian.JIRA.
Jira (PUP-10211) 'puppet module install --module_repository' never finishes
Title: Message Title Lee Lowder commented on PUP-10211 Re: 'puppet module install --module_repository' never finishes As an update, if I "curl https://artifactory..com/api/puppet/puppet-forge/v3/releases?limit=20=20"` I get a wall of json back. However, when I use `puppet module install puppetlabs/stdlib --module_repository = https://artifactory..com/api/puppet/puppet-forge` it tries to download from `https://artifactory..com/api/puppet/puppet-forge/api/puppet/puppet-forge/v3/releases?limit=20=20` which 404s. Oddly, it keeps trying this, forever (I've let it run for 30+ minutes before) If I pass in `https://artifactory..com/` then it tries to use `https://artifactory..com/v3/releases?module` which results in a 404. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340717.1577458334000.9725.1577494500083%40Atlassian.JIRA.
Jira (PUP-10211) {brief summary of issue}
Title: Message Title
Lee Lowder created an issue
Puppet / PUP-10211
{brief summary of issue}
Issue Type:
Bug
Affects Versions:
PUP 6.10.1, PUP 6.11.1
Assignee:
Unassigned
Created:
2019/12/27 6:52 AM
Priority:
Normal
Reporter:
Lee Lowder
When I add `–module_repository https://artifactory..com/api/puppet/puppet-forge` to my fixtures, my unit tests just hang forever. When I run `puppet module install puppetlabs/stdlib --debug --module_repository https://artifactory..com/api/puppet/puppet-forge` on puppet 6.10.1 directly, or on 6.10.1 or 6.11.1 via pdk bundle exec, I see the following: ``` Debug: HTTP GET https://artifactory..com/api/puppet/puppet-forge/api/puppet/puppet-forge/v3/releases?limit=20=20 Debug: HTTP GET https://artifactory..com/api/puppet/puppet-forge/api/puppet/puppet-forge/v3/releases?limit=20=20 Debug: HTTP GET https://artifactory..com/api/puppet/puppet-forge/api/puppet/puppet-forge/v3/releases?limit=20=20 ``` repeating until I kill it. If I use `–module_repository https://artifactory..com`, then I get a 404 with it trying the URL https://artifactory..com/v3/releases?module=pupetlabs-stdlib_by=version_fields=readme%2Cchangelog%2Clicense%2Curi%2Cmodule%2Ctags%2Csupported%2Cdownlaods%2Ccreated_at%2Cupdated_at%2Cdeleted_at ``` I've set this up using a combination of Artifactory documentation, and the documentation for puppet and puppet_spec_helper, but have not been able to get it to install modules from my local Artifactory based forge. (FWIW, I have r10k installing modules from it successfully)
Jira (BOLT-819) Documentation unclear
Title: Message Title Lee Lowder created an issue Puppet Task Runner / BOLT-819 Documentation unclear Issue Type: Bug Assignee: Unassigned Created: 2018/08/29 5:34 AM Priority: Normal Reporter: Lee Lowder The documentation around the --nodes param is unclear. All the examples only show host names being used, but the help output and https://puppet.com/docs/bolt/0.x/bolt_command_reference.html#command-options have a note about IPv6 addresses, with and without ports. No where that I could find does it explicitly state that `–nodes` can take IP addresses as arguments, though in my testing, using IPv4 addresses did actually work. The docs and examples should be clarified around this, and also state explicitly if it is expected what you can use for the nodes list - names, iipv4, ipv6,and / or a mixture of the three, as well as what sort of globbing or regex type functions are available. For example, if all the IP addresses I need to specify share 3 of 4 elements in their dotted quad, is there a way from the command line to easily specify this and just list out the last portion for those nodes? Add Comment
Jira (PDOC-215) Type aliases are not handled well
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-215 Type aliases are not handled well Issue Type: New Feature Assignee: Unassigned Created: 2018/02/15 9:37 AM Priority: Normal Reporter: Lee Lowder There is currently no way to document type aliases using Strings. They are not really mentioned in any of the documentation, or the proposed style guide for Strings. They are ignored when documentation is rendered. If a class param uses them, it shows the name of the alias, but NOT what it makes up. There should be some way to separately document these, and the param type listing should link to it or provide it as an expandable element or such. Add Comment This message was sent
Jira (PDOC-214) Add ability to customize the template
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-214 Add ability to customize the template Issue Type: New Feature Assignee: Unassigned Created: 2018/02/15 9:34 AM Priority: Normal Reporter: Lee Lowder There should be a simple, documented method for customizing the rendered HTML output - adding custom sections or reordering things, applying custom CSS, etc. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDOC-213) Add support for @note tag
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-213 Add support for @note tag Issue Type: New Feature Assignee: Unassigned Created: 2018/02/15 9:33 AM Priority: Normal Reporter: Lee Lowder Strings should support the @note YARD tag in rendered documentation. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDOC-212) Add support for @todo tag
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-212 Add support for @todo tag Issue Type: New Feature Assignee: Unassigned Created: 2018/02/15 9:32 AM Priority: Normal Reporter: Lee Lowder Strings should support the YARD @todo tag in rendered documentation. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDOC-211) Add support for generating a "meta index"
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-211 Add support for generating a "meta index" Issue Type: New Feature Assignee: Unassigned Created: 2018/02/15 9:28 AM Priority: Normal Reporter: Lee Lowder when you run `puppet strings server` it parses all the modules in your modulepath and then generates a master/meta index. This is not currently possible to do using `puppet strings generate` which is done per module. It would be super useful to be able to feed generate a list of modules or a modulepath and have it generate documentation like puppet strings server does. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDOC-196) Documentation misleading about acceptable tags
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-196 Documentation misleading about acceptable tags Issue Type: Bug Affects Versions: PDOC 1.1.1 Assignee: Unassigned Created: 2018/01/09 11:31 AM Environment: Strings 1.1.1, yard 0.9.9, Ruby 2.1.9p490 (2016-03-30 revision 54437) [i386-mingw32], puppet 4.5.3 on win7 Strings command ran from a "Start command prompt with puppet" instance, non-admin user Priority: Normal Reporter: Lee Lowder The docs for Strings states: The most commonly used tags for Strings are: ... For a complete list of tags, see the YARD Tags Overview. This implies that while the tags in the list are the most often used ones, any valid tag can be used. However, when I used the @todo and @note tags they did not show up in my rendered HTML documentation as expected. This ticket is intended to request that support for the additional tags be added, and that the documentation be updated to reflect actual behavior in the mean time since adding the tags may be non-trivial.
Jira (PUP-7950) Allow specifying an MD5 URI for files with HTTP(s) sources
Title: Message Title
Lee Lowder created an issue
Puppet / PUP-7950
Allow specifying an MD5 URI for files with HTTP(s) sources
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2017/09/14 9:03 AM
Priority:
Normal
Reporter:
Lee Lowder
Because a simple "touch" command can change the ctime/mtime on files, and thus leading to false changes (which could then trigger service or exec refreshes). there should be a way to specify a URI that contains an MD5sum or other checksum value for files that use http or https based sources.
Example:
file {
'/some/path/to/some_file.ext':
source => 'http:://example.com/files/some_file.ext',
checksum_source =>
Jira (FACT-1429) Facter returns 0 if you look up an non-existant fact
Title: Message Title
Lee Lowder created an issue
Facter / FACT-1429
Facter returns 0 if you look up an non-existant fact
Issue Type:
Improvement
Affects Versions:
FACT 3.2.0
Assignee:
Unassigned
Created:
2016/05/23 11:31 AM
Priority:
Normal
Reporter:
Lee Lowder
Using facter 3.2.0 (commit 5e45299d76599d17f1f1337eaee6a64363904a2)
{{$ facter - p doesnotexist
$ echo $? 0 $}}
There should be an option comparable to `--detailed-exitcodes` that the puppet agent supports, or such behavior should be available by default.
Add Comment
Jira (HI-482) String literals should literally be literal
Title: Message Title Lee Lowder commented on HI-482 Re: String literals should literally be literal I really feel that closing this is the wrong thing to do, especially since the reason seems to be "this is hard, so no." Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5541) Package resources should support pessimistic versioning
Title: Message Title Lee Lowder created an issue Puppet / PUP-5541 Package resources should support pessimistic versioning Issue Type: Improvement Assignee: Unassigned Created: 2015/11/23 6:19 AM Priority: Normal Reporter: Lee Lowder The package resource should let you ensure a range of versions, similiar to how pessimistic versioning works with gems. This would let you ensure a range, and have it act like `ensure => latest` but only install minor or patch level upgrades depending on how you specify the version. This would create less work for admins, as they could get bugfix releases automatically, but not have to worry about a breaking major change version getting in without them explicitly choosing it. Add Comment
Jira (PUP-5476) notify resource should have a refreshonly attribute
Title: Message Title Lee Lowder updated an issue Puppet / PUP-5476 notify resource should have a refreshonly attribute Change By: Lee Lowder Summary: notify resource should hae have a refreshonly attribute Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5476) notify resource should hae a refreshonly attribute
Title: Message Title Lee Lowder created an issue Puppet / PUP-5476 notify resource should hae a refreshonly attribute Issue Type: Improvement Assignee: Unassigned Created: 2015/11/05 8:30 AM Priority: Normal Reporter: Lee Lowder The notify resource should have a refreshonly attribute, so you can set up notify events that only happen if something else happens, such as if a file changes or a service restarts. There are cases where a senior admin may do things that are not clear to a junior, and a notify would help explain the behavior, but it doesn't need to be shown every time. Another example would be when a config file changes requires a service to restart, but the restart needs to be done at a later time. Add Comment
Jira (PUP-4434) File type can't only use setgid for directory, and skip over files
Title: Message Title Lee Lowder created an issue Puppet / PUP-4434 File type can't only use setgid for directory, and skip over files Issue Type: Bug Assignee: Unassigned Created: 2015/04/17 7:23 AM Labels: support customer Priority: Normal Reporter: Lee Lowder (Note, this was manually copied from a redmine ticket) Given a directory: $dir = '/some/dir/' You may wish to recursively ensure a certain mode such as: u=rw,g=r As you all know, this cleverly adds +x to directories, but not to files. (good!) You may also decide that you’d like to setgid (+s) for the directory…
Jira (PUP-4434) File type can't only use setgid for directory, and skip over files
Title: Message Title Lee Lowder commented on PUP-4434 Re: File type can't only use setgid for directory, and skip over files https://projects.puppetlabs.com/issues/20001 (original ticket) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4426) group resource doesn't work on Windows when members is an array and noop is used
Title: Message Title
Lee Lowder created an issue
Puppet / PUP-4426
group resource doesn't work on Windows when members is an array and noop is used
Issue Type:
Bug
Affects Versions:
PUP 3.7.4
Assignee:
Unassigned
Created:
2015/04/16 9:55 AM
Labels:
customer support
Priority:
Normal
Reporter:
Lee Lowder
The following resource fails:
group { 'administrators':
ensure = present,
Jira (PUP-4423) Deprecation warning for non-string file modes is unclear
Title: Message Title Lee Lowder created an issue Puppet / PUP-4423 Deprecation warning for non-string file modes is unclear Issue Type: Improvement Affects Versions: PUP 3.7.4 Assignee: Unassigned Created: 2015/04/16 7:12 AM Labels: support customer Priority: Normal Reporter: Lee Lowder When a file doesn't use a string for the mode,the error given at run time is: Warning: Non-string values for the file mode property are deprecated. It must be a string, either a symbolic mode like 'o+w,a+r' or an octal representation like '0644' or '755'. (at /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/type/file/mode.rb:69:in `block (2 levels) in module:Puppet')
Jira (PUP-4054) create_resources() error messages are less useful in 3.x then they were in 2.x
Title: Message Title Lee Lowder created an issue Puppet / PUP-4054 create_resources() error messages are less useful in 3.x then they were in 2.x Issue Type: Bug Assignee: Unassigned Created: 2015/02/27 7:20 AM Labels: support customer Priority: Normal Reporter: Lee Lowder In PE 2.8 (Puppet 2.7.x) this function will show the file/line number detail of the Puppet DSL code where the exception occurred. In PE 3.x(including PE 3.7 / Puppet 3.7) it shows the file/line number of the Puppet DSL where the create_resources() function was invoked - which is not helpful. Add Comment
Jira (PDB-1246) Add V3 API deprecation message
Title: Message Title Lee Lowder commented on PDB-1246 Re: Add V3 API deprecation message My biggest issue is that I don't think a version of the API should be deprecated before the next version is stable. Ideally, version X is deprecated when version X+1is stable. At the next major release after that (or if X+1 becomes stable in a major release, the same release), then version X - 1 is removed. This way, at any given point, there is a a single deprecated version of the API, a single stable/current version, and then the experimental version. This largely echos Ken's concerns. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1253) There should be a way to replace a subset of facts
Title: Message Title Lee Lowder created an issue PuppetDB / PDB-1253 There should be a way to replace a subset of facts Issue Type: Improvement Assignee: Unassigned Created: 2015/02/24 8:21 AM Labels: customer support Priority: Normal Reporter: Lee Lowder The replace_facts command API endpoint replaces all facts. There should be a way to only replace a subset of facts, leaving other facts at the present value. Add Comment
Jira (PDB-1235) Possible memory leaks / GC issues
Title: Message Title Lee Lowder created an issue PuppetDB / PDB-1235 Possible memory leaks / GC issues Issue Type: Bug Affects Versions: PDB 1.6.3 Assignee: Unassigned Created: 2015/02/13 11:59 AM Labels: support customer Priority: Normal Reporter: Lee Lowder The version of PuppetDB ( 1.6.3) that ships with PE 3.3.2 appears to have either a memory leak, or an issue with garbage collection. From a customer: I’ve bumped the java heap size several times now, and it seems to be able to chew up what ever we bump it up to. This would seem to be an indication of poor garbage collection and/or memory leaks. Currently that heap is at 2.5 gigs, after getting warnings when it was at 1.5 gigs.
Jira (PUP-3975) puppet device should have a puppet apply equivilant
Title: Message Title Lee Lowder created an issue Puppet / PUP-3975 puppet device should have a puppet apply equivilant Issue Type: Improvement Assignee: Unassigned Created: 2015/02/06 12:30 PM Labels: support customer Priority: Normal Reporter: Lee Lowder The puppet device face should have a mode of functioning that works with out a master, like how puppet apply is used without a master. This would be useful when debugging device based modules. Add Comment
Jira (PUP-2018) `puppet certificate generate` Generates Two CSRs in One Run
Title: Message Title Lee Lowder updated an issue Puppet / PUP-2018 `puppet certificate generate` Generates Two CSRs in One Run Change By: Lee Lowder Affects Version/s: PUP3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2018) `puppet certificate generate` Generates Two CSRs in One Run
Title: Message Title Lee Lowder commented on PUP-2018 Re: `puppet certificate generate` Generates Two CSRs in One Run This issue exists in PE 3.2.x - PE 3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3673) type validation ignores tags when catalog is being converted to RAL format
Title: Message Title Lee Lowder created an issue Puppet / PUP-3673 type validation ignores tags when catalog is being converted to RAL format Issue Type: Bug Affects Versions: PUP 3.4.3 Assignee: Unassigned Created: 2014/11/14 6:15 AM Labels: support Priority: Normal Reporter: Lee Lowder Type validations are being executed during the conversion of the catalog to RAL format during the prepare_and_retrieve_catalog phase. This conversion to RAL is not being filtered by tags in any way Add Comment
Jira (PUP-3657) Using create_resource or some other Ruby methodology for creating resources allows for invalid resource references
Title: Message Title
Lee Lowder commented on PUP-3657
Re: Using create_resource or some other Ruby methodology for creating resources allows for invalid resource references
Using a simple test case and PE 3.7.0 / Puppet 3.7.2:
class case_test{
case_test::foo{'hello my name is inigo montoya': }
create_resources( 'file', { '/tmp/foo' = { ensure = present, require = Case_test::foo['hello my name is inigo montoya'] } } )
}
This results in the following error:
[root@pe-370-master production]# puppet agent -t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote
Jira (PUP-3630) Odd behavior with noop
Title: Message Title Jay Wallace created an issue Puppet / PUP-3630 Odd behavior with noop Issue Type: Bug Assignee: Unassigned Created: 2014/11/06 12:48 PM Labels: support Priority: Normal Reporter: Jay Wallace This behavior is really quirky. It seems if a defined type is restructured to include the noop parameter, you get the expected behavior described initially in the ticket (ie a noop overwrite). Without restructuring the defined type, noop = false will not take precedence over what is set in let's say site.pp. This could be due to an issue with the way noop is being inherited by the resources with the defined type. I am using inherited pretty loosely here, as this isn't actually the way this works. Further investigation needed, please feel free to either escalate or open a bug with my last update. Add Comment
Jira (PUP-3630) Odd behavior with noop
Title: Message Title Lee Lowder updated an issue Puppet / PUP-3630 Odd behavior with noop Change By: Lee Lowder Thisbehaviorisreallyquirky.Itseemsifadefinedtypeisrestructuredtoincludethenoopparameter,yougettheexpectedbehaviordescribedinitiallyintheticket(ieanoopoverwrite).Withoutrestructuringthedefinedtype,noop=falsewillnottakeprecedenceoverwhatissetinlet'ssaysite.pp.Thiscouldbeduetoanissuewiththewaynoopisbeinginheritedbytheresourceswiththedefinedtype.Iamusinginheritedprettylooselyhere,asthisisn'tactuallythewaythisworks. Furtherinvestigationneeded,pleasefeelfreetoeitherescalateoropenabugwithmylastupdate. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-953) Observed PuppetDB database connection leak
Title: Message Title Lee Lowder created an issue PuppetDB / PDB-953 Observed PuppetDB database connection leak Issue Type: Bug Affects Versions: 1.6.3 Assignee: Unassigned Created: 13/Oct/14 7:43 AM Labels: support Priority: Normal Reporter: Lee Lowder (This was reported by a customer) Yesterday I cutover from an old to a new PuppetDB infrastructure based on PuppetDB 1.6.3.1 in PE 3.3.1 (pe-puppetdb-1.6.3.1-1.el6.noarch). Not long after we cutover I experienced an issue which hadn't previously appeared in the old environment. The number of connections to the PostgreSQL backend (pe-postgresql-9.2.7-9.pe.el6.x86_64) continued to climb until we hit the maximum number of allowed connections in Postgres and PuppetDB (and the Console) were no longer able to make new connections and the environment ground to a halt. I did not see this behavior in any of my pre-cutover testing in the new environment so it may be only something occurs under sustained load, though it is possible it may have been there but gone unobserved. I have run a number of tests and I believe I have isolated the configuration setting responsible for the behavior. My tests point to conn-lifetime in PuppetDB's database.ini file as the culprit. The scenario I originally started with is that I had PuppetDB's database.ini file set with the following:
Jira (FACT-655) EC2 facts on Solaris don't use arp -an
Title: Message Title
Lee Lowder created an issue
Facter / FACT-655
EC2 facts on Solaris don't use arp -an
Issue Type:
Bug
Assignee:
Eric Sorenson
Created:
14/Aug/14 10:53 AM
Labels:
support
Priority:
Normal
Reporter:
Lee Lowder
In this commit, https://github.com/puppetlabs/facter/commit/0d6636261336a36d4fdaaf950218ccaa95d61487 the arp command for Solaris was changed to use arp -a instead of {{arp -an}.
The reason given is:
This is an invalid command on Solaris 8, but not 9 or 10.
This is no long valid, as Solaris 8 is no longer supported - PE currently only supports Solaris 10 and 11.
Add Comment
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Lee Lowder created an issue Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Created: 11/Aug/14 9:09 AM Priority: Normal Reporter: Lee Lowder If a catalog has a dependency cycle in it, the catalog fails to apply, but it counts it as a successful run. # puppet agent -t Info: Retrieving plugin Info: Loading facts in /opt/puppet/share/puppet/modules/postgresql/lib/facter/postgres_default_version.rb Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/root_home.rb Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/facter_dot_d.rb Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/puppet_vardir.rb Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/pe_version.rb Info: Loading facts in /opt/puppet/share/puppet/modules/pe_staging/lib/facter/staging_http_get.rb Info: Loading facts in /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/pe_build.rb Info: Loading facts in /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/windows.rb Info: Loading facts in /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/platform_tag.rb Info: Loading facts in /opt/puppet/share/puppet/modules/firewall/lib/facter/iptables_version.rb Info: Loading facts in /opt/puppet/share/puppet/modules/firewall/lib/facter/iptables_persistent_version.rb Info: Loading facts in /opt/puppet/share/puppet/modules/firewall/lib/facter/ip6tables_version.rb Info: Loading facts in
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Lee Lowder commented on an issue Re: Hiera should support alternate environments While multiple masters are easy to setup - for both open source and Enterprise users, each master will consume at least one Enterprise license, and potentially 3 licenses if a split install is used. So using multiple masters is one possible workaround for some cases, it is not always a practical or viable one. There is also the cost that comes into effect. While spinning up a new VM is usually relatively cheap, it is not always an insignificant cost in terms of time, effort, hardware and licensing. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google
Jira (PUP-2736) the hosts resource should match on the IP address
Title: Message Title Lee Lowder updated an issue Puppet / PUP-2736 the hosts resource should match on the IP address Change By: Lee Lowder Labels: Support Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2736) the hosts resource should match on the IP address
Title: Message Title Lee Lowder created an issue Puppet / PUP-2736 the hosts resource should match on the IP address Issue Type: Improvement Assignee: Unassigned Created: 06/Jun/14 9:45 AM Priority: Normal Reporter: Lee Lowder [from a customer] In my opinion, the host resource type has a deficiency. The primary key of /etc/hosts file is ip address, not the host name. so if the IP address set by the Œhost resource conflicts with other entry, it should either be corrected or at least have an error generated to expose the conflict. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title Lee Lowder created an issue Puppet / PUP-2689 A node can't always collect its own exported resources Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Attachments: exported resource bug - Table of results.pdf Created: 28/May/14 7:29 AM Labels: support Priority: Normal Reporter: Lee Lowder Depending on how tags are applied, a node does not collect its own resources. Setting the tag metaparameter in a resource default results in none of the test nodes collecting this resource. When the tag function is used, then each node collects the other nodes resources, but not it's own. When the resource has a tag = metaparameter applied directly, then all resources are collected. However, even when the tag is given as a string rather than an array, the resource is collected ( at least on some resource types, notify, setting the tag as a string did not fully work for a concat resource )
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title
Lee Lowder commented on an issue
Re: A node can't always collect its own exported resources
My main desires are to have things work in a more consistent manner, for things to work as expected based on the documentation, and also to have better documentation where there differences/exceptions.
What that winds up looking like, I don't really care.
I was simply trying to document what I found, and also provide as much information to those who could investigate more deeply than I could.
Add Comment
Puppet / PUP-2689
A node can't always collect its own exported resources
Depending on how tags are applied, a node does not collect its own resources. Setting the {{tag}} metaparameter in a resource default results in none of the test nodes collecting this resource. When the {{tag}} function is used, then each node collects the other nodes resources, but not it's own. When the resource has a {{tag =}} metaparameter ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups
Jira (PUP-1352) package ensure = purged is too noisy!
Title: Message Title Lee Lowder updated an issue Puppet / PUP-1352 package ensure = purged is too noisy! Change By: Lee Lowder Labels: redmine support Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2381) Tags should issue an error when they are invalid
Title: Message Title Lee Lowder created an issue Puppet / PUP-2381 Tags should issue an error when they are invalid Issue Type: Bug Affects Versions: 3.5.1, 3.4.3, 2.7.23 Assignee: Unassigned Created: 29/Apr/14 6:29 AM Priority: Normal Reporter: Lee Lowder The docs ( http://docs.puppetlabs.com/puppet/3/reference/lang_reserved.html#tags ) state ( emphasis added) that tags names should confirm to \A[a-z0-9_][a-z0-9_:\.\-]*\Z and also: Tags must begin with a lowercase letter, number, or underscore, and can include: Lowercase letters Numbers Underscores Colons Periods
Jira (PUP-2306) Puppet::Util::Execution.execute no longer returns a String
Title: Message Title Lee Lowder created an issue Puppet / PUP-2306 Puppet::Util::Execution.execute no longer returns a String Issue Type: Bug Affects Versions: 3.4.0 Assignee: Unassigned Created: 18/Apr/14 12:52 PM Priority: Normal Reporter: Lee Lowder Commit 732d450 ( https://github.com/puppetlabs/puppet/commit/732d450 ) changed the return type of Puppet::Util::Execution.execute from a String, to a new string subclass Puppet::ProcessOutput. This is not a fully backwards compatible change, and causes problems where things do strict type checking - for example, the chomp() function in stdlib. Add Comment
Jira (PUP-1989) puppet doc doesn't clean up after itself
Title: Message Title Lee Lowder updated an issue Puppet / PUP-1989 puppet doc doesn't clean up after itself Change By: Lee Lowder Labels: support Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1989) puppet doc doesn't clean up after itself
Title: Message Title Lee Lowder created an issue Puppet / PUP-1989 puppet doc doesn't clean up after itself Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Created: 19/Mar/14 12:57 PM Priority: Normal Reporter: Lee Lowder After running puppet doc --all --mode rdoc --outputdir /var/www/html/puppet/doc --debug --modulepath /etc/puppetlabs/puppet/modules from /etc/puppetlabs/puppet/modules there are a lot of .html files left laying around in the modules. [root@pe-320-master pe-320-master.puppetdebug.vlan]# cd /etc/puppetlabs/puppet/modules/ntp/ [root@pe-320-master ntp]# ll total 136 -r--r--r-- 1 root pe-puppet 3365 Mar 3 17:35 CHANGELOG.md -r--r--r-- 1 root pe-puppet 657 Mar 3 17:35 CONTRIBUTING.md -r--r--r-- 1 root pe-puppet 573 Mar 3 17:35 Gemfile -rw-r--r-- 1 root root 14310 Mar 19 07:50 Gemfile.html -r--r--r-- 1 root pe-puppet 11346 Mar 3 17:35 LICENSE -rw-r--r-- 1 root root 24270 Mar 19 07:50 LICENSE.html drwxr-xr-x 2 root pe-puppet 4096 Mar 19 07:50 manifests -r--r--r-- 1 root pe-puppet 4347 Mar 3 17:35 metadata.json -r--r--r-- 1 root pe-puppet 399 Mar 3 17:35 Modulefile -rw-r--r-- 1 root root 14079 Mar 19 07:50 Modulefile.html -r--r--r-- 1 root pe-puppet44 Mar 3 17:35 Rakefile -rw-r--r-- 1 root root 13625 Mar 19 07:50 Rakefile.html -r--r--r-- 1 root pe-puppet 5606 Mar 3 17:35 README.markdown drwxr-xr-x 6 root pe-puppet 4096 Mar 19 06:27 spec drwxr-xr-x 2 root pe-puppet 4096 Mar 19 06:27 templates drwxr-xr-x 2 root pe-puppet 4096 Mar 3 17:35 tests
