Jira (PDB-5363) PuppetDB 7.7.1 not available on Docker Hub
Title: Message Title Chris Boot created an issue PuppetDB / PDB-5363 PuppetDB 7.7.1 not available on Docker Hub Issue Type: Bug Affects Versions: PDB 7.7.1 Assignee: Unassigned Components: PuppetDB Created: 2021/11/10 2:05 PM Environment: Docker Hub Labels: Docker Priority: Major Reporter: Chris Boot The Docker images for PuppetDB 7.7.1 are not available at https://hub.docker.com/r/puppet/puppetdb/tags. Given the changes in the agent and server depend on the newer PuppetDB, several setups may be at risk of getting broken by partial upgrades. Add Comment
Jira (PDB-5279) Docker: please update Java to 11 or higher
Title: Message Title Chris Boot created an issue PuppetDB / PDB-5279 Docker: please update Java to 11 or higher Issue Type: Improvement Assignee: Unassigned Created: 2021/09/18 8:50 AM Environment: Docker containers as published by the PuppetDB project, which use Ubuntu 18.04 (Bionic). Priority: Normal Reporter: Chris Boot Recently both PuppetDB and Puppet Server enabled TLSv1.3 support by default, but this is unusable with the published Docker containers as they use the Java 8 JRE rather than the Java 11 JRE. Given the TLSv1.3 support I assume that Java 11 is supported, and Java 11 is included in the Ubuntu 18.04 base image that the container uses, so I believe that this should be a one-line change in the Dockerfile. Add Comment
Jira (PUP-10799) networking.interfaces fact not appearing
Title: Message Title Chris Boot created an issue Puppet / PUP-10799 networking.interfaces fact not appearing Issue Type: Bug Affects Versions: PUP 7.0.0 Assignee: Unassigned Attachments: facter-networking-interfaces.log, facter-networking-primary.log, facter-networking.log Created: 2020/12/03 4:40 AM Priority: Normal Reporter: Chris Boot Puppet Version: 7.0.0 Puppet Server Version: 6.14.1 OS Name/Version: Debian testing (bullseye) On one of my nodes, Puppet does not pick up the networking.interfaces fact. The fact is visible when querying Facter directly for the top-level fact (e.g. facter networking) but does not show up through Puppet (e.g. puppet facts show networking) or when querying the sub-fact value (e.g. facter networking.interfaces). Add Comment
Jira (PDB-4591) Latest report no longer updated for unchanged reports
Title: Message Title Chris Boot created an issue PuppetDB / PDB-4591 Latest report no longer updated for unchanged reports Issue Type: Bug Affects Versions: PDB 6.7.3 Assignee: Unassigned Components: PuppetDB Created: 2019/11/16 3:47 PM Environment: PuppetDB 6.7.3 PostgreSQL 9.6.16 Priority: Major Reporter: Chris Boot The report_timestamp of nodes, and the report obtained by querying for the latest_report?, are not updated for unchanged reports. This makes tools that want the latest report instead obtain reports from hours ago. Querying for all reports on a node still shows the unchanged reports, however. Reverting to PuppetDB 6.7.2 fixes this, but this is complicated by the addition of a database migration in 6.7.3.
Jira (PUP-6415) static_compiler: symlinks in recursed directories don't work
Title: Message Title Chris Boot commented on PUP-6415 Re: static_compiler: symlinks in recursed directories don't work Essentially we strive to only use packages from trusted sources, and as much as possible only from distributors themselves. For Debian, most packages are already provided (via the main distribution or backports), or at a pinch we have Debian Developers (including myself) on staff who can contribute packages back to Debian that we'll also use. For Red Hat and CentOS we'll use EPEL but the ecosystem is very different. Unfortunately, as most distributors don't like to distribute bleeding edge packages (for good reasons generally), we won't get updated Puppet packages without going for 3rd party package sources like yours. We've had bad experiences using 3rd party sources before. Often such sources include packages unrelated to what's shipped and play havoc with others packages' dependencies. Other times packages ship their own versions of libraries such as OpenSSL and then don't bother keeping them up to date. The quality of such packages and sources is very variable. This kind of thing makes us very reluctant to reach for 3rd party packages unless we absolutely have to. I'm not saying your package repo or packages are like this at all, but once burned... Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6415) static_compiler: symlinks in recursed directories don't work
Title: Message Title Chris Boot commented on PUP-6415 Re: static_compiler: symlinks in recursed directories don't work So I've now had the chance to try out Static Catalogues in my lab (er, at home) Puppet setup. It seems to work well and does indeed appear to provide a replacement for the static_compiler terminus, at least at first glance. I also now understand much better how it works and how it essentially collects all the file metadata and delivers it with the catalogue. It's nice to see a new approach to this that really seems to work. Where this fails is that it requires use of the PuppetServer Java blob on the server, and Puppet 4.4+ on the client. We can use the static_compiler today and it mostly works, and works with Puppet 2.7 agents (which we still have in the field). Yes, we can migrate from distribution-supported Puppet packages to the PC1 versions in many cases but we've not had any particular reason to before. It also doesn't look like Debian is intending on going down the Java/PuppetServer route at all at the time being, which will inconvenience people like us. In my opinion it would be useful if you could apply the patch to 4.x branches at least, despite the static_compiler now being deprecated. (Now if only the richardc/datacat module could/would use this, that would be awesome!) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6415) static_compiler: symlinks in recursed directories don't work
Title: Message Title Chris Boot commented on PUP-6415 Re: static_compiler: symlinks in recursed directories don't work Hi Josh, I'm disappointed to hear that the static compiler is deprecated, it seems to help solve some real-world performance issues for me among other things. I've read up briefly about the replacement static catalogs system and it doesn't seem as mature to me. I know this isn't necessarily the right place to ask questions about it, but how does it handle directories and server-side recursion? symlinks? We've been trying to use the static compiler to drastically reduce the number of requests for metadata that our agents send to our masters. We use Puppet to manage our own clients' systems, and those systems are geographically very dispersed and many are on the end of unreliable or high-latency links where simply combining all the metadata into the catalogue makes things run far smoother both for our agents and our masters. Please reconsider. Regards, Chris Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6415) static_compiler: symlinks in recursed directories don't work
Title: Message Title Chris Boot commented on PUP-6415 Re: static_compiler: symlinks in recursed directories don't work Pull request in https://github.com/puppetlabs/puppet/pull/5026 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6415) static_compiler: symlinks in recursed directories don't work
Title: Message Title
Chris Boot updated an issue
Puppet / PUP-6415
static_compiler: symlinks in recursed directories don't work
Change By:
Chris Boot
When using the {{static_compiler}} terminus with a resource definition like the following:{code}file { '/tmp/somedir':ensure => directory,owner => 'root',group => 'root',links => 'manage',mode=> '0644',recurse => true,source => 'puppet:///modules/mymodule/somedir/',}{code}When the source directory contains a symlink, catalog application aborts because the symlink has no target:{ { code} } Error: /Stage[main]/Mymodule::Myclass/File[/tmp/somedir/foo]/ensure: change from absent to link failed: Cannot create a symlink without a target{ { code} } I have a patch for this bug that I will send in via GitHub shortly. Unfortunately, writing an rspec test to check for this condition is beyond my grasp of Ruby.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6415) static_compiler: symlinks in recursed directories don't work
Title: Message Title
Chris Boot created an issue
Puppet / PUP-6415
static_compiler: symlinks in recursed directories don't work
Issue Type:
Bug
Affects Versions:
PUP 4.5.2, PUP 3.8.7
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2016/06/16 8:54 AM
Environment:
Ruby 2.1, Linux
Priority:
Normal
Reporter:
Chris Boot
When using the static_compiler terminus with a resource definition like the following:
file { '/tmp/somedir':
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title Chris Boot commented on FACT-1394 Re: Warning printed when 'ip route show' output contains "linkdown" FACT-1405 is possibly a duplicate of this bug. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1405) Facter does not like next hop flags in ip route output
Title: Message Title Chris Boot commented on FACT-1405 Re: Facter does not like next hop flags in ip route output This is a possible duplicate of FACT-1394. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1405) Facter does not like next hop flags in ip route output
Title: Message Title Chris Boot commented on FACT-1405 Re: Facter does not like next hop flags in ip route output This also occurs on Debian Stretch (testing), but not on Debian Jessie (stable) even with a back-ported kernel. I suspect this is due to the former using iproute2_4.3.0-1 rather than 3.16.0-2. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3619) Hiera: future+strict_variables fails with uncaught throw :undefined_variable
Title: Message Title
Chris Boot commented on PUP-3619
Re: Hiera: future+strict_variables fails with uncaught throw :undefined_variable
Right, I've tried this with 3.7.3 and still get the issue. It seems it comes from Hiera resolving the hierarchy. If I create a hiera.yaml file with the following content:
---
:hierarchy:
- "%{foobar}"
... the bug is apparent. If I replace foobar with fqdn or another fact, then the catalogue applies.
I guess strictly speaking it is an undefined variable, but it crops up in a really unexpected place. In my case, I was using this for additional ENC-provided variables to be able to influence the hierarchy.
The doubly strange thing is that this only appears for me on parametric classes where I don't override the default value, as that's when the value is automatically looked up in Hiera.
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-3619) Hiera: future+strict_variables fails with uncaught throw :undefined_variable
Title: Message Title
Chris Boot updated an issue
Puppet / PUP-3619
Hiera: future+strict_variables fails with uncaught throw :undefined_variable
Change By:
Chris Boot
The following fails:{noformat}puppet apply --config /dev/null -e 'class foo($bar='test') { notify { "bar=${bar}": } } class { 'foo': }' --parser future --strict_variables{noformat}with:{noformat}Error: Evaluation Error: Error while evaluating a Resource Statement, Error from DataBinding 'hiera' while looking up 'foo::bar': uncaught throw :undefined_variable at line 1:51 on node babbage.bootc.euError: Evaluation Error: Error while evaluating a Resource Statement, Error from DataBinding 'hiera' while looking up 'foo::bar': uncaught throw :undefined_variable at line 1:51 on node babbage.bootc.eu{noformat} This was fine in Puppet 3.7.1.
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 (PUP-3619) Hiera: future+strict_variables fails with uncaught throw :undefined_variable
Title: Message Title
Chris Boot created an issue
Puppet / PUP-3619
Hiera: future+strict_variables fails with uncaught throw :undefined_variable
Issue Type:
Bug
Affects Versions:
PUP 3.7.2
Assignee:
Unassigned
Created:
2014/11/05 12:45 AM
Priority:
Major
Reporter:
Chris Boot
The following fails:
puppet apply --config /dev/null -e 'class foo($bar='test') { notify { "bar=${bar}": } } class { 'foo': }' --parser future --strict_variables
with:
Error: Evaluation Error: Error while evaluating a Resource Statement, Error from DataBinding 'hiera' while looking up 'foo::ba
