Jira (PDB-4573) Update winston (PuppetDB 6.7.2)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4573 Update winston (PuppetDB 6.7.2) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:48 PM Due Date: 2019/10/23 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4570) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.7.2)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4570 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.7.2) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:47 PM Due Date: 2019/10/15 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PDB-4572) Check builds, promote to PE (PuppetDB 6.7.2)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4572 Check builds, promote to PE (PuppetDB 6.7.2) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:48 PM Due Date: 2019/10/18 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4571) Bump versions, push directly, and tag (PuppetDB 6.7.2)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4571 Bump versions, push directly, and tag (PuppetDB 6.7.2) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:47 PM Due Date: 2019/10/18 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in
Jira (PDB-4569) Merge-up, branch, and create pipelines (PuppetDB 6.7.2)
Title: Message Title
Nirupama Mantha created an issue
PuppetDB / PDB-4569
Merge-up, branch, and create pipelines (PuppetDB 6.7.2)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/10/22 6:47 PM
Due Date:
2019/10/15
Priority:
Normal
Reporter:
Nirupama Mantha
(Initial planned release date: 2019-10-22) 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).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> 6.3.x
Merge
Jira (PDB-4568) PuppetDB 6.7.2 2019-10-22 Release
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4568 PuppetDB 6.7.2 2019-10-22 Release Issue Type: Epic Assignee: Austin Blatt Created: 2019/10/22 6:47 PM Priority: Normal Reporter: Nirupama Mantha PuppetDB 6.7.2 2019-10-22 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4566) Check builds, promote to PE (PuppetDB 6.3.6)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4566 Check builds, promote to PE (PuppetDB 6.3.6) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:46 PM Due Date: 2019/10/18 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4567) Update winston (PuppetDB 6.3.6)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4567 Update winston (PuppetDB 6.3.6) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:46 PM Due Date: 2019/10/23 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4564) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.6)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4564 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.6) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:45 PM Due Date: 2019/10/15 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PDB-4565) Bump versions, push directly, and tag (PuppetDB 6.3.6)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4565 Bump versions, push directly, and tag (PuppetDB 6.3.6) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:45 PM Due Date: 2019/10/18 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in
Jira (PDB-4563) Merge-up, branch, and create pipelines (PuppetDB 6.3.6)
Title: Message Title
Nirupama Mantha created an issue
PuppetDB / PDB-4563
Merge-up, branch, and create pipelines (PuppetDB 6.3.6)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/10/22 6:45 PM
Due Date:
2019/10/15
Priority:
Normal
Reporter:
Nirupama Mantha
(Initial planned release date: 2019-10-22) 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).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> 6.3.x
Merge
Jira (PDB-4562) PuppetDB 6.3.6 2019-10-22 Release
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4562 PuppetDB 6.3.6 2019-10-22 Release Issue Type: Epic Assignee: Austin Blatt Created: 2019/10/22 6:45 PM Priority: Normal Reporter: Nirupama Mantha PuppetDB 6.3.6 2019-10-22 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4560) Check builds, promote to PE (PuppetDB 5.2.11)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4560 Check builds, promote to PE (PuppetDB 5.2.11) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:30 PM Due Date: 2019/10/18 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4561) Update winston (PuppetDB 5.2.11)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4561 Update winston (PuppetDB 5.2.11) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:30 PM Due Date: 2019/10/23 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4559) Bump versions, push directly, and tag (PuppetDB 5.2.11)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4559 Bump versions, push directly, and tag (PuppetDB 5.2.11) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:30 PM Due Date: 2019/10/18 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in
Jira (PDB-4558) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.11)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4558 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.11) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/22 6:30 PM Due Date: 2019/10/15 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-22) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PDB-4556) PuppetDB 5.2.11 2019-10-22 Release
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4556 PuppetDB 5.2.11 2019-10-22 Release Issue Type: Epic Assignee: Austin Blatt Created: 2019/10/22 6:29 PM Priority: Normal Reporter: Nirupama Mantha PuppetDB 5.2.11 2019-10-22 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4557) Merge-up, branch, and create pipelines (PuppetDB 5.2.11)
Title: Message Title
Nirupama Mantha created an issue
PuppetDB / PDB-4557
Merge-up, branch, and create pipelines (PuppetDB 5.2.11)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/10/22 6:29 PM
Due Date:
2019/10/15
Priority:
Normal
Reporter:
Nirupama Mantha
(Initial planned release date: 2019-10-22) 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).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> 6.3.x
Merge
Jira (PDB-4540) DNS_ALT_NAMES set by docker puppetdb >= 6.6.0
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4540 DNS_ALT_NAMES set by docker puppetdb >= 6.6.0 Change By: Austin Blatt Fix Version/s: PDB 6.7.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.327885.157010857.2166.1571793540415%40Atlassian.JIRA.
Jira (PDB-4555) PuppetDB connection failure causing shutdown
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown Change By: Austin Blatt Acceptance Criteria: PuppetDB does not crash on startup when Postgres is not available and will retry the connection until a successful connection is made 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.331358.1571766062000.1881.1571785560228%40Atlassian.JIRA.
Jira (PDB-4555) PuppetDB connection failure causing shutdown
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4555
PuppetDB connection failure causing shutdown
Change By:
Austin Blatt
I believe this PuppetDB _requires_ Postgres to be started before PuppetDB, otherwise its first connection to the database will fail, causing PuppetDB to throw and error and shutdown with the following message{code}ERROR [p.t.internal] Error during service start!!! java.sql.SQLTransientConnectionException: PDBMigrationsPool - Connection is not available, request timed out after 3011ms.{code}Previously, if postgresql was not up, PuppetDB would retry the connection with the message{code}ERROR [p.p.c.services] Will retry database connection after temporary failure: java.sql.SQLTransientConnectionException: PDBMigrationsPool - Connection is not available, request timed out after 3008ms.{code}This was introduced by [this query|https://github.com/puppetlabs/puppetdb/pull/3097/files#diff-66cce979c7939fbe2d11a146eae980ccR397] to Postgres that happens outside the "try again" loop for database migrations.If it fails to get a database connection , it will bring the whole PuppetDB down unlike the migrations which allowed PuppetDB to try again failures .
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4555) PuppetDB connection failure causing shutdown
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown Change By: Austin Blatt Issue Type: Improvement Bug 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.331358.1571766062000.1858.1571785320758%40Atlassian.JIRA.
Jira (PDB-4555) PuppetDB connection failure causing shutdown
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown Change By: Austin Blatt Affects Version/s: PDB 5.2.10 Affects Version/s: PDB 6.3.5 Affects Version/s: PDB 6.7.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.331358.1571766062000.1862.1571785320771%40Atlassian.JIRA.
Jira (PDB-4555) PuppetDB connection failure causing shutdown
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4555
PuppetDB connection failure causing shutdown
Change By:
Austin Blatt
PuppetDB _requires_ Postgres to be started before PuppetDB, otherwise its first connection to the database will fail, causing PuppetDB to throw and error and shutdown with the following message{code}ERROR [p.t.internal] Error during service start!!! java.sql.SQLTransientConnectionException: PDBMigrationsPool - Connection is not available, request timed out after 3011ms.{code}Previously, if postgresql was not up running , PuppetDB would retry the connection with the message{code}ERROR [p.p.c.services] Will retry database connection after temporary failure: java.sql.SQLTransientConnectionException: PDBMigrationsPool - Connection is not available, request timed out after 3008ms.{code}This was introduced by [this query|https://github.com/puppetlabs/puppetdb/pull/3097/files#diff-66cce979c7939fbe2d11a146eae980ccR397] to Postgres that happens outside the "try again" loop for database connection failures.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4547) Add wire format validation for deactivate node commands
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4547 Add wire format validation for deactivate node commands Change By: Austin Blatt Fix Version/s: PDB 5.2.11 Fix Version/s: PDB 6.7.2 Fix Version/s: PDB 6.3.6 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.328359.1570488647000.1731.1571783940561%40Atlassian.JIRA.
Jira (PDB-4555) PuppetDB connection failure causing shutdown
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown Change By: Austin Blatt Fix Version/s: PDB 5.2.11 Fix Version/s: PDB 6.7.2 Fix Version/s: PDB 6.3.6 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.331358.1571766062000.1739.1571783940605%40Atlassian.JIRA.
Jira (PDB-4550) Restore post-migration "vacuum analyze" machinery
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4550 Restore post-migration "vacuum analyze" machinery Change By: Austin Blatt Fix Version/s: PDB 5.2.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.329601.1571174302000.1723.1571783880509%40Atlassian.JIRA.
Jira (PDB-4550) Restore post-migration "vacuum analyze" machinery
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4550 Restore post-migration "vacuum analyze" machinery Change By: Austin Blatt Fix Version/s: PDB 6.7.2 Fix Version/s: PDB 6.3.6 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.329601.1571174302000.1728.1571783880531%40Atlassian.JIRA.
Jira (PDB-4506) Don't hang on C-c during migration
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4506 Don't hang on C-c during migration Change By: Austin Blatt Fix Version/s: PDB 6.7.2 Fix Version/s: PDB 6.3.6 Fix Version/s: PDB 5.2.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.324995.156873961.1717.1571783880476%40Atlassian.JIRA.
Jira (PDB-4528) Should we reject/warn on improperly formated configure-expiration cmds
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4528 Should we reject/warn on improperly formated configure-expiration cmds Change By: Zachary Kent Fix Version/s: PDB 6.7.2 Fix Version/s: PDB 6.3.6 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.327686.157003698.1694.1571783520333%40Atlassian.JIRA.
Jira (PUP-10107) Unvendor pathspec
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10107 Unvendor pathspec Change By: Josh Cooper Team: Coremunity 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.331409.1571780406000.1374.1571780460334%40Atlassian.JIRA.
Jira (PUP-10107) Unvendor pathspec
Title: Message Title Josh Cooper created an issue Puppet / PUP-10107 Unvendor pathspec Issue Type: Task Assignee: Unassigned Created: 2019/10/22 2:40 PM Priority: Normal Reporter: Josh Cooper pathspec was vendored in puppet years ago to support puppet module build. That functionality has since been removed, and pathspec is not used in puppet. In 6.x (this ticket) we should unvendor pathspec and add it as a runtime dependency so as to not break anyone. In 7.0, remove the runtime dependency. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4555) PuppetDB connection failure causing shutdown
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown Change By: Austin Blatt I believe this was introduced by [this query|https://github.com/puppetlabs/puppetdb/pull/3097/files#diff-66cce979c7939fbe2d11a146eae980ccR397] to Postgres that happens outside the "try again" loop for database migrations.If it fails to get a database connection, it will bring the whole PuppetDB down unlike the migrations which allowed PuppetDB to try 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.331358.1571766062000.820.1571766540134%40Atlassian.JIRA.
Jira (PDB-4555) PuppetDB connection failure causing shutdown
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown Issue Type: Improvement Assignee: Austin Blatt Created: 2019/10/22 10:41 AM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PUP-9823) Add recording of function and template usage for Impact Analysis
Title: Message Title Henrik Lindberg commented on PUP-9823 Re: Add recording of function and template usage for Impact Analysis Note that users can override a function by sticking a Puppet Language variant of the function definition in their site.pp with the same name as any other function (in puppet, in a module etc.). 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.316251.156294648.388.1571752200198%40Atlassian.JIRA.
Jira (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title Usatenko Andrii commented on PUP-9604 Re: Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression) JANELLE JAMES Hi. You changed the status of this ticket to 'needs information'. We are experiencing this issue and I think i can provide all required information. 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.303516.1554431387000.372.1571750940237%40Atlassian.JIRA.
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10097 Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent Change By: Patrick Grant CS Priority: Needs Priority 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.328673.1570644934000.307.1571740260373%40Atlassian.JIRA.
Jira (PUP-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Austin Boyd updated an issue Puppet / PUP-8470 Unable to modify local user group membership with forcelocal Change By: Austin Boyd Zendesk Ticket IDs: 32283 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.237430.1519070351000.269.1571738940435%40Atlassian.JIRA.
Jira (PUP-9312) puppet package provider fails when reading from registry
Title: Message Title Austin Boyd updated an issue Puppet / PUP-9312 puppet package provider fails when reading from registry Change By: Austin Boyd Zendesk Ticket IDs: 32364 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.284764.1542043672000.257.1571738820314%40Atlassian.JIRA.
Jira (PUP-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Austin Boyd updated an issue Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Change By: Austin Boyd Zendesk Ticket IDs: 32385 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.164716.1480628822000.251.1571738760913%40Atlassian.JIRA.
Jira (PUP-9240) Solaris SMF service has to support non global zone
Title: Message Title Austin Boyd updated an issue Puppet / PUP-9240 Solaris SMF service has to support non global zone Change By: Austin Boyd Zendesk Ticket IDs: 32270 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.280676.1539674657000.223.1571738760779%40Atlassian.JIRA.
Jira (PUP-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Austin Boyd updated an issue Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Change By: Austin Boyd Zendesk Ticket IDs: 32385 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.164716.1480628822000.198.1571738160899%40Atlassian.JIRA.
Jira (PUP-9312) puppet package provider fails when reading from registry
Title: Message Title Austin Boyd updated an issue Puppet / PUP-9312 puppet package provider fails when reading from registry Change By: Austin Boyd Zendesk Ticket IDs: 32364 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.284764.1542043672000.195.1571738160879%40Atlassian.JIRA.
Jira (PUP-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Austin Boyd updated an issue Puppet / PUP-8470 Unable to modify local user group membership with forcelocal Change By: Austin Boyd Zendesk Ticket IDs: 32283 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.237430.1519070351000.175.1571737920517%40Atlassian.JIRA.
Jira (PUP-9240) Solaris SMF service has to support non global zone
Title: Message Title Austin Boyd updated an issue Puppet / PUP-9240 Solaris SMF service has to support non global zone Change By: Austin Boyd Zendesk Ticket IDs: 32270 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.280676.1539674657000.163.1571737800583%40Atlassian.JIRA.
Jira (PDB-3928) Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-3928 Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern Change By: Austin Boyd Zendesk Ticket IDs: 32254 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.253827.1527712293000.124.1571737620484%40Atlassian.JIRA.
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10097 Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent Change By: Mihai Buzgau Zendesk Ticket IDs: 36615 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328673.1570644934000.85.1571735821299%40Atlassian.JIRA.
Jira (FACT-2059) premature loading of module-provided facts under `-p`
Title: Message Title George Mrejea assigned an issue to Unassigned Facter / FACT-2059 premature loading of module-provided facts under `-p` Change By: George Mrejea Assignee: George Mrejea 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.328315.1570469412000.72.1571734680387%40Atlassian.JIRA.
Jira (FACT-2054) Facter::Core::Execution.execute incorrectly expands shell builtins
Title: Message Title George Mrejea assigned an issue to George Mrejea Facter / FACT-2054 Facter::Core::Execution.execute incorrectly expands shell builtins Change By: George Mrejea Assignee: George Mrejea 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.327886.1570111406000.68.1571734620139%40Atlassian.JIRA.
Jira (FACT-2059) premature loading of module-provided facts under `-p`
Title: Message Title George Mrejea assigned an issue to George Mrejea Facter / FACT-2059 premature loading of module-provided facts under `-p` Change By: George Mrejea Assignee: George Mrejea 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.328315.1570469412000.65.1571733120176%40Atlassian.JIRA.
Jira (FACT-2059) premature loading of module-provided facts under `-p`
Title: Message Title
George Mrejea updated an issue
Facter / FACT-2059
premature loading of module-provided facts under `-p`
Change By:
George Mrejea
When running {{facter -p}} on windows with the puppetlabs/ciscopuppet module pluginsynced to the agent, facter is loading {{facter/cisco.rb}} from {{C:/ProgramData/PuppetLabs/puppet/cache/lib}} before setting up the {{$LOAD_PATH}} to load that file's dependencies from there. Please see the attached screenshot for the debug modifications I did and the results on the machine showing the issue.To make sure there is nothing wonky with the {{facter/cisco_nexus}} file itself, a {{require}} within a {{setcode}} worked fine.Regular agent runs work fine and do not show any errors. h3. Desired Behaviour{{facter -p}} loads files from puppet's cache only once, after {{$LOAD_PATH}} has been properly initialised.
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
