Jira (PUP-10928) Puppet falls back to non-rich data if there is binary data in the catalog
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10928 Puppet falls back to non-rich data if there is binary data in the catalog Change By: Josh Cooper Team: Night's Watch Phoenix 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.388074.1613713885000.14780.1644612120031%40Atlassian.JIRA.
Jira (PUP-11347) `puppet parser validate` ignores plans
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11347 `puppet parser validate` ignores plans Change By: Josh Cooper Team: Phoenix 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.423063.163654689.14769.1644611220032%40Atlassian.JIRA.
Jira (PUP-9578) Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9578 Remove distinction between `puppet parser validate` and `puppet parser validate --tasks` Change By: Josh Cooper Team: Froyo Phoenix 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.301178.155320275.14768.1644611160157%40Atlassian.JIRA.
Jira (PDB-4549) Document case-insensitive regular expressions
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4549 Document case-insensitive regular expressions Change By: Rob Browning Assignee: Rob Browning 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.326619.1569433817000.14610.1644605940032%40Atlassian.JIRA.
Jira (PDB-4650) Issues w/ HA page in PDB docs
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4650 Issues w/ HA page in PDB docs Change By: Rob Browning Assignee: Rob Browning 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.345425.1581032171000.14597.1644605040039%40Atlassian.JIRA.
Jira (PDB-5067) (Docs) Reference the correct "Enable Puppet Package Repo" task link
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5067 (Docs) Reference the correct "Enable Puppet Package Repo" task link Change By: Rob Browning Assignee: Rob Browning 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.390928.1615575187000.14584.1644603660051%40Atlassian.JIRA.
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 Comm
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 (FACT-3091) Facter is missing the sys-filesystems gem
Title: Message Title Tim Meusel commented on FACT-3091 Re: Facter is missing the sys-filesystems gem This came up on IRC again. We found https://tickets.puppetlabs.com/browse/FACT-3106. Due to this the factsets in facterdb are inconsistent. Because you don't pull in all the depencencies/not even document it. Can you please fix this? 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.422725.1636446253000.14389.1644582600029%40Atlassian.JIRA.
Jira (FACT-3106) No virt-what in puppet-agent 7 so is_virtual is wrong
Title: Message Title Tim Meusel updated an issue Facter / FACT-3106 No virt-what in puppet-agent 7 so is_virtual is wrong Change By: Tim Meusel In factor facter the is_virtual and other similar facts are very dependent upon thevirt-whatcommand being available. Since this commit to puppet-agent[https://github.com/puppetlabs/puppet-agent/commit/a1a06ba3f42419e]virt-what was removed from the puppet-agent package.I expect it may have been an unintentional consequence to stop these core facts from working out of the box with the puppet-agent package?Installing the system provided virt-what and everything works again but this should be a dep or at least documented if that is the way forward. For reference some history on the subject.https://tickets.puppetlabs.com/browse/FACT-822 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 fr
Jira (FACT-3106) No virt-what in puppet-agent 7 so is_virtual is wrong
Title: Message Title Steve Traylen updated an issue Facter / FACT-3106 No virt-what in puppet-agent 7 so is_virtual is wrong Change By: Steve Traylen In factor the is_virtual and other similar facts is are very dependent upon thevirt-whatcommand being availabe available . Since this commit to puppet-agent[https://github.com/puppetlabs/puppet-agent/commit/a1a06ba3f42419e]virt-what was removed from the puppet-agent package.I expect it may have been an unintentional consequence to stop these core facts from working out of the box with the puppet-agent package?Installing the system provide provided virt-what and everything works again but this should be a dep or at least documented if that is the way forward. For reference some history on the subject.https://tickets.puppetlabs.com/browse/FACT-822 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
Jira (FACT-3106) No virt-what in puppet-agent 7 so is_virtual is wrong
Title: Message Title Steve Traylen created an issue Facter / FACT-3106 No virt-what in puppet-agent 7 so is_virtual is wrong Issue Type: Improvement Affects Versions: FACT 4.2.7 Assignee: Unassigned Components: Facter 4 Created: 2022/02/11 4:23 AM Environment: puppet-agent 7 facter 4 Priority: Normal Reporter: Steve Traylen In factor the is_virtual and other similar facts is very dependent upon the virt-what command being availabe. Since this commit to puppet-agent https://github.com/puppetlabs/puppet-agent/commit/a1a06ba3f42419e virt-what was removed from the puppet-agent package. I expect it may have been an unintentional consequence to stop these core facts from working out of the box with the puppet-agent package? Installing the system provide virt-what and everything works again but this should be a dep or at least documented if that is the way forward. For reference some history on the subject. https://tickets.puppetlabs.com/browse/FACT-822
Jira (HI-627) Update CI matrix to verify it works on ruby 2.7/3
Title: Message Title Tim Meusel commented on HI-627 Re: Update CI matrix to verify it works on ruby 2.7/3 Now that Ruby 3.1 is out, it would be quite helpful to have that as well. 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.410076.1628192723000.14183.1644570540025%40Atlassian.JIRA.
Jira (PUP-11347) `puppet parser validate` ignores plans
Title: Message Title Tim Meusel commented on PUP-11347 Re: `puppet parser validate` ignores plans > In other words, you could pass either --tasks or --plans, but we'd prefer and document --plans (similar to what we do for serverport & masterport). I agree with you. I think that's a good way. > Please file a PDK ticket for that. https://tickets.puppetlabs.com/browse/PDK-1774 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.423063.163654689.14181.1644570180051%40Atlassian.JIRA.
Jira (PUP-9578) Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`
Title: Message Title Tim Meusel commented on PUP-9578 Re: Remove distinction between `puppet parser validate` and `puppet parser validate --tasks` Ping I noticed this a few times during trainings and I think fixing this would lower the entrybar for newcomers. 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.301178.155320275.14176.1644568680036%40Atlassian.JIRA.
