Jira (PDB-5523) Add Ubuntu 22.04 Jammy (x86_64) FOSS support
Title: Message Title Koen Dierckx updated an issue PuppetDB / PDB-5523 Add Ubuntu 22.04 Jammy (x86_64) FOSS support Change By: Koen Dierckx Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.458563.1660040376000.1607.1679295240035%40Atlassian.JIRA.
Jira (PDB-5523) Add Ubuntu 22.04 Jammy (x86_64) FOSS support
Title: Message Title Koen Dierckx commented on PDB-5523 Re: Add Ubuntu 22.04 Jammy (x86_64) FOSS support Is this on a roadmap, any ETA ? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.458563.1660040376000.27020.1662092820046%40Atlassian.JIRA.
Jira (PDB-5523) Add Ubuntu 22.04 Jammy (x86_64) FOSS support
Title: Message Title Koen Dierckx updated an issue PuppetDB / PDB-5523 Add Ubuntu 22.04 Jammy (x86_64) FOSS support Change By: Koen Dierckx Summary: Add Ubuntu 22.04 Jammy (x86_64) FOSS support Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.458563.1660040376000.9098.1660040460039%40Atlassian.JIRA.
Jira (PDB-5523) Add Ubuntu 22.04 (x86_64) FOSS support
Title: Message Title Koen Dierckx created an issue PuppetDB / PDB-5523 Add Ubuntu 22.04 (x86_64) FOSS support Issue Type: New Feature Assignee: Unassigned Components: PuppetDB Created: 2022/08/09 3:19 AM Priority: Major Reporter: Koen Dierckx Puppet Agent already has first builds available https://tickets.puppetlabs.com/browse/PA-4233 https://apt.puppetlabs.com/pool/jammy/puppet7/p/index.html But as we make extensive usage of puppetdb, we can not proceed with our tests without puppetdb / puppetdb termini Add Comment
Jira (PDB-5454) The pg_trgm postgresql extension is no longer inside the contrib package, but available by default since postgresql version 10
Title: Message Title
Koen Dierckx updated an issue
PuppetDB / PDB-5454
The pg_trgm postgresql extension is no longer inside the contrib package, but available by default since postgresql version 10
Change By:
Koen Dierckx
PuppetDB requires the pg_trgm extensionThe puppetdb module will install this extension with the class puppetdb::database::postgresqlThis extension *used* to be provided by a package called postgresql-contrib, and that is installed by the class \{ '::postgresql::server::contrib': }But this extension is being bundled with the postgresql package since version 10, so there is no longer a need to include the contrib package with class \{ '::postgresql::server::contrib': } Create a PR[https://github.com/puppetlabs/puppetlabs-puppetdb/pull/ 348 350 ] FYIIn our case, we have configured the puppetdb module, to use postgresql 13class { 'puppetdb': postgres_version => "13", After applying this manifest, we end up with both postgresql 13 and 14 installed This is caused by the contrib package pulling in the postgresql package as a dependency[https://wiki.postgresql.org/wiki/Apt]_*Note:* This repository provides "postgresql", "postgresql-contrib", and "postgresql-client" meta-packages that depend on the latest postgresql-x.y, ... packages, similar to the ones present in Debian and Ubuntu. Once a new PostgreSQL version is released, these meta-packages will be updated to depend on the new version._Unfortunately once a new postgresql version is released, there is no longer a meta package for the previous version available in the official postgresql apt repository for postgresql-contribAnd then the install of the postgresql-contrib package will also pull in the latest version of postgresql as its dependency.So in its core this is a package availability issue on the postgresql side and not a puppetdb issue. Created an issue for this here [https://redmine.postgresql.org/issues/7169]
Add Comment
Jira (PDB-5454) The pg_trgm postgresql extension is no longer inside the contrib package, but available by default since postgresql version 10
Title: Message Title
Koen Dierckx updated an issue
PuppetDB / PDB-5454
The pg_trgm postgresql extension is no longer inside the contrib package, but available by default since postgresql version 10
Change By:
Koen Dierckx
PuppetDB requires the pg_trgm extensionThe puppetdb module will install this extension with the class puppetdb::database::postgresqlThis extension *used* to be provided by a package called postgresql-contrib, and that is installed by the class \{ '::postgresql::server::contrib': }But this extension is being bundled with the postgresql package since version 10, so there is no longer a need to include the contrib package with class \{ '::postgresql::server::contrib': } Create a PR[https://github.com/puppetlabs/puppetlabs-puppetdb/pull/348] FYIIn our case, we have configured the puppetdb module, to use postgresql 13class { 'puppetdb': postgres_version => "13", After applying this manifest, we end up with both postgresql 13 and 14 installed This is caused by the contrib package pulling in the postgresql package as a dependency[https://wiki.postgresql.org/wiki/Apt]_*Note:* This repository provides "postgresql", "postgresql-contrib", and "postgresql-client" meta-packages that depend on the latest postgresql-x.y, ... packages, similar to the ones present in Debian and Ubuntu. Once a new PostgreSQL version is released, these meta-packages will be updated to depend on the new version._Unfortunately once a new postgresql version is released, there is no longer a meta package for the previous version available in the official postgresql apt repository for postgresql-contribAnd then the install of the postgresql-contrib package will also pull in the latest version of postgresql as its dependency.So in its core this is a package availability issue on the postgresql side and not a puppetdb issue. Created an issue for this here [https://redmine.postgresql.org/issues/7169]
Add Comment
Jira (PDB-5454) The pg_trgm postgresql extension is no longer inside the contrib package, but available by default since postgresql version 10
Title: Message Title
Koen Dierckx updated an issue
PuppetDB / PDB-5454
The pg_trgm postgresql extension is no longer inside the contrib package, but available by default since postgresql version 10
Change By:
Koen Dierckx
PuppetDB requires the pg_trgm extensionThe puppetdb module will install this extension with the class puppetdb::database::postgresqlThis extension *used* to be provided by a package called postgresql-contrib, and that is installed by the class \{ '::postgresql::server::contrib': }But this extension is now being bundled with the postgresql package since version 10 , so there is no longer a need to include the contrib package with class \{ '::postgresql::server::contrib': } FYIIn our case, we have configured the puppetdb module, to use postgresql 13class { 'puppetdb': postgres_version => "13", After applying this manifest, we end up with both postgresql 13 and 14 installed This is caused by the contrib package pulling in the postgresql package as a dependency[https://wiki.postgresql.org/wiki/Apt]_*Note:* This repository provides "postgresql", "postgresql-contrib", and "postgresql-client" meta-packages that depend on the latest postgresql-x.y, ... packages, similar to the ones present in Debian and Ubuntu. Once a new PostgreSQL version is released, these meta-packages will be updated to depend on the new version._Unfortunately once a new postgresql version is released, there is no longer a meta package for the previous version available in the official postgresql apt repository for postgresql-contribAnd then the install of the postgresql-contrib package will also pull in the latest version of postgresql as its dependency.So in its core this is a package availability issue on the postgresql side and not a puppetdb issue. Created an issue for this here [https://redmine.postgresql.org/issues/7169]
Add Comment
Jira (PDB-5454) The pg_trgm postgresql extension is no longer inside the contrib package, but available by default since postgresql version 10
Title: Message Title Koen Dierckx updated an issue PuppetDB / PDB-5454 The pg_trgm postgresql extension is no longer inside the contrib package, but available by default since postgresql version 10 Change By: Koen Dierckx Summary: The pg_trgm postgresql extension is no longer inside the contrib package, but available by default since postgresql version 10 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.434971.1644586338000.1.1644592260049%40Atlassian.JIRA.
Jira (PDB-5454) The pg_trgm postgresql extension is no longer inside the contrib package, but available by default
Title: Message Title
Koen Dierckx updated an issue
PuppetDB / PDB-5454
The pg_trgm postgresql extension is no longer inside the contrib package, but available by default
Change By:
Koen Dierckx
Currently PuppetDB requires the pg_trgm extension from the postgresql-contrib package. The puppetdb module will install this extension with the class puppetdb::database::postgresqlThis extension is *used* to be provided by a package called postgresql-contrib, and that is installed by class the class \{ ':: postgresql::server::contrib ': } The But this extension is now being bundled with the postgresql package , so there is called no longer a need to include the contrib package with class \{ ':: postgresql - ::server:: contrib (on Ubuntu ) ': } FYIIn our case, we have configured the puppetdb module, to use postgresql 13class { 'puppetdb': postgres_version => "13", After applying this manifest, we end up with both postgresql 13 and 14 installed This is caused by the contrib package pulling in the postgresql package as a dependency [https://wiki.postgresql.org/wiki/Apt]_*Note:* This repository provides "postgresql", "postgresql-contrib", and "postgresql-client" meta-packages that depend on the latest postgresql-x.y, ... packages, similar to the ones present in Debian and Ubuntu. Once a new PostgreSQL version is released, these meta-packages will be updated to depend on the new version._ Unfortunately once a new postgresql version is released, there is no longer a meta package for the previous version available in the official postgresql apt repository for postgresql-contribAnd then the install of the postgresql-contrib package will also pull in the latest version of postgresql as its dependency. In our case, we have configured the puppetdb module, to use postgresql 13class { 'puppetdb': postgres_version => "13",But on the server, we now have both postgresql 13 and 14 installed So in its core this is a package availability issue on the postgresql side and not a puppetdb issue. Created an issue for this here [https://redmine.postgresql.org/issues/7169] But perhaps the pg_trgm functionality can be dropped/replaced ?And that would drop the need for the postgresql-contrib packageAnd that avoids the entire dependency issue
Add
Jira (PDB-5454) The pg_trgm postgresql extension is no longer inside the contrib package, but available by default
Title: Message Title Koen Dierckx updated an issue PuppetDB / PDB-5454 The pg_trgm postgresql extension is no longer inside the contrib package, but available by default Change By: Koen Dierckx Summary: Is the The pg_trgm postgresql extention from postgresql- extension is no longer inside the contrib really needed ? package, but available by default Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.434971.1644586338000.14432.1644591180034%40Atlassian.JIRA.
Jira (PDB-5454) Is the pg_trgm postgresql extention from postgresql-contrib really needed ?
Title: Message Title
Koen Dierckx updated an issue
PuppetDB / PDB-5454
Is the pg_trgm postgresql extention from postgresql-contrib really needed ?
Change By:
Koen Dierckx
Currently PuppetDB requires the pg_trgm extension from the postgresql-contrib package. The puppetdb module will install this extension with the class puppetdb::database::postgresqlThis extension is provided by a package and is installed by class postgresql::server::contribThe package is called postgresql-contrib (on Ubuntu ) [https://wiki.postgresql.org/wiki/Apt]_*Note:* This repository provides "postgresql", "postgresql-contrib", and "postgresql-client" meta-packages that depend on the latest postgresql-x.y, ... packages, similar to the ones present in Debian and Ubuntu. Once a new PostgreSQL version is released, these meta-packages will be updated to depend on the new version._ Unfortunately once a new postgresql version is released, there is no longer a meta package for the previous version available in the official postgresql apt repository for postgresql-contribAnd then the install of the postgresql-contrib package will also pull in the latest version of postgresql as its dependency. In our case, we have configured the puppetdb module, to use postgresql 13class { 'puppetdb': postgres_version => "13",But on the server, we now have both postgresql 13 and 14 installed So in its core this is a package availability issue on the postgresql side and not a puppetdb issue. Created an issue for this here [https://redmine.postgresql.org/issues/7169] But perhaps the pg_trgm functionality can be dropped/replaced ?And that would drop the need for the postgresql-contrib packageAnd that avoids the entire dependency issue
Add Comment
Jira (PDB-5454) Is the pg_trgm postgresql extention from postgresql-contrib really needed ?
Title: Message Title
Koen Dierckx created an issue
PuppetDB / PDB-5454
Is the pg_trgm postgresql extention from postgresql-contrib really needed ?
Issue Type:
Bug
Assignee:
Unassigned
Components:
PuppetDB
Created:
2022/02/11 5:32 AM
Priority:
Normal
Reporter:
Koen Dierckx
Currently PuppetDB requires the pg_trgm extension from the postgresql-contrib package. The puppetdb module will install this extension with the class puppetdb::database::postgresql This extension is provided by a package and is installed by class postgresql::server::contrib The package is called postgresql-contrib (on Ubuntu ) https://wiki.postgresql.org/wiki/Apt Note: This repository provides "postgresql", "postgresql-contrib", and "postgresql-client" meta-packages that depend on the latest postgresql-x.y, ... packages, similar to the ones present in Debian and Ubuntu. Once a new PostgreSQL version is released, these meta-packages will be updated to depend on the new version. Unfortunately once a new postgresql version is released, there is no longer a meta package for the previous version available in the official postgresql apt repository for postgresql-contrib And then the install of the postgresql-contrib package will also pull in the latest version of postgresql as its dependency. In our case, we have configured the puppetdb module, to use postgresql 13 class { 'puppetdb': postgres_version => "13", But on the server, we now have both postgresql 13 and 14 installed So in its core this is a package availability issue on the postgresql side and not a puppetdb issue. But perhaps the pg_trgm functionality can be dropped/replaced ? And that would drop the need for the postgresql-contrib package And that avoids the entire dependency issue
Jira (PDB-4597) Puppetdb module issues notice every run for postgresql-contrib with postgres11 (on Debian Buster)
Title: Message Title Koen Dierckx commented on PDB-4597 Re: Puppetdb module issues notice every run for postgresql-contrib with postgres11 (on Debian Buster) We solved by setting the parameter through hiera postgresql::globals::contrib_package_name: postgresql-contrib But the correct solution is to fix the default package name inside the manifest code (we are running Ubuntu 20.04) 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.337962.1575554108000.121943.1630565340027%40Atlassian.JIRA.
Jira (FACT-769) Add ability to filter facts
Title: Message Title Koen Dierckx updated an issue Facter / FACT-769 Add ability to filter facts Change By: Koen Dierckx Affects Version/s: FACT 4.2.3 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.61937.1418924889000.121942.1630564920109%40Atlassian.JIRA.
Jira (FACT-769) Add ability to filter facts
Title: Message Title Koen Dierckx commented on FACT-769 Re: Add ability to filter facts Disabling the entire fact block is not an option, as our puppet code uses parts of that block. e.g. 1 the networking block contains information about our primary nics (ens192, eth0, ...), that are being used within our puppet manifests But as a docker host also that same block is filled with docker virtual nics like veth02b3fa9, veth06e56a9, br-2aa431d10302, br-38a3698b07e8 we do not care about e.g.2 We have the same issue with the mountpoints block, it contains the common mounts like / and /boot we use inside puppet but it is also polluted with docker mounts /run/docker/netns/... and /var/lib/docker/overlay2/... So a filtering system would solve this, so we could ignore entries we are not interested in e.g. 1 veth and br- for networking e.g. 2 /run/docker/netns and /var/lib/docker/overlay2 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.61937.1418924889000.121939.1630564620041%40Atlassian.JIRA.
