Jira (BOLT-1300) Update install docs to point to puppet-tools repo
Title: Message Title Garrett Guillotte commented on BOLT-1300 Re: Update install docs to point to puppet-tools repo For reference, KB #0357 is live at https://support.puppet.com/hc/en-us/articles/360034356933 and SUP-1282 is resolved. 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.308071.1557427938000.105320.1568852040560%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title
Thomas Kishel commented on PUP-10017
Re: Collapse dependency failures into Class level failures
For a more extreme example:
class rrr {
file { '/fail/file_in_rrr.txt':
content => 'hello',
}
}
class ddd {
require rrr
range(1,99).each |$n| {
file { "/tmp/file_${n}_in_ddd.txt":
content => 'hello',
}
}
}
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Thomas Kishel commented on PUP-10017 Re: Collapse dependency failures into Class level failures The above is implemented in the PR. 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.324379.1568220393000.105296.1568851260221%40Atlassian.JIRA.
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Austin Blatt commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs Yeah, that sounds like a reasonable change. 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.220461.1509743938000.105171.1568847060458%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-10017 Collapse dependency failures into Class level failures Change By: Thomas Kishel Attachment: without_coalesce.png 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.324379.1568220393000.105107.1568846401177%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-10017 Collapse dependency failures into Class level failures Change By: Thomas Kishel When a Class has a failed dependency, every individual resource in the class generates a notice level message about the dependency failure and a warning level message about skipping the resource, as well as a skip event in the report. This can generate a large number of messages and a large report if there are many dependencies, or multiple layers of dependencies. At large-node and/or large-code scale, one dependency failure can create an overwhelming number of warnings ... obscuring the root cause and increasing the use of system resources required to process and store the resulting reports. If possible, all of the skipped resources should be collapsed into the containing class and the messages and skip event should be done at the class level. It looks like the most recent work on this was done in PUP-3930 and commit 32e2bf2. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-10017 Collapse dependency failures into Class level failures Change By: Thomas Kishel Attachment: with_coalesce.png 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.324379.1568220393000.105112.1568846401199%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-10017 Collapse dependency failures into Class level failures Change By: Thomas Kishel Attachment: with_and_without_coalesce.png 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.324379.1568220393000.105102.1568846401155%40Atlassian.JIRA.
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Nick Walker commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs Can we just add a limit 2000 to the summary query? That should make it even more lightweight 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.220461.1509743938000.105062.1568845740540%40Atlassian.JIRA.
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Austin Blatt commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs Yes, we already batch the transfer in sets of 2,000, but we leave the summary query open and start the next set. My general plan is to end that query entirely after the first batch and start over. Unfortunately that'll mean we re-run the summary query every 2,000 items transferred, but those are fairly lightweight queries afaik (we should verify that during this work and optimize where necessary if that is not the case). 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.220461.1509743938000.104922.1568842020334%40Atlassian.JIRA.
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Nick Walker commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs It seems like when we're looking for commands to sync we should do a select columns from table LIMIT and then sync those commands and commit the change and keep looping until we don't have sync work left to do. That way we commit changes in small batches and don't leave a long running transaction. Austin Blatt is that reasonable? 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.220461.1509743938000.104837.1568840820617%40Atlassian.JIRA.
Jira (PDB-4509) Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Austin Blatt commented on PDB-4509 Re: Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8" Scot Kreienkamp it seems like this is not the first time someone has hit it, and this Puppet Users thread has the same error that your encountered, but alas, no resolution. But we can start off where they were. Can you attach the output of psql -c '\l+'? 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.325166.1568831083000.104771.1568840040458%40Atlassian.JIRA.
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Charlie Sharpsteen commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs Since the description is fairly technical, a higher level overview is: The primary and replica become de-synced and copying the data required to sync back up will take several hours. After a couple hours, the DB queries that are running for sync start to severely impact the performance of the database that is providing the data. At this point, the PE administrator has to start periodically interrupting the connection between the two PuppetDB instances in order to force the sync to avoid queries that run long enough to avoid a performance impact. 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.220461.1509743938000.104646.1568839140430%40Atlassian.JIRA.
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Yasmin Rajabi commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs Rob Browning when we last chatted you mentioned this was on the backlog, do you have an idea where it sits? 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.220461.1509743938000.104609.1568838721340%40Atlassian.JIRA.
Jira (PDB-4509) Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Scot Kreienkamp commented on PDB-4509 Re: Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8" Manual steps ran: createuser -DRSP puppetdb createdb -E UTF8 -O puppetdb puppetdb psql puppetdb -c 'create extension pg_trgm' As a troubleshooting step I configured puppetdb to connect using the postgres user. No change. 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.325166.1568831083000.104393.1568832000444%40Atlassian.JIRA.
Jira (PDB-4509) Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4509 Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8" Change By: Austin Blatt Team: PuppetDB Summary: Puppetdb 6.5, PG9.6.15, fresh Fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8" Method Found: Needs Assessment Customer Feedback 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
Jira (PUP-10024) Make environment caching thread safe
Title: Message Title Patrick Carlisle moved an issue Puppet / PUP-10024 Make environment caching thread safe Change By: Patrick Carlisle Key: SERVER PUP - 2617 10024 Project: Puppet Server 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.323043.1567196846000.104386.1568831940681%40Atlassian.JIRA.
Jira (PDB-4509) Puppetdb 6.5, PG9.6.15, fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Austin Blatt commented on PDB-4509 Re: Puppetdb 6.5, PG9.6.15, fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8" Robert Roland Can you take a look at this error? It's in the same realm as your md5 to sha1 migration change, so I want to check if you know what would cause this error off the top of your head. 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.325166.1568831083000.104378.1568831880450%40Atlassian.JIRA.
Jira (PUP-9933) Make indirector settings thread-local
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9933 Make indirector settings thread-local Change By: Maggie Dreyer Release Notes: Not Needed 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.306744.1556579701000.104373.1568831700373%40Atlassian.JIRA.
Jira (PDB-4468) Partitioning of resource_events: Migration test for initial creation of partitions
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4468 Partitioning of resource_events: Migration test for initial creation of partitions Change By: Zachary Kent Fix Version/s: PDB 6.7.0 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.319330.1564695363000.104360.1568831520506%40Atlassian.JIRA.
Jira (PDB-4467) Partitioning of resource_events: Migrate existing events to partitioned tables
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4467 Partitioning of resource_events: Migrate existing events to partitioned tables Change By: Zachary Kent Fix Version/s: PDB 6.7.0 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.319329.1564695312000.104348.1568831400482%40Atlassian.JIRA.
Jira (PDB-4509) Puppetdb 6.5, PG9.6.15, fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Scot Kreienkamp updated an issue PuppetDB / PDB-4509 Puppetdb 6.5, PG9.6.15, fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8" Change By: Scot Kreienkamp Attachment: puppetdb.log 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.325166.1568831083000.104336.1568831280324%40Atlassian.JIRA.
Jira (PDB-4466) Partitioning of resource_events: GC by dropping expired partitions
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4466 Partitioning of resource_events: GC by dropping expired partitions Change By: Zachary Kent Fix Version/s: PDB 6.7.0 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.319328.1564695244000.104332.1568831220242%40Atlassian.JIRA.
Jira (PDB-4420) SPIKE: Partitioning of tables
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4420 SPIKE: Partitioning of tables Change By: Zachary Kent Fix Version/s: PDB 6.7.0 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.313028.1560891829000.104323.1568831160664%40Atlassian.JIRA.
Jira (PDB-4509) Puppetdb 6.5, PG9.6.15, fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Scot Kreienkamp created an issue PuppetDB / PDB-4509 Puppetdb 6.5, PG9.6.15, fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8" Issue Type: Bug Affects Versions: PDB 6.5.0 Assignee: Unassigned Components: PuppetDB Created: 2019/09/18 11:24 AM Environment: RHEL7.7, PG9.6.15, puppet-agent-6.8.1, puppetdb-6.5.0 puppetdb=# select extname from pg_extension; extname - plpgsql pg_trgm Locale: LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= Priority: Normal Reporter: Scot Kreienkamp On first start of puppetdb after install it is failing with error: 2019-09-18T13:31:10.415-04:00 INFO [p.p.s.migrate] Applying database migration version 43 2019-09-18T13:31:10.456-04:00 ERROR [p.p.s.migrate] Caught SQLException during migration java.sql.BatchUpdateException: Batch entry 1 CREATE AGGREGATE sha1_agg (BYTEA) ( sfunc = dual_sha1, stype = bytea, initcond = '\x00' ) was aborted: ERROR: invalid byte sequence for encoding "UTF8": 0x00 Call getNextException to see other errors in the batch.
Jira (PDB-4456) Add support for import/export for "replace catalog inputs"
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4456 Add support for import/export for "replace catalog inputs" Change By: Zachary Kent Fix Version/s: PDB 6.7.0 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.317966.1563991828000.104285.1568830680281%40Atlassian.JIRA.
Jira (PUP-9933) Make indirector settings thread-local
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9933 Make indirector settings thread-local Change By: Maggie Dreyer Fix Version/s: SERVER 6.6.1 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.306744.1556579701000.104277.1568830620701%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title
Andreas Ntaflos commented on PUP-10016
Re: Systemd provider is not correctly selected as the service provider if puppet is run as non root
Gheorghe Popescu Thank you for creating a ticket for this! Since commenting in https://tickets.puppetlabs.com/browse/PUP-7312 I have not been able to reliably reproduce the issue I was having using Vagrant. I have created a minimal Puppet module for this at https://github.com/antaflos/puppet-foobar. On our in-house built Ubuntu 18.04 Vagrant boxes the spec tests would reliably fail with the aforementioned error message, but on the official ubuntu/bionic64 boxes (https://app.vagrantup.com/ubuntu/boxes/bionic64) the spec tests would reliably pass. I have no idea why and still cannot figure it out. Drives me crazy I am glad this issue got attention and a fix so quickly! Thanks to all involved! Not that it matters much now, and just out of curiosity: couldn't Puppet also just look at /sbin/init, much like it looked at /proc/1/exe and read the symlink target? This works for regular users, not just root. As in:
confine :true => Puppet::FileSystem.exist?('/sbin/init') && Puppet::FileSystem.readlink('/sbin/init').include?('systemd')
Maybe in addition to looking at /proc/1/exe, i.e.:
confine :true => (Puppet::FileSystem.exist?('/proc/1/exe') && Puppet::FileSystem.readlink('/proc/1/exe').include?('systemd')) ||
(Puppet::FileSystem.exist?('/sbin/init') && Puppet::FileSystem.readlink('/sbin/init').include?('systemd'))
Add Comment
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title Patrick Grant commented on PUP-9996 Re: Stdlib : ensure_resources function does not throw an error if dependent resource type is missing Thanks Jarret, finally got another chance at a replication today and restarting the puppetserver solves this particular issue. As soon as I did, the correct error was presented, I will close the ticket. 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.323404.1567607979000.103925.1568825700434%40Atlassian.JIRA.
Jira (PDB-4508) puppetdb-termini for puppet standalone try to connect to master
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4508 puppetdb-termini for puppet standalone try to connect to master Change By: Josh Cooper Fix Version/s: PDB 6.6.0 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.285263.1542291964000.103666.1568818741116%40Atlassian.JIRA.
Jira (PDB-4508) puppetdb-termini for puppet standalone try to connect to master
Title: Message Title Josh Cooper moved an issue PuppetDB / PDB-4508 puppetdb-termini for puppet standalone try to connect to master Change By: Josh Cooper Affects Version/s: PUP 6.0.4 Key: PUP PDB - 9314 4508 Project: Puppet PuppetDB 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.285263.1542291964000.103654.1568818741064%40Atlassian.JIRA.
Jira (FACT-2018) Google Compute Engine metadata facts need endpoint change
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-2018 Google Compute Engine metadata facts need endpoint change Change By: Gabriel Nagy Assignee: Gabriel Nagy 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.324465.156829223.103638.1568817000469%40Atlassian.JIRA.
Jira (FACT-2028) Networking facts for Windows
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2028 Networking facts for Windows Issue Type: Task Assignee: Oana Tanasoiu Created: 2019/09/18 7:27 AM Priority: Normal Reporter: Oana Tanasoiu 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
Jira (PUP-9314) puppetdb-termini for puppet standalone try to connect to master
Title: Message Title Louis Coilliot commented on PUP-9314 Re: puppetdb-termini for puppet standalone try to connect to master Hello, I struggled with the same problem. I don't know exactly when it has been fixed, but it works for me now. puppet-agent-6.9.0 puppetdb-termini-6.6.0 Also I needed some additional parameters to make it work, in the configuration, in puppetdb.conf and puppet.conf. This is detailed in the comments (2019/09/18) of the ticket PDB-4487 (https://tickets.puppetlabs.com/browse/PDB-4487) 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.285263.1542291964000.103625.1568816160246%40Atlassian.JIRA.
Jira (PUP-10023) Expand the apt provider to support virtual packages
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10023 Expand the apt provider to support virtual packages Change By: Mihai Buzgau Sprint: NW - 2019-09-18 , NW - 2019-10-02 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.324926.1568705952000.103616.1568815983790%40Atlassian.JIRA.
Jira (PUP-9465) group resource type misunderstands/misuses libuser
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9465 group resource type misunderstands/misuses libuser Change By: Mihai Buzgau Sprint: NW - 2019-08-21, NW - 2019-09-03, NW - 2019-09-18 , NW - 2019-10-02 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.293306.1548368109000.103591.1568815983676%40Atlassian.JIRA.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Mihai Buzgau Sprint: NW - 2019-08-07, NW - 2019-08-21, NW - 2019-09-03, NW - 2019-09-18 , NW - 2019-10-02 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.267945.153332494.103579.1568815983508%40Atlassian.JIRA.
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9719 Cannot run Puppet Agent as Administrator if first PA run is done as System Change By: Mihai Buzgau Sprint: PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23, NW - 2019-08-07, NW - 2019-08-21, NW - 2019-09-03, NW - 2019-09-18 , NW - 2019-10-02 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.310162.1558726819000.103571.1568815983471%40Atlassian.JIRA.
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-6382 Add "Automatic (delayed start)" as option for Service Resource on Windows Change By: Mihai Buzgau Story Points: 3 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.135151.1464896598000.103551.1568815204239%40Atlassian.JIRA.
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-6382 Add "Automatic (delayed start)" as option for Service Resource on Windows Change By: Mihai Buzgau Sprint: NW - 2019-10-02 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.135151.1464896598000.103540.1568815203548%40Atlassian.JIRA.
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-6382 Add "Automatic (delayed start)" as option for Service Resource on Windows Change By: Mihai Buzgau Team: Platform OS Night's Watch 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.135151.1464896598000.103529.1568815203368%40Atlassian.JIRA.
Jira (PUP-9314) puppetdb-termini for puppet standalone try to connect to master
Title: Message Title Craig Watson commented on PUP-9314 Re: puppetdb-termini for puppet standalone try to connect to master This is fixed by PDB-4487 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.285263.1542291964000.103518.1568815140247%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is overridden by http_proxy environment variable
Title: Message Title Dhumala commented on PUP-9990 Re: no_proxy config setting is overridden by http_proxy environment variable Its not yet solved 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.322755.1567086003000.103436.1568809560633%40Atlassian.JIRA.
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Louis Coilliot commented on PDB-4487 Re: PuppetDB Terminus with Masterless Fails on SSL Errors I confirm this solution is correct. All warnings and errors have disappeared and I can now set the `cache: puppetdb_apply` for facts in routes.yaml. The puppetdb SSL proxy certificate must be signed by a CA trusted in /etc/pki/tls/certs/ca-bundle.crt, so for a custom private SSL certificate and CA you need to update the trusted CA list (see : update-ca-trust on CentOS, update-ca-certificates on Debian). Or set an other target for the localcacert parameter. I agree that it should be mentioned in the doc here : https://puppet.com/docs/puppetdb/6.6/connect_puppet_apply.html#option-a-set-up-an-ssl-proxy-for-puppetdb Thanks a lot for your understanding and reactivity. 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.321961.1566490124000.103408.1568806140256%40Atlassian.JIRA.
Jira (PUP-9471) User management fails on MacOS 10.14 (Mojave)
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9471 User management fails on MacOS 10.14 (Mojave) Change By: Gheorghe Popescu Sprint: PR - Triage, PR - 2019-03-06 , NW - 2019-10-02 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.294488.1549047148000.103235.1568794860803%40Atlassian.JIRA.
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Craig Watson commented on PDB-4487 Re: PuppetDB Terminus with Masterless Fails on SSL Errors Louis Coilliot Can you add this to `puppetb.conf` and retry? ``` verify_client_certificate = false ``` 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.321961.1566490124000.103217.1568794800444%40Atlassian.JIRA.
Jira (FACT-2004) cloud fact does not detect Azure with NetworkManager
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2004 cloud fact does not detect Azure with NetworkManager Change By: Gheorghe Popescu Story Points: 3 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.322752.1567082147000.103204.1568794500715%40Atlassian.JIRA.
Jira (PUP-9978) dnf package provider should support modularity streams
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9978 dnf package provider should support modularity streams Change By: Gheorghe Popescu Story Points: 8 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.322208.1566835009000.103197.1568794140701%40Atlassian.JIRA.
Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-
Puppet::Type.type('yumrepo') wrongly reports enabled repo
Change By:
Gheorghe Popescu
Story Points:
1
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.323658.1567695504000.103176.1568793540182%40Atlassian.JIRA.
Jira (FACT-2016) Add the scope of found ipv6 addresses (global/linklocal/...) as a fact
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2016 Add the scope of found ipv6 addresses (global/linklocal/...) as a fact Change By: Gheorghe Popescu Story Points: 5 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.324361.1568209514000.103170.1568793000169%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10017 Collapse dependency failures into Class level failures Change By: Gheorghe Popescu Story Points: 3 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.324379.1568220393000.103160.1568792640384%40Atlassian.JIRA.
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Louis Coilliot commented on PDB-4487 Re: PuppetDB Terminus with Masterless Fails on SSL Errors Hello, I've tested with puppetdb-termini-6.6.0-1.el7.noarch released yesterday and it's not better. With puppetdb-termini-6.6.0 : ``` /opt/puppetlabs/puppet/bin/puppet apply --modulepath=/deploy/environments/dev/modules -e 'include base' Error: Failed to initialize SSL: The CA certificates are missing from '/etc/puppetlabs/puppet/ssl/certs/ca.pem' Error: Run `puppet agent -t` Error: Cached facts for centos7-sandbox-acl.c.int-lz1-dtp.internal failed: Failed to find facts from PuppetDB at puppet:8140: The CA certificates are missing from '/etc/puppetlabs/puppet/ssl/certs/ca.pem' Error: Failed to initialize SSL: The CA certificates are missing from '/etc/puppetlabs/puppet/ssl/certs/ca.pem' Error: Run `puppet agent -t` Error: The CA certificates are missing from '/etc/puppetlabs/puppet/ssl/certs/ca.pem' Error: Could not run: Could not retrieve facts for centos7-sandbox-acl.c.int-lz1-dtp.internal: The CA certificates are missing from '/etc/puppetlabs/puppet/ssl/certs/ca.pem' Wrapped exception: The CA certificates are missing from '/etc/puppetlabs/puppet/ssl/certs/ca.pem ``` With puppetdb-termini-6.4.0 (after 2 `yum downgrade puppetdb-termini`) : ``` /opt/puppetlabs/puppet/bin/puppet apply --modulepath=/deploy/environments/dev/modules -e 'include base' Warning: Puppet::SSL::Host is deprecated and will be removed in a future release of Puppet. (location: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/host.rb:235:in `initialize') Error: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known) Error: Cached facts for centos7-sandbox-acl.c.int-lz1-dtp.internal failed: Failed to find facts from PuppetDB at puppet:8140: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known) Notice: Compiled catalog for centos7-sandbox-acl.c.int-lz1-dtp.internal in environment dev in 0.30 seconds Notice: Applied catalog in 1.60 seconds ``` The apply is OK although I still have a non blocking error related (I guess) to another issue (https://tickets.puppetlabs.com/browse/PUP-9314 : puppetdb-termini for puppet standalone try to connect to master) Add Comment
Jira (FACT-2018) Google Compute Engine metadata facts need endpoint change
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2018 Google Compute Engine metadata facts need endpoint change Change By: Gheorghe Popescu Story Points: 2 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.324465.156829223.103143.1568792220208%40Atlassian.JIRA.
