Jira (PDB-5662) Update load testing doc to include generate tool
Title: Message Title Joshua Partlow created an issue PuppetDB / PDB-5662 Update load testing doc to include generate tool Issue Type: Task Assignee: Unassigned Created: 2023/06/13 10:27 AM Priority: Normal Reporter: Joshua Partlow Update documentation/load_testing_tool.markdown to include information on the generate tool added in PDB-5591, PDB-5592, PDB-5593. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Joshua Partlow commented on PDB-5633 Re: Investigate why (some?) command discards aren't including the stack Sorry, Gareth, there must be something going on with Jira. I didn't get notified about any of these comments until today for some reason. Yes, your syntax is correct now, but I'm not sure about the best way to force a discard. Rob Browning? Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.484959.1682619597000.8752.1686585840031%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow commented on PDB-5593 Re: Generating report data Pez had failed I think due to the openssl issue breaking cast for postgres. Rekicked as that is resolved now, to get this into PE main. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481308.1676309116000.5173.1686071760023%40Atlassian.JIRA.
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Joshua Partlow commented on PDB-5633 Re: Investigate why (some?) command discards aren't including the stack Hi Gareth; yes, that's the file that has pe-puppetdb's JAVA_ARGS. One thing to note is that that env var is managed by puppet; so if you need any reliability or permanence around the change, I believe you will want to adjust puppet_enterprise::profile::puppetdb::java_args where they probably already have memory settings set. I think you'd be adding a "XX:-OmitStackTraceInFastThrow" => "" to the map. But I would double check with someone else in support that I'm not leading you astray on the best way to provide these kind of one off java args overrides for customers. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.484959.1682619597000.4480.1685728140033%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob in reports.logs)** variable*** tags array*** message** plugin lines** could have debug lines*** a pe primary report with --debug, for example, adds ~11000 log entries and 5MB to the report.* metrics (stored as a blob in reports.metrics)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** stored as a blob (reports.resources)** but changed resource properties stored in resource_events*** so each resource events array has one event per resource property change, (file content, owner, mode, for instance would be three events), but typically just one containment_path (corresponds to depth of resource in catalog graph) most variable* old_value* new_value* messageProbably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports. Benchmark varies timestamps, but not events. Also need to think about unchanged resources. Does generate deal with that, or should benchmark mutate reports with that flag on or off? Will add a flag to generate for now. Add Comment This message was sent by Atlassian Jira
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob in reports.logs)** variable*** tags array*** message** plugin lines** could have debug lines* ** a pe primary report with --debug, for example, adds ~11000 log entries and 5MB to the report.* metrics (stored as a blob in reports.metrics)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** stored as a blob (reports.resources)** but changed resource properties stored in resource_events*** so each resource events array has one event per resource property change, (file content, owner, mode, for instance would be three events), but typically just one containment_path (corresponds to depth of resource in catalog graph) most variable* old_value* new_value* messageProbably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports.Also need to think about unchanged resources. Does generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5644) Puppet db export does not include unchanged resources in exported reports.
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5644 Puppet db export does not include unchanged resources in exported reports. Change By: Joshua Partlow Running 'puppet db export' for reports that have unchanged resources (in in the reports.resources blob), produces a report with an empty resources array. (If there are resource_events, then the array will have just those resources that had resource_event).The expectation is that export would round trip the resources. https://github.com/puppetlabs/puppetdb/blob/dd869e84721e79e54a100d96873560e2d10dc054/src/puppetlabs/puppetdb/reports.clj#L283-L290C37 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PDB-5644) Puppet db export does not include unchanged resources in exported reports.
Title: Message Title Joshua Partlow created an issue PuppetDB / PDB-5644 Puppet db export does not include unchanged resources in exported reports. Issue Type: Bug Affects Versions: PDB 8.0.0, PDB 7.13.0 Assignee: Unassigned Components: PuppetDB Created: 2023/05/11 5:06 PM Priority: Normal Reporter: Joshua Partlow Running 'puppet db export' for reports that have unchanged resources (in in the reports.resources blob), produces a report with an empty resources array. (If there are resource_events, then the array will have just those resources that had resource_event). The expectation is that export would round trip the resources. Add Comment
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob in reports.logs )** variable*** tags array*** message** plugin lines** could have debug lines* metrics (stored as a blob in reports.metrics )** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** containment_path stored as a blob ( corresponds to depth of resource in catalog graph reports.resources )** events array ( but changed resource properties stored as in resource_events ) *** most variable old_value new_value message*** so each resource events array has one event per resource property change, (file content, owner, mode, for instance would be three events), but typically just one containment_path (corresponds to depth of resource in catalog graph) most variable* old_value* new_value* message Probably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports.Also need to think about unchanged resources. Does generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob)** variable*** tags array*** message** plugin lines** could have debug lines* metrics (stored as a blob)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** containment_path (corresponds to depth of resource in catalog graph)** events array (stored as resource_events)*** most variable old_value new_value message*** ever more than 1 one event ? per resource property change, (file content, owner, mode, for instance would be three events), but typically just one Probably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports.Also need to think about unchanged resources. Does generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481308.1676309116000.12304.1683750060030%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob)** variable*** tags array*** message** plugin lines** could have debug lines* metrics (stored as a blob)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** containment_path (corresponds to depth of resource in catalog graph)** events array (stored as resource_events)*** most variable old_value new_value message*** ever more than 1 event?Probably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports.Also need to think about unchanged resources. So Does generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5643) PQL parsing of OR clauses can result in OOM errors
Title: Message Title
Joshua Partlow updated an issue
PuppetDB / PDB-5643
PQL parsing of OR clauses can result in OOM errors
Change By:
Joshua Partlow
There seems to be enough inefficiency in [instaparse|https://github.com/Engelberg/instaparse] such that large(ish) sets of OR clauses can eat up available memory.In a 2021.7.2 e2-custom-4-10240 GCP test instance with 1G allocated to puppetdb's heap, this query was enough to oom in ~3m:{code}reports { latest_report? = true and (certname = "foo22" orcertname = "foo21" orcertname = "foo20" orcertname = "foo19" orcertname = "foo18" orcertname = "foo17" orcertname = "foo16" orcertname = "foo15" orcertname = "foo14" orcertname = "foo13" orcertname = "foo12" orcertname = "foo11" orcertname = "foo10" orcertname = "foo9" orcertname = "foo8" orcertname = "foo7" orcertname = "foo6" orcertname = "foo5" orcertname = "foo4" orcertname = "foo3" orcertname = "foo2" orcertname = "foo1" )}{code}The effect is exponential. Calling it with 21 OR clauses, the query succeeded in 31s, with 20 in 7s, with 19 in 4s, and so on back down to <1 once you reach 16 clauses.We'll need to see if our grammar can be tweaked again to avoid this, similar to what Rob did in PDB-5260, or if we're looking at a parser re-write to fix this. WORKAROUNDS: Use IN instead of a set of ORs; or wrap the ORs in parentheses, although in general an IN will be faster on the postgres side once this eventually parses and postgres is actually running it. ACTION:Look through and see if there is an improvement using instaparse. Do not necessarily re-write the parser just for this bug.
Add Comment
Jira (PDB-5643) PQL parsing of OR clauses can result in OOM errors
Title: Message Title
Joshua Partlow created an issue
PuppetDB / PDB-5643
PQL parsing of OR clauses can result in OOM errors
Issue Type:
Bug
Affects Versions:
PDB 7.12.1
Assignee:
Unassigned
Created:
2023/05/03 1:26 PM
Priority:
Normal
Reporter:
Joshua Partlow
There seems to be enough inefficiency in instaparse such that large(ish) sets of OR clauses can eat up available memory. In a 2021.7.2 e2-custom-4-10240 GCP test instance with 1G allocated to puppetdb's heap, this query was enough to oom in ~3m:
reports {
latest_report? = true and (
certname = "foo22" or
certname = "foo21" or
certname = "foo20" or
Jira (PDB-5591) Generating factset data examples
Title: Message Title Joshua Partlow commented on PDB-5591 Re: Generating factset data examples Note to self, review https://puppet.atlassian.net/browse/PUP-9577 and PUP-11088 and ensure we can adjust the factset to produce such examples. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481306.1676309066000.9248.1682610660024%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow - Events * logs (stored as a blob)** variable*** tags array*** message** plugin lines** could have debug lines* metrics (stored as a blob)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** containment_path (corresponds to depth of resource in catalog graph)** events array (stored as resource_events)*** most variable old_value new_value message*** ever more than 1 event?Probably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports. Also need to think about unchanged resources. So generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5631) Fix puppetlabs-puppetdb modules specs
Title: Message Title Joshua Partlow created an issue PuppetDB / PDB-5631 Fix puppetlabs-puppetdb modules specs Issue Type: Task Assignee: Unassigned Created: 2023/04/19 1:02 PM Priority: Normal Reporter: Joshua Partlow The puppetlabs-puppetdb module's specs are broken, dating back to the postgres module updates, probably. We need to get them working again and then hook them up to a github action so they run. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5592) Generating catalog data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5592 Generating catalog data Change By: Joshua Partlow Fix Version/s: PDB 8.0.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481307.1676309101000.4845.1681319400020%40Atlassian.JIRA.
Jira (PDB-5622) Puppetdb acceptance test failures
Title: Message Title Joshua Partlow commented on PDB-5622 Re: Puppetdb acceptance test failures Austin Blatt or Rob Browning suggestion was that jenkins needs to build with Java 11. Our docs do seem to indicate Java 11+ here, but project.clj looks to allow 8 here. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483790.1680130559000.1870.1680131760035%40Atlassian.JIRA.
Jira (PDB-5589) Investigate pdb upgrade times with migration 81/82
Title: Message Title Joshua Partlow commented on PDB-5589 Re: Investigate pdb upgrade times with migration 81/82 Same issue for resource_events, except it's just the old primary key 'resource_events_hash_*' that is left over in the migrated partitions. Effectively replaced by the new pkey on event_hash, timestamp. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480704.1675468795000.1412.1680047640237%40Atlassian.JIRA.
Jira (PDB-5589) Investigate pdb upgrade times with migration 81/82
Title: Message Title
Joshua Partlow commented on PDB-5589
Re: Investigate pdb upgrade times with migration 81/82
Regarding the index differences between 7.12.1 and 7.x with migrations 81 and 82, it took a little bit for me to get up to speed here, but I think I'm now seeing the same thing you are, Austin Blatt. On 7.12.1 we have the following report partition indexes:
"reports_cached_catalog_status_on_fail_20230320z" btree (cached_catalog_status) WHERE cached_catalog_status = 'on_failure'::text
"reports_catalog_uuid_idx_20230320z" btree (catalog_uuid)
"idx_reports_certname_end_time_20230320z" btree (certname, end_time)
"idx_reports_producer_timestamp_by_hour_certname_20230320z" btree (date_trunc('hour'::text, timezone('UTC'::text, producer_timestamp)), producer_timestamp, certname)
"reports_end_time_idx_20230320z" btree (end_time)
"reports_environment_id_idx_20230320z" btree (environment_id)
"reports_job_id_idx_20230320z" btree (job_id) WHERE job_id IS NOT NULL
"reports_noop_idx_20230320z" btree (noop) WHERE noop = true
"idx_reports_noop_pending_20230320z" btree (noop_pending) WHERE noop_pending = true
"idx_reports_prod_20230320z" btree (producer_id)
Jira (PDB-5591) Generating factset data examples
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow PuppetDB / PDB-5591 Generating factset data examples Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481306.1676309066000.1805.1679349180025%40Atlassian.JIRA.
Jira (PDB-5592) Generating catalog data
Title: Message Title Joshua Partlow commented on PDB-5592 Re: Generating catalog data Austin Blatt for total catalog size, are we talking kb mb gb? Based on a really large number of resources (so instead of setting num-resources)? Based on adding something like large content blobs to File resources? Something else? For edge depth, I figure we are talking here about the deepest nesting, as, for example, class->class->defined type->resource. Are there queries in pdb that reconstruct those relations? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481307.1676309101000.3024.1677876840019%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481308.1676309116000.2412.1677698220128%40Atlassian.JIRA.
Jira (PDB-5591) Generating factset data examples
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5591 Generating factset data examples Change By: Joshua Partlow Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481306.1676309066000.2409.1677698160023%40Atlassian.JIRA.
Jira (PDB-5592) Generating catalog data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5592 Generating catalog data Change By: Joshua Partlow Sprint: Skeletor 03/01/2023 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481307.1676309101000.1561.1677606300032%40Atlassian.JIRA.
Jira (PDB-5592) Generating catalog data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5592 Generating catalog data Change By: Joshua Partlow Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481307.1676309101000.1560.1677606240020%40Atlassian.JIRA.
Jira (PDB-5592) Generating catalog data
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow PuppetDB / PDB-5592 Generating catalog data Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481307.1676309101000.1559.1677606180023%40Atlassian.JIRA.
Jira (PDB-5594) SPIKE - can we use clojure/data.generators
Title: Message Title
Joshua Partlow commented on PDB-5594
Re: SPIKE - can we use clojure/data.generators
I've looked at clojure.data.generators some, and also at the existing pdb functions for generating resources, and data elements. I wrote some little catalog generator functions in the cli.benchmark to sort of feel my way around. Catalogs should have internal consistency, though, with a set of resources that are linked into a graph by a set of edge references. For the most part, our existing functions seem sufficient to get us started. I expect the data.generators library can help with an additional helper functions that might be needed. Here's a simple and incomplete example that I will try to flesh out for PDB-5592: https://github.com/jpartlow/puppetdb/tree/tmp/pdb-5592. Rob pointed me to spec.alpha, and schema.generators. Since pdb has some schema related to the wire formats for facts, catalogs and reports, I worked with schema.generator for a while to try and get a feel for how it would work. Since it would potentially generate directly from our existing schema I thought it might keep things simpler. Under the hood, schema.generators relies on the test.check library for generation (pdb has a dev dependency on an older test.check 0.9.0, just for the test suite atm). However given the need for internally consistent self-referential resource/events/edges in catalogs and reports, data generation isn't as straight forward as just blowing some random strings into a set of leaf properties. I think test.check is sufficiently complex to deal with that by using functions like gen/bind and gen/let so that building a catalog in phases would allow edges to be built from earlier generated resources, for example. But the real problem I had was that test-check is just too random. For example, as a test of generating fact values:
local-test=> (clojure.pprint/pprint (tc/sample (tc/map tc/string-alphanumeric (tc/recursive-gen (fn [inner] (tc/one-of [(tc/vector inner) (tc/map tc/string-alphanumeric inner)])) tc/string-alphanumeric) {:min-elements 5 :max-elements 10}) 2))
({"" [],
"2" ["G" "4x"],
"A" [["T"]],
"QP" [{}],
"W2" {"" {}},
Jira (PDB-5553) Remove foreign keys from report partitions
Title: Message Title Joshua Partlow commented on PDB-5553 Re: Remove foreign keys from report partitions This is merged up to main in ef929079a which is in 2023.1.0-rc1-74-g0c461fa, and that has run in the pe main ci. But that currently has a bunch of failures related to the test forge cert being expired. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472747.1666299762000.1320.1677527640139%40Atlassian.JIRA.
Jira (PDB-5553) Remove foreign keys from report partitions
Title: Message Title Joshua Partlow commented on PDB-5553 Re: Remove foreign keys from report partitions The 7.x pipeline passed, and this is in 2021.7.3-rc1-60-gee127a6 which has been through the 2021.7.x integration pipeline. Adding a merge up pr for main now. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472747.1666299762000.1027.1677265380092%40Atlassian.JIRA.
Jira (PDB-5592) Generating catalog data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5592 Generating catalog data Change By: Joshua Partlow - Number of classes (correlates to "source files" in a control-repo)- Number of resources- Number of resources- Size of title string (this is indexed for queries, so its size is important)- Total size of Catalog- "Depth" of ordering edge DAG Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481307.1676309101000.11075.1676580420029%40Atlassian.JIRA.
Jira (PDB-5594) SPIKE - can we use clojure/data.generators
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow PuppetDB / PDB-5594 SPIKE - can we use clojure/data.generators Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481309.1676309254000.10963.1676570520088%40Atlassian.JIRA.
Jira (PDB-4688) Deprecation removals for PuppetDB 8
Title: Message Title Joshua Partlow commented on PDB-4688 Re: Deprecation removals for PuppetDB 8 This is in 2023.1.0-rc1-51-ga570859 and has been through the main puppetdb and pe-integration pipelines, which are green. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356709.1587757722000.9656.1676064960023%40Atlassian.JIRA.
Jira (PDB-4972) puppetdb-7.0.0 still requires java-1.8.0-openjdk-headless
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-4972 puppetdb-7.0.0 still requires java-1.8.0-openjdk-headless Change By: Joshua Partlow Fix Version/s: pdb 7.0.2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.379070.160597919.9605.1676059320028%40Atlassian.JIRA.
Jira (PDB-5278) Grouping by a fact with a / in the name generates 500
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5278 Grouping by a fact with a / in the name generates 500 Change By: Joshua Partlow Affects Version/s: PDB 6.18.2 Affects Version/s: PDB 6.18.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.416232.1631899059000.9596.1676058600023%40Atlassian.JIRA.
Jira (PDB-5226) Dotted fact path group by doesn't group
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5226 Dotted fact path group by doesn't group Change By: Joshua Partlow Affects Version/s: PDB 6.18.1 Affects Version/s: PDB 6.18.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.409525.1627947342000.9595.1676058540181%40Atlassian.JIRA.
Jira (PDB-5449) Update pgjdbc
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5449 Update pgjdbc Change By: Joshua Partlow Fix Version/s: PDB 7.9.1 Fix Version/s: PDB 7.9.2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.433937.1643841148000.9564.1676056920037%40Atlassian.JIRA.
Jira (PDB-5534) PuppetDB query slowdown with Postgres 9.6.4
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5534 PuppetDB query slowdown with Postgres 9.6.4 Change By: Joshua Partlow Affects Version/s: PDB 6.20.1 Affects Version/s: PDB 6.20.2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.466293.1662101308000.9563.1676056860026%40Atlassian.JIRA.
Jira (PDB-5449) Update pgjdbc
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5449 Update pgjdbc Change By: Joshua Partlow Fix Version/s: PDB 6.20.1 Fix Version/s: PDB 6.20.2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.433937.1643841148000.9557.1676056440179%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Joshua Partlow Fix Version/s: PDB 7.12.2 Fix Version/s: PDB 8.0.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.475715.1669757045000.9457.1676050440042%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5554 Remove partitions in a non-world-blocking way Change By: Joshua Partlow Fix Version/s: PDB 7.12.2 Fix Version/s: PDB 8.0.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.9458.1676050440109%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow commented on PDB-5567 Re: Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions This is in 2021.7.3-rc1-41-g502f631, and 2023.1.0-rc1-51-ga570859, both of which have gone through nightly PE integration CI. There are some 2021.7 failures that look to be scattered, unrelated abs/vmpooler allocation or connectivity type errors. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.475715.1669757045000.9443.1676049960029%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Joshua Partlow Labels: docs Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.475715.1669757045000.9444.1676049960077%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow commented on PDB-5554 Re: Remove partitions in a non-world-blocking way This is in 2021.7.3-rc1-41-g502f631, and 2023.1.0-rc1-51-ga570859, both of which have gone through nightly PE integration CI. There are some 2021.7 failures that look to be scattered, unrelated abs/vmpooler allocation or connectivity type errors. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.9442.1676049900021%40Atlassian.JIRA.
Jira (PDB-5587) Check builds, promote to PE (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow commented on PDB-5587 Re: Check builds, promote to PE (Puppet Platform 7.23.0) PE is already using later 7.12.2-snapshot builds. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480626.1675199002000.8849.1675884780025%40Atlassian.JIRA.
Jira (PDB-5586) Bump versions, push directly, and tag (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow commented on PDB-5586 Re: Bump versions, push directly, and tag (Puppet Platform 7.23.0) Austin completed this in 1e411a4d8 a few weeks back. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480625.1675199001000.8050.1675724040085%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Joshua Partlow PDB-5554 intended to improve performance around partition remove by making use of `alter table detach partition concurrently`. But that can only be used with declarative partitions and our partitions are inheritance based.Migrate resource_events and reports partitioning to [declarative partitions|https://www.postgresql.org/docs/current/ddl-partitioning.html].[https://www.2ndquadrant.com/en/blog/how-to-migrate-from-inheritance-based-partitioning-to-declarative-partitioning-in-postgresql/] is one example.Need to validate that this migration won't have a significant impact on larger databases with a significant number of reports and events.NOTE: * The minimum PostgreSQL version is now 11 with these migrations. * Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Joshua Partlow PDB-5554 intended to improve performance around partition remove by making use of `alter table detach partition concurrently`. But that can only be used with declarative partitions and our partitions are inheritance based.Migrate resource_events and reports partitioning to [declarative partitions|https://www.postgresql.org/docs/current/ddl-partitioning.html].[https://www.2ndquadrant.com/en/blog/how-to-migrate-from-inheritance-based-partitioning-to-declarative-partitioning-in-postgresql/] is one example.Need to validate that this migration won't have a significant impact on larger databases with a significant number of reports and events. NOTE: The minimum PostgreSQL version is now 11 with these migrations. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Joshua Partlow Release Notes: Enhancement Release Notes Summary: The reports and resource_events tables were migrated to use PostgreSQL declarative partitioning in support of PDB-5554.This changes requires a minimum of PostgreSQL 11. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.475715.1669757045000.7707.1675469700043%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5554 Remove partitions in a non-world-blocking way Change By: Joshua Partlow Labels: docs Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.7706.1675469520027%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5554 Remove partitions in a non-world-blocking way Change By: Joshua Partlow Release Notes: Enhancement Release Notes Summary: PuppetDB installations with PostgreSQL 14+ will detach reports and resource_events partitions concurrently before dropping them. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.7705.1675469460026%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow commented on PDB-5567 Re: Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Charlie Sharpsteen this is the migration ticket supporting PDB-5554 I pinged you about. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.475715.1669757045000.7704.1675469400093%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow commented on PDB-5554 Re: Remove partitions in a non-world-blocking way Charlie Sharpsteen this pdb change will be going into 7.x and 8.x/main and makes an adjustment to gc, but only if you are running PG14+. This allows us to detach the tables with reduced locking before dropping them. The PG11 workflow should be unchanged. However this required adjusting the reports and resource_events tables and their partitions to use postgresql declarative partitioning instead of the older inheritance partitioning available in PG10. That's PDB-5567. That also locked in pdb postgresql requirements to PG11 as a minimum. PR is open here if you want to review it. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.7702.1675469340022%40Atlassian.JIRA.
Jira (PDB-5589) Investigate pdb upgrade times with migration 81/82
Title: Message Title Joshua Partlow created an issue PuppetDB / PDB-5589 Investigate pdb upgrade times with migration 81/82 Issue Type: Task Assignee: Unassigned Components: PuppetDB, PuppetDB Enterprise Created: 2023/02/03 3:59 PM Priority: Normal Reporter: Joshua Partlow Double check how much time the index regeneration from pdb migrations 81/82 takes (these migrations rejigger the reports/resource_events partitions to use declarative partitioning). Time to upgrade In versions of PG 11.17 the reports_noop_idx indexes generated on the child partitions is named differently than in 11.18 (for example, reports_20230130z_noop_idx instead of reports_noop_idx_20230130z, see: https://github.com/puppetlabs/puppetdb/pull/3748/commits/133c3771e84d8b389bb4eca74907f7b03a96e389). It would be good to validate what the indexes look like after upgrading on =11.18 (possibly easiest to test this with PE) Add Comment
Jira (PDB-5586) Bump versions, push directly, and tag (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5586 Bump versions, push directly, and tag (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480625.1675199001000.6432.1675206840044%40Atlassian.JIRA.
Jira (PDB-5588) Update ticket templates (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5588 Update ticket templates (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480627.1675199003000.6434.1675206840142%40Atlassian.JIRA.
Jira (PDB-5587) Check builds, promote to PE (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5587 Check builds, promote to PE (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480626.1675199002000.6433.1675206840095%40Atlassian.JIRA.
Jira (PDB-5584) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5584 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480623.167519900.6430.1675206780110%40Atlassian.JIRA.
Jira (PDB-5585) Draft release notes (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5585 Draft release notes (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480624.1675199001000.6431.1675206780157%40Atlassian.JIRA.
Jira (PDB-5583) Merge-up, branch, and create pipelines (Puppet Platform 7.23.0)
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5583 Merge-up, branch, and create pipelines (Puppet Platform 7.23.0) Change By: Joshua Partlow Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480622.1675198999000.6429.1675206780045%40Atlassian.JIRA.
Jira (PDB-5581) Github PR pipeline doesn't report after first job
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5581 Github PR pipeline doesn't report after first job Change By: Joshua Partlow Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479496.1674513484000.3410.1674513600026%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow commented on PDB-5567 Re: Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions PR is up for some initial review. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.475715.1669757045000.67527.1671235260051%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow commented on PDB-5554 Re: Remove partitions in a non-world-blocking way PR is up for some initial review. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.67528.1671235260126%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Joshua Partlow Sprint: Skeletor 12/07/2022 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.475715.1669757045000.61975.1669758480085%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.475715.1669757045000.61973.1669758420030%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow created an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Issue Type: Improvement Assignee: Unassigned Created: 2022/11/29 1:24 PM Priority: Normal Reporter: Joshua Partlow PDB-5554 intended to improve performance around partition remove by making use of `alter table detach partition concurrently`. But that can only be used with declarative partitions and our partitions are inheritance based. Migrate resource_events and reports partitioning to declarative partitions. https://www.2ndquadrant.com/en/blog/how-to-migrate-from-inheritance-based-partitioning-to-declarative-partitioning-in-postgresql/ is one example. Need to validate that this migration won't have a significant impact on larger databases with a significant number of reports and events. Add Comment
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow commented on PDB-5554 Re: Remove partitions in a non-world-blocking way Testing https://github.com/puppetlabs/puppetdb/pull/3748 with Postgresql 14 turned up that use of alter table detach partition assumes the tables use postgresql declarative partitioning, and our tables achieve partitioning with inheritance and triggers. So this isn't something we can implement without changing the method of partitioning. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.61947.1669754460445%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow commented on PDB-5554 Re: Remove partitions in a non-world-blocking way Is this intended only for main? If I'm understanding it, 'detach partition * concurrently' is only supported in Postgres 14 and 7.x still allows Postgres 11. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.54755.1667329980071%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5554 Remove partitions in a non-world-blocking way Change By: Joshua Partlow Sprint: Skeletor 11/09/2022 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.54701.1667327100032%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow PuppetDB / PDB-5554 Remove partitions in a non-world-blocking way Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.54700.1667327040185%40Atlassian.JIRA.
Jira (PUP-11061) Two Sensitive instances with the same value are not equal
Title: Message Title
Joshua Partlow updated an issue
Puppet / PUP-11061
Two Sensitive instances with the same value are not equal
Change By:
Joshua Partlow
Release Notes:
Enhancement
Release Notes Summary:
Previously two instances of type Sensitive would not compare as equal if their underlying strings were equal. This patch changed that behavior allowing comparisons such as '$a = Sensitive("secret"); $b = Sensitive("secret"); notice($a == $b)' to return true.
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.399467.1620941435000.48142.1622754960141%40Atlassian.JIRA.
Jira (PUP-11061) Two Sensitive instances with the same value are not equal
Title: Message Title Joshua Partlow commented on PUP-11061 Re: Two Sensitive instances with the same value are not equal I updated the pr to test hash, so unwrap isn't involved. For context, the case I tripped over was using bolt_spec to verify a task with a sensitive parameter. The spec runner couldn't match the expectation because it was matching the parameter hashes, and the sensitive parameter values were unequal... Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.399467.1620941435000.37038.1621463460087%40Atlassian.JIRA.
Jira (PUP-11061) Two Sensitive instances with the same value are not equal
Title: Message Title
Joshua Partlow created an issue
Puppet / PUP-11061
Two Sensitive instances with the same value are not equal
Issue Type:
Bug
Affects Versions:
PUP 7.6.0
Assignee:
Unassigned
Components:
Type System
Created:
2021/05/13 2:30 PM
Priority:
Normal
Reporter:
Joshua Partlow
Puppet Version: 7.6.0 Two instances of lib/puppet/pops/types/p_sensitive_type.rb Sensitive with the same value are not equal. The class is just using default object id for equality. Desired Behavior:
jpartlow@work1804:~/work/src/puppet$ puppet apply -e '$a = Sensitive("secret"); $b = Sensitive("secret"); notice($a == $b)'
Notice: Scope(Class[main]): true
Notice: Compiled catalog for work1804.platform9.puppet.net in environment production in 0.03 seconds
Notice: Applied catalog in 0.08 seconds
Jira (PDB-4682) PuppetDB sync status doesn't get updated when finished
Title: Message Title Joshua Partlow commented on PDB-4682 Re: PuppetDB sync status doesn't get updated when finished Don't see it in 2019.5.0, which relies on puppetdb sync like 2018.1, to sync the replica: [root@wrong-coastline ~]# cat /opt/puppetlabs/server/pe_build ; echo 2019.5.0 [root@wrong-coastline ~]# puppet infra status Notice: Contacting services for status information... File Sync Client Service: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:8140/ Puppet Server: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:8140/ Classifier: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:4433/classifier-api RBAC: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:4433/rbac-api Activity Service: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:4433/activity-api PuppetDB: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:8081/pdb Info: Last sync successfully completed 141 seconds ago (at 2020-04-02T21:14:00.710Z)
Jira (PDB-4682) PuppetDB sync status doesn't get updated when finished
Title: Message Title Joshua Partlow commented on PDB-4682 Re: PuppetDB sync status doesn't get updated when finished Working on master 2019.6.0-rc2-60-ge16e31b, but that's with replication streaming, so probably no sync after. I'll check 2019.5.0. [root@medical-singing pe_manager]# cat /opt/puppetlabs/server/pe_build ; echo 2019.6.0-rc2-60-ge16e31b [root@medical-singing pe_manager]# puppet infra status Notice: Contacting services for status information... Code Manager: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:8170/ File Sync Storage Service: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:8140/ File Sync Client Service: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:8140/ Puppet Server: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:8140/ Classifier: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:4433/classifier-api RBAC: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:4433/rbac-api Activity Service: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:4433/activity-api
Jira (PDB-4602) Guard PuppetDB migrations against simultaneous writers
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-4602 Guard PuppetDB migrations against simultaneous writers Change By: Joshua Partlow Epic Name: serial migrations PDB Serial Migrations 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.339273.1576193168000.18877.1581104340232%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Joshua Partlow commented on PDB-4479 Re: Deactivate node commands sync after garbage collection Austin Blatt What build of PE did this land in? And what fix versions? 2019.y only? Has the main master pe integration ci run with it? 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.320599.1565648011000.18604.1581098160255%40Atlassian.JIRA.
Jira (PDB-4635) puppetdb_avg_mem larger than baseline values
Title: Message Title Joshua Partlow commented on PDB-4635 Re: puppetdb_avg_mem larger than baseline values Nick Walker Would this be changes from https://github.com/puppetlabs/puppet-enterprise-modules/pull/772 or https://github.com/puppetlabs/puppet-enterprise-modules/pull/842? 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.343321.1579814655000.35496.1579815540660%40Atlassian.JIRA.
Jira (PUP-10135) Have a command to stop and start all puppet services
Title: Message Title Joshua Partlow commented on PUP-10135 Re: Have a command to stop and start all puppet services Ah, sorry, didn't see this. We could add an action to puppet-infra, and/or possibly a bolt plan. I'll switch this to the PE project and it'll flow into our backlog, though I'm not certain what priority it will end up with. The installer uses [pe_install::upgrade::stop_services|https://github.com/puppetlabs/puppet-enterprise-modules/blob/master/modules/pe_install/manifests/upgrade/stop_services.pp]. 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.334488.1573557533000.28991.1573589640225%40Atlassian.JIRA.
Jira (PUP-10122) Only collect checksum metadata for links pointing to files
Title: Message Title Joshua Partlow commented on PUP-10122 Re: Only collect checksum metadata for links pointing to files I blame the comma? 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.333946.1573148555000.25117.1573244100083%40Atlassian.JIRA.
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title Joshua Partlow commented on PUP-10029 Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow I opened https://github.com/puppetlabs/bolt/issues/1242 to discuss how to handle this issue in Bolt. 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.325693.1569277631000.111723.1569346321016%40Atlassian.JIRA.
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title
Joshua Partlow commented on PUP-10029
Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Hmm, that's interesting, that does work:
[root@wuh7cxdfusfnult ~]# cat test.rb
require 'puppet'
Puppet.initialize_settings
env = Puppet.lookup(:environments).get(Puppet[:environment])
Puppet.override(:current_environment => env, :loaders => Puppet::Pops::Loaders.new(env)) do
require 'puppet/datatypes/error'
e = Puppet::DataTypes::Error.new('foo')
puts e.to_s
end
[root@wuh7cxdfusfnult ~]# /opt/puppetlabs/puppet/bin/ruby test.rb
Error({'msg' => 'foo'})
So the issue I'm seeing appears to be a case of Bolt handling an error instance outside of a context with loaders available, here. Unless you consider the Puppet::DataTypes::Error.to_s requiring loaders a bug in and of itself?
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title Joshua Partlow commented on PUP-10029 Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow Hi Thomas Hallgren, yeah, I was originally trying to require 'puppet/datatypes/error', but that has some add behavior, see below: [root@wuh7cxdfusfnult ~]# /opt/puppetlabs/puppet/bin/irb irb(main):001:0> require 'puppet' => true irb(main):002:0> require 'puppet/datatypes' => false irb(main):003:0> require 'puppet/datatypes/error' Traceback (most recent call last): 7: from /opt/puppetlabs/puppet/bin/irb:11:in `' 6: from (irb):3 5: from /opt/puppetlabs/puppet/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 4: from /opt/puppetlabs/puppet/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 3: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/datatypes/error.rb:1:in `'
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title Joshua Partlow commented on PUP-10029 Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow Henrik Lindberg Hi there; bumped into this while working with Bolt apply(). Looks like Puppet::DataTypes::Error.to_s() is broken, or something else is going on that I'm not following...getting an isolated instance of Puppet::DataTypes::Error to test against wasn't straight forward . 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.325693.1569277631000.110550.1569277800167%40Atlassian.JIRA.
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title Joshua Partlow created an issue Puppet / PUP-10029 A Puppet::DataTypes::Error#to_s() fails with a stack overflow Issue Type: Bug Affects Versions: PUP 6.10.0 Assignee: Unassigned Created: 2019/09/23 3:27 PM Priority: Normal Reporter: Joshua Partlow Puppet Version: 6.10 (master) Instances of Puppet::DataTypes::Error end up recursively overflowing the stack calling to_s(). [root@wuh7cxdfusfnult installer]# /opt/puppetlabs/puppet/bin/puppet --version 6.10.0 [root@wuh7cxdfusfnult installer]# /opt/puppetlabs/puppet/bin/irb irb(main):001:0> require 'puppet' r=> true
Jira (PUP-9931) Make Context thread local
Title: Message Title Joshua Partlow commented on PUP-9931 Re: Make Context thread local Patrick Carlisle There are two test methods left in the Puppet class which need to be removed because Puppet::Context no longer has the methods they call: https://github.com/puppetlabs/puppet/blob/6.9.0/lib/puppet.rb#L277-L287 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.306716.1556578082000.102305.1568749201026%40Atlassian.JIRA.
Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6
Title: Message Title Joshua Partlow commented on PDB-4373 Re: PDB has issues upgrading to versions later than 6.1 on centos6 Thanks! 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.309068.155804266.98566.1568415120373%40Atlassian.JIRA.
Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6
Title: Message Title Joshua Partlow commented on PDB-4373 Re: PDB has issues upgrading to versions later than 6.1 on centos6 Hi Austin, do you know what build of pdb this would be in now? 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.309068.155804266.97796.1568395320402%40Atlassian.JIRA.
Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6
Title: Message Title Joshua Partlow commented on PDB-4373 Re: PDB has issues upgrading to versions later than 6.1 on centos6 What build of puppetdb should we expect this changes in in 2019.2.x? 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.309068.155804266.77533.1567026660247%40Atlassian.JIRA.
Jira (BOLT-1397) The wait_until_available() function should return (or make accessible) details of why it timed out.
Title: Message Title Joshua Partlow commented on BOLT-1397 Re: The wait_until_available() function should return (or make accessible) details of why it timed out. Some notes from Cas: "I think that instead of batch_connected and connected? simply rescuing connection errors and returning false, they would need to pass along the connection error. https://github.com/puppetlabs/bolt/blob/b062fa3faed7fa8600ef17275a46933b37a12bc6/lib/bolt/transport/base.rb#L175 https://github.com/puppetlabs/bolt/blob/b062fa3faed7fa8600ef17275a46933b37a12bc6/lib/bolt/transport/ssh.rb#L79-L83 That way instead of the timeout error we could give the pass through the connection error." 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312526.1560550967000.48331.1560555180200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1397) The wait_until_available() function should return (or make accessible) details of why it timed out.
Title: Message Title Joshua Partlow created an issue Puppet Task Runner / BOLT-1397 The wait_until_available() function should return (or make accessible) details of why it timed out. Issue Type: Improvement Assignee: Unassigned Created: 2019/06/14 3:22 PM Priority: Normal Reporter: Joshua Partlow If a user has a basic connection problem, such as needing --no-host-key-check or --user=root, Bolt provides a useful error message explaining the problem. It would be nice if the error returned included the underlying reason for failure, or at least made it possible to find this via _catch_errors. Example of a host key error: jpartlow@work1804:~/work/src/enterprise_tasks$ bolt plan run enterprise_tasks::testing::install_pe master=n7il9hevr7qj949.delivery.puppetlabs.net tarball=/home/jpartlow/pe_builds/puppet-enterprise-2019.2.0-rc1-1 58-ga04d97d-ubuntu-18.04-amd64.tar Starting: plan enterprise_tasks::testing::install_pe
Jira (BOLT-57) Download a file
Title: Message Title Joshua Partlow commented on BOLT-57 Re: Download a file Ran into this ticket as well; need to synchronizing /etc/puppetlabs/enterprise between infrastructure nodes in a bolt plan run from a separate controller node. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.208527.1504138043000.45302.1560376801103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1142) Following bolt installation instructions on a PE node can be dangerous
Title: Message Title Joshua Partlow commented on BOLT-1142 Re: Following bolt installation instructions on a PE node can be dangerous From the perspective of PE's installer tooling, the agent version is fixed between installations; nothing manages the puppet-agent version until the next run of the installer script from the next version PE tarball. But if a repo source has more recent versions of puppet-agent and someone uses the package manager, for, say an os upgrade (PE-26356), then the agent can get upgraded unexpectedly, potentially breaking PE. (Mostly adding this note for my own reference and to tie the two tickets together). 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4280) Ensure PE upgrade will work properly with reports migration
Title: Message Title Joshua Partlow commented on PDB-4280 Re: Ensure PE upgrade will work properly with reports migration Austin Blatt I know nothing about how two puppetdb's negotiate a sync. Are there two cases here? 1. primary puppetdb wants to sync to the replica puppetdb, initiates contact with the replica 2. replica puppetdb wants to sync to the primary puppetdb, initiates contact with the primary In case #1, is it reasonably for puppetdb to check the status endpoint of the host it is going to sync with and stop if it is < 6.3 (assuming that's the API change version)? In case #2, is there a point where primary puppetdb, having been contacted to establish a sync, could again check the syncing nodes status endpoint and abort? Or is what you are saying that there is no negotiation, and a 'sync' is just one instance pushing a bunch of SQL to another? 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4280) Ensure PE upgrade will work properly with reports migration
Title: Message Title Joshua Partlow commented on PDB-4280 Re: Ensure PE upgrade will work properly with reports migration Nick Walker I have a 2019.1 primary and replica configured, and both have /etc/puppetlabs/puppetdb/conf.d/sync.ini. On the primary it's pointing to the replica, and on the replica it's pointing to the primary. primary: nptm5vsc0i0y618.delivery.puppetlabs.net replica: yyhgstm8f74vq91.delivery.puppetlabs.net The primary master's sync peers are set in the PE HA Master node group: https://yyhgstm8f74vq91.delivery.puppetlabs.net/#/configure/groups/13a5d374-ee67-4a91-ab1f-22321ea55d67/classes That system was from a `frankenbuilder 2019.1 --install --provision` 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4280) Ensure PE upgrade will work properly with reports migration
Title: Message Title Joshua Partlow commented on PDB-4280 Re: Ensure PE upgrade will work properly with reports migration Hmm, that's a good point; I see the problem now. I'll have to think about the z requirements. Nick Walker What are the upgrade requirements? We could possibly tighten that? 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4280) Ensure PE upgrade will work properly with reports migration
Title: Message Title Joshua Partlow commented on PDB-4280 Re: Ensure PE upgrade will work properly with reports migration What's the blocker preventing puppetdb from recognizing that it it's counterpart is a different version? 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4280) Ensure PE upgrade will work properly with reports migration
Title: Message Title Joshua Partlow commented on PDB-4280 Re: Ensure PE upgrade will work properly with reports migration Upgrade is one node at a time. The installer itself only handles upgrade of primary infrastructure (all the services that you would have a basic monolithic install of PE). In some configurations, you may have most services except postgres on one node, and a separately managed postgresql node. In older configurations, you might have separate primary master, puppetdb (and postgres), and console nodes. But I believe the specific installation we are concerned with are HA installations of PE, which, for the most part, look like a single monolithic primary and a single monolithic replica. There's a puppetdb instance backed to a postgres instance on each of those nodes. The replica is secondary infrastructure. It is not upgraded by the installer, but by a separate upgrade script. But, regardless, each node is upgraded individually by the admin running the installer on each node in sequence, or in the case of secondary infrastructure like the replica, running the upgrade script on that node after the primary infrastructure is upgraded and running fully again. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-8998) Remove Faces related to CA and certificate handling
Title: Message Title Joshua Partlow commented on PUP-8998 Re: Remove Faces related to CA and certificate handling Maggie Dreyer the pe_support_script module (part of pe-modules) calls puppet cert. cc Charlie Sharpsteen pe_install you already know about. I ack'd the pe-modules, but only found those two references. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
