Jira (PDB-5082) Update winston (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-5082 Update winston (PuppetDB 6.16.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/03/25 1:14 PM Due Date: 2021/04/21 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-20) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-5078) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-5078 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.16.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/03/25 1:14 PM Due Date: 2021/04/06 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-20) Ensure all tickets referenced in the commit log have a the release's fixVersion, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by checking out the branches you will be releasing, ensuring they are in sync with the upstream puppetlabs repo and running the rake task bundle install; bundle exec rake release:reconcile[NEXT_VER,LAST_VER] This assumes you have the puppetdb repo as the cwd and the pe repo at ../pe-puppetdb-extensions. These can be overridden by the PDB_PATH and PDB_PE_PATH environment variables. The rake task will explain any mismatches that exist between Jira and the repos and ask you to investigate any tickets that do not start with a PDB ticket, (maint), (docs), or (i18n) Add Comment
Jira (PDB-5078) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5078 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.16.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392891.1616703264000.174656.1616703300676%40Atlassian.JIRA.
Jira (PDB-5081) Check builds, promote to PE (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-5081 Check builds, promote to PE (PuppetDB 6.16.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/03/25 1:14 PM Due Date: 2021/04/09 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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 promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. If a release branch has already been cut Rebuild the pacakge promotion job with the release branch set instead of master or 2018.1.x. Once it's promoted to the release branch checkout the release branch of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb bundle exec rake report:packages If there were any important dependency bumps, such as to fix a bug or CVE, verify that they were updated by navigating to the release and then to the pe-puppetdb package on [pebuildinfo|pebuildinfo.slice.puppetlabs.net/].
Jira (PDB-5079) Draft release notes (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-5079 Draft release notes (PuppetDB 6.16.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/03/25 1:14 PM Due Date: 2021/04/18 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-20) Write release notes for the release based on the tickets found in the previous step. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown. Request review from the docs team by pinging @clairecadman in the opened PR, at least one day before Ready to Ship The opened PR should be approved prior to a go\/no-go. Release notes must be ready before a go. Docs are built daily and at release time. If notes need to be published out of band ask in `#prod-docs`.
Jira (PDB-5077) Merge-up, branch, and create pipelines (PuppetDB 6.16.0)
Title: Message Title
Morgan Rhodes created an issue
PuppetDB / PDB-5077
Merge-up, branch, and create pipelines (PuppetDB 6.16.0)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2021/03/25 1:14 PM
Due Date:
2021/04/06
Priority:
Normal
Reporter:
Morgan Rhodes
(Initial planned release date: 2021-04-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-5081) Check builds, promote to PE (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5081 Check builds, promote to PE (PuppetDB 6.16.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392894.1616703275000.174662.1616703300945%40Atlassian.JIRA.
Jira (PDB-5077) Merge-up, branch, and create pipelines (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5077 Merge-up, branch, and create pipelines (PuppetDB 6.16.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392890.1616703261000.174654.1616703300588%40Atlassian.JIRA.
Jira (PDB-5080) Bump versions, push directly, and tag (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5080 Bump versions, push directly, and tag (PuppetDB 6.16.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392893.1616703271000.174660.1616703300852%40Atlassian.JIRA.
Jira (PDB-5079) Draft release notes (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5079 Draft release notes (PuppetDB 6.16.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392892.1616703268000.174658.1616703300763%40Atlassian.JIRA.
Jira (PDB-5082) Update winston (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5082 Update winston (PuppetDB 6.16.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392896.1616703282000.174664.1616703301034%40Atlassian.JIRA.
Jira (PDB-5080) Bump versions, push directly, and tag (PuppetDB 6.16.0)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-5080 Bump versions, push directly, and tag (PuppetDB 6.16.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/03/25 1:14 PM Due Date: 2021/04/09 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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 (PUP-10991) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10991 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.22.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392868.1616703185000.174637.1616703240426%40Atlassian.JIRA.
Jira (PUP-10992) Publish documentation and updates and release notes (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10992 Publish documentation and updates and release notes (Puppet Platform 6.22.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/03/25 1:13 PM Due Date: 2021/04/20 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10994) Update Confluence and JIRA based on release (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10994 Update Confluence and JIRA based on release (Puppet Platform 6.22.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392872.1616703201000.174643.1616703240657%40Atlassian.JIRA.
Jira (PUP-10992) Publish documentation and updates and release notes (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10992 Publish documentation and updates and release notes (Puppet Platform 6.22.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392869.1616703188000.174639.1616703240480%40Atlassian.JIRA.
Jira (PUP-10991) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10991 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.22.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/03/25 1:13 PM Due Date: 2021/04/19 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10995) Communicate scope and timeline of next release (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10995 Communicate scope and timeline of next release (Puppet Platform 6.22.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392873.1616703205000.174645.1616703240745%40Atlassian.JIRA.
Jira (PUP-10993) Send release announcement (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10993 Send release announcement (Puppet Platform 6.22.0) Issue Type: Task Assignee: Jacklyn Kinsler Created: 2021/03/25 1:13 PM Due Date: 2021/04/20 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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.22.0 is now available".
Jira (PUP-10990) Prepare release announcement (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10990 Prepare release announcement (Puppet Platform 6.22.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392866.1616703178000.174635.1616703240375%40Atlassian.JIRA.
Jira (PUP-10994) Update Confluence and JIRA based on release (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10994 Update Confluence and JIRA based on release (Puppet Platform 6.22.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/03/25 1:13 PM Due Date: 2021/04/21 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10993) Send release announcement (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10993 Send release announcement (Puppet Platform 6.22.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392871.1616703196000.174641.1616703240568%40Atlassian.JIRA.
Jira (PUP-10995) Communicate scope and timeline of next release (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10995 Communicate scope and timeline of next release (Puppet Platform 6.22.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/03/25 1:13 PM Due Date: 2021/04/21 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10986) Puppet Platform 6.22.0 Release - 2021-04-20
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10986 Puppet Platform 6.22.0 Release - 2021-04-20 Issue Type: Epic Assignee: Nirupama Mantha Created: 2021/03/25 1:12 PM Due Date: 2021/04/20 Priority: Normal Reporter: Morgan Rhodes Puppet Platform 6.22.0 Release - 2021-04-20 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10987) Prepare JIRA and Confluence for release (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10987 Prepare JIRA and Confluence for release (Puppet Platform 6.22.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392863.1616703167000.174625.1616703180380%40Atlassian.JIRA.
Jira (PUP-10987) Prepare JIRA and Confluence for release (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10987 Prepare JIRA and Confluence for release (Puppet Platform 6.22.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/03/25 1:12 PM Due Date: 2021/04/07 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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.22.0 and puppet-agent 6.22.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-10989) Prepare documentation updates and release notes (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10989 Prepare documentation updates and release notes (Puppet Platform 6.22.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/03/25 1:12 PM Due Date: 2021/04/09 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10989) Prepare documentation updates and release notes (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10989 Prepare documentation updates and release notes (Puppet Platform 6.22.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392865.1616703174000.174629.1616703180556%40Atlassian.JIRA.
Jira (PUP-10988) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10988 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.22.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/03/25 1:12 PM Due Date: 2021/04/07 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10988) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10988 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.22.0) Change By: Morgan Rhodes Epic Link: PUP-10986 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392864.161670317.174627.1616703180469%40Atlassian.JIRA.
Jira (PUP-10990) Prepare release announcement (Puppet Platform 6.22.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10990 Prepare release announcement (Puppet Platform 6.22.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/03/25 1:12 PM Due Date: 2021/04/19 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10985) `puppet facts diff` does not output facts that only exist in Facter 4
Title: Message Title
Nick Walker created an issue
Puppet / PUP-10985
`puppet facts diff` does not output facts that only exist in Facter 4
Issue Type:
Task
Assignee:
Unassigned
Created:
2021/03/25 12:07 PM
Priority:
Normal
Reporter:
Nick Walker
The Problem Given the following facts
Given the following facts:
cat /opt/puppetlabs/facter/facts.d/foo.bar.txt
foo.bar=true
cat /opt/puppetlabs/facter/facts.d/c.d.json
{
"c.d":
Jira (PUP-10985) `puppet facts diff` does not output facts that only exist in Facter 4
Title: Message Title Nick Walker assigned an issue to Mihai Buzgau Puppet / PUP-10985 `puppet facts diff` does not output facts that only exist in Facter 4 Change By: Nick Walker Assignee: Mihai Buzgau Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392859.1616699279000.174573.1616699340113%40Atlassian.JIRA.
Jira (PDB-5076) Update winston (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5076 Update winston (PuppetDB 7.3.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392856.1616697611000.174535.1616697662229%40Atlassian.JIRA.
Jira (PDB-5074) Bump versions, push directly, and tag (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-5074 Bump versions, push directly, and tag (PuppetDB 7.3.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/03/25 11:40 AM Due Date: 2021/04/16 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-5074) Bump versions, push directly, and tag (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5074 Bump versions, push directly, and tag (PuppetDB 7.3.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392853.161669760.174531.1616697662052%40Atlassian.JIRA.
Jira (PDB-5075) Check builds, promote to PE (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5075 Check builds, promote to PE (PuppetDB 7.3.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392854.1616697603000.174533.1616697662140%40Atlassian.JIRA.
Jira (PDB-5076) Update winston (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-5076 Update winston (PuppetDB 7.3.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/03/25 11:40 AM Due Date: 2021/04/21 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-20) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-5075) Check builds, promote to PE (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-5075 Check builds, promote to PE (PuppetDB 7.3.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/03/25 11:40 AM Due Date: 2021/04/16 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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 promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. If a release branch has already been cut Rebuild the pacakge promotion job with the release branch set instead of master or 2018.1.x. Once it's promoted to the release branch checkout the release branch of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb bundle exec rake report:packages If there were any important dependency bumps, such as to fix a bug or CVE, verify that they were updated by navigating to the release and then to the pe-puppetdb package on [pebuildinfo|pebuildinfo.slice.puppetlabs.net/].
Jira (PDB-5071) Merge-up, branch, and create pipelines (PuppetDB 7.3.0)
Title: Message Title
Morgan Rhodes created an issue
PuppetDB / PDB-5071
Merge-up, branch, and create pipelines (PuppetDB 7.3.0)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2021/03/25 11:39 AM
Due Date:
2021/04/13
Priority:
Normal
Reporter:
Morgan Rhodes
(Initial planned release date: 2021-04-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-5073) Draft release notes (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5073 Draft release notes (PuppetDB 7.3.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392852.1616697596000.174488.1616697600443%40Atlassian.JIRA.
Jira (PDB-5072) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-5072 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.3.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/03/25 11:39 AM Due Date: 2021/04/13 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-20) Ensure all tickets referenced in the commit log have a the release's fixVersion, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by checking out the branches you will be releasing, ensuring they are in sync with the upstream puppetlabs repo and running the rake task bundle install; bundle exec rake release:reconcile[NEXT_VER,LAST_VER] This assumes you have the puppetdb repo as the cwd and the pe repo at ../pe-puppetdb-extensions. These can be overridden by the PDB_PATH and PDB_PE_PATH environment variables. The rake task will explain any mismatches that exist between Jira and the repos and ask you to investigate any tickets that do not start with a PDB ticket, (maint), (docs), or (i18n) Add Comment
Jira (PDB-5071) Merge-up, branch, and create pipelines (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5071 Merge-up, branch, and create pipelines (PuppetDB 7.3.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392850.161669759.174484.1616697600304%40Atlassian.JIRA.
Jira (PDB-5073) Draft release notes (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-5073 Draft release notes (PuppetDB 7.3.0) Issue Type: Task Assignee: Austin Blatt Created: 2021/03/25 11:39 AM Due Date: 2021/04/18 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-20) Write release notes for the release based on the tickets found in the previous step. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown. Request review from the docs team by pinging @clairecadman in the opened PR, at least one day before Ready to Ship The opened PR should be approved prior to a go\/no-go. Release notes must be ready before a go. Docs are built daily and at release time. If notes need to be published out of band ask in `#prod-docs`.
Jira (PDB-5072) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.3.0)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-5072 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.3.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392851.1616697593000.174486.1616697600392%40Atlassian.JIRA.
Jira (PUP-10983) Update Confluence and JIRA based on release (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10983 Update Confluence and JIRA based on release (Puppet Platform 7.6.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/03/25 11:38 AM Due Date: 2021/04/21 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10977) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10977 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.6.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/03/25 11:38 AM Due Date: 2021/04/14 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10978) Prepare documentation updates and release notes (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10978 Prepare documentation updates and release notes (Puppet Platform 7.6.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/03/25 11:38 AM Due Date: 2021/04/16 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10984) Communicate scope and timeline of next release (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10984 Communicate scope and timeline of next release (Puppet Platform 7.6.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392833.1616697535000.174479.1616697540894%40Atlassian.JIRA.
Jira (PUP-10984) Communicate scope and timeline of next release (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10984 Communicate scope and timeline of next release (Puppet Platform 7.6.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/03/25 11:38 AM Due Date: 2021/04/21 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10976) Prepare JIRA and Confluence for release (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10976 Prepare JIRA and Confluence for release (Puppet Platform 7.6.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/03/25 11:38 AM Due Date: 2021/04/14 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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.6.0 and puppet-agent 7.6.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-10981) Publish documentation and updates and release notes (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10981 Publish documentation and updates and release notes (Puppet Platform 7.6.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392829.1616697519000.174473.1616697540708%40Atlassian.JIRA.
Jira (PUP-10979) Prepare release announcement (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10979 Prepare release announcement (Puppet Platform 7.6.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392826.1616697508000.174469.1616697540601%40Atlassian.JIRA.
Jira (PUP-10978) Prepare documentation updates and release notes (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10978 Prepare documentation updates and release notes (Puppet Platform 7.6.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392825.1616697504000.174467.1616697540586%40Atlassian.JIRA.
Jira (PUP-10980) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10980 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.6.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/03/25 11:38 AM Due Date: 2021/04/19 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10981) Publish documentation and updates and release notes (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10981 Publish documentation and updates and release notes (Puppet Platform 7.6.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/03/25 11:38 AM Due Date: 2021/04/20 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10976) Prepare JIRA and Confluence for release (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10976 Prepare JIRA and Confluence for release (Puppet Platform 7.6.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392823.1616697497000.174463.1616697540447%40Atlassian.JIRA.
Jira (PUP-10980) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10980 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.6.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392828.1616697515000.174471.1616697540657%40Atlassian.JIRA.
Jira (PUP-10979) Prepare release announcement (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10979 Prepare release announcement (Puppet Platform 7.6.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/03/25 11:38 AM Due Date: 2021/04/19 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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-10983) Update Confluence and JIRA based on release (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10983 Update Confluence and JIRA based on release (Puppet Platform 7.6.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392832.1616697531000.174477.1616697540844%40Atlassian.JIRA.
Jira (PUP-10977) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10977 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.6.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392824.1616697501000.174465.1616697540536%40Atlassian.JIRA.
Jira (PUP-10975) Puppet Platform 7.6.0 Release - 2021-04-20
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10975 Puppet Platform 7.6.0 Release - 2021-04-20 Issue Type: Epic Assignee: Nirupama Mantha Created: 2021/03/25 11:38 AM Due Date: 2021/04/20 Priority: Normal Reporter: Morgan Rhodes Puppet Platform 7.6.0 Release - 2021-04-20 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10982) Send release announcement (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10982 Send release announcement (Puppet Platform 7.6.0) Issue Type: Task Assignee: Jacklyn Kinsler Created: 2021/03/25 11:38 AM Due Date: 2021/04/20 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2021-04-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.6.0 is now available".
Jira (PUP-10982) Send release announcement (Puppet Platform 7.6.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10982 Send release announcement (Puppet Platform 7.6.0) Change By: Morgan Rhodes Epic Link: PUP-10975 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392831.1616697527000.174475.1616697540756%40Atlassian.JIRA.
Jira (PDB-5070) Determine query that provides (dotted) factpaths
Title: Message Title
Austin Blatt commented on PDB-5070
Re: Determine query that provides (dotted) factpaths
I believe the query that can identify any top-level dotted fact names is
curl -X POST http://localhost:8080/pdb/query/v4/fact-names \
-H 'Content-Type:application/json' \
-d '{"query": ["~", "name", ".*\\..*"]}'
The exact escaping needed to make that . match only a . may differ based on where the POST is originating. From the command line my first attempt with a sngle backslash produced the error
Json parse error at line 1, column 30:
{"query": ["~", "name", ".*\..*"]}
^
Unrecognized character escape '.' (code 46)
Jira (PDB-5070) Determine query that provides (dotted) factpaths
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5070 Determine query that provides (dotted) factpaths Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392629.1616610675000.174441.1616696940323%40Atlassian.JIRA.
Jira (PUP-10974) service enable=mask fails when service isn't present
Title: Message Title
Steven Pritchard created an issue
Puppet / PUP-10974
service enable=mask fails when service isn't present
Issue Type:
Bug
Affects Versions:
PUP 7.5.0
Assignee:
Unassigned
Components:
Types and Providers
Created:
2021/03/25 11:20 AM
Priority:
Normal
Reporter:
Steven Pritchard
Puppet Version: 6.21.1, 7.5.0 Puppet Server Version: N/A OS Name/Version: CentOS 7 With the systemd provider, setting enable to mask on a service that does not exist fails. Desired Behavior: Masking a service should work whether or not the service exists (the way that setting enable to false works either way). Actual Behavior:
[root@puppet ~]# systemctl list-unit-files | grep madeup
[root@puppet ~]# puppet resource service madeup
service { 'madeup':
ensure => 'stopped',
Jira (PDB-5043) Collect common PDB queries used in PE console pages
Title: Message Title Margaret Lee commented on PDB-5043 Re: Collect common PDB queries used in PE console pages Customers that have hit issues with console queries for tracking: Duke Energy Huntington Bank SCB Progressive JPMC Cognizant CSIRO PwC Abu Dhabi cc Mihai Buzgau Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388381.1614031085000.174372.1616693340188%40Atlassian.JIRA.
Jira (PUP-10973) `puppet facts diff` output should be pretty
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10973 `puppet facts diff` output should be pretty Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392811.1616691172000.174341.1616691360256%40Atlassian.JIRA.
Jira (PUP-10973) `puppet facts diff` output should be pretty
Title: Message Title Nick Walker updated an issue Puppet / PUP-10973 `puppet facts diff` output should be pretty Change By: Nick Walker Issue Type: Task Improvement Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392811.1616691172000.174333.1616691240029%40Atlassian.JIRA.
Jira (PUP-10973) `puppet facts diff` output should be pretty
Title: Message Title
Nick Walker created an issue
Puppet / PUP-10973
`puppet facts diff` output should be pretty
Issue Type:
Task
Assignee:
Unassigned
Created:
2021/03/25 9:52 AM
Priority:
Normal
Reporter:
Nick Walker
The Problem The output of `puppet facts diff` is all smashed on one line instead of being human readable.
[root@master20198-latest-centos ~]# puppet facts diff
{"foo.bar":{"new_value":null,"old_value":"true"},"pe_postgresql_info.data_partition_available_bytes":{"new_value":59176595456,"old_value":59176505344},"platform_tag":{"new_value":"centos-7-x86_64","old_value":"el-7-x86_64"},"puppet_inventory_metadata.packages.last_collection_time":{"new_value":"0.4702s","old_value":"0.588s"}}
I have to run it through another tool like python or jq to effectively read the output
[root@master20198-latest-centos ~]# puppet facts diff | python -m json.tool
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Gabriel Nagy commented on FACT-2994 Re: selinux fact is not properly detected by Facter 4 From your previous comments I understood that selinuxfs wasn't mounted and Facter 4 still reported enabled=true I have a PR open to fix the discrepancy between Facter 3 and 4: https://github.com/puppetlabs/facter/pull/2328 Once we have a nightly build out with this I'll let you know Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.391989.1616519382000.174284.1616689680043%40Atlassian.JIRA.
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Vadym Chepkov commented on FACT-2994 Re: selinux fact is not properly detected by Facter 4 I am still curious, why you can't reproduce it In the kickstart we use to build image we have these packages section: %packages @^minimal-environment dhcp-client net-tools network-scripts tar -NetworkManager* -biosdevname -dnf-plugin-spacewalk -dracut-config-rescue -firewalld -iwl*firmware -kexec-tools -microcode_ctl
Jira (PDB-5070) Determine query that provides (dotted) factpaths
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-5070
Determine query that provides (dotted) factpaths
Change By:
Nick Walker
h1. Background Facter 4 auto-converts facts with dots in the *name* to make it a structured fact.So {code}foo.bar = true{code} becomes {code}foo = { bar => true }{code} However, you can still have dots in keys inside of a structured fact so{code} baz = { zzz.yyy => true } {code} does not change in facter 4 because keys inside of a structured fact can contain dots without getting auto-converted. Only the top level name of a fact is auto-converted when it contains dots. h1. What we need to do We need to construct a pdb query that can determine if customers currently have facts with dots in the name of the fact but not worry about keys inside of a structured fact. This is so we can find cases where users with puppet < 7 will be affected by this change and can prepare appropriately because they know they are affected.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-5070) Determine query that provides (dotted) factpaths
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-5070
Determine query that provides (dotted) factpaths
Change By:
Nick Walker
Facter 4 auto-converts facts with dots in the *name* to make it a structured fact.So {code}foo.bar = true{code} becomes {code}foo = { bar => true }{code} However, you can still have dots in keys inside of a structured fact so{code} baz = { zzz.yyy => true } {code} does not change in facter 4 because keys inside of a structured fact can contain dots without getting auto-converted. Only the top level name of a fact is auto-converted when it contains dots.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit
Jira (PDB-5043) Collect common PDB queries used in PE console pages
Title: Message Title Florin Dragos commented on PDB-5043 Re: Collect common PDB queries used in PE console pages Collected PE console queries: https://gist.github.com/florindragos/60ecf47da45911a60d091d2d863b87c6 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388381.1614031085000.174133.1616683140034%40Atlassian.JIRA.
Jira (FACT-2996) Performance regression gathering networking facts in facter 4.x
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-2996 Performance regression gathering networking facts in facter 4.x Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392713.1616618206000.174093.1616679660030%40Atlassian.JIRA.
Jira (FACT-2997) Domain fact cannot be resolved on travis without ffi
Title: Message Title Jake Spain updated an issue Facter / FACT-2997 Domain fact cannot be resolved on travis without ffi Change By: Jake Spain Labels: customer0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392776.1616656236000.174084.1616678880027%40Atlassian.JIRA.
Jira (FACT-2997) Domain fact cannot be resolved on travis without ffi
Title: Message Title Jake Spain commented on FACT-2997 Re: Domain fact cannot be resolved on travis without ffi We also started experiencing a similar issue when the facter gem was bumped from 4.0.51 to 5.0.52 with tests run by cd4pe on puppetlabs-modules. Here is an example of a failing job #6253, which boils down to the fact "$trusted['certname']" being unable to resolve anywhere in our profiles, such as this. I can reproduce the failure locally by downloading the version of the control repo used for testing here, extracting and cd into the tarball dir and running "docker run --rm -v ~/.ssh:/root/.ssh -v $(PWD)/jobs/unix:/cd4pe_job -v $(PWD)/repo:/repo genebean/puppet-dev-tools:update-testing "/cd4pe_job/JOB"". Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392776.1616656236000.174083.1616678820037%40Atlassian.JIRA.
Jira (FACT-2997) Domain fact cannot be resolved on travis without ffi
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2997 Domain fact cannot be resolved on travis without ffi Change By: Gheorghe Popescu https://github.com/puppetlabs/facter/pull/2315 changed the way we resolve hostname on domain, also relying on FFI.When FFI is not installed, Facter will not continue to search for hostname and domain and it will not resolve the facts.This was noticed in puppetserver-ca-cli pipeline.A fix was done in https://github.com/puppetlabs/facter/pull/2318 but this is not sufficient.If FFI cannot be load loaded , we must log a debug message and continue the search. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Gabriel Nagy commented on FACT-2994 Re: selinux fact is not properly detected by Facter 4 Vadym Chepkov Indeed the selinux fact behaves differently on Facter 4 as it sets enabled = true as soon as it finds the mountpoint in /proc/self/mounts, without also checking for the config file. However, since you don't have selinux mounted at all, I'm not sure what would cause the fact to appear as true. In any case, this might be fixed if we also check for the existence of the config file, like Facter 3 does. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.391989.1616519382000.174056.1616673840103%40Atlassian.JIRA.
Jira (PUP-10972) puppet facts diff produces unexpected results
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10972 puppet facts diff produces unexpected results Change By: Mihai Buzgau Labels: community Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392050.1616527457000.173908.1616660880188%40Atlassian.JIRA.
Jira (FACT-2996) Performance regression gathering networking facts in facter 4.x
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2996 Performance regression gathering networking facts in facter 4.x Change By: Mihai Buzgau Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392713.1616618206000.173899.1616660700044%40Atlassian.JIRA.
Jira (FACT-2996) Performance regression gathering networking facts in facter 4.x
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2996 Performance regression gathering networking facts in facter 4.x Change By: Mihai Buzgau Sprint: NW - 2021-03-31 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392713.1616618206000.173900.1616660700089%40Atlassian.JIRA.
Jira (FACT-2996) Performance regression gathering networking facts in facter 4.x
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2996 Performance regression gathering networking facts in facter 4.x Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392713.1616618206000.173898.1616660640220%40Atlassian.JIRA.
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2994 selinux fact is not properly detected by Facter 4 Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.391989.1616519382000.173895.1616660640068%40Atlassian.JIRA.
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2994 selinux fact is not properly detected by Facter 4 Change By: Mihai Buzgau Sprint: NW - 2021-03-31 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.391989.1616519382000.173897.1616660640176%40Atlassian.JIRA.
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2994 selinux fact is not properly detected by Facter 4 Change By: Mihai Buzgau Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.391989.1616519382000.173896.1616660640131%40Atlassian.JIRA.
Jira (FACT-2997) Domain fact cannot be resolved on travis without ffi
Title: Message Title Gheorghe Popescu created an issue Facter / FACT-2997 Domain fact cannot be resolved on travis without ffi Issue Type: Bug Assignee: Unassigned Created: 2021/03/25 12:10 AM Priority: Normal Reporter: Gheorghe Popescu https://github.com/puppetlabs/facter/pull/2315 changed the way we resolve hostname on domain, also relying on FFI. When FFI is not installed, Facter will not continue to search for hostname and domain and it will not resolve the facts. This was noticed in puppetserver-ca-cli pipeline. A fix was done in https://github.com/puppetlabs/facter/pull/2318 but this is not sufficient. If FFI cannot be load, we must log a debug message and continue the search. Add Comment
Jira (PUP-10971) Provide JSON option for last run summary
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10971 Provide JSON option for last run summary Change By: Mihai Buzgau Labels: community Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.391912.1616381463000.173885.1616655900031%40Atlassian.JIRA.
Jira (FACT-2996) Performance regression gathering networking facts in facter 4.x
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2996 Performance regression gathering networking facts in facter 4.x Change By: Mihai Buzgau Labels: community Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392713.1616618206000.173884.1616655480034%40Atlassian.JIRA.
