date:20200819

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10628  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance regression with large hashes using lookup   
 

  
 
 
 
 

 
 Thanks Oleksandr Shtepa! I was able to reproduce using your instructions:  
 
 
 
 
 # puppet --version  
 
 
 6.17.0  
 
 
 # cd /etc/puppetlabs/puppet  
 
 
 # cat hiera.yaml  
 
 
 ---  
 
 
 version: 5  
 
 
 defaults:  
 
 
   datadir: .  
 
 
   data_hash: yaml_data  
 
 
 hierarchy:  
 
 
   - name: test  
 
 
 path: test.yaml  
 
 
 # echo -e 'hash1:\n  hash2:\nhash3:' > test.yaml  
 
 
 # for i in {1..2000}; do echo "  key$i: value$i" >> test.yaml ; done

Jira (PUP-10628) Performance regression with large hashes using lookup

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10628  
 
 
  Performance regression with large hashes using lookup   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Attachment: 
 rbspy-2020-08-20-gAPdCc51RI.flamegraph.svg  
 

  
 
 
 
 

 
 
 

 
 
 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.369684.1597848926000.19923.1597902420037%40Atlassian.JIRA.

Jira (PDB-4861) Check builds, promote to PE (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4861  
 
 
  Check builds, promote to PE (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369835.1597884019000.19851.1597884060588%40Atlassian.JIRA.

Jira (PDB-4858) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4858  
 
 
  Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369832.1597884008000.19845.1597884060323%40Atlassian.JIRA.

Jira (PDB-4857) Merge-up, branch, and create pipelines (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4857  
 
 
  Merge-up, branch, and create pipelines (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Austin Blatt  
 
 
Created: 
 2020/08/19 5:40 PM  
 
 
Due Date: 
2020/08/18 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) 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 
 
 
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 -> master 
 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. Then, prepare the branch for release:

Jira (PDB-4862) Update winston (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4862  
 
 
  Update winston (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369837.1597884027000.19853.1597884060679%40Atlassian.JIRA.

Jira (PDB-4860) Bump versions, push directly, and tag (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4860  
 
 
  Bump versions, push directly, and tag (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369834.1597884015000.19849.1597884060499%40Atlassian.JIRA.

Jira (PDB-4857) Merge-up, branch, and create pipelines (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4857  
 
 
  Merge-up, branch, and create pipelines (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369831.1597884004000.19843.1597884060236%40Atlassian.JIRA.

Jira (PDB-4858) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4858  
 
 
  Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Austin Blatt  
 
 
Created: 
 2020/08/19 5:40 PM  
 
 
Due Date: 
2020/08/18 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) Ensure all tickets referenced in the commit log have a the release's fixVersion, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by checking out the branches you will be releasing, ensuring they are in sync with the upstream puppetlabs repo and running the rake task  bundle install; bundle exec rake release:reconcile[NEXT_VER,LAST_VER] This assumes you have the puppetdb repo as the cwd and the pe repo at ../pe-puppetdb-extensions. These can be overridden by the PDB_PATH and PDB_PE_PATH environment variables. The rake task will explain any mismatches that exist between Jira and the repos and ask you to investigate any tickets that do not start with a PDB ticket, (maint), (docs), or (i18n)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PDB-4860) Bump versions, push directly, and tag (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4860  
 
 
  Bump versions, push directly, and tag (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Austin Blatt  
 
 
Created: 
 2020/08/19 5:40 PM  
 
 
Due Date: 
2020/08/21 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) (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. 
 
 
Check that puppetdb and pe-puppetdb-extensions are on the same version of clj-parent, and that is the same clj-parent version that puppetserver will release with. 
 Disable automatic promotions: 
 
If a PE release branch has not been cut, 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.

Jira (PDB-4861) Check builds, promote to PE (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4861  
 
 
  Check builds, promote to PE (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Austin Blatt  
 
 
Created: 
 2020/08/19 5:40 PM  
 
 
Due Date: 
2020/08/21 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) 
 
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. 
 
 
If a release branch has already been cut Rebuild the pacakge promotion job with the release branch set instead of master or 2018.1.x. 
 
 
Once it's promoted to the release branch checkout the release branch of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb 
  bundle exec rake report:packages 
 
If there were any important dependency bumps, such as to fix a bug or CVE, verify that they were updated by navigating to the release and then to the pe-puppetdb package on [pebuildinfo|pebuildinfo.slice.puppetlabs.net/].

Jira (PDB-4862) Update winston (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4862  
 
 
  Update winston (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Austin Blatt  
 
 
Created: 
 2020/08/19 5:40 PM  
 
 
Due Date: 
2020/08/26 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) Update winston to make these tickets more accurate for next time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

Jira (PDB-4859) Draft release notes (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4859  
 
 
  Draft release notes (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369833.1597884011000.19847.1597884060411%40Atlassian.JIRA.

Jira (PDB-4859) Draft release notes (PuppetDB 6.12.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4859  
 
 
  Draft release notes (PuppetDB 6.12.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Austin Blatt  
 
 
Created: 
 2020/08/19 5:40 PM  
 
 
Due Date: 
2020/08/23 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) 
 
Write release notes for the release based on the tickets found in the previous step. 
 
Check any tickets for a docs tab with desired information. 
The release notes go in puppetdb\/documentation\/release_notes.markdown. 
Request review from the docs team by pinging @clairecadman in the opened PR, at least one day before Ready to Ship 
The opened PR should be approved prior to a go\/no-go. Release notes must be ready before a go. 
Docs are built daily and at release time. If notes need to be published out of band ask in `#prod-docs`.

Jira (PUP-10632) Prepare documentation updates and release notes (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10632  
 
 
  Prepare documentation updates and release notes (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369805.1597883901000.19828.1597883940591%40Atlassian.JIRA.

Jira (PUP-10634) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10634  
 
 
  Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2020/08/19 5:38 PM  
 
 
Due Date: 
2020/08/24 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in #proj-puppet-releases Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-10636) Send release announcement (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10636  
 
 
  Send release announcement (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Eric Griswold  
 
 
Created: 
 2020/08/19 5:38 PM  
 
 
Due Date: 
2020/08/25 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - 
 
Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. 
If this release has security implications, also send to puppet-security-annou...@googlegroups.com. 
Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.18.0 is now available".

Jira (PUP-10633) Prepare release announcement (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10633  
 
 
  Prepare release announcement (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Claire Cadman  
 
 
Created: 
 2020/08/19 5:38 PM  
 
 
Due Date: 
2020/08/24 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Claire Cadman for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-10631) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10631  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2020/08/19 5:38 PM  
 
 
Due Date: 
2020/08/19 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in Slack) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-10637) Update Confluence and JIRA based on release (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10637  
 
 
  Update Confluence and JIRA based on release (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369812.1597883929000.19838.1597883941031%40Atlassian.JIRA.

Jira (PUP-10630) Prepare JIRA and Confluence for release (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10630  
 
 
  Prepare JIRA and Confluence for release (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369803.1597883893000.19824.1597883940411%40Atlassian.JIRA.

Jira (PUP-10635) Publish documentation and updates and release notes (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10635  
 
 
  Publish documentation and updates and release notes (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Claire Cadman  
 
 
Created: 
 2020/08/19 5:38 PM  
 
 
Due Date: 
2020/08/25 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-10631) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10631  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369804.1597883897000.19826.1597883940500%40Atlassian.JIRA.

Jira (PUP-10638) Communicate scope and timeline of next release (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10638  
 
 
  Communicate scope and timeline of next release (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369813.1597883933000.19840.1597883941119%40Atlassian.JIRA.

Jira (PUP-10638) Communicate scope and timeline of next release (Puppet Platform 6.18.0)

Title: Message Title

Eric Griswold created an issue

Puppet / PUP-10638

Communicate scope and timeline of next release (Puppet Platform 6.18.0)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2020/08/19 5:38 PM

Due Date:
2020/08/26

Labels:
release

Priority:
Normal

Reporter:
Eric Griswold

(Initial planned release date: 2020-08-25) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.

Jira (PUP-10634) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10634  
 
 
  Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369808.1597883913000.19832.1597883940767%40Atlassian.JIRA.

Jira (PUP-10632) Prepare documentation updates and release notes (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10632  
 
 
  Prepare documentation updates and release notes (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Claire Cadman  
 
 
Created: 
 2020/08/19 5:38 PM  
 
 
Due Date: 
2020/08/21 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2020-08-25) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-10636) Send release announcement (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10636  
 
 
  Send release announcement (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369811.1597883925000.19836.1597883940943%40Atlassian.JIRA.

Jira (PUP-10629) Puppet Platform 6.18.0 Release - 2020-08-25

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10629  
 
 
  Puppet Platform 6.18.0 Release - 2020-08-25
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2020/08/19 5:38 PM  
 
 
Due Date: 
2020/08/25 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 Puppet Platform 6.18.0 Release - 2020-08-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

Jira (PUP-10635) Publish documentation and updates and release notes (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10635  
 
 
  Publish documentation and updates and release notes (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369809.1597883916000.19834.1597883940855%40Atlassian.JIRA.

Jira (PUP-10630) Prepare JIRA and Confluence for release (Puppet Platform 6.18.0)

Title: Message Title

Eric Griswold created an issue

Puppet / PUP-10630

Prepare JIRA and Confluence for release (Puppet Platform 6.18.0)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2020/08/19 5:38 PM

Due Date:
2020/08/19

Labels:
release

Priority:
Normal

Reporter:
Eric Griswold

(Initial planned release date: 2020-08-25) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.18.0 and puppet-agent 6.18.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y

Jira (PUP-10637) Update Confluence and JIRA based on release (Puppet Platform 6.18.0)

Title: Message Title

Eric Griswold created an issue

Puppet / PUP-10637

Update Confluence and JIRA based on release (Puppet Platform 6.18.0)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2020/08/19 5:38 PM

Due Date:
2020/08/26

Labels:
release

Priority:
Normal

Reporter:
Eric Griswold

(Initial planned release date: 2020-08-25) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the

Jira (PUP-10633) Prepare release announcement (Puppet Platform 6.18.0)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10633  
 
 
  Prepare release announcement (Puppet Platform 6.18.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10629  
 

  
 
 
 
 

 
 
 

 
 
 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.369806.1597883905000.19830.1597883940679%40Atlassian.JIRA.

Jira (PDB-4855) /pdb/dashboard/data: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number

2020-08-19 Thread Hai Wu (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hai Wu commented on  PDB-4855  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: /pdb/dashboard/data: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number   
 

  
 
 
 
 

 
 This is awesome! Thank you for fast response, really appreciate it!  
 

  
 
 
 
 

 
 
 

 
 
 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.369694.1597852778000.19749.1597877220032%40Atlassian.JIRA.

Jira (PDB-4855) /pdb/dashboard/data: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number

2020-08-19 Thread Austin Blatt (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt commented on  PDB-4855  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: /pdb/dashboard/data: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number   
 

  
 
 
 
 

 
 Thanks for the bug report Hai Wu, we've got a fix up for review now and a release that's currently planned for next week, so hopefully we'll get this out quickly.  
 

  
 
 
 
 

 
 
 

 
 
 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.369694.1597852778000.19502.1597860720169%40Atlassian.JIRA.

Jira (PDB-4855) /pdb/dashboard/data: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number

2020-08-19 Thread Austin Blatt (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt assigned an issue to Austin Blatt  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4855  
 
 
  /pdb/dashboard/data: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Assignee: 
 Austin Blatt  
 

  
 
 
 
 

 
 
 

 
 
 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.369694.1597852778000.19481.1597860180037%40Atlassian.JIRA.

Jira (PUP-10615) Add facts and vars back to PAL ScriptCompiler scope

2020-08-19 Thread Tom Beech (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10615  
 
 
  Add facts and vars back to PAL ScriptCompiler scope   
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Comment: 
 PAL's script compiler now sets local facts for the compiler's scope. A previous change to PAL removed setting facts, which resulted in breaking changes to the script compiler API. Now, setting local facts in the script compiler's scope by setting the 'set_local_facts' option to 'false' for 'with_script_compiler'. This option is set to 'true' by default.  
 

  
 
 
 
 

 
 
 

 
 
 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.368742.1597093035000.19283.1597854060171%40Atlassian.JIRA.

Jira (PUP-10615) Add facts and vars back to PAL ScriptCompiler scope

2020-08-19 Thread Tom Beech (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10615  
 
 
  Add facts and vars back to PAL ScriptCompiler scope   
 

  
 
 
 
 

 
 PAL's script compiler now sets local facts for the compiler's scope. A previous change to PAL removed setting facts, which resulted in breaking changes to the script compiler API. Now, setting local facts in the script compiler's scope by setting the 'set_local_facts' option to 'false' for 'with_script_compiler'. This option is set to 'true' by default.  
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Release Notes: 
 Bug Fix  
 
 
Release Notes Summary: 
 Added local facts back to PAL's script compiler scope.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

Jira (PDB-4853) Always rethrow exceptions from fatal error handler

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4853  
 
 
  Always rethrow exceptions from fatal error handler   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 6.11.4  
 

  
 
 
 
 

 
 
 

 
 
 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.369291.1597680316000.19261.1597853280026%40Atlassian.JIRA.

Jira (PDB-4812) Change command broadcast config syntax

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4812  
 
 
  Change command broadcast config syntax   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 6.11.4  
 

  
 
 
 
 

 
 
 

 
 
 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.365930.1594762631000.19259.1597853220053%40Atlassian.JIRA.

Jira (PDB-4853) Always rethrow exceptions from fatal error handler

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4853  
 
 
  Always rethrow exceptions from fatal error handler   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Release Notes: 
 Not Needed  
 

  
 
 
 
 

 
 
 

 
 
 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.369291.1597680316000.19260.1597853220095%40Atlassian.JIRA.

Jira (PUP-10627) write public information to puppet_dir/public

2020-08-19 Thread Luchian Nemes (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luchian Nemes assigned an issue to Luchian Nemes  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10627  
 
 
  write public information to puppet_dir/public   
 

  
 
 
 
 

 
Change By: 
 Luchian Nemes  
 
 
Assignee: 
 Luchian Nemes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.369665.1597829487000.19255.1597853160454%40Atlassian.JIRA.

Jira (PDB-4856) puppetdb dashbard failing after upgrade to latest release

2020-08-19 Thread Hai Wu (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hai Wu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4856  
 
 
  puppetdb dashbard failing after upgrade to latest release   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/08/19 9:02 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Hai Wu  
 

  
 
 
 
 

 
 after upgrading to latest puppetdb puppetdb-6.11.3-1.el7.noarch: its dashboard no longer working:   2020-08-19T11:00:53.384-05:00 WARN [o.e.j.s.HttpChannel] /pdb/dashboard/data java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number at clojure.lang.Numbers.multiply(Numbers.java:173) at puppetlabs.puppetdb.dashboard$fn_42532$get_dashboard_data42537$fn42538$iter4253942543$fn42544$fn_42545.invoke(dashboard.clj:162) at puppetlabs.puppetdb.dashboard$fn_42532$get_dashboard_data42537$fn42538$iter4253942543$fn_42544.invoke(dashboard.clj:158) at clojure.lang.LazySeq.sval(LazySeq.java:42) at clojure.lang.LazySeq.seq(LazySeq.java:51) at clojure.lang.RT.seq(RT.java:535) at clojure.core$seq__5402.invokeStatic(core.clj:137) at clojure.core$seq__5402.invoke(core.clj:137) at schema.spec.collection$element_transformer$fn__3840.invoke(collection.clj:26) at schema.spec.collection.CollectionSpec$fn__3880.invoke(collection.clj:79) at clojure.core$comp$fn__5807.invoke(core.clj:2569) at puppetlabs.puppetdb.dashboard$fn_42532$get_dashboard_data_42537.invoke(dashboard.clj:156) at puppetlabs.puppetdb.dashboard$build_app$fn__42568.invoke(dashboard.clj:171) at bidi.ring$fn__32322.invokeStatic(ring.cljc:25) at bidi.ring$fn__32322.invoke(ring.cljc:21) at bidi.ring$fn_32307$G32302_32316.invoke(ring.cljc:16) at puppetlabs.puppetdb.middleware$fn_33208$make_pdb_handler33217$fn33220$fn_33222.invoke(middleware.clj:397) at compojure.core$routing$fn__1859.invoke(core.clj:151) at clojure.core$some.invokeStatic(core.clj:2701) at clojure.core$some.invoke(core.clj:2692) at compojure.core$routing.invokeStatic(core.clj:151) at compojure.core$routing.doInvoke(core.clj:148) at clojure.lang.RestFn.invoke(RestFn.java:423) at puppetlabs.puppetdb.pdb_routing$wrap_with_context$fn__46395.invoke(pdb_routing.clj:34) at compojure.core$if_context$fn__1883.invoke(core.clj:218) at compojure.core$routing$fn__1859.invoke(core.clj:151) at clojure.core$some.invokeStatic(core.clj:2701) at

Jira (PDB-4812) Change command broadcast config syntax

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4812  
 
 
  Change command broadcast config syntax   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Epic Link: 
 PE PDB - 28233 4653  
 

  
 
 
 
 

 
 
 

 
 
 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.365930.1594762631000.19244.1597852920029%40Atlassian.JIRA.

Jira (PDB-4855) /pdb/dashboard/data: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number

2020-08-19 Thread Hai Wu (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hai Wu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4855  
 
 
  /pdb/dashboard/data: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PDB 6.11.3  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 PuppetDB  
 
 
Created: 
 2020/08/19 8:59 AM  
 
 
Environment: 
 RHEL76, puppetdb  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Hai Wu  
 

  
 
 
 
 

 
 Today after upgrading from puppetdb-6.7.1-1.el7.noarch to puppetdb-6.11.3-1.el7.noarch on RHEL76 host, the following error messages start showing up all the time, and now pdb/jetty is not working at all. The basic function for puppetdb seems to be still working, just its dashboard is now down.  it seems this error matching this earlier issue from long time ago: https://tickets.puppetlabs.com/si/jira.issueviews:issue-html/PDB-3312/PDB-3312.html Any workaround for this one?  2020-08-19T10:52:29.435-05:00 WARN [o.e.j.s.HttpChannel] /pdb/dashboard/data java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Number at clojure.lang.Numbers.multiply(Numbers.java:173) at puppetlabs.puppetdb.dashboard$fn_42532$get_dashboard_data42537$fn42538$iter4253942543$fn42544$fn_42545.invoke(dashboard.clj:162) at puppetlabs.puppetdb.dashboard$fn_42532$get_dashboard_data42537$fn42538$iter4253942543$fn_42544.invoke(dashboard.clj:158) at clojure.lang.LazySeq.sval(LazySeq.java:42) at clojure.lang.LazySeq.seq(LazySeq.java:51) at clojure.lang.RT.seq(RT.java:535) at clojure.core$seq__5402.invokeStatic(core.clj:137) at clojure.core$seq__5402.invoke(core.clj:137) at

Jira (PDB-4835) Create cmd broadcast multi db migration tests

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4835  
 
 
  Create cmd broadcast multi db migration tests   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Release Notes: 
 Not Needed  
 

  
 
 
 
 

 
 
 

 
 
 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.367707.1596046893000.19232.1597852680033%40Atlassian.JIRA.

Jira (PDB-4812) Change command broadcast config syntax

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning assigned an issue to Rob Browning  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4812  
 
 
  Change command broadcast config syntax   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Assignee: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

 
 
 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.365930.1594762631000.19230.1597852620034%40Atlassian.JIRA.

Jira (PDB-4835) Create cmd broadcast multi db migration tests

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4835  
 
 
  Create cmd broadcast multi db migration tests   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 6.11.4  
 

  
 
 
 
 

 
 
 

 
 
 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.367707.1596046893000.19229.1597852560573%40Atlassian.JIRA.

Jira (PUP-10626) puppet node deactivate and external CA - cert revocation can't be disabled

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10626  
 
 
  puppet node deactivate and external CA - cert revocation can't be disabled   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 *Puppet Version: 6.15.0* *Puppet Server Version: 6.11.1* *OS Name/Version: CentOS 7*When using an external certificate authority it's assumed that a working puppet-ca endpoint is not required.However  `  {{ puppet node deactivate ` }}  always attempts a revocation and failsas a result.   *Desired Behavior:* * {{ puppet node deactivate foo.example.org ** }} should delete node from PDB as is the case with puppetdb 5 * *Actual Behavior:* * With puppet 6 *  * {noformat} puppet node deactivate b7g19n0014.cern.ch*  *  Error: Request to https://puppet:8140/puppet-ca/v1 failed after 0.004 seconds: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not * * known) *  * Wrapped exception: *  {noformat}      we have no configuration for ca_server so default puppet is chosen.For info we are running pupetserver with: {noformat}   # cat /etc/puppetlabs/puppetserver/services.d/ca.cfg puppetlabs.services.ca.certificate-authority-disabled-service/certificate-authority-disabled-service {noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

Jira (PUP-10626) puppet node deactivate and external CA - cert revocation can't be disabled