Jira (PDB-5619) Publish release notes (Puppet Platform 7.24.0)
Title: Message Title Nick Burgan assigned an issue to Nick Burgan PuppetDB / PDB-5619 Publish release notes (Puppet Platform 7.24.0) Change By: Nick Burgan Assignee: Nick Burgan 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.483614.1679700066000.2352.1680306120023%40Atlassian.JIRA.
Jira (PDB-5618) Check builds, promote to PE (Puppet Platform 7.24.0)
Title: Message Title Nick Burgan assigned an issue to Nick Burgan PuppetDB / PDB-5618 Check builds, promote to PE (Puppet Platform 7.24.0) Change By: Nick Burgan Assignee: Nick Burgan 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.483613.1679700065000.2015.1680201720092%40Atlassian.JIRA.
Jira (PDB-5617) Bump versions, push directly, and tag (Puppet Platform 7.24.0)
Title: Message Title Nick Burgan assigned an issue to Nick Burgan PuppetDB / PDB-5617 Bump versions, push directly, and tag (Puppet Platform 7.24.0) Change By: Nick Burgan Assignee: Nick Burgan 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.483612.1679700065000.2013.1680201540026%40Atlassian.JIRA.
Jira (PDB-5614) Merge-up, branch, and create pipelines (Puppet Platform 7.24.0)
Title: Message Title Nick Burgan assigned an issue to Nick Burgan PuppetDB / PDB-5614 Merge-up, branch, and create pipelines (Puppet Platform 7.24.0) Change By: Nick Burgan Assignee: Nick Burgan 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.483609.1679700062000.1993.1680199800286%40Atlassian.JIRA.
Jira (PDB-5614) Merge-up, branch, and create pipelines (Puppet Platform 7.24.0)
Title: Message Title
Nick Burgan updated an issue
PuppetDB / PDB-5614
Merge-up, branch, and create pipelines (Puppet Platform 7.24.0)
Change By:
Nick Burgan
(Initial planned release date: 2023-04-04)Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS). * [jenkins: main|https://jenkins-enterprise.delivery.puppetlabs.net/view/puppetdb/view/main/]* [jenkins: 7.x|https://jenkins-enterprise.delivery.puppetlabs.net/view/puppetdb/view/7.x/]* [travis: puppetdb|https://app.travis-ci.com/github/puppetlabs/puppetdb/branches]* [travis: pe-puppetdb-extensions|https://app.travis-ci.com/github/puppetlabs/pe-puppetdb-extensions/branches]-Do merge-ups: - * - Merge 7.x -> main - - Important: Do this for both the core puppetdb repo and the pe-puppetdb-extensions repo! - - These should be submitted as PRs and merged after tests pass, if there's anything remotely interesting about the merges. If the merges are boring, then direct push is fine.-SKIP ALL REMAINING STEPS - We are leaving them here until wehave a better place to document the process to create a newbranch. When we release a new Y version we do it off of main andcut a maintained branch later (if at all).Then, prepare the branch for release: * If needed, create the branch (off of main, almost certainly)* Check that there aren't any essential updates to ezbake needed in this release* Update the branch in the README's Travis CI build icon link* Update the version in project.clj in both repos. Continue to use a -SNAPSHOT version for now* Push each branch *directly* to the puppetlabs github repo.Update ci-job-configs: * [ https://github.com/puppetlabs/ci-job-configs/blob/main/jenkii/enterprise/projects/puppetdb.yaml#L49-L52 ] * [ https://github.com/puppetlabs/ci-job-configs/blob/main/jenkii/enterprise/projects/puppetdb.yaml#L170-L180 ] * Add a new tab to Jenkins if needed: hit the + tab in the link here [ https://jenkins-enterprise.delivery.puppetlabs.net/view/puppetdb/ ] , select "list view", and add the following rule to the regex section that matches the build you're preparing. Example: (?!experimental).*puppetdb.*5.2.xUpdate travis to add a cron job for the new branch: * [ https://app.travis-ci.com/github/puppetlabs/puppetdb/settings ] * [ https://app.travis-ci.com/github/puppetlabs/pe-puppetdb-extensions/settings ] Update the headers in all the puppetdb docs: * changes need to be made to the puppet-docs repo. See [this PR|https://github.com/puppetlabs/puppet-docs/pull/888/files] for an example.Update travis integration test refs: * Once Puppet and PuppetServer have created their release branches, update our testing defaults and .travis.yml file to run integration tests against the new branches. Our strategy is to test the corresponding release branches of Puppet and PuppetServer and the previous release branches for each release branch of
Jira (PDB-5614) Merge-up, branch, and create pipelines (Puppet Platform 7.24.0)
Title: Message Title
Nick Burgan updated an issue
PuppetDB / PDB-5614
Merge-up, branch, and create pipelines (Puppet Platform 7.24.0)
Change By:
Nick Burgan
(Initial planned release date: 2023-04-04)Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).* [jenkins: main|https://jenkins-enterprise.delivery.puppetlabs.net/view/puppetdb/view/main/]* [jenkins: 7.x|https://jenkins-enterprise.delivery.puppetlabs.net/view/puppetdb/view/7.x/]* [travis: puppetdb|https://app.travis-ci.com/github/puppetlabs/puppetdb/branches]* [travis: pe-puppetdb-extensions|https://app.travis-ci.com/github/puppetlabs/pe-puppetdb-extensions/branches] - Do merge-ups:* Merge 7.x -> mainImportant: Do this for both the core puppetdb repo and thepe-puppetdb-extensions repo!These should be submitted as PRs and merged after tests pass, if there'sanything remotely interesting about the merges. If the merges are boring,then direct push is fine. - SKIP ALL REMAINING STEPS - We are leaving them here until wehave a better place to document the process to create a newbranch. When we release a new Y version we do it off of main andcut a maintained branch later (if at all).Then, prepare the branch for release:* If needed, create the branch (off of main, almost certainly)* Check that there aren't any essential updates to ezbake needed in this release* Update the branch in the README's Travis CI build icon link* Update the version in project.clj in both repos. Continue to use a -SNAPSHOT version for now* Push each branch *directly* to the puppetlabs github repo.Update ci-job-configs:* https://github.com/puppetlabs/ci-job-configs/blob/main/jenkii/enterprise/projects/puppetdb.yaml#L49-L52* https://github.com/puppetlabs/ci-job-configs/blob/main/jenkii/enterprise/projects/puppetdb.yaml#L170-L180* Add a new tab to Jenkins if needed: hit the + tab in the link here https://jenkins-enterprise.delivery.puppetlabs.net/view/puppetdb/, select "list view", and add the following rule to the regex section that matches the build you're preparing. Example: (?!experimental).*puppetdb.*5.2.xUpdate travis to add a cron job for the new branch:* https://app.travis-ci.com/github/puppetlabs/puppetdb/settings* https://app.travis-ci.com/github/puppetlabs/pe-puppetdb-extensions/settingsUpdate the headers in all the puppetdb docs:* changes need to be made to the puppet-docs repo. See [this PR|https://github.com/puppetlabs/puppet-docs/pull/888/files] for an example.Update travis integration test refs:* Once Puppet and PuppetServer have created their release branches, update our testing defaults and .travis.yml file to run integration tests against the new branches. Our strategy is to test the corresponding release branches of Puppet and PuppetServer and the previous release branches for each release branch of PuppetDB.* ext/test-conf/puppet-ref-default and
Jira (PDB-5482) Log query PQL text (when available) when log-queries is true
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-5482 Log query PQL text (when available) when log-queries is true Change By: Nick Burgan Sprint: Froyo - 4/27/2022, Dumpling 7-5-22 , Dumpling 7-19-22 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.443535.1649866678000.57920.1657041480053%40Atlassian.JIRA.
Jira (PUP-11435) Puppet 6.26 and 7.13 may
Title: Message Title
Nick Burgan updated an issue
Puppet / PUP-11435
Puppet 6.26 and 7.13 may
Change By:
Nick Burgan
Commit 78246ca8d08dee770886f0940a6472c45483d627 first released in 6.26.0 and 7.13.0 speeds up rspec tests but breaks puppet-enteprise-modules due to the way {{Facter.reset}} breaks stubbing for a custom fact. https://github.com/puppetlabs/puppet/commit/78246ca8d08dee770886f0940a6472c45483d627
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.432469.164315863.2118.1643236800069%40Atlassian.JIRA.
Jira (PUP-11435) Puppet 6.26 and 7.13 may cause specs to fail
Title: Message Title Nick Burgan updated an issue Puppet / PUP-11435 Puppet 6.26 and 7.13 may cause specs to fail Change By: Nick Burgan Summary: Puppet 6.26 and 7.13 maycause specs to fail Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.432469.164315863.2119.1643236800133%40Atlassian.JIRA.
Jira (PUP-11435) Puppet 6.26 and 7.13 may
Title: Message Title Nick Burgan commented on PUP-11435 Re: Puppet 6.26 and 7.13 may Found more instances of this cropping up. When we want to use our own test facts, the facter.reset seems to change things to have it start reading facts from the node you are running tests on instead. For example, https://github.com/puppetlabs/puppet-enterprise-modules/blob/main/modules/pe_install/spec/hosts/monolithic_spec.rb is loading up a set of facts from rspec-puppet-facts for different OS types and doing let(:facts} to set them (https://github.com/puppetlabs/puppet-enterprise-modules/blob/main/modules/pe_install/spec/shared/contexts.rb#L11-L18). At https://github.com/puppetlabs/puppet-enterprise-modules/blob/main/modules/pe_install/spec/hosts/monolithic_spec.rb#L267 which runs https://github.com/puppetlabs/puppet-enterprise-modules/blob/main/modules/pe_install/spec/hosts/monolithic_spec.rb#L4-L6, the first compile uses the test's facts, but the second one ends up picking up the test runner node's facts, I assume because the facter.reset happened in there somewhere. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.432469.164315863.2093.1643235300381%40Atlassian.JIRA.
Jira (PUP-10884) 'puppet facts show' gives conversion error on 6.x agent
Title: Message Title Nick Burgan updated an issue Puppet / PUP-10884 'puppet facts show' gives conversion error on 6.x agent Change By: Nick Burgan Comment: -Is this a recent change? We are using `puppet facts show` in a job in CI, and it just started failing due to this.-Disregard, I was mistaken. This was a recent addition to our test. 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.385667.1612200398000.134820.1612556820247%40Atlassian.JIRA.
Jira (PUP-10884) 'puppet facts show' gives conversion error on 6.x agent
Title: Message Title Nick Burgan commented on PUP-10884 Re: 'puppet facts show' gives conversion error on 6.x agent Is this a recent change? We are using `puppet facts show` in a job in CI, and it just started failing due to this. 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.385667.1612200398000.134809.1612556640045%40Atlassian.JIRA.
Jira (PUP-10884) 'puppet facts show' gives conversion error on 6.x agent
Title: Message Title Nick Burgan commented on PUP-10884 Re: 'puppet facts show' gives conversion error on 6.x agent It appears to be this: https://github.com/puppetlabs/puppet/blob/6.x/lib/puppet/indirector/face.rb#L78-L84 [8] pry(#)> whereami From: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/face.rb:85 Puppet::Indirector::Face#find implementation, required on Ruby 1.8: 76: when_invoked do |*args| 77: # Default the key to Puppet[:certname] if none is supplied 78: if args.length == 1 79: key = Puppet[:certname] 80: options = args.last 81: else 82: key, options = *args 83: end 84: require 'pry-byebug';binding.pry
Jira (PUP-10884) 'puppet facts show' gives conversion error on 6.x agent
Title: Message Title Nick Burgan updated an issue Puppet / PUP-10884 'puppet facts show' gives conversion error on 6.x agent Change By: Nick Burgan Summary: 'puppet facts show' always gives conversion error on 6.x agent 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.385667.1612200398000.129492.1612200720143%40Atlassian.JIRA.
Jira (PUP-10884) 'puppet facts show' always gives conversion error
Title: Message Title
Nick Burgan updated an issue
Puppet / PUP-10884
'puppet facts show' always gives conversion error
Change By:
Nick Burgan
*Puppet Version:* 6.20.0*Puppet Server Version:* 2019.8.x latest*OS Name/Version:* Centos 7When running 'puppet facts show ', if fact_name doesn't exist, rather than the it seems to always give a conversion error saying so, you get . {code}[root@cute-remainder ~]# puppet facts show abcd operatingsystem Error: no implicit conversion of Symbol into IntegerError: Try 'puppet help facts find' for usage{code} Whereas on Appears to be limited to 6.x, as 7.x you get{code}[root@choosy-trio ~]# puppet facts show abcd{ “abcd”: “”}{code}*Desired Behavior:*Either a blank value is returned, or an error is given that tells still showing the user the appropriate fact doesn't exist . *Actual Behavior:*Symbol to integer conversion error
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed
Jira (PUP-10884) 'puppet facts show' always gives conversion error
Title: Message Title Nick Burgan updated an issue Puppet / PUP-10884 'puppet facts show' always gives conversion error Change By: Nick Burgan Summary: Using 'puppet facts show' with a fact that doesn't exist always gives conversion error 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.385667.1612200398000.129488.1612200660094%40Atlassian.JIRA.
Jira (PUP-10884) Using 'puppet facts show' with a fact that doesn't exist gives conversion error
Title: Message Title Nick Burgan created an issue Puppet / PUP-10884 Using 'puppet facts show' with a fact that doesn't exist gives conversion error Issue Type: Bug Affects Versions: PUP 6.20.0 Assignee: Unassigned Created: 2021/02/01 9:26 AM Priority: Normal Reporter: Nick Burgan Puppet Version: 6.20.0 Puppet Server Version: 2019.8.x latest OS Name/Version: Centos 7 When running 'puppet facts show ', if fact_name doesn't exist, rather than the error saying so, you get [root@cute-remainder ~]# puppet facts show abcd Error: no implicit conversion of Symbol into Integer Error: Try 'puppet help facts find' for usage Whereas on 7.x you get
Jira (PUP-10851) Error "Entry 'allow *' is unsupported and will be ignored" shown during PE upgrade
Title: Message Title Nick Burgan created an issue Puppet / PUP-10851 Error "Entry 'allow *' is unsupported and will be ignored" shown during PE upgrade Issue Type: Task Assignee: Unassigned Created: 2021/01/12 3:11 PM Priority: Normal Reporter: Nick Burgan The error Entry 'allow *' is unsupported and will be ignored shows up when upgrading to PE 2021 with Puppet 7. Since the file is managed to remove this entry once the puppet run that upgrades the primary completes (https://github.com/puppetlabs/puppet-enterprise-modules/commit/e7659a96562dced9fdd09b850c5a7947bed7043c), it would be great to be able to either suppress this message, or remove it if it is unnecessary. Add Comment This message was
Jira (PDB-4872) Provide certificate-allowlist and facts-blocklist as config aliases
Title: Message Title Nick Burgan commented on PDB-4872 Re: Provide certificate-allowlist and facts-blocklist as config aliases Things in the modules that will need changes when this is implemented (double check I didn't miss any, though): https://github.com/puppetlabs/puppet-enterprise-modules/blob/master/modules/puppet_enterprise/manifests/puppetdb/database_ini.pp#L112 https://github.com/puppetlabs/puppet-enterprise-modules/blob/master/modules/puppet_enterprise/manifests/puppetdb/database_ini.pp#L117 https://github.com/puppetlabs/puppet-enterprise-modules/blob/d63b11863f7c3b016e0c78cb5709cc5c841da042/modules/puppet_enterprise/manifests/profile/puppetdb.pp#L82 https://github.com/puppetlabs/puppet-enterprise-modules/blob/07a1ba6d5bd88c39fd4c3e8700737ac57c372eff/modules/puppet_enterprise/manifests/puppetdb/jetty_ini.pp#L130 https://github.com/puppetlabs/puppet-enterprise-modules/blob/master/modules/puppet_enterprise/manifests/certs/puppetdb_allowlist.pp#L24 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
Jira (PUP-10573) Add metaparameter to flush/refetch resource information
Title: Message Title
Nick Burgan updated an issue
Puppet / PUP-10573
Add metaparameter to flush/refetch resource information
Change By:
Nick Burgan
Some resource types can have an effect on other types, such as {{yumrepo}} and {{package}}. In this example, when a {{package}} resource is encountered in a catalog, puppet prefetches package version information from the package provider. However, if a {{yumrepo}} resource (or perhaps a {{file}} resource for apt or {{ini_setting}} resource for zypper) then changes the underlying repo that other packages come from, even if that first applied package is entirely unrelated, puppet will not refetch package information and end up using stale information for the application of later package resources. This was the bug in PE-28931. Having a metaparameter, something like {{invalidate_prefetch}} or {{flush_type}}, that takes a resource type and tells Puppet to flush its cached information for that type and refetch it, would mitigate this problem. It would probably only need to be performed if the resource was applying corrective changes.{code:java} file { '/etc/yum.repos.d/foo.repo': ensure => present, source => 'puppet:///modules/foo.repo', invalidate_prefetch => Package,}{code} While it is possible to ensure, say, {{yumrepo}} resources come before all {{package}} resources via a resource collector, usage of these collectors is not always ideal (or in the case of PE management code, we can't just collect all packages due to our use of virtual resources).In general, this is a constraint in Puppet's ability to easily model desired state. If one {{package}} resource is entirely unrelated to other {{yumrepo}} / {{package}} resources, it should not have an effect on them.
Add Comment
Jira (PUP-10573) Add metaparameter to flush/refetch resource information
Title: Message Title
Nick Burgan created an issue
Puppet / PUP-10573
Add metaparameter to flush/refetch resource information
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2020/07/01 4:36 PM
Priority:
Normal
Reporter:
Nick Burgan
Some resource types can have an effect other types, such as yumrepo and package. In this example, when a package resource is encountered in a catalog, puppet prefetches package version information from the package provider. However, if a yumrepo resource (or perhaps a file resource for apt or ini_setting resource for zypper) then changes the underlying repo that other packages come from, even if that first applied package is entirely unrelated, puppet will not refetch package information and end up using stale information for the application of later package resources. This was the bug in PE-28931. Having a metaparameter, something like invalidate_prefetch or flush_type, that takes a resource type and tells Puppet to flush its cached information for that type and refetch it, would mitigate this problem. It would probably only need to be performed if the resource was applying corrective changes.
file { '/etc/yum.repos.d/foo.repo':
ensure => present,
source => 'puppet:///modules/foo.repo',
Jira (PDB-4707) Provide a subcommand to list the available migrations
Title: Message Title Nick Burgan commented on PDB-4707 Re: Provide a subcommand to list the available migrations If we can get PE-28943 done through the pe_install::upgrade::puppetdb class, we shouldn't need this command. 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.356932.1588029202000.63001.1589492520139%40Atlassian.JIRA.
Jira (PDB-4682) PuppetDB sync status doesn't get updated when finished
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4682 PuppetDB sync status doesn't get updated when finished Change By: Nick Burgan 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.354044.1585853662000.44423.1587579600068%40Atlassian.JIRA.
Jira (PDB-4637) Lock out the puppetdb data user during migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4637 Lock out the puppetdb data user during migration Change By: Nick Burgan Story Points: 2 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.343744.1580162942000.44418.1587579481320%40Atlassian.JIRA.
Jira (PDB-4637) Lock out the puppetdb data user during migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4637 Lock out the puppetdb data user during migration Change By: Nick Burgan Sprint: HA Team 2020-03-11, HA Team 2020-03-25, HA Team 2020-04-08, HA Team 2020-04-22 (SS 4/15) , HA Team 2020-05-05 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.343744.1580162942000.44389.1587579240057%40Atlassian.JIRA.
Jira (PDB-4682) PuppetDB sync status doesn't get updated when finished
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4682 PuppetDB sync status doesn't get updated when finished Change By: Nick Burgan Sprint: HA Team 2020-04-22 (SS 4/15) , HA Team 2020-05-05 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.354044.1585853662000.44390.1587579240100%40Atlassian.JIRA.
Jira (PDB-4675) Deadlock when creating/inserting into a new report partition
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4675 Deadlock when creating/inserting into a new report partition Change By: Nick Burgan Story Points: 3 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.350469.1584566547000.33959.1586370480360%40Atlassian.JIRA.
Jira (PDB-4678) PuppetDB cannot make DB connections when javax.net.ssl.trustStore is used
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4678 PuppetDB cannot make DB connections when javax.net.ssl.trustStore is used Change By: Nick Burgan Story Points: 2 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.351066.158509873.33960.1586370480403%40Atlassian.JIRA.
Jira (PDB-4644) If unset, resource-events-ttl should track report-ttl
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4644 If unset, resource-events-ttl should track report-ttl Change By: Nick Burgan Sprint: HA Team 2020-02-26, HA Team 2020-03-25, HA Team 2020-04-08 , HA Team 2020-04-22 (SS 4/15) 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.345022.1580840958000.33947.1586370240132%40Atlassian.JIRA.
Jira (PDB-4637) Lock out the puppetdb data user during migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4637 Lock out the puppetdb data user during migration Change By: Nick Burgan Sprint: HA Team 2020-03-11, HA Team 2020-03-25, HA Team 2020-04-08 , HA Team 2020-04-22 (SS 4/15) 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.343744.1580162942000.33948.1586370240175%40Atlassian.JIRA.
Jira (PDB-4676) Investigate OOM errors during the report partitioning migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4676 Investigate OOM errors during the report partitioning migration Change By: Nick Burgan Sprint: HA Team 2020-04-08 , HA Team 2020-04-22 (SS 4/15) 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.350711.1584735864000.33946.1586370240087%40Atlassian.JIRA.
Jira (PDB-4675) Deadlock when creating/inserting into a new report partition
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4675 Deadlock when creating/inserting into a new report partition Change By: Nick Burgan Sprint: HA Team 2020-04-08 , HA Team 2020-04-22 (SS 4/15) 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.350469.1584566547000.33949.1586370240219%40Atlassian.JIRA.
Jira (PDB-4678) PuppetDB cannot make DB connections when javax.net.ssl.trustStore is used
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4678 PuppetDB cannot make DB connections when javax.net.ssl.trustStore is used Change By: Nick Burgan Sprint: HA Team 2020-04-08 , HA Team 2020-04-22 (SS 4/15) 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.351066.158509873.33950.1586370240263%40Atlassian.JIRA.
Jira (PUP-10401) Pip package provider outputs warning on puppet run
Title: Message Title Nick Burgan created an issue Puppet / PUP-10401 Pip package provider outputs warning on puppet run Issue Type: Bug Assignee: Unassigned Created: 2020/03/30 3:55 PM Priority: Normal Reporter: Nick Burgan Puppet Version: 6.14.0.135.gaf1499b7 (but may have started happening in earlier builds) Puppet Server Version: N/A, but using latest PE master build (rc2-37) OS Name/Version: centos 6, sles 12, ubuntu 18.04 When doing a puppet agent -t run, the following warnings are printed. /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:18: warning: already initialized constant PIP_VERSION /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:18: warning: previous definition of PIP_VERSION was here /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:19: warning: already initialized constant PIP_VERSION_RANGE /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:19: warning: previous definition of PIP_VERSION_RANGE was here
Jira (PDB-4172) Allow metrics during startup
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4172 Allow metrics during startup Change By: Nick Burgan Sprint: HA Team (Ready For Work) 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.282135.1540387252000.23860.1585591560088%40Atlassian.JIRA.
Jira (PDB-4172) Allow metrics during startup
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4172 Allow metrics during startup Change By: Nick Burgan Story Points: 5 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.282135.1540387252000.23859.1585591560044%40Atlassian.JIRA.
Jira (PDB-4157) Review impact of connection limits in clj-http-client
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4157 Review impact of connection limits in clj-http-client Change By: Nick Burgan Sprint: HA Team (Ready For Work) 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.280669.1539661927000.23856.1585591440084%40Atlassian.JIRA.
Jira (PDB-4157) Review impact of connection limits in clj-http-client
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4157 Review impact of connection limits in clj-http-client Change By: Nick Burgan Story Points: 5 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.280669.1539661927000.23855.1585591440039%40Atlassian.JIRA.
Jira (PDB-4644) If unset, resource-events-ttl should track report-ttl
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4644 If unset, resource-events-ttl should track report-ttl Change By: Nick Burgan Fix Version/s: PDB 6.10.0 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.345022.1580840958000.20774.1585160160029%40Atlassian.JIRA.
Jira (PDB-4676) Investigate OOM errors during the report partitioning migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4676 Investigate OOM errors during the report partitioning migration Change By: Nick Burgan Sprint: HA Team (Ready For Work) 2020-04-08 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.350711.1584735864000.20772.1585159860025%40Atlassian.JIRA.
Jira (PDB-4675) Deadlock when creating/inserting into a new report partition
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4675 Deadlock when creating/inserting into a new report partition Change By: Nick Burgan Fix Version/s: PDB 6.10.0 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.350469.1584566547000.20771.1585159800099%40Atlassian.JIRA.
Jira (PDB-4675) Deadlock when creating/inserting into a new report partition
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4675 Deadlock when creating/inserting into a new report partition Change By: Nick Burgan 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.350469.1584566547000.20770.1585159800045%40Atlassian.JIRA.
Jira (PDB-4644) If unset, resource-events-ttl should track report-ttl
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4644 If unset, resource-events-ttl should track report-ttl Change By: Nick Burgan Story Points: 2 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.345022.1580840958000.20762.1585159560027%40Atlassian.JIRA.
Jira (PDB-4644) If unset, resource-events-ttl should track report-ttl
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4644 If unset, resource-events-ttl should track report-ttl Change By: Nick Burgan Sprint: HA Team 2020-02-26, HA Team 2020-03-25 , HA Team 2020-04-08 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.345022.1580840958000.20757.1585159440047%40Atlassian.JIRA.
Jira (PDB-4637) Lock out the puppetdb data user during migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4637 Lock out the puppetdb data user during migration Change By: Nick Burgan Sprint: HA Team 2020-03-11, HA Team 2020-03-25 , HA Team 2020-04-08 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.343744.1580162942000.20758.1585159440092%40Atlassian.JIRA.
Jira (PDB-4172) Allow metrics during startup
Title: Message Title Nick Burgan commented on PDB-4172 Re: Allow metrics during startup May not be as urgent now that initial sync doesn't take long with streaming provision. However, if we still want metrics during potentially long migrations (e.g. report table migration), we might still want to look into this. Dylan Ratcliffe What do you think? 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.282135.1540387252000.18275.1584988140076%40Atlassian.JIRA.
Jira (PDB-4654) Adjust PDB config to allow for multiple write dbs
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4654 Adjust PDB config to allow for multiple write dbs Change By: Nick Burgan Sprint: HA Team (Ready For Work) 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.347165.1582246233000.18243.1584987420151%40Atlassian.JIRA.
Jira (PDB-4654) Adjust PDB config to allow for multiple write dbs
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4654 Adjust PDB config to allow for multiple write dbs Change By: Nick Burgan 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.347165.1582246233000.18242.1584987420107%40Atlassian.JIRA.
Jira (PDB-4659) Create acceptance tests that simulate PDB command broadcast
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4659 Create acceptance tests that simulate PDB command broadcast Change By: Nick Burgan 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.347259.1582314337000.18239.1584987240047%40Atlassian.JIRA.
Jira (PDB-4659) Create acceptance tests that simulate PDB command broadcast
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4659 Create acceptance tests that simulate PDB command broadcast Change By: Nick Burgan Sprint: HA Team (Ready For Work) 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.347259.1582314337000.18240.1584987240103%40Atlassian.JIRA.
Jira (PDB-4658) Audit how command broadcast changes will affect metrics and the dlo
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4658 Audit how command broadcast changes will affect metrics and the dlo Change By: Nick Burgan 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.347256.1582313765000.18237.1584987120045%40Atlassian.JIRA.
Jira (PDB-4658) Audit how command broadcast changes will affect metrics and the dlo
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4658 Audit how command broadcast changes will affect metrics and the dlo Change By: Nick Burgan Sprint: HA Team (Ready For Work) 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.347256.1582313765000.18238.1584987120089%40Atlassian.JIRA.
Jira (PDB-4656) Adjust PDB ingest to submit commands to multiple DBs
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4656 Adjust PDB ingest to submit commands to multiple DBs Change By: Nick Burgan Story Points: 5 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.347208.1582247529000.18235.1584987060203%40Atlassian.JIRA.
Jira (PDB-4655) Audit error handling/shutdown behavior when PDB is in broadcast mode
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4655 Audit error handling/shutdown behavior when PDB is in broadcast mode Change By: Nick Burgan Sprint: HA Team (Ready For Work) 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.347207.1582246732000.18233.1584987060111%40Atlassian.JIRA.
Jira (PDB-4656) Adjust PDB ingest to submit commands to multiple DBs
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4656 Adjust PDB ingest to submit commands to multiple DBs Change By: Nick Burgan Sprint: HA Team (Ready For Work) 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.347208.1582247529000.18236.1584987060247%40Atlassian.JIRA.
Jira (PDB-4656) Adjust PDB ingest to submit commands to multiple DBs
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4656 Adjust PDB ingest to submit commands to multiple DBs Change By: Nick Burgan Story Points: 5 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.347208.1582247529000.18234.1584987060156%40Atlassian.JIRA.
Jira (PDB-4655) Audit error handling/shutdown behavior when PDB is in broadcast mode
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4655 Audit error handling/shutdown behavior when PDB is in broadcast mode Change By: Nick Burgan 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.347207.1582246732000.18231.158498726%40Atlassian.JIRA.
Jira (PDB-4676) Investigate OOM errors during the report partitioning migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4676 Investigate OOM errors during the report partitioning migration Change By: Nick Burgan Sprint: HA Team (Ready For Work) 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.350711.1584735864000.18229.1584986940051%40Atlassian.JIRA.
Jira (PDB-4676) Investigate OOM errors during the report partitioning migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4676 Investigate OOM errors during the report partitioning migration Change By: Nick Burgan Fix Version/s: PDB 6.10.0 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.350711.1584735864000.18230.1584986940095%40Atlassian.JIRA.
Jira (PDB-4676) Investigate OOM errors during the report partitioning migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4676 Investigate OOM errors during the report partitioning migration Change By: Nick Burgan Story Points: 5 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.350711.1584735864000.18228.1584986880083%40Atlassian.JIRA.
Jira (PDB-4637) Lock out the puppetdb data user during migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4637 Lock out the puppetdb data user during migration Change By: Nick Burgan Story Points: 3 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.343744.1580162942000.10275.1583950260107%40Atlassian.JIRA.
Jira (PDB-4672) Add at-at periodic monitor to check for migration mismatch
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4672 Add at-at periodic monitor to check for migration mismatch Change By: Nick Burgan Story Points: 3 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.348442.1583265198000.10273.1583950260048%40Atlassian.JIRA.
Jira (PDB-4639) Add connection init check to Hikari pools
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4639 Add connection init check to Hikari pools Change By: Nick Burgan Story Points: 2 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.343754.1580164659000.10274.1583950260103%40Atlassian.JIRA.
Jira (PDB-4637) Lock out the puppetdb data user during migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4637 Lock out the puppetdb data user during migration Change By: Nick Burgan Sprint: HA Team 2020-03-11 , HA Team 2020-03-25 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.343744.1580162942000.10254.1583949840199%40Atlassian.JIRA.
Jira (PDB-4672) Add at-at periodic monitor to check for migration mismatch
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4672 Add at-at periodic monitor to check for migration mismatch Change By: Nick Burgan Sprint: HA Team 2020-03-11 , HA Team 2020-03-25 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.348442.1583265198000.10252.1583949840112%40Atlassian.JIRA.
Jira (PDB-4639) Add connection init check to Hikari pools
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4639 Add connection init check to Hikari pools Change By: Nick Burgan Sprint: HA Team 2020-03-11 , HA Team 2020-03-25 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.343754.1580164659000.10253.1583949840156%40Atlassian.JIRA.
Jira (PDB-4637) Lock out the puppetdb data user during migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4637 Lock out the puppetdb data user during migration Change By: Nick Burgan Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343744.1580162942000.1006.1582745280335%40Atlassian.JIRA.
Jira (PDB-4639) Add connection init check to Hikari pools
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4639 Add connection init check to Hikari pools Change By: Nick Burgan Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343754.1580164659000.1002.1582745220367%40Atlassian.JIRA.
Jira (PDB-4636) Add migrate configuration option
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4636 Add migrate configuration option Change By: Nick Burgan Story Points: 2 3 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343741.1580162292000.966.1582744620228%40Atlassian.JIRA.
Jira (PDB-4644) If unset, resource-events-ttl should track report-ttl
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4644 If unset, resource-events-ttl should track report-ttl Change By: Nick Burgan Sprint: HA Team 2020-02-26, HA Team 2020-03- 11 25 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.345022.1580840958000.852.1582744140247%40Atlassian.JIRA.
Jira (PDB-4636) Add migrate configuration option
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4636 Add migrate configuration option Change By: Nick Burgan Sprint: HA Team 2020-02-12, HA Team 2020-02-26 , HA Team 2020-03-11 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.343741.1580162292000.839.1582744080923%40Atlassian.JIRA.
Jira (PDB-4644) If unset, resource-events-ttl should track report-ttl
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4644 If unset, resource-events-ttl should track report-ttl Change By: Nick Burgan Sprint: HA Team 2020-02-26 , HA Team 2020-03-11 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.345022.1580840958000.843.1582744081163%40Atlassian.JIRA.
Jira (PDB-4644) If unset, resource-events-ttl should track report-ttl
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4644 If unset, resource-events-ttl should track report-ttl Change By: Nick Burgan Acceptance Criteria: * When unset in database.ini, resource-events-ttl follows report-ttl 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.345022.1580840958000.23927.1581534840460%40Atlassian.JIRA.
Jira (PDB-4644) If unset, resource-events-ttl should track report-ttl
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4644 If unset, resource-events-ttl should track report-ttl Change By: Nick Burgan Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.345022.1580840958000.23923.1581534782163%40Atlassian.JIRA.
Jira (PDB-2423) Limit initial sync to catalogs, factsets, and deactivate node commands
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-2423 Limit initial sync to catalogs, factsets, and deactivate node commands Change By: Nick Burgan Sprint: HA Team 2020-01-29, HA Team 2020-02-12 , HA Team 2020-02-26 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.116056.1455149697000.23796.1581534302134%40Atlassian.JIRA.
Jira (PDB-3751) PDB Sync should allow a separate setting for the maximum amount of reports to sync
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-3751 PDB Sync should allow a separate setting for the maximum amount of reports to sync Change By: Nick Burgan Sprint: HA Team 2020-01-29, HA Team 2020-02-12 , HA Team 2020-02-26 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.220818.1510072105000.23805.1581534302432%40Atlassian.JIRA.
Jira (PDB-4636) Add migrate configuration option
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4636 Add migrate configuration option Change By: Nick Burgan Sprint: HA Team 2020-02-12 , HA Team 2020-02-26 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.343741.1580162292000.23819.1581534302675%40Atlassian.JIRA.
Jira (PDB-4636) Add configration option migrate
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4636 Add configration option migrate Change By: Nick Burgan Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343741.1580162292000.5331.1580326620311%40Atlassian.JIRA.
Jira (PDB-4638) Move migrations into a single transaction
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4638 Move migrations into a single transaction Change By: Nick Burgan Sprint: HA Team 2020-02-12 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.343751.1580164488000.5323.1580326500341%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Nick Burgan Sprint: HA Team 2020-01-15, HA Team 2020-01-29 , HA Team 2020-02-12 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.5201.1580324640855%40Atlassian.JIRA.
Jira (PDB-3751) PDB Sync should allow a separate setting for the maximum amount of reports to sync
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-3751 PDB Sync should allow a separate setting for the maximum amount of reports to sync Change By: Nick Burgan Sprint: HA Team 2020-01-29 , HA Team 2020-02-12 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.220818.1510072105000.5216.1580324641479%40Atlassian.JIRA.
Jira (PDB-2423) Limit initial sync to catalogs, factsets, and deactivate node commands
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-2423 Limit initial sync to catalogs, factsets, and deactivate node commands Change By: Nick Burgan Sprint: HA Team 2020-01-29 , HA Team 2020-02-12 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.116056.1455149697000.5210.1580324641212%40Atlassian.JIRA.
Jira (PDB-3751) PDB Sync should allow a separate setting for the maximum amount of reports to sync
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-3751 PDB Sync should allow a separate setting for the maximum amount of reports to sync Change By: Nick Burgan Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.220818.1510072105000.25426.1579116540911%40Atlassian.JIRA.
Jira (PDB-3751) PDB Sync should allow a separate setting for the maximum amount of reports to sync
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-3751 PDB Sync should allow a separate setting for the maximum amount of reports to sync Change By: Nick Burgan Release Notes: Enhancement 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.220818.1510072105000.25432.1579116541183%40Atlassian.JIRA.
Jira (PDB-3751) PDB Sync should allow a separate setting for the maximum amount of reports to sync
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-3751 PDB Sync should allow a separate setting for the maximum amount of reports to sync Change By: Nick Burgan Sprint: HA Team 2020-01-29 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.220818.1510072105000.25421.1579116540691%40Atlassian.JIRA.
Jira (PDB-2423) Limit initial sync to catalogs, factsets, and deactivate node commands
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-2423 Limit initial sync to catalogs, factsets, and deactivate node commands Change By: Nick Burgan Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.116056.1455149697000.25418.1579116481039%40Atlassian.JIRA.
Jira (PDB-2423) Limit initial sync to catalogs, factsets, and deactivate node commands
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-2423 Limit initial sync to catalogs, factsets, and deactivate node commands Change By: Nick Burgan Release Notes: Enhancement 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.116056.1455149697000.25409.1579116480679%40Atlassian.JIRA.
Jira (PDB-2423) Limit initial sync to catalogs, factsets, and deactivate node commands
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-2423 Limit initial sync to catalogs, factsets, and deactivate node commands Change By: Nick Burgan Sprint: HA Team 2020-01-29 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.116056.1455149697000.25398.1579116420623%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Nick Burgan Sprint: HA Team 2020-01-15 , HA Team 2020-01-29 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.25250.1579115401336%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Nick Burgan Sprint: HA Team 2019-12-18 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.54262.1575487560412%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Nick Burgan Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320599.1565648011000.54255.1575487500333%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Nick Burgan Release Notes: Bug Fix 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.54249.1575487440931%40Atlassian.JIRA.
Jira (PUP-9746) Puppet ssl submit_request does not translate custom oids correctly
Title: Message Title Nick Burgan commented on PUP-9746 Re: Puppet ssl submit_request does not translate custom oids correctly Can this go into 6.0.x as well, since `puppet ssl` is present there too? 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.311950.1560208202000.43199.1560295080459%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
