Jira (PDB-5094) Add some initial query tests
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-5094 Add some initial query tests Change By: Eric Thompson Priority: Normal Critical Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.394361.1617754897000.23212.1619806440189%40Atlassian.JIRA.
Jira (PDB-5105) Benchmark console query performance and identify slow queries
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-5105 Benchmark console query performance and identify slow queries Change By: Eric Thompson Priority: High Critical Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.395324.161841225.23213.1619806440236%40Atlassian.JIRA.
Jira (PUP-11051) Systemd not recognized as service_provider on Ubuntu 17 +
Title: Message Title Jack Casey updated an issue Puppet / PUP-11051 Systemd not recognized as service_provider on Ubuntu 17 + Change By: Jack Casey *Puppet Version: 4.10.12* *Puppet Server Version: 2.8.1* *OS Name/Version: Ubuntu 20.04 (Focal Fossa)*The service_provider fact is resolved as `debian` on Ubuntu 20 and Puppet 4.10.x. This should be resolved as systemd. In more recent versions of Puppet this is resolved with the notdefaultfor function future-proofing. However for Puppet 4.10.x the versions need to be explicitly specified.*Desired Behavior:* The service_provider should be recognized as systemd*Actual Behavior:*The service_provider is recognized as debian*Examples:*$ puppet --version 4.10.12$ facter -p | grep service_provider service_provider => systemd$ hostnamectl | grep "Operating System" Operating System: Ubuntu 20.04.2 LTS A PR to fix this issue is available here: [https://github.com/puppetlabs/puppet/pull/ 8591 8593 ] Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11051) Systemd not recognized as service_provider on Ubuntu 17 +
Title: Message Title Jack Casey updated an issue Puppet / PUP-11051 Systemd not recognized as service_provider on Ubuntu 17 + Change By: Jack Casey *Puppet Version: 4.10.12* *Puppet Server Version: 2.8.1* *OS Name/Version: Ubuntu 20.04 (Focal Fossa)*The service_provider fact is resolved as `debian` on Ubuntu 20 and Puppet 4.10.x. This should be resolved as ` systemd ` . In more recent versions of Puppet this is resolved with the ` notdefaultfor ` function future-proofing. However for Puppet 4.10.x the versions need to be explicitly specified.*Desired Behavior:* ** The service_provider should be recognized as ` systemd ` *Actual Behavior:*The service_provider is recognized as ` debian ` *Examples:* ``` $ puppet --version4.10.12$ facter -p | grep service_providerservice_provider => systemd$ hostnamectl | grep "Operating System" Operating System: Ubuntu 20.04.2 LTS ``` A PR to fix this issue is available here: [ https://github.com/puppetlabs/puppet/pull/8591 ] Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11051) Systemd not recognized as service_provider on Ubuntu 17 +
Title: Message Title Jack Casey created an issue Puppet / PUP-11051 Systemd not recognized as service_provider on Ubuntu 17 + Issue Type: Bug Affects Versions: PUP 4.10.12 Assignee: Jack Casey Created: 2021/04/30 9:52 AM Priority: Low Reporter: Jack Casey Puppet Version: 4.10.12 Puppet Server Version: 2.8.1 OS Name/Version: Ubuntu 20.04 (Focal Fossa) The service_provider fact is resolved as `debian` on Ubuntu 20 and Puppet 4.10.x. This should be resolved as `systemd`. In more recent versions of Puppet this is resolved with the `notdefaultfor` function future-proofing. However for Puppet 4.10.x the versions need to be explicitly specified. Desired Behavior: **The service_provider should be recognized as `systemd` Actual Behavior: The service_provider is recognized as `debian` Examples: ``` $ puppet --version 4.10.12 $ facter -p | grep service_provider service_provider => systemd $ hostnamectl | grep "Operating System" Operating System: Ubuntu 20.04.2 LTS ``` A PR to fix this issue is available here: https://github.com/puppetlabs/puppet/pull/8591 Add Comment
Jira (PDB-5094) Add some initial query tests
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-5094 Add some initial query tests Change By: Eric Thompson Epic Link: PE-31891 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.394361.1617754897000.22786.1619799900044%40Atlassian.JIRA.
Jira (PDB-5105) Benchmark console query performance and identify slow queries
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-5105 Benchmark console query performance and identify slow queries Change By: Eric Thompson Epic Link: PE-31891 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.395324.161841225.22785.1619799840086%40Atlassian.JIRA.
Jira (PDB-2590) /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini
Title: Message Title Frédéric Lespez commented on PDB-2590 Re: /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini Seeing this bug since PDB 6.15 on Debian Buster. I have never seen it before. Running puppetdb ssl-setup -f also changes the permissions of the jetty.ini file from 644 to 640 which prevents PuppetDB to start. Before running puppetdb ssl-setup -f: # ls -l /etc/puppetlabs/puppetdb/conf.d/jetty.ini-rw-r--r-- 1 root root 2554 mars 27 17:18 /etc/puppetlabs/puppetdb/conf.d/jetty.ini After running puppetdb ssl-setup -f: # ls -l /etc/puppetlabs/puppetdb/conf.d/jetty.ini-rw-r- 1 root root 2592 mars 27 17:19 /etc/puppetlabs/puppetdb/conf.d/jetty.ini Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11050) Ruby 3 doesn't accept an opts hash
Title: Message Title
Ewoud Kohl van Wijngaarden created an issue
Puppet / PUP-11050
Ruby 3 doesn't accept an opts hash
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2021/04/30 5:06 AM
Priority:
Normal
Reporter:
Ewoud Kohl van Wijngaarden
This code no longer works in Ruby 3:
FileUtils.install(mf, omf, {:mode => 0644, :preserve => true, :verbose => true})
This does:
FileUtils.install(mf, omf, mode: 0644, preserve: true, verbose: true)
Jira (PUP-10926) Cloudinit support for Puppet 6 onwards
Title: Message Title Steve Shipway commented on PUP-10926 Re: Cloudinit support for Puppet 6 onwards The cc_puppet.py currently shipped with RHEL7/Centos7 can support Puppet6, but not by its default configuration. You need to give additional options similar to: puppet install: true version: 6.12.0 package_name: 'puppet-agent' conf_file: '/etc/puppetlabs/puppet/puppet.conf' Alternatively, if you have your puppet agent installed in your base image (which is preferable) then you can put "install: false" and omit the "version:" option. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
