Jira (PUP-10212) SSL negotiation fails with "tls_process_ske_dhe:dh key too small"
Title: Message Title Justin Stoller commented on PUP-10212 Re: SSL negotiation fails with "tls_process_ske_dhe:dh key too small" We typically target the latest and earliest versions of a major OS release. ie, we have Redhat 7.1 in our CI system for that compatibility guarantee, and that image comes with Java 1.8 b08. I have a feeling we can make an exception that users should have been upgrading to builds of the JDK with better security, even if they've stayed on jdk8. I'll have to run that by RE or Product first and get the images updated. I'm out next week so I won't get an answer for a bit. 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.336537.1574710008000.141709.1613182200035%40Atlassian.JIRA.
Jira (PUP-10816) selinux support missing for zfs
Title: Message Title Carson Gaspar commented on PUP-10816 Re: selinux support missing for zfs The fix is trivial - add zfs to the filesystem list. What can I do to get this applied upstream? 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.380435.1607463462000.141491.1613170500144%40Atlassian.JIRA.
Jira (PUP-10920) Communicate scope and timeline of next release (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10920 Communicate scope and timeline of next release (Puppet Platform 6.21.1) Change By: Eric Griswold Epic Link: PUP-10911 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.387547.161316838.141448.1613168401652%40Atlassian.JIRA.
Jira (PUP-10913) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10913 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.21.1) Change By: Eric Griswold Epic Link: PUP-10911 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.387538.1613168349000.141434.1613168401260%40Atlassian.JIRA.
Jira (PUP-10913) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10913 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.21.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/02/12 2:19 PM Due Date: 2021/02/12 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10912) Prepare JIRA and Confluence for release (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10912 Prepare JIRA and Confluence for release (Puppet Platform 6.21.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/02/12 2:19 PM Due Date: 2021/02/12 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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.21.1 and puppet-agent 6.21.1 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-10918) Send release announcement (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10918 Send release announcement (Puppet Platform 6.21.1) Issue Type: Task Assignee: Jacklyn Kinsler Created: 2021/02/12 2:19 PM Due Date: 2021/02/16 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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.21.1 is now available".
Jira (PUP-10915) Prepare release announcement (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10915 Prepare release announcement (Puppet Platform 6.21.1) Issue Type: Task Assignee: Claire Cadman Created: 2021/02/12 2:19 PM Due Date: 2021/02/15 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10919) Update Confluence and JIRA based on release (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10919 Update Confluence and JIRA based on release (Puppet Platform 6.21.1) Change By: Eric Griswold Epic Link: PUP-10911 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.387546.1613168377000.141446.1613168401564%40Atlassian.JIRA.
Jira (PUP-10914) Prepare documentation updates and release notes (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10914 Prepare documentation updates and release notes (Puppet Platform 6.21.1) Change By: Eric Griswold Epic Link: PUP-10911 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.387539.1613168352000.141436.1613168401275%40Atlassian.JIRA.
Jira (PUP-10915) Prepare release announcement (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10915 Prepare release announcement (Puppet Platform 6.21.1) Change By: Eric Griswold Epic Link: PUP-10911 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.387540.1613168355000.141438.1613168401365%40Atlassian.JIRA.
Jira (PUP-10911) Puppet Platform 6.21.1 Release - 2021-02-16
Title: Message Title Eric Griswold created an issue Puppet / PUP-10911 Puppet Platform 6.21.1 Release - 2021-02-16 Issue Type: Epic Assignee: Nirupama Mantha Created: 2021/02/12 2:19 PM Due Date: 2021/02/16 Priority: Normal Reporter: Eric Griswold Puppet Platform 6.21.1 Release - 2021-02-16 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10914) Prepare documentation updates and release notes (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10914 Prepare documentation updates and release notes (Puppet Platform 6.21.1) Issue Type: Task Assignee: Claire Cadman Created: 2021/02/12 2:19 PM Due Date: 2021/02/14 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10916) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10916 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.21.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/02/12 2:19 PM Due Date: 2021/02/15 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10919) Update Confluence and JIRA based on release (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10919 Update Confluence and JIRA based on release (Puppet Platform 6.21.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/02/12 2:19 PM Due Date: 2021/02/17 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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 des
Jira (PUP-10918) Send release announcement (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10918 Send release announcement (Puppet Platform 6.21.1) Change By: Eric Griswold Epic Link: PUP-10911 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.387545.1613168373000.141444.1613168401512%40Atlassian.JIRA.
Jira (PUP-10917) Publish documentation and updates and release notes (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10917 Publish documentation and updates and release notes (Puppet Platform 6.21.1) Change By: Eric Griswold Epic Link: PUP-10911 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.387543.1613168366000.141442.1613168401425%40Atlassian.JIRA.
Jira (PUP-10912) Prepare JIRA and Confluence for release (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10912 Prepare JIRA and Confluence for release (Puppet Platform 6.21.1) Change By: Eric Griswold Epic Link: PUP-10911 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.387537.1613168345000.141432.1613168401172%40Atlassian.JIRA.
Jira (PUP-10920) Communicate scope and timeline of next release (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10920 Communicate scope and timeline of next release (Puppet Platform 6.21.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/02/12 2:19 PM Due Date: 2021/02/17 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10916) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10916 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.21.1) Change By: Eric Griswold Epic Link: PUP-10911 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.387542.1613168362000.141440.1613168401413%40Atlassian.JIRA.
Jira (PUP-10917) Publish documentation and updates and release notes (Puppet Platform 6.21.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10917 Publish documentation and updates and release notes (Puppet Platform 6.21.1) Issue Type: Task Assignee: Claire Cadman Created: 2021/02/12 2:19 PM Due Date: 2021/02/16 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10910) Communicate scope and timeline of next release (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10910 Communicate scope and timeline of next release (Puppet Platform 7.4.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/02/12 2:17 PM Due Date: 2021/02/17 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10909) Update Confluence and JIRA based on release (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10909 Update Confluence and JIRA based on release (Puppet Platform 7.4.1) Change By: Eric Griswold Epic Link: PUP-10901 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.387524.1613168221000.141405.1613168280352%40Atlassian.JIRA.
Jira (PUP-10910) Communicate scope and timeline of next release (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10910 Communicate scope and timeline of next release (Puppet Platform 7.4.1) Change By: Eric Griswold Epic Link: PUP-10901 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.387525.1613168224000.141407.1613168280439%40Atlassian.JIRA.
Jira (PUP-10909) Update Confluence and JIRA based on release (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10909 Update Confluence and JIRA based on release (Puppet Platform 7.4.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/02/12 2:17 PM Due Date: 2021/02/17 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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 desc
Jira (PUP-10907) Publish documentation and updates and release notes (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10907 Publish documentation and updates and release notes (Puppet Platform 7.4.1) Change By: Eric Griswold Epic Link: PUP-10901 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.387521.1613168209000.141399.1613168220560%40Atlassian.JIRA.
Jira (PUP-10903) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10903 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.4.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/02/12 2:16 PM Due Date: 2021/02/12 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10907) Publish documentation and updates and release notes (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10907 Publish documentation and updates and release notes (Puppet Platform 7.4.1) Issue Type: Task Assignee: Claire Cadman Created: 2021/02/12 2:16 PM Due Date: 2021/02/16 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10901) Puppet Platform 7.4.1 Release - 2021-02-16
Title: Message Title Eric Griswold created an issue Puppet / PUP-10901 Puppet Platform 7.4.1 Release - 2021-02-16 Issue Type: Epic Assignee: Nirupama Mantha Created: 2021/02/12 2:16 PM Due Date: 2021/02/16 Priority: Normal Reporter: Eric Griswold Puppet Platform 7.4.1 Release - 2021-02-16 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10902) Prepare JIRA and Confluence for release (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10902 Prepare JIRA and Confluence for release (Puppet Platform 7.4.1) Change By: Eric Griswold Epic Link: PUP-10901 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.387515.1613168189000.141389.1613168220379%40Atlassian.JIRA.
Jira (PUP-10903) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10903 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.4.1) Change By: Eric Griswold Epic Link: PUP-10901 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.387516.1613168192000.141391.1613168220393%40Atlassian.JIRA.
Jira (PUP-10905) Prepare release announcement (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10905 Prepare release announcement (Puppet Platform 7.4.1) Issue Type: Task Assignee: Claire Cadman Created: 2021/02/12 2:16 PM Due Date: 2021/02/15 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10905) Prepare release announcement (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10905 Prepare release announcement (Puppet Platform 7.4.1) Change By: Eric Griswold Epic Link: PUP-10901 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.387518.1613168199000.141395.1613168220495%40Atlassian.JIRA.
Jira (PUP-10908) Send release announcement (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10908 Send release announcement (Puppet Platform 7.4.1) Change By: Eric Griswold Epic Link: PUP-10901 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.387523.1613168217000.141401.1613168220662%40Atlassian.JIRA.
Jira (PUP-10902) Prepare JIRA and Confluence for release (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10902 Prepare JIRA and Confluence for release (Puppet Platform 7.4.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/02/12 2:16 PM Due Date: 2021/02/12 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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.4.1 and puppet-agent 7.4.1 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to re
Jira (PUP-10904) Prepare documentation updates and release notes (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10904 Prepare documentation updates and release notes (Puppet Platform 7.4.1) Change By: Eric Griswold Epic Link: PUP-10901 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.387517.1613168196000.141393.1613168220447%40Atlassian.JIRA.
Jira (PUP-10908) Send release announcement (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10908 Send release announcement (Puppet Platform 7.4.1) Issue Type: Task Assignee: Jacklyn Kinsler Created: 2021/02/12 2:16 PM Due Date: 2021/02/16 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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.4.1 is now available".
Jira (PUP-10906) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10906 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.4.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2021/02/12 2:16 PM Due Date: 2021/02/15 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10906) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10906 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.4.1) Change By: Eric Griswold Epic Link: PUP-10901 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.387520.1613168206000.141397.1613168220548%40Atlassian.JIRA.
Jira (PUP-10904) Prepare documentation updates and release notes (Puppet Platform 7.4.1)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10904 Prepare documentation updates and release notes (Puppet Platform 7.4.1) Issue Type: Task Assignee: Claire Cadman Created: 2021/02/12 2:16 PM Due Date: 2021/02/14 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-02-16) 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-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title Josh Cooper commented on PUP-10896 Re: Puppet users with forcelocal are no longer idempotent Passed CI in c683110fc0c376d226750c2898ea724c33d75791 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.386956.1612964187000.140768.1613149980334%40Atlassian.JIRA.
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10896 Puppet users with forcelocal are no longer idempotent Change By: Josh Cooper Fix Version/s: PUP 6.21.1 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.386956.1612964187000.140758.1613149740027%40Atlassian.JIRA.
Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10896 Puppet users with forcelocal are no longer idempotent Change By: Josh Cooper Fix Version/s: PUP 7.4.1 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.386956.1612964187000.140757.1613149440027%40Atlassian.JIRA.
Jira (PDB-5018) Provide way to stop/start command processing using ExecutorService
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie PuppetDB / PDB-5018 Provide way to stop/start command processing using ExecutorService Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.386968.1612970282000.140726.1613147820036%40Atlassian.JIRA.
Jira (PUP-10899) Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10899
Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Change By:
Luchian Nemes
Our [puppetlabs-acl|https://github.com/luchihoratiu/puppetlabs-acl] module lists changes with the users under *APPLICATION PACKAGE AUTHORITY* as a known limitation as follows:{panel} When referring to accounts in the {{APPLICATION PACKAGE AUTHORITY}}, use either their SID values or their unqualified names. The Windows API has well documented bugs preventing the fully qualified account names from being used. * {{S-1-15-2-1}} or {{ALL APPLICATION PACKAGES}}, but _not_ {{APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES}}. This account may only be referenced on Windows 2012R2 (kernel 6.3) or newer. * {{S-1-15-2-2}} or {{ALL RESTRICTED APPLICATION PACKAGES}}, but _not_ {{APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES}}. This account may only be referenced on Windows 2016 (kernel 10.0) or newer.{panel}Using above advice, the following manifest works and is idempotent :{code:puppet}acl { 'C:\\My Folder': permissions => [ { identity => 'ALL RESTRICTED APPLICATION PACKAGES', rights => ['read','write','execute']} ],}{code}But when trying to add other permissions (new ones), the following error occurs: *Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass* *C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:25:in `from_string_to_wide_string'* Example:{code:puppet}acl { 'C:\\My Folder': permissions => [ { identity => 'Administrators', rights => ['read','write','execute']} ],}{code}This limitation is brought by [puppet|https://github.com/puppetlabs/puppet] implementation of [https://github.com/puppetlabs/puppet/blob/main/lib/puppet/util/windows/principal.rb#L47] which takes the username as it is. A special filtering for usernames starting with *APPLICATION PACKAGE AUTHORITY\ \ * (and split it accordingly if so) would solve this issue.
Add Comment
Jira (PUP-10899) Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10899
Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Change By:
Luchian Nemes
Our [puppetlabs-acl|https://github.com/luchihoratiu/puppetlabs-acl] module lists changes with the users under *APPLICATION PACKAGE AUTHORITY* as a known limitation as follows:{panel} When referring to accounts in the {{APPLICATION PACKAGE AUTHORITY}}, use either their SID values or their unqualified names. The Windows API has well documented bugs preventing the fully qualified account names from being used. * {{S-1-15-2-1}} or {{ALL APPLICATION PACKAGES}}, but _not_ {{APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES}}. This account may only be referenced on Windows 2012R2 (kernel 6.3) or newer. * {{S-1-15-2-2}} or {{ALL RESTRICTED APPLICATION PACKAGES}}, but _not_ {{APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES}}. This account may only be referenced on Windows 2016 (kernel 10.0) or newer.{panel}Using above advice, the following manifest works and is idempotent :{code:puppet}acl { 'C:\\My Folder': permissions => [ { identity => 'ALL RESTRICTED APPLICATION PACKAGES', rights => ['read','write','execute']} ],}{code}But when trying to add other permissions (new ones), the following error occurs: *Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass* *C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:25:in `from_string_to_wide_string'* Example:{code:puppet}acl { 'C:\\My Folder': permissions => [ { identity => 'Administrators', rights => ['read','write','execute']} ],}{code}This limitation is brought by [puppet|https://github.com/puppetlabs/puppet] implementation of [https://github.com/puppetlabs/puppet/blob/main/lib/puppet/util/windows/principal.rb#L47] which takes the username as it is. A special filtering for usernames starting with *APPLICATION PACKAGE AUTHORITY\ \ * (and split it accordingly if so) would solve this issue.
Add Comment
Jira (PUP-10899) Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10899
Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Change By:
Luchian Nemes
Our [puppetlabs-acl|https://github.com/luchihoratiu/puppetlabs-acl] module lists changes with the users under *APPLICATION PACKAGE AUTHORITY* as a known limitation as follows:{panel} When referring to accounts in the {{APPLICATION PACKAGE AUTHORITY}}, use either their SID values or their unqualified names. The Windows API has well documented bugs preventing the fully qualified account names from being used. * {{S-1-15-2-1}} or {{ALL APPLICATION PACKAGES}}, but _not_ {{APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES}}. This account may only be referenced on Windows 2012R2 (kernel 6.3) or newer. * {{S-1-15-2-2}} or {{ALL RESTRICTED APPLICATION PACKAGES}}, but _not_ {{APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES}}. This account may only be referenced on Windows 2016 (kernel 10.0) or newer.{panel}Using above advice, the following manifest works and is idempotent :{code:puppet}acl { 'C:\\My Folder': permissions => [ { identity => 'ALL RESTRICTED APPLICATION PACKAGES', rights => ['read','write','execute']} ],}{code}But when trying to add other permissions (new ones), the following error occurs: *Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass* *C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:25:in `from_string_to_wide_string'* Example:{code:puppet}acl { 'C:\\My Folder': permissions => [ { identity => 'Administrators', rights => ['read','write','execute']} ],}{code}This limitation is brought by [puppet|https://github.com/puppetlabs/puppet] implementation of [https://github.com/puppetlabs/puppet/blob/main/lib/puppet/util/windows/principal.rb#L47] which takes the username as it is. A special filtering for usernames starting with *APPLICATION PACKAGE AUTHORITY \\ * (and split it accordingly if so) would solve this issue.
Add Comment
Jira (PUP-10899) Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10899
Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Change By:
Luchian Nemes
Our [puppetlabs-acl|https://github.com/luchihoratiu/puppetlabs-acl] module lists changes with the users under *APPLICATION PACKAGE AUTHORITY* as a known limitation as follows:{panel} When referring to accounts in the {{APPLICATION PACKAGE AUTHORITY}}, use either their SID values or their unqualified names. The Windows API has well documented bugs preventing the fully qualified account names from being used. * {{S-1-15-2-1}} or {{ALL APPLICATION PACKAGES}}, but _not_ {{APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES}}. This account may only be referenced on Windows 2012R2 (kernel 6.3) or newer. * {{S-1-15-2-2}} or {{ALL RESTRICTED APPLICATION PACKAGES}}, but _not_ {{APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES}}. This account may only be referenced on Windows 2016 (kernel 10.0) or newer.{panel}Using above advice, the following manifest works and is idempotent :{code:puppet}acl { 'C:\\My Folder': permissions => [ { identity => 'ALL RESTRICTED APPLICATION PACKAGES', rights => ['read','write','execute']} ],}{code}But when trying to add other permissions (new ones), the following error occurs:*Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass* *C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:25:in `from_string_to_wide_string'* Example:{code:puppet}acl { 'C:\\My Folder': permissions => [ { identity => 'Administrators', rights => ['read','write','execute']} ],}{code}This limitation is brought by [puppet|https://github.com/puppetlabs/puppet] implementation of [https://github.com/puppetlabs/puppet/blob/main/lib/puppet/util/windows/principal.rb#L47] which takes the username as it is. A special filtering for usernames starting with *APPLICATION PACKAGE AUTHORITY\\* (and split it accordingly if so) would solve this issue.
Add Comment
Jira (PUP-10899) Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10899
Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Change By:
Luchian Nemes
Our [puppetlabs-acl|https://github.com/luchihoratiu/puppetlabs-acl] module lists changes with the users under *APPLICATION PACKAGE AUTHORITY* as a known limitation as follows:{panel} When referring to accounts in the {{APPLICATION PACKAGE AUTHORITY}}, use either their SID values or their unqualified names. The Windows API has well documented bugs preventing the fully qualified account names from being used. * {{S-1-15-2-1}} or {{ALL APPLICATION PACKAGES}}, but _not_ {{APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES}}. This account may only be referenced on Windows 2012R2 (kernel 6.3) or newer. * {{S-1-15-2-2}} or {{ALL RESTRICTED APPLICATION PACKAGES}}, but _not_ {{APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES}}. This account may only be referenced on Windows 2016 (kernel 10.0) or newer.{panel}Using above advice, the following manifest works and is idempotent :{code:puppet}acl { 'C:\\My Folder': permissions => [ { identity => 'ALL RESTRICTED APPLICATION PACKAGES', rights => ['read','write','execute']} ],}{code}But when trying to add other permissions (new ones), the following error occurs:*Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass* *C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:25:in `from_string_to_wide_string'* Example:{code:puppet}acl { 'C:\\My Folder': permissions => [ { identity => 'Administrators', rights => ['read','write','execute']} ],}{code}This limitation is brought by [puppet|https://github.com/puppetlabs/puppet] implementation of [https://github.com/puppetlabs/puppet/blob/main/lib/puppet/util/windows/principal.rb#L47] which takes the username as it is. A special filtering for usernames starting with *APPLICATION PACKAGE AUTHORITY \\ * (and split it accordingly if so) would solve this issue.
Add Comment
