Jira (PUP-3995) Prevent node resource names from overlapping with other resources
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-3995
Prevent node resource names from overlapping with other resources
Change By:
Josh Cooper
Release Notes:
Bug Fix
Release Notes Summary:
If a node statement has the same name as an included class "node 'abc' { include abc }", the Puppet used to silently ignore the class, as it thought the class had already been included.
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.67460.1423598528000.71028.1625094120198%40Atlassian.JIRA.
Jira (PUP-3995) Prevent node resource names from overlapping with other resources
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3995 Prevent node resource names from overlapping with other resources Change By: Josh Cooper Fix Version/s: PUP 7.9.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.67460.1423598528000.71019.1625093940150%40Atlassian.JIRA.
Jira (PUP-3995) Prevent node resource names from overlapping with other resources
Title: Message Title Josh Cooper commented on PUP-3995 Re: Prevent node resource names from overlapping with other resources Merged to main in https://github.com/puppetlabs/puppet/commit/c6923c49e6d3882920be03619735b8441b21ef38 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.67460.1423598528000.71020.1625093940201%40Atlassian.JIRA.
Jira (PDB-5142) Restart pdb service or fix the delete-reports task
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5142 Restart pdb service or fix the delete-reports task Change By: Austin Blatt Release Notes Summary: The `delete-reports` subcommand now restarts the puppetdb service after deleting reports Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.401081.1622152132000.71003.1625093760267%40Atlassian.JIRA.
Jira (PDB-5142) Restart pdb service or fix the delete-reports task
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5142 Restart pdb service or fix the delete-reports task Change By: Austin Blatt Release Notes: Enhancement Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.401081.1622152132000.70995.1625093700757%40Atlassian.JIRA.
Jira (PDB-5142) Restart pdb service or fix the delete-reports task
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5142 Restart pdb service or fix the delete-reports task Change By: Austin Blatt Fix Version/s: PDB 6.18.0 Fix Version/s: PDB 7.5.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.401081.1622152132000.70975.1625093640303%40Atlassian.JIRA.
Jira (PDB-5142) Restart pdb service or fix the delete-reports task
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5142 Restart pdb service or fix the delete-reports task Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.401081.1622152132000.70811.1625085240166%40Atlassian.JIRA.
Jira (PDB-5142) Restart pdb service or fix the delete-reports task
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5142 Restart pdb service or fix the delete-reports task Change By: Austin Blatt Sprint: HAHA/Grooming HA 2021-07-14 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.401081.1622152132000.70810.1625085000199%40Atlassian.JIRA.
Jira (PDB-5114) Don't validate every query row returned against the schema
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5114 Don't validate every query row returned against the schema Change By: Austin Blatt Sprint: HAHA/Grooming, HA 2021-06-02 , HA 2021-07-14 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.396667.1619041342000.70808.1625084940086%40Atlassian.JIRA.
Jira (PDB-5131) Enable drop joins by default
Title: Message Title Austin Blatt assigned an issue to Unassigned PuppetDB / PDB-5131 Enable drop joins by default Change By: Austin Blatt Assignee: Zachary Kent Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.399827.1621377697000.70807.1625084940040%40Atlassian.JIRA.
Jira (PDB-5131) Enable drop joins by default
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5131 Enable drop joins by default Change By: Austin Blatt Sprint: HAHA/Grooming, HA 2021-06-02 , HA 2021-07-14 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.399827.1621377697000.70806.1625084880099%40Atlassian.JIRA.
Jira (PUP-11141) Prepare documentation updates and release notes (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11141 Prepare documentation updates and release notes (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405230.1625081268000.70633.1625081280544%40Atlassian.JIRA.
Jira (PDB-5178) Draft release notes (PuppetDB 6.18.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5178 Draft release notes (PuppetDB 6.18.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405288.1625081536000.70721.1625081580412%40Atlassian.JIRA.
Jira (PDB-5181) Update winston (PuppetDB 6.18.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5181 Update winston (PuppetDB 6.18.0) Issue Type: Task Assignee: Rob Browning Created: 2021/06/30 12:32 PM Due Date: 2021/07/21 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PDB-5180) Check builds, promote to PE (PuppetDB 6.18.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5180 Check builds, promote to PE (PuppetDB 6.18.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405290.1625081544000.70725.1625081580589%40Atlassian.JIRA.
Jira (PDB-5181) Update winston (PuppetDB 6.18.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5181 Update winston (PuppetDB 6.18.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405292.1625081552000.70727.1625081580676%40Atlassian.JIRA.
Jira (PDB-5178) Draft release notes (PuppetDB 6.18.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5178 Draft release notes (PuppetDB 6.18.0) Issue Type: Task Assignee: Rob Browning Created: 2021/06/30 12:32 PM Due Date: 2021/07/18 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) Ensure all tickets have release notes. This query, once you've reconciled the Jira ticket fix versions in the previous step and configured the query with the current release version(s), will identify tickets whose release notes are not complete. Ask your team members to complete any tickets that need release notes (if the ticket's release note is simple you may write release notes for other people's tickets, but you certainly don't have to). Write release notes for the release based on the tickets found in the previous step. One of the simplest ways to gather release notes (once you've completed the step above to ensure every ticket that needs a release note has one) is to use this Jira query be sure to replace the fixVersions with the versions you are releasing and if you don't see release notes you'll need to verify that you're in List View and add the "Release Notes", "Release Notes Summary", and "fixVersion/s" columns to the page. All those view settings are configured in the top right via the two drop-downs below Share, Export, and Tools. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown.
Jira (PDB-5176) Merge-up, branch, and create pipelines (PuppetDB 6.18.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5176 Merge-up, branch, and create pipelines (PuppetDB 6.18.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405286.1625081529000.70717.1625081580237%40Atlassian.JIRA.
Jira (PDB-5180) Check builds, promote to PE (PuppetDB 6.18.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5180 Check builds, promote to PE (PuppetDB 6.18.0) Issue Type: Task Assignee: Rob Browning Created: 2021/06/30 12:32 PM Due Date: 2021/07/04 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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 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. Checkout the branch you promoted to (either the automatic branch like 2018.1.x or the release branch like 2019.8.1-release) of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb using the below rake command. 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
Jira (PDB-5179) Bump versions, push directly, and tag (PuppetDB 6.18.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5179 Bump versions, push directly, and tag (PuppetDB 6.18.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405289.162508154.70723.1625081580500%40Atlassian.JIRA.
Jira (PDB-5177) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.18.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5177 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.18.0) Issue Type: Task Assignee: Rob Browning Created: 2021/06/30 12:32 PM Due Date: 2021/07/01 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) Ensure all tickets referenced in the commit log have 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-5177) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.18.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5177 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.18.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405287.1625081533000.70719.1625081580324%40Atlassian.JIRA.
Jira (PDB-5179) Bump versions, push directly, and tag (PuppetDB 6.18.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5179 Bump versions, push directly, and tag (PuppetDB 6.18.0) Issue Type: Task Assignee: Rob Browning Created: 2021/06/30 12:32 PM Due Date: 2021/07/04 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) (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-5176) Merge-up, branch, and create pipelines (PuppetDB 6.18.0)
Title: Message Title
Eric Griswold created an issue
PuppetDB / PDB-5176
Merge-up, branch, and create pipelines (PuppetDB 6.18.0)
Issue Type:
Task
Assignee:
Rob Browning
Created:
2021/06/30 12:32 PM
Due Date:
2021/07/01
Priority:
Normal
Reporter:
Eric Griswold
(Initial planned release date: 2021-07-20) 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 (PUP-11157) Communicate scope and timeline of next release (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11157 Communicate scope and timeline of next release (Puppet Platform 6.24.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/30 12:31 PM Due Date: 2021/07/21 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11155) Send release announcement (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11155 Send release announcement (Puppet Platform 6.24.0) Issue Type: Task Assignee: Eric Griswold Created: 2021/06/30 12:31 PM Due Date: 2021/07/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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.24.0 is now available".
Jira (PUP-11157) Communicate scope and timeline of next release (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11157 Communicate scope and timeline of next release (Puppet Platform 6.24.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405271.1625081473000.70715.1625081521324%40Atlassian.JIRA.
Jira (PUP-11154) Publish documentation and updates and release notes (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11154 Publish documentation and updates and release notes (Puppet Platform 6.24.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405267.162508146.70709.1625081520992%40Atlassian.JIRA.
Jira (PUP-11156) Update Confluence and JIRA based on release (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11156 Update Confluence and JIRA based on release (Puppet Platform 6.24.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/30 12:31 PM Due Date: 2021/07/21 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11156) Update Confluence and JIRA based on release (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11156 Update Confluence and JIRA based on release (Puppet Platform 6.24.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405270.162508147.70713.1625081521181%40Atlassian.JIRA.
Jira (PUP-11155) Send release announcement (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11155 Send release announcement (Puppet Platform 6.24.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405269.1625081465000.70711.1625081521088%40Atlassian.JIRA.
Jira (PUP-11152) Prepare release announcement (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11152 Prepare release announcement (Puppet Platform 6.24.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/06/30 12:30 PM Due Date: 2021/07/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11152) Prepare release announcement (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11152 Prepare release announcement (Puppet Platform 6.24.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405264.1625081452000.70687.1625081461269%40Atlassian.JIRA.
Jira (PUP-11149) Prepare JIRA and Confluence for release (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11149 Prepare JIRA and Confluence for release (Puppet Platform 6.24.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/30 12:30 PM Due Date: 2021/07/02 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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.24.0 and puppet-agent 6.24.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-11148) Puppet Platform 6.24.0 Release - 2021-07-20
Title: Message Title Eric Griswold created an issue Puppet / PUP-11148 Puppet Platform 6.24.0 Release - 2021-07-20 Issue Type: Epic Assignee: Aidan Nathanson Created: 2021/06/30 12:30 PM Due Date: 2021/07/20 Priority: Normal Reporter: Eric Griswold Puppet Platform 6.24.0 Release - 2021-07-20 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11151) Prepare documentation updates and release notes (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11151 Prepare documentation updates and release notes (Puppet Platform 6.24.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/06/30 12:30 PM Due Date: 2021/07/04 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11154) Publish documentation and updates and release notes (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11154 Publish documentation and updates and release notes (Puppet Platform 6.24.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/06/30 12:31 PM Due Date: 2021/07/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11153) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11153 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.24.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405266.1625081457000.70689.1625081461365%40Atlassian.JIRA.
Jira (PUP-11149) Prepare JIRA and Confluence for release (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11149 Prepare JIRA and Confluence for release (Puppet Platform 6.24.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405261.1625081443000.70681.1625081461033%40Atlassian.JIRA.
Jira (PUP-11153) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11153 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.24.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/30 12:30 PM Due Date: 2021/07/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11150) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11150 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.24.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/30 12:30 PM Due Date: 2021/07/02 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11151) Prepare documentation updates and release notes (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11151 Prepare documentation updates and release notes (Puppet Platform 6.24.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405263.1625081449000.70685.1625081461180%40Atlassian.JIRA.
Jira (PUP-11150) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.24.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11150 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.24.0) Change By: Eric Griswold Epic Link: PUP-11148 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405262.1625081446000.70683.1625081461125%40Atlassian.JIRA.
Jira (PDB-5174) Check builds, promote to PE (PuppetDB 7.5.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5174 Check builds, promote to PE (PuppetDB 7.5.0) Issue Type: Task Assignee: Rob Browning Created: 2021/06/30 12:29 PM Due Date: 2021/07/09 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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 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. Checkout the branch you promoted to (either the automatic branch like 2018.1.x or the release branch like 2019.8.1-release) of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb using the below rake command. 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
Jira (PDB-5175) Update winston (PuppetDB 7.5.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5175 Update winston (PuppetDB 7.5.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405259.162508137.70660.1625081400899%40Atlassian.JIRA.
Jira (PDB-5170) Merge-up, branch, and create pipelines (PuppetDB 7.5.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5170 Merge-up, branch, and create pipelines (PuppetDB 7.5.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405253.1625081346000.70650.1625081400426%40Atlassian.JIRA.
Jira (PDB-5172) Draft release notes (PuppetDB 7.5.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5172 Draft release notes (PuppetDB 7.5.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405255.1625081354000.70654.1625081400605%40Atlassian.JIRA.
Jira (PDB-5173) Bump versions, push directly, and tag (PuppetDB 7.5.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5173 Bump versions, push directly, and tag (PuppetDB 7.5.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405256.1625081357000.70656.1625081400693%40Atlassian.JIRA.
Jira (PDB-5171) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.5.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5171 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.5.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405254.162508135.70652.1625081400517%40Atlassian.JIRA.
Jira (PDB-5170) Merge-up, branch, and create pipelines (PuppetDB 7.5.0)
Title: Message Title
Eric Griswold created an issue
PuppetDB / PDB-5170
Merge-up, branch, and create pipelines (PuppetDB 7.5.0)
Issue Type:
Task
Assignee:
Rob Browning
Created:
2021/06/30 12:29 PM
Due Date:
2021/07/06
Priority:
Normal
Reporter:
Eric Griswold
(Initial planned release date: 2021-07-20) 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-5173) Bump versions, push directly, and tag (PuppetDB 7.5.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5173 Bump versions, push directly, and tag (PuppetDB 7.5.0) Issue Type: Task Assignee: Rob Browning Created: 2021/06/30 12:29 PM Due Date: 2021/07/09 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) (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-5171) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.5.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5171 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.5.0) Issue Type: Task Assignee: Rob Browning Created: 2021/06/30 12:29 PM Due Date: 2021/07/06 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) Ensure all tickets referenced in the commit log have 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-5172) Draft release notes (PuppetDB 7.5.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5172 Draft release notes (PuppetDB 7.5.0) Issue Type: Task Assignee: Rob Browning Created: 2021/06/30 12:29 PM Due Date: 2021/07/18 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) Ensure all tickets have release notes. This query, once you've reconciled the Jira ticket fix versions in the previous step and configured the query with the current release version(s), will identify tickets whose release notes are not complete. Ask your team members to complete any tickets that need release notes (if the ticket's release note is simple you may write release notes for other people's tickets, but you certainly don't have to). Write release notes for the release based on the tickets found in the previous step. One of the simplest ways to gather release notes (once you've completed the step above to ensure every ticket that needs a release note has one) is to use this Jira query be sure to replace the fixVersions with the versions you are releasing and if you don't see release notes you'll need to verify that you're in List View and add the "Release Notes", "Release Notes Summary", and "fixVersion/s" columns to the page. All those view settings are configured in the top right via the two drop-downs below Share, Export, and Tools. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown.
Jira (PDB-5174) Check builds, promote to PE (PuppetDB 7.5.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5174 Check builds, promote to PE (PuppetDB 7.5.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405257.1625081361000.70658.1625081400792%40Atlassian.JIRA.
Jira (PDB-5175) Update winston (PuppetDB 7.5.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5175 Update winston (PuppetDB 7.5.0) Issue Type: Task Assignee: Rob Browning Created: 2021/06/30 12:29 PM Due Date: 2021/07/21 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11145) Send release announcement (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11145 Send release announcement (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405236.1625081284000.70644.1625081340321%40Atlassian.JIRA.
Jira (PUP-11146) Update Confluence and JIRA based on release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11146 Update Confluence and JIRA based on release (Puppet Platform 7.8.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/30 12:28 PM Due Date: 2021/07/21 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11145) Send release announcement (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11145 Send release announcement (Puppet Platform 7.8.0) Issue Type: Task Assignee: Eric Griswold Created: 2021/06/30 12:28 PM Due Date: 2021/07/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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 7.8.0 is now available".
Jira (PUP-11147) Communicate scope and timeline of next release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11147 Communicate scope and timeline of next release (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405238.1625081291000.70648.1625081340497%40Atlassian.JIRA.
Jira (PUP-11146) Update Confluence and JIRA based on release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11146 Update Confluence and JIRA based on release (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405237.1625081288000.70646.1625081340408%40Atlassian.JIRA.
Jira (PUP-11147) Communicate scope and timeline of next release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11147 Communicate scope and timeline of next release (Puppet Platform 7.8.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/30 12:28 PM Due Date: 2021/07/21 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11138) Puppet Platform 7.8.0 Release - 2021-07-20
Title: Message Title Eric Griswold created an issue Puppet / PUP-11138 Puppet Platform 7.8.0 Release - 2021-07-20 Issue Type: Epic Assignee: Aidan Nathanson Created: 2021/06/30 12:27 PM Due Date: 2021/07/20 Priority: Normal Reporter: Eric Griswold Puppet Platform 7.8.0 Release - 2021-07-20 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11143) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11143 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.8.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/30 12:27 PM Due Date: 2021/07/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11139) Prepare JIRA and Confluence for release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11139 Prepare JIRA and Confluence for release (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405228.1625081262000.70629.1625081280437%40Atlassian.JIRA.
Jira (PUP-11143) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11143 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405233.1625081276000.70637.1625081280684%40Atlassian.JIRA.
Jira (PUP-11142) Prepare release announcement (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11142 Prepare release announcement (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405231.162508127.70635.1625081280597%40Atlassian.JIRA.
Jira (PUP-11140) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11140 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.8.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/30 12:27 PM Due Date: 2021/07/07 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11142) Prepare release announcement (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11142 Prepare release announcement (Puppet Platform 7.8.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/06/30 12:27 PM Due Date: 2021/07/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11140) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11140 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405229.1625081265000.70631.1625081280490%40Atlassian.JIRA.
Jira (PUP-11144) Publish documentation and updates and release notes (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11144 Publish documentation and updates and release notes (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11138 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405234.1625081278000.70639.1625081280792%40Atlassian.JIRA.
Jira (PUP-11139) Prepare JIRA and Confluence for release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11139 Prepare JIRA and Confluence for release (Puppet Platform 7.8.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/30 12:27 PM Due Date: 2021/07/07 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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 7.8.0 and puppet-agent 7.9.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-11141) Prepare documentation updates and release notes (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11141 Prepare documentation updates and release notes (Puppet Platform 7.8.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/06/30 12:27 PM Due Date: 2021/07/09 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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-11144) Publish documentation and updates and release notes (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11144 Publish documentation and updates and release notes (Puppet Platform 7.8.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/06/30 12:27 PM Due Date: 2021/07/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-07-20) 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 (PDB-5168) Log PQL parsing time whenever it's "too long"
Title: Message Title
Austin Blatt commented on PDB-5168
Re: Log PQL parsing time whenever it's "too long"
Here's an example of a pql query with 1,600 certnames that takes a long time to compile on the repl.
=> (require '[puppetlabs.puppetdb.pql :as pql] :reload-all)
=> (do (time (pql/parse-pql-query (str "nodes[] { certname in [\"" (clojure.string/join "\", \"" (repeat 1600 "heavy-empire.delivery.puppetlabs.net")) "\"] }" ))) nil)
"Elapsed time: 20993.829089 msecs"
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
Jira (PDB-5168) Log PQL parsing time whenever it's "too long"
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5168 Log PQL parsing time whenever it's "too long" Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2021/06/30 11:29 AM Priority: Normal Reporter: Rob Browning It appears that the PQL parser can go off the rails, and it might even be a known, more general issue: https://stackoverflow.com/questions/64165847/unbelievably-bad-parse-time For now, so we can get a better impression of the scope of the problem, let's compute the PQL parse time and log it at warning level whenever it's greater than say 1 second. (Not sure about 1s, but we can determine the exact value before we merge.) Add Comment
Jira (FACT-3054) clean_up_interfaces_response in lib/facter/resolvers/networking.rb should also handle IPv6
Title: Message Title Ruben van Staveren created an issue Facter / FACT-3054 clean_up_interfaces_response in lib/facter/resolvers/networking.rb should also handle IPv6 Issue Type: Bug Affects Versions: FACT 4.2.0, FACT 4.2.1 Assignee: Unassigned Components: Facter 4 Created: 2021/06/30 10:51 AM Priority: Normal Reporter: Ruben van Staveren clean_up_interfaces_response in lib/facter/resolvers/networking.rb only handles the IPv4 case "10.16.132.213 --> 10.16.132.213", but it should also cases where IPv6 is being used (2001:db8:cafe::132:213 --> 2001:db8:cafe::132:213) Symptom Jun 18 19:09:59 host puppet-agent[3958]: (Facter) invalid address: 2001:db8:cafe::213:1001:db8:cafe::213:2 Add Comment
Jira (PDB-5052) puppetlabs-puppetdb module defaults to installing the unsupported combination of Postgres 9.6 and PuppetDB 7
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5052 puppetlabs-puppetdb module defaults to installing the unsupported combination of Postgres 9.6 and PuppetDB 7 Change By: Austin Blatt Team: HA Ghost Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389161.1614367275000.70369.1625071500067%40Atlassian.JIRA.
Jira (PDB-5135) PuppetDB should warn about resource titles that exceed Postgres index sizes
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5135 PuppetDB should warn about resource titles that exceed Postgres index sizes Change By: Austin Blatt Team: PuppetDB Ghost Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.399989.162152585.70370.1625071500095%40Atlassian.JIRA.
Jira (PUP-9577) Large numbers of facts cause slow performance
Title: Message Title
Reid Vandewiele commented on PUP-9577
Re: Large numbers of facts cause slow performance
The customer triage that was put in place, and which decisively solved the issue, was to patch the Puppet::Parser::TemplateWrapper class to filter which ivars are set. Filter:
require 'delegate'
class ToHashScopeFilterDelegator < SimpleDelegator
def to_hash(*args)
__getobj__.to_hash(*args).reject { |k, _| k.start_with?('badfact_') }
end
end
Patch:
Puppet::Parser::TemplateWrapper.class_eval do
def scope
ToHashScopeFilterDelegator.new(@__scope__)
end
end
Jira (PUP-9577) Large numbers of facts cause slow performance
Title: Message Title Justin Stoller commented on PUP-9577 Re: Large numbers of facts cause slow performance I think the state we left this was that: There was a support escalation with SF that was hit by this, we offered GC and JRuby tuning to hopefully help. We outlined a couple potential "fixes" for this: Parse ERB templates prior to evaluating them to see what variables we need for the scope. Possible costs in performance for the not-large-facts case and in general maintenance. Deprecate @ivar fact references and allow users to disable ivars as facts (skipping the slow paths). Probably has a large ecosystem lift? Would love to hear CS input on that. Share variables between templates, may only incur the facts -> ivars cost once per catalog, may have edge cases. I'd love to know if either of the performance mitigations were helpful? and how much work CS believes it would be to move users to not using instance variables for facts? Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the
Jira (PDB-5142) Restart pdb service or fix the delete-reports task
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5142 Restart pdb service or fix the delete-reports task Change By: Austin Blatt Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.401081.1622152132000.70205.1625068200145%40Atlassian.JIRA.
Jira (PDB-5142) Restart pdb service or fix the delete-reports task
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5142 Restart pdb service or fix the delete-reports task Change By: Austin Blatt Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.401081.1622152132000.70204.1625068200101%40Atlassian.JIRA.
Jira (PDB-5142) Restart pdb service or fix the delete-reports task
Title: Message Title Austin Blatt commented on PDB-5142 Re: Restart pdb service or fix the delete-reports task This is trivial, we can add it to the sprint today if we want Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.401081.1622152132000.70201.1625068140629%40Atlassian.JIRA.
Jira (FACT-3053) Incorrect license for lib/facter/custom_facts/core/legacy_facter.rb?
Title: Message Title Clay Caviness created an issue Facter / FACT-3053 Incorrect license for lib/facter/custom_facts/core/legacy_facter.rb? Issue Type: Bug Assignee: Unassigned Created: 2021/06/30 8:45 AM Priority: Normal Reporter: Clay Caviness The top-level LICENSE file for Facter is MIT. However lib/facter/custom_facts/core/legacy_facter.rb has an Apache 2.0 license notice at the top of the file. Is this correct, or just a remnant of the old Facter license that was copied over? Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11129) Cached environment may not be deleted if the directory is removed
Title: Message Title Gheorghe Popescu commented on PUP-11129 Re: Cached environment may not be deleted if the directory is removed https://github.com/puppetlabs/puppet/pull/8663/files ❯ ls ~/.puppetlabs/etc/code/environments/ production 2.7.2 ❯ bx ruby envs.rb Listed test53724, production environments Deleted test53724 environment Listed production environments Add Comment
Jira (PDB-5105) Benchmark console query performance and identify slow queries
Title: Message Title Andrei Filipovici commented on PDB-5105 Re: Benchmark console query performance and identify slow queries I added the 3 sandboxes (1000, 10.000, 100.000) to pdb-n1-prod.ops.puppetlabs.net, at: /home/andrei.filipovici/sandboxes I added in the database section of pdb.ini, in all sandboxes the following settings: node-ttl = 0s node-purge-ttl = 0s report-ttl = 0s resource-events-ttl = 0s Ingestion time for the 10.000 nodes sandbox was a little over half an hour and for the 100.000 nodes was roughly 8 and a half hours. Maximum JVM heap size for the 100.000 nodes sandbox was 10Gb. In the attachment is a print screen for the 100.000 nodes sandbox after it finished ingestion. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395324.161841225.69955.1625062140036%40Atlassian.JIRA.
Jira (PDB-5105) Benchmark console query performance and identify slow queries
Title: Message Title Andrei Filipovici updated an issue PuppetDB / PDB-5105 Benchmark console query performance and identify slow queries Change By: Andrei Filipovici Attachment: Screenshot 2021-06-30 at 16.53.07.png Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395324.161841225.69945.1625061780142%40Atlassian.JIRA.
Jira (PUP-11137) Puppet cannot query non-ASCII users
Title: Message Title
Dorin Pleava created an issue
Puppet / PUP-11137
Puppet cannot query non-ASCII users
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/06/30 6:05 AM
Priority:
Normal
Reporter:
Dorin Pleava
On Debian 10(might be also other platforms affected) when querying a user that contains non-ASCII characters in its name, puppet errors out as seen below:
root@fell-scattergun:~# puppet --version
6.23.0
root@fell-scattergun:~# cat manifest.pp
user { 'Gérard':
ensure => present,
Jira (PUP-11129) Cached environment may not be deleted if the directory is removed
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-11129 Cached environment may not be deleted if the directory is removed Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405015.162492624.69849.1625055780035%40Atlassian.JIRA.
Jira (FACT-2109) Next steps
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2109 Next steps Change By: Bogdan Irimie Epic Status: To Do Done Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.334239.1573464314000.69834.1625052360039%40Atlassian.JIRA.
Jira (FACT-2568) Automate teste for Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2568 Automate teste for Facter 4 Change By: Bogdan Irimie Epic Status: To Do Done Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356334.1587549193000.69833.1625052300027%40Atlassian.JIRA.
Jira (FACT-2796) Mechanism that allows one OS to inherit facts from another OS
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2796 Mechanism that allows one OS to inherit facts from another OS Change By: Bogdan Irimie Sub-team: ghost Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.351411.1585322789000.69832.1625052180102%40Atlassian.JIRA.
Jira (FACT-1937) Get facter metrics in order to compare different versions
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1937 Get facter metrics in order to compare different versions Change By: Bogdan Irimie Sub-team: ghost Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316641.1563283571000.69831.1625052180040%40Atlassian.JIRA.
Jira (FACT-2508) How can we better interact with the community
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2508 How can we better interact with the community Change By: Bogdan Irimie Sub-team: ghost Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.351402.158531593.69830.1625052060035%40Atlassian.JIRA.
Jira (PUP-11136) When Upgraded Puppet 5 to 6, Unable to Render ERB files via Template Function.
Title: Message Title
Gurender updated an issue
Puppet / PUP-11136
When Upgraded Puppet 5 to 6, Unable to Render ERB files via Template Function.
Change By:
Gurender
*Puppet Version: 6.15.0* *Puppet Server Version: 6.15.3* *OS Name/Version: Centos 7.8* *Ruby Version: ruby 2.0.0p648 (2015-12-16) [x86_64-linux]* We have upgraded puppet 5 to 6, then executed our one module which was using templates, it was of course using template function to invoke erb file but on puppet agent run it gives following error:- Info: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Retrieving localesError: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, undefined method `[]' for Puppet::Pops::Loader::RubyLegacyFunctionInstantiator::Puppet:Module (file: /etc/puppet/environments/production/modules/test/manifests/init.pp, line: 4, column: 20) on node xxxWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping runContent of init.pp:- class test{file { 'test': content => template('test/test.erb'), ensure => file, path => '/etc/test', } *Desired Behavior: Should Render erb file.**Actual Behavior: gives of Error 500 with "undefined method `[]'"*
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11136) When Upgraded Puppet 5 to 6, Unable to Render ERB files via Template Function.
Title: Message Title
Gurender created an issue
Puppet / PUP-11136
When Upgraded Puppet 5 to 6, Unable to Render ERB files via Template Function.
Issue Type:
Bug
Affects Versions:
PUP 6.15.0
Assignee:
Unassigned
Components:
Compiler
Created:
2021/06/30 3:32 AM
Priority:
Normal
Reporter:
Gurender
Puppet Version: 6.15.0 Puppet Server Version: 6.15.3 OS Name/Version: Centos 7.8 We have upgraded puppet 5 to 6, then executed our one module which was using templates, it was of course using template function to invoke erb file but on puppet agent run it gives following error:- Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, undefined method `[]' for Puppet::Pops::Loader::RubyLegacyFunctionInstantiator::Puppet:Module (file: /etc/puppet/environments/production/modules/test/manifests/init.pp, line: 4, column: 20) on node xxx Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Content of init.pp:- class test{ file { 'test': content => template('test/test.erb'), ensure => file, path => '/etc/test', } Desired Behavior: Should Render erb file. Actual Behavior: gives of Error 500 with "undefined method `[]'"
Jira (PDB-5159) Change filenames from PDB export to be compatible with stockpile
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5159 Change filenames from PDB export to be compatible with stockpile Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.403562.1623830393000.69756.1625044980031%40Atlassian.JIRA.
Jira (PUP-11029) pip ensure=>latest fails with pip>=20.3.0
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11029 pip ensure=>latest fails with pip>=20.3.0 Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395833.1618592933000.69755.1625044860028%40Atlassian.JIRA.
Jira (FACT-3001) Debug output shows facter gets called thousands of times
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3001 Debug output shows facter gets called thousands of times Change By: Ciprian Badescu Sprint: NW-2021-07- 14 28 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.393130.1617033494000.69751.1625044320053%40Atlassian.JIRA.
Jira (FACT-3032) Spec integration tests failing when IPv6 not set
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3032 Spec integration tests failing when IPv6 not set Change By: Ciprian Badescu Sprint: NW-2021-07- 14 28 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397332.1619595305000.69752.1625044320076%40Atlassian.JIRA.
