Jira (PDB-5374) Bump versions, push directly, and tag (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5374 Bump versions, push directly, and tag (Puppet Platform 7.13.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/11/15 2:15 PM Due Date: 2021/12/03 Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) (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-5376) Update winston (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5376 Update winston (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423548.1637014539000.7653.1637014560801%40Atlassian.JIRA.
Jira (PDB-5371) Merge-up, branch, and create pipelines (Puppet Platform 7.13.0)
Title: Message Title
tefoji created an issue
PuppetDB / PDB-5371
Merge-up, branch, and create pipelines (Puppet Platform 7.13.0)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2021/11/15 2:15 PM
Due Date:
2021/11/30
Priority:
Normal
Reporter:
tefoji
(Initial planned release date: 2021-12-07) 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-5375) Check builds, promote to PE (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5375 Check builds, promote to PE (Puppet Platform 7.13.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/11/15 2:15 PM Due Date: 2021/12/03 Priority: Normal Reporter: tefoji 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-5376) Update winston (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5376 Update winston (Puppet Platform 7.13.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/11/15 2:15 PM Due Date: 2021/12/08 Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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-5373) Draft release notes (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5373 Draft release notes (Puppet Platform 7.13.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/11/15 2:15 PM Due Date: 2021/12/05 Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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-5375) Check builds, promote to PE (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5375 Check builds, promote to PE (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423547.1637014536000.7651.1637014560710%40Atlassian.JIRA.
Jira (PDB-5373) Draft release notes (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5373 Draft release notes (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423545.1637014531000.7647.1637014560533%40Atlassian.JIRA.
Jira (PDB-5374) Bump versions, push directly, and tag (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5374 Bump versions, push directly, and tag (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423546.1637014533000.7649.1637014560621%40Atlassian.JIRA.
Jira (PDB-5371) Merge-up, branch, and create pipelines (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5371 Merge-up, branch, and create pipelines (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423543.1637014525000.7643.1637014560347%40Atlassian.JIRA.
Jira (PDB-5372) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5372 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.13.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/11/15 2:15 PM Due Date: 2021/11/30 Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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-5372) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5372 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423544.1637014528000.7645.1637014560442%40Atlassian.JIRA.
Jira (PUP-11358) Prepare release announcement (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11358 Prepare release announcement (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423522.1637014446000.7629.1637014500533%40Atlassian.JIRA.
Jira (PUP-11359) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11359 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423524.1637014451000.7631.1637014500621%40Atlassian.JIRA.
Jira (PUP-11360) Publish documentation and updates and release notes (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11360 Publish documentation and updates and release notes (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423525.1637014454000.7633.1637014500709%40Atlassian.JIRA.
Jira (PUP-11357) Prepare documentation updates and release notes (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11357 Prepare documentation updates and release notes (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423521.1637014443000.7627.1637014500445%40Atlassian.JIRA.
Jira (PUP-11363) Communicate scope and timeline of next release (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11363 Communicate scope and timeline of next release (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423529.1637014466000.7639.1637014500982%40Atlassian.JIRA.
Jira (PUP-11362) Update Confluence and JIRA based on release (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11362 Update Confluence and JIRA based on release (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423528.1637014463000.7637.1637014500893%40Atlassian.JIRA.
Jira (PUP-11356) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue Puppet / PUP-11356 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.13.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/11/15 2:14 PM Due Date: 2021/12/01 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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-11358) Prepare release announcement (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue Puppet / PUP-11358 Prepare release announcement (Puppet Platform 7.13.0) Issue Type: Task Assignee: Heston Hoffman Created: 2021/11/15 2:14 PM Due Date: 2021/12/06 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Heston Hoffman 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-11359) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue Puppet / PUP-11359 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.13.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/11/15 2:14 PM Due Date: 2021/12/06 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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-11356) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11356 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423520.163701444.7625.1637014500355%40Atlassian.JIRA.
Jira (PUP-11362) Update Confluence and JIRA based on release (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue Puppet / PUP-11362 Update Confluence and JIRA based on release (Puppet Platform 7.13.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/11/15 2:14 PM Due Date: 2021/12/09 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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 description and
Jira (PUP-11360) Publish documentation and updates and release notes (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue Puppet / PUP-11360 Publish documentation and updates and release notes (Puppet Platform 7.13.0) Issue Type: Task Assignee: Heston Hoffman Created: 2021/11/15 2:14 PM Due Date: 2021/12/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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-11357) Prepare documentation updates and release notes (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue Puppet / PUP-11357 Prepare documentation updates and release notes (Puppet Platform 7.13.0) Issue Type: Task Assignee: Heston Hoffman Created: 2021/11/15 2:14 PM Due Date: 2021/12/03 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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-11363) Communicate scope and timeline of next release (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue Puppet / PUP-11363 Communicate scope and timeline of next release (Puppet Platform 7.13.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/11/15 2:14 PM Due Date: 2021/12/09 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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-11361) Send release announcement (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11361 Send release announcement (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423527.163701446.7635.1637014500797%40Atlassian.JIRA.
Jira (PUP-11361) Send release announcement (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue Puppet / PUP-11361 Send release announcement (Puppet Platform 7.13.0) Issue Type: Task Assignee: Isaac Hammes Created: 2021/11/15 2:14 PM Due Date: 2021/12/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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.13.0 is now available"
Jira (PUP-11354) Puppet Platform 7.13.0 Release - 2021-12-07
Title: Message Title tefoji created an issue Puppet / PUP-11354 Puppet Platform 7.13.0 Release - 2021-12-07 Issue Type: Epic Assignee: Aidan Nathanson Created: 2021/11/15 2:13 PM Due Date: 2021/12/07 Priority: Normal Reporter: tefoji Puppet Platform 7.13.0 Release - 2021-12-07 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11355) Prepare JIRA and Confluence for release (Puppet Platform 7.13.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11355 Prepare JIRA and Confluence for release (Puppet Platform 7.13.0) Change By: tefoji Epic Link: PUP-11354 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.423519.1637014437000.7623.1637014440209%40Atlassian.JIRA.
Jira (PUP-11355) Prepare JIRA and Confluence for release (Puppet Platform 7.13.0)
Title: Message Title tefoji created an issue Puppet / PUP-11355 Prepare JIRA and Confluence for release (Puppet Platform 7.13.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/11/15 2:13 PM Due Date: 2021/12/01 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2021-12-07) 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.13.0 and puppet-agent 7.13.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to reference
Jira (PDB-5336) Create migration 75 schema diff test
Title: Message Title Stel Abrego assigned an issue to Stel Abrego PuppetDB / PDB-5336 Create migration 75 schema diff test Change By: Stel Abrego Assignee: Stel Abrego 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.420124.1634664881000.7348.1637000940569%40Atlassian.JIRA.
Jira (PDB-5336) Create migration 75 schema diff test
Title: Message Title Stel Abrego updated an issue PuppetDB / PDB-5336 Create migration 75 schema diff test Change By: Stel Abrego Sprint: HAHA/Grooming HA 2021-11-17 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.420124.1634664881000.7347.1637000940522%40Atlassian.JIRA.
Jira (FACT-3077) Inconsistent values coming from facter-ng output
Title: Message Title Erwin Solis commented on FACT-3077 Re: Inconsistent values coming from facter-ng output T-Mobile was hoping to see his fixed in 2019.8.9 so I just want to pile on that LTS customers have a need. 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.418363.1633415924000.7291.1636998420140%40Atlassian.JIRA.
Jira (PUP-11352) ToDataSerializer which loses track of the current path
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11352 ToDataSerializer which loses track of the current path Change By: Ciprian Badescu Team: Night's Watch 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.423439.1636986377000.7096.1636990860194%40Atlassian.JIRA.
Jira (PUP-11353) "silence_warnings" argument doesn't affect the "non-string hash key" warning
Title: Message Title Ciprian Badescu created an issue Puppet / PUP-11353 "silence_warnings" argument doesn't affect the "non-string hash key" warning Issue Type: Bug Assignee: Unassigned Created: 2021/11/15 6:28 AM Priority: Normal Reporter: Ciprian Badescu The gory details are in https://tickets.puppetlabs.com/browse/PUP-11321, in this ticket we should fix silence_warnings: We are currently using the "silence_warnings" argument when saving the transaction store, but that doesn't affect the "non-string hash key" warning. It probably should. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11352) ToDataSerializer which loses track of the current path
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11352 ToDataSerializer which loses track of the current path Change By: Ciprian Badescu Sprint: NW - 2021-12-01(02) 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.423439.1636986377000.7032.1636986540093%40Atlassian.JIRA.
Jira (PUP-11352) ToDataSerializer which loses track of the current path
Title: Message Title Ciprian Badescu created an issue Puppet / PUP-11352 ToDataSerializer which loses track of the current path Issue Type: Bug Assignee: Unassigned Created: 2021/11/15 6:26 AM Priority: Normal Reporter: Ciprian Badescu The gory details are in https://tickets.puppetlabs.com/browse/PUP-11321, in this ticket we should fix ToDataSerializer: There's a bug in the ToDataSerializer which loses track of the current path, so we get repeated elements in the warning message: ['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["listen_address"]' ['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["broadcast_rpc_address"]'
Jira (PUP-11351) Puppet::Transaction::Persistence:0x00005598a2c1ebf8 warnings on puppet run
Title: Message Title
Ciprian Badescu updated an issue
Puppet / PUP-11351
Puppet::Transaction::Persistence:0x5598a2c1ebf8 warnings on puppet run
Change By:
Ciprian Badescu
The gory details are in https://tickets.puppetlabs.com/browse/PUP-11321, in this ticket we should fix the warning messages:{code: java console }Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["listen_address"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["broadcast_rpc_address"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["rpc_address"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["num_tokens"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["auto_bootstrap"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["cluster_name"]' Warning:
Jira (PUP-11351) Puppet::Transaction::Persistence:0x00005598a2c1ebf8 warnings on puppet run
Title: Message Title
Ciprian Badescu updated an issue
Puppet / PUP-11351
Puppet::Transaction::Persistence:0x5598a2c1ebf8 warnings on puppet run
Change By:
Ciprian Badescu
The gory details are in https://tickets.puppetlabs.com/browse/PUP-11321, in this ticket we should fix the warning messages:{code:java}Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["listen_address"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["broadcast_rpc_address"]'Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["rpc_address"]'Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["num_tokens"]'Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["auto_bootstrap"]'Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["cluster_name"]'Warning:
Jira (PUP-11351) Puppet::Transaction::Persistence:0x00005598a2c1ebf8 warnings on puppet run
Title: Message Title
Ciprian Badescu updated an issue
Puppet / PUP-11351
Puppet::Transaction::Persistence:0x5598a2c1ebf8 warnings on puppet run
Change By:
Ciprian Badescu
The gory details are in https://tickets.puppetlabs.com/browse/PUP-11321, in this ticket we should fix the warning messages:{code:java} Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["listen_address"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["broadcast_rpc_address"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["rpc_address"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["num_tokens"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["auto_bootstrap"]' Warning: #['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0]['resources']['Yaml_settings[cassandra::config]']['parameters']['values']['system_value'][0] contains a hash with an Array key. It will be converted to the String '["cluster_name"]' Warning:
Jira (FACT-3093) Facter fails to resolve custom/environment facts in some circumstances
Title: Message Title
Ciprian Badescu commented on FACT-3093
Re: Facter fails to resolve custom/environment facts in some circumstances
Adam Tkac, calling Facter.value outside setcode block is causing this kind of issues. The same effect can be obtained using confine }}and {{has_weight statements and will be correctly solved by Facter. Can you try that?
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.423055.1636538936000.7000.1636985640035%40Atlassian.JIRA.
Jira (PUP-8220) Verify trusted facts are overridden consistently
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-8220 Verify trusted facts are overridden consistently Change By: Dorin Pleava Release Notes: Bug Fix Release Notes Summary: When using puppet lookup with --facts, if the facts file overrides any ofhostname, domain, fqdn, clientcert, then it must override all of them. 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.224769.1512033958000.6979.1636984200040%40Atlassian.JIRA.
Jira (FACT-3096) facter execution API is stripping spaces
Title: Message Title
Ciprian Badescu updated an issue
Facter / FACT-3096
facter execution API is stripping spaces
Change By:
Ciprian Badescu
Facter execution API is stripping leading and trailing white-spaces, observed while working on https://tickets.puppetlabs.com/browse/FACT-3094It's visible on all Facter 4 versions and in Facter 3 version , not on Facter 2Reproduction:{code:java} [root@urgent-equating ~]# echo X$(/opt/puppetlabs/puppet/bin/ruby -e "require '/opt/puppetlabs/puppet/lib/libfacter.so'; puts Facter::Core::Execution.execute('echo \" A B \"') ")YXA BY[root@urgent-equating ~]# gem install facterFetching: facter-4.2.5.gem (100%)Successfully installed facter-4.2.51 gem installed[root@urgent-equating ~]# echo X$(ruby -e "require 'facter'; puts Facter::Core::Execution.execute('echo \" A B \"') ")YXA BY[root@urgent-equating ~]# gem uninstall facterRemove executables: facterin addition to the gem? [Yn] yRemoving facterSuccessfully uninstalled facter-4.2.5[root@urgent-equating ~]# gem install facter -v 2.5.7Fetching: facter-2.5.7.gem (100%)Successfully installed facter-2.5.71 gem installed[root@urgent-equating ~]# echo X$(ruby -e "require 'facter'; puts Facter::Core::Execution.execute('echo \" A B \"') ")YX A B Y{code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3096) facter execution API is stripping spaces
Title: Message Title
Ciprian Badescu updated an issue
Facter / FACT-3096
facter execution API is stripping spaces
Change By:
Ciprian Badescu
Facter execution API is stripping leading and trailing white-spaces, observed while working on https://tickets.puppetlabs.com/browse/FACT-3094 It's visible on all Facter 4 and Facter 3 version, not on Facter 2 Reproduction:{code:java} echo X$(/opt/puppetlabs/puppet/bin/ruby -e "require '/opt/puppetlabs/puppet/lib/libfacter.so'; puts Facter::Core::Execution.execute('echo \" A B \"') ")YXA BY [root@urgent-equating ~]# gem install facterFetching: facter-4.2.5.gem (100%)Successfully installed facter-4.2.51 gem installed[root@urgent-equating ~]# echo X$(ruby -e "require 'facter'; puts Facter::Core::Execution.execute('echo \" A B \"') ")YXA BY [root@urgent-equating ~]# gem uninstall facterRemove executables: facterin addition to the gem? [Yn] yRemoving facterSuccessfully uninstalled facter-4.2.5[root@urgent-equating ~]# gem install facter -v 2.5.7Fetching: facter-2.5.7.gem (100%)Successfully installed facter-2.5.71 gem installed[root@urgent-equating ~]# echo X$(ruby -e "require 'facter'; puts Facter::Core::Execution.execute('echo \" A B \"') ")YX A B Y {code} It's visible on all Facter 4 version, not on Facter 2
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3095) Build Facter for JRuby on redhatfips-8-x86_64
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3095 Build Facter for JRuby on redhatfips-8-x86_64 Change By: Ciprian Badescu The [Facter configurations in puppet-agent|https://github.com/puppetlabs/puppet-agent/blob/ master 1dbd7d46f9adcc0b90d93c51c856933c9e8f6ea3 /configs/components/facter.rb #L44-L45 ] needs to be updated to build Facter for JRuby on redhatfips-8-x86_64. 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.423338.1636748933000.6964.1636982040101%40Atlassian.JIRA.
Jira (FACT-3096) facter execution API is stripping spaces
Title: Message Title
Ciprian Badescu created an issue
Facter / FACT-3096
facter execution API is stripping spaces
Issue Type:
Bug
Affects Versions:
FACT 4.2.5
Assignee:
Unassigned
Created:
2021/11/15 1:57 AM
Priority:
Normal
Reporter:
Ciprian Badescu
Facter execution API is stripping leading and trailing white-spaces, observed while working on https://tickets.puppetlabs.com/browse/FACT-3094 Reproduction:
[root@urgent-equating ~]# gem install facter
Fetching: facter-4.2.5.gem (100%)
Successfully installed facter-4.2.5
1 gem installed
[root@urgent-equating ~]# echo X$(ruby -e "require 'facter'; puts Facter::Core::Execution.execute('echo \" A B \"') ")Y
Jira (FACT-3094) DEBUG Facter::Resolvers::Aix::Mountpoints - Could not resolve mountpoints
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3094 DEBUG Facter::Resolvers::Aix::Mountpoints - Could not resolve mountpoints Change By: Ciprian Badescu Sprint: NW - 2021-11-17 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.423320.1636725775000.6744.1636964700041%40Atlassian.JIRA.
