Jira (FACT-2952) Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-2952 Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3 Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389552.161471215.157174.1614844560103%40Atlassian.JIRA.
Jira (PDB-5054) Speed up the currently slow aggregate-event-counts query
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5054 Speed up the currently slow aggregate-event-counts query Issue Type: Improvement Assignee: Austin Blatt Attachments: agg-count-query.explain, agg-count-query.sql Created: 2021/03/03 4:04 PM Priority: Normal Reporter: Austin Blatt The aggregate-event-counts query is quite slow when there are lots of resource events, which can happen by mistakenly creating a recursive file resource. The slow query then breaks the Events page of the console, where a user would go to diagnose those kinds of issues. The query and explain analyze have been loaded into https://explain.depesz.com/s/IWFD but they are also attached in files for longevity. Add Comment
Jira (PDB-5053) Move sync expired resource_event filter to report ingest
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5053 Move sync expired resource_event filter to report ingest Change By: Zachary Kent Labels: tsr-pdb-backlog Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389887.1614814159000.156929.1614814860125%40Atlassian.JIRA.
Jira (PDB-5053) Move sync expired resource_event filter to report ingest
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5053 Move sync expired resource_event filter to report ingest Change By: Zachary Kent pdbext sync has a filter in the [:clean-up-record-fn|https://github.com/puppetlabs/pe-puppetdb-extensions/blob/6.x/src/puppetlabs/pe_puppetdb_extensions/sync/core.clj#L173-L179] for reports which removes any *resource_events* which would be expired locally. This filter was added to account for differing ttls between *reports* and *resource_events*. We wanted to avoid a situation where GC would clean up a *resource_event* partition and then sync would pull a report with *resource_events* that recreated the deleted partition. As a result if an *event* is pulled out of a *resource* in a *report* we could have reports which don't exactly match between two pdbs syncing with one another. This problem could become more pronounced when we add the ability to disable *resource_event* storage in PDB-3653. If the *resource-event-ttl* is set to 0 the sync filter will strip out all * resource resource_events * *events* in the reports it transfers. It would be better if the check for expired *resource_events* was moved into the *report* ingestion code. That way sync would keep the report identical on both sides. To do this we would need to remove the filter in the [:clean-up-record-fn|https://github.com/puppetlabs/pe-puppetdb-extensions/blob/6.x/src/puppetlabs/pe_puppetdb_extensions/sync/core.clj#L173-L179] for reports and adjust at least the [dont-pull-events-that-would-be-expired-locally|https://github.com/puppetlabs/pe-puppetdb-extensions/blob/6.x/test/puppetlabs/pe_puppetdb_extensions/sync/end_to_end_test.clj#L939] test to check that the *resource-events* partitions aren't created not that the events don't exist in the report body. On the FOSS side we'll want to add a check based on the *resource-event-ttl* in the *scf/storage.clj/add-report!\** function in the section where [resource_events|https://github.com/puppetlabs/puppetdb/blob/6.x/src/puppetlabs/puppetdb/scf/storage.clj#L1415] are stored. If we add a filter there which discards any *resource_events* which would be expired based on their *timestamp* that should allow us to avoid the issue of sync creating expired partitions and allow us to keep reports the same on both sides of sync.
Jira (PDB-5053) Move sync expired resource_event filter to report ingest
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5053 Move sync expired resource_event filter to report ingest Change By: Zachary Kent pdbext sync has a filter in the [:clean-up-record-fn|https://github.com/puppetlabs/pe-puppetdb-extensions/blob/6.x/src/puppetlabs/pe_puppetdb_extensions/sync/core.clj#L173-L179] for reports which removes any *resource_events* which would be expired locally. This filter was added to account for differing ttls between *reports* and *resource_events*. We wanted to avoid a situation where GC would clean up a *resource_event* partition and then sync would pull a report with *resource_events* that recreated the deleted partition. As a result if an *event* is pulled out of a *resource* in a *report* we could have reports which don't exactly match between two pdbs syncing with one another. This problem could become more pronounced when we add the ability to disable *resource_event* storage in PDB-3653. If the *resource-event-ttl* is set to 0 the sync filter will strip out all * resource_events resource * *events* in the reports it transfers. It would be better if the check for expired *resource_events* was moved into the *report* ingestion code. That way sync would keep the report identical on both sides. To do this we would need to remove the filter in the [:clean-up-record-fn|https://github.com/puppetlabs/pe-puppetdb-extensions/blob/6.x/src/puppetlabs/pe_puppetdb_extensions/sync/core.clj#L173-L179] for reports and adjust at least the [dont-pull-events-that-would-be-expired-locally|https://github.com/puppetlabs/pe-puppetdb-extensions/blob/6.x/test/puppetlabs/pe_puppetdb_extensions/sync/end_to_end_test.clj#L939] test to check that the *resource-events* partitions aren't created not that the events don't exist in the report body. On the FOSS side we'll want to add a check based on the *resource-event-ttl* in the *scf/storage.clj/add-report!\** function in the section where [resource_events|https://github.com/puppetlabs/puppetdb/blob/6.x/src/puppetlabs/puppetdb/scf/storage.clj#L1415] are stored. If we add a filter there which discards any *resource_events* which would be expired based on their *timestamp* that should allow us to avoid the issue of sync creating expired partitions and allow us to keep reports the same on both sides of sync.
Jira (PDB-5053) Move sync expired resource_event filter to report ingest
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-5053 Move sync expired resource_event filter to report ingest Issue Type: Bug Assignee: Unassigned Created: 2021/03/03 3:29 PM Priority: Normal Reporter: Zachary Kent pdbext sync has a filter in the :clean-up-record-fn for reports which removes any resource_events which would be expired locally. This filter was added to account for differing ttls between reports and resource_events. We wanted to avoid a situation where GC would clean up a resource_event partition and then sync would pull a report with resource_events that recreated the deleted partition. As a result if an event is pulled out of a resource in a report we could have reports which don't exactly match between two pdbs syncing with one another. This problem could become more pronounced when we add the ability to disable resource_event storage in PDB-3653. If the resource-event-ttl is set to 0 the sync filter will strip out all resource_events in the reports it transfers. It would be better if the check for expired resource_events was moved into the report ingestion code. That way sync would keep the report identical on both sides. To do this we would need to remove the filter in the :clean-up-record-fn for reports and adjust at least the dont-pull-events-that-would-be-expired-locally test to check that the resource-events partitions aren't created not that the events don't exist in the report body. On the FOSS side we'll want to add a check based on the resource-event-ttl in the scf/storage.clj/add-report!* function in the section where resource_events are stored. If we add a filter there which discards any resource_events which would be expired based on their timestamp that should allow us to avoid the issue of sync creating expired partitions and allow us to keep reports the same on both sides of sync.
Jira (FACT-2134) Facter should distinguish between CentOS 8 and CentOS 8 Stream
Title: Message Title Peter Meier commented on FACT-2134 Re: Facter should distinguish between CentOS 8 and CentOS 8 Stream Sorry for cross-posting that from the github issue (https://github.com/puppetlabs/facter/pull/2291#issuecomment-790039719), BUT this is (from my point of view) in the way it got merged now heavily breaking tons of puppet modules out there. I would consider to release that change only with a major facter release (and thus major puppet version). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.336204.1574351826000.156727.1614804420032%40Atlassian.JIRA.
Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts
Title: Message Title Josh Cooper created an issue Facter / FACT-2956 Facter should ensure core facts are resolved before loading custom facts Issue Type: Bug Assignee: Unassigned Created: 2021/03/03 11:21 AM Priority: Normal Reporter: Josh Cooper Facter 4 calls Kernel.load on all custom ruby facts before core facts have been resolved. If the custom ruby facts has code outside a setcode block, then it's possible for core facts like Facter.value(:operatingsystem) to return nil, like FACT-2880. It is true that custom facts shouldn't misbehave that way, but a single misbehaving custom fact can prevent PE from managing itself. We also don't have tooling/validation to warn or prevent users from doing this, so there are many examples of it in practice. We should be more defensive about this. One way would be to ensure core facts are resolved before custom facts are loaded. It would still be possible for a custom fact with a higher weight to override the core fact, but at least the core fact would never have a nil value. Facter 3 didn't have this issue because core facts were implemented in C++ and evaluated before loading custom ruby facts. Add Comment
Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title Josh Cooper commented on FACT-2937 Re: 'puppet facts show' logs error when stdlib is installed Makes sense, thanks! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.386159.1612446678000.156228.1614789840036%40Atlassian.JIRA.
Jira (FACT-2955) AIX - mismatched processor frequencies found; facter will only report one of them
Title: Message Title Lionel Widmer created an issue Facter / FACT-2955 AIX - mismatched processor frequencies found; facter will only report one of them Issue Type: Bug Affects Versions: FACT 3.y Assignee: Unassigned Components: PE Created: 2021/03/03 8:19 AM Priority: Normal Reporter: Lionel Widmer On some AIX LPARS we get the following warnings when running facter (also when Puppet is resolving facts): 2021-03-03 17:09:43.233892 WARN puppetlabs.facter - mismatched processor frequencies found; facter will only report one of them 2021-03-03 17:09:43.237845 WARN puppetlabs.facter - mismatched processor frequencies found; facter will only report one of them This warning is due to the fact, after a hardware migration, the old processor entries are still present in the AIX ODM database. From this output, you can see all processor resources. Only the Active ones are in used, the Defined ones are the old ones: lsdev -Cc processor proc0 Available 00-00 Processor proc2 Defined 00-02 Processor proc4 Defined 00-04 Processor proc8 Available 00-08 Processor As you can see from the following output, processor frequencies between the Defined (old hardware) procs and Available (current hardware procs) are different, and this is expected: lsattr -El proc0 frequency 372400 Processor Speed False smt_enabled true Processor SMT enabled False smt_threads 8 Processor SMT threads False state enable Processor state False type PowerPC_POWER8 Processor type False lsattr -El proc2 frequency 470400 Processor Speed False smt_enabled true Processor SMT enabled False smt_threads 2 Processor SMT threads False state enable Processor state False type PowerPC_POWER6 Processor type False lsattr -El proc4 frequency 310800 Processor Speed False smt_enabled true Processor SMT enabled False
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: Jarret Lavallee CS Rank: 7580 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156160.1614788100300%40Atlassian.JIRA.
Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title Kevin Reeuwijk updated an issue Facter / FACT-2937 'puppet facts show' logs error when stdlib is installed Change By: Kevin Reeuwijk Comment: This breaks PE 2021.0.0 for me, I can't use the product at all in this state. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.386159.1612446678000.156120.1614786900131%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: Jarret Lavallee CS Priority: Needs Priority Major Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156093.1614785760083%40Atlassian.JIRA.
Jira (FACT-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-1847 Implement "cloud" fact Azure identification for Windows platform Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.247441.1524674206000.156076.1614784920030%40Atlassian.JIRA.
Jira (FACT-2943) Fix os.name detection of AlmaLinux
Title: Message Title Christoph Schug commented on FACT-2943 Re: Fix os.name detection of AlmaLinux Mihai Buzgau, no, I don't mind, it's appreciated Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.387803.1613568551000.156057.1614784020023%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: zendesk.jira Zendesk Ticket Count: 8 9 Zendesk Ticket IDs: 35285, 35946,36746,36888,37704,39044,40977,41896,41998 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156051.1614783480027%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: zendesk.jira Zendesk Ticket Count: 7 8 Zendesk Ticket IDs: 35946, 36746,36888,37704,39044,40977,41896,41998 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156050.1614782940031%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: zendesk.jira Zendesk Ticket Count: 6 7 Zendesk Ticket IDs: 36746, 36888, 37704,39044,40977,41896,41998 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156049.1614782880026%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: zendesk.jira Zendesk Ticket Count: 5 6 Zendesk Ticket IDs: 36746, 37704,39044,40977,41896,41998 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156048.1614782820080%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: zendesk.jira Zendesk Ticket Count: 4 5 Zendesk Ticket IDs: 37704, 39044,40977,41896,41998 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156046.1614782760026%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: zendesk.jira Zendesk Ticket Count: 3 4 Zendesk Ticket IDs: 39044, 40977,41896,41998 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156045.1614782700045%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: zendesk.jira Zendesk Ticket Count: 2 3 Zendesk Ticket IDs: 40977, 41896,41998 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156044.1614782640026%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: zendesk.jira Zendesk Ticket Count: 1 2 Zendesk Ticket IDs: 41896, 41998 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156043.1614782580174%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: zendesk.jira Zendesk Ticket Count: 1 Zendesk Ticket IDs: 41998 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389668.1614728039000.156039.1614782520043%40Atlassian.JIRA.
Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title Kevin Reeuwijk commented on FACT-2937 Re: 'puppet facts show' logs error when stdlib is installed This breaks PE 2021.0.0 for me, I can't use the product at all in this state. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.386159.1612446678000.156020.1614779400026%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Vadym Chepkov commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails Something occurred to me. Is it possible the problem is on 'presentation' side and not on functionality? I looked through puppetserver.log on the replica and I do see nodes connecting to it during primary shutdown: 2021-03-03T07:27:53.295-05:00 INFO [qtp1835431929-14632] [puppetserver] Puppet Not using expired facts for pubtstx-web104.example.com from cache; expired at 2020-09-01 11:55:17 -0400 2021-03-03T07:27:53.356-05:00 INFO [qtp1835431929-14632] [puppetserver] Puppet Caching facts for pubtstx-web104.example.com 2021-03-03T07:27:55.563-05:00 ERROR [clojure-agent-send-off-pool-13553] [p.e.file-sync-errors] File Sync failure during sync or fetch phase: Couldn't connect to server (https://infdevx-puppet202.example.com:8140/file-sync/v1/latest-commits): (Connection refused). So, maybe the problem is with how agent handles the exception? Ideally, agent shouldn't through an error in the log and into submitted report if it was able to recover? At the end the problem manifests itself with splunk and report processor sounding false alerts Add Comment
Jira (PUP-10943) Windows package provider continues to read DisplayVersion key after embedded NULL
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10943 Windows package provider continues to read DisplayVersion key after embedded NULL Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.388985.1614292739000.156008.1614777840283%40Atlassian.JIRA.
Jira (FACT-2952) Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-2952 Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3 Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389552.161471215.156006.1614777840194%40Atlassian.JIRA.
Jira (FACT-2952) Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3
Title: Message Title Dorin Pleava assigned an issue to Unassigned Facter / FACT-2952 Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3 Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389552.161471215.156007.1614777840239%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Vadym Chepkov updated an issue Puppet / PUP-10844 Agent failures with server_list when one puppetserver fails Change By: Vadym Chepkov Attachment: puppet-agents.txt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.381638.1608653215000.155988.1614775560074%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Vadym Chepkov updated an issue Puppet / PUP-10844 Agent failures with server_list when one puppetserver fails Change By: Vadym Chepkov Attachment: puppet.txt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.381638.1608653215000.155989.1614775560124%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Vadym Chepkov updated an issue Puppet / PUP-10844 Agent failures with server_list when one puppetserver fails Change By: Vadym Chepkov Attachment: puppet-agents.txt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.381638.1608653215000.155974.1614775020041%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Vadym Chepkov commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails I have upgraded non-prod environment and non-prod nodes and problem persists in PE2019.8.5 with puppet 6.21.1. The root cause, which was in the ticket description maybe not accurate, but they method Jarret Lavallee used is still valid. I extracted events from splunk after I shutdown pe-pupeptserver on the primary puppet-agents.txt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.381638.1608653215000.155975.1614775020100%40Atlassian.JIRA.
Jira (FACT-2950) Root of structured core facts cannot be overriden by a custom fact
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Facter / FACT-2950 Root of structured core facts cannot be overriden by a custom fact Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389257.1614583384000.155962.1614773460031%40Atlassian.JIRA.
Jira (PUP-10922) The fqdn_rand() function should not assume case-consistency in the fqdn fact
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10922 The fqdn_rand() function should not assume case-consistency in the fqdn fact Change By: Mihai Buzgau Sprint: NW - 2021-03-03 , NW - 2021-03-17 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.387597.1613401978000.155949.1614771360036%40Atlassian.JIRA.
Jira (PUP-10947) Revist the exclude_list for puppet facts diff command
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10947 Revist the exclude_list for puppet facts diff command Change By: Mihai Buzgau Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389694.1614756311000.155912.1614770160040%40Atlassian.JIRA.
Jira (FACT-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1847 Implement "cloud" fact Azure identification for Windows platform Change By: Mihai Buzgau Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.247441.1524674206000.155911.1614769500029%40Atlassian.JIRA.
Jira (FACT-2930) Inconsistent handling of Date types in custom facts
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2930 Inconsistent handling of Date types in custom facts Change By: Mihai Buzgau Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.385405.1611950891000.155905.1614768600079%40Atlassian.JIRA.
Jira (FACT-2943) Fix os.name detection of AlmaLinux
Title: Message Title Mihai Buzgau commented on FACT-2943 Re: Fix os.name detection of AlmaLinux Christoph Schug thanks for your contribution! do you mind if we give you a shout-out for this in our release announcement? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.387803.1613568551000.155896.1614768360033%40Atlassian.JIRA.
Jira (PUP-10929) Syntax error in previously valid puppet code due to removal of application orchestration keywords
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10929 Syntax error in previously valid puppet code due to removal of application orchestration keywords Change By: Mihai Buzgau Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.388276.1614006941000.155895.1614768240030%40Atlassian.JIRA.
Jira (PUP-10943) Windows package provider continues to read DisplayVersion key after embedded NULL
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10943 Windows package provider continues to read DisplayVersion key after embedded NULL Change By: Mihai Buzgau Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.388985.1614292739000.155877.1614764880027%40Atlassian.JIRA.
Jira (FACT-2952) Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2952 Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3 Change By: Mihai Buzgau Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389552.161471215.155876.1614764700041%40Atlassian.JIRA.
Jira (FACT-2950) Root of structured core facts cannot be overriden by a custom fact
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2950 Root of structured core facts cannot be overriden by a custom fact Change By: Mihai Buzgau Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389257.1614583384000.155875.1614764340038%40Atlassian.JIRA.
Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title Mihai Buzgau commented on FACT-2937 Re: 'puppet facts show' logs error when stdlib is installed This ticket addresses the --show-legacy CLI option that was created with the intent to "hide" legacy facts and not to block them. Blocking should block facts. For example, if a user decides to block the EC2 metadata, any module that relies on this information will no longer work. By default Facter 4 does not block any facts, it only provides a couple of pre-defined block groups that users can be used. These default groups also serve as examples for creating new groups. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.386159.1612446678000.155842.1614761040029%40Atlassian.JIRA.
Jira (PDB-5050) Extend puppetlabs-puppetdb module to allow certificate connections to postgresql
Title: Message Title Florin Dragos assigned an issue to Florin Dragos PuppetDB / PDB-5050 Extend puppetlabs-puppetdb module to allow certificate connections to postgresql Change By: Florin Dragos Assignee: Florin Dragos Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.388738.1614177642000.155812.1614758880345%40Atlassian.JIRA.
Jira (PUP-10947) Revist the exclude_list for puppet facts diff command
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10947 Revist the exclude_list for puppet facts diff command Change By: Mihai Buzgau Sprint: NW - 2021-03-17 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389694.1614756311000.155801.1614758400359%40Atlassian.JIRA.
