Jira (PDB-5118) Bump versions, push directly, and tag (PuppetDB 7.4.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5118 Bump versions, push directly, and tag (PuppetDB 7.4.0) Issue Type: Task Assignee: Zachary Kent Created: 2021/04/28 2:44 PM Due Date: 2021/05/21 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Check that puppetdb and pe-puppetdb-extensions are on the same version of clj-parent, and that is the same clj-parent version that puppetserver will release with. Disable automatic promotions: If a PE release branch has not been cut, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing.
Jira (PDB-5115) Merge-up, branch, and create pipelines (PuppetDB 7.4.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5115 Merge-up, branch, and create pipelines (PuppetDB 7.4.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397522.1619646244000.21229.1619646301709%40Atlassian.JIRA.
Jira (PDB-5119) Check builds, promote to PE (PuppetDB 7.4.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5119 Check builds, promote to PE (PuppetDB 7.4.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397526.1619646259000.21237.1619646302065%40Atlassian.JIRA.
Jira (PDB-5120) Update winston (PuppetDB 7.4.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5120 Update winston (PuppetDB 7.4.0) Issue Type: Task Assignee: Zachary Kent Created: 2021/04/28 2:44 PM Due Date: 2021/05/26 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PDB-5117) Draft release notes (PuppetDB 7.4.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5117 Draft release notes (PuppetDB 7.4.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397524.1619646252000.21233.1619646301888%40Atlassian.JIRA.
Jira (PDB-5117) Draft release notes (PuppetDB 7.4.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5117 Draft release notes (PuppetDB 7.4.0) Issue Type: Task Assignee: Zachary Kent Created: 2021/04/28 2:44 PM Due Date: 2021/05/23 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) Write release notes for the release based on the tickets found in the previous step. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown. Request review from the docs team by pinging @clairecadman in the opened PR, at least one day before Ready to Ship The opened PR should be approved prior to a go\/no-go. Release notes must be ready before a go. Docs are built daily and at release time. If notes need to be published out of band ask in `#prod-docs`.
Jira (PDB-5118) Bump versions, push directly, and tag (PuppetDB 7.4.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5118 Bump versions, push directly, and tag (PuppetDB 7.4.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397525.1619646256000.21235.1619646301976%40Atlassian.JIRA.
Jira (PDB-5120) Update winston (PuppetDB 7.4.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5120 Update winston (PuppetDB 7.4.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397528.1619646268000.21239.1619646302152%40Atlassian.JIRA.
Jira (PDB-5115) Merge-up, branch, and create pipelines (PuppetDB 7.4.0)
Title: Message Title
Eric Griswold created an issue
PuppetDB / PDB-5115
Merge-up, branch, and create pipelines (PuppetDB 7.4.0)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2021/04/28 2:44 PM
Due Date:
2021/05/18
Priority:
Normal
Reporter:
Eric Griswold
(Initial planned release date: 2021-05-25) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> master
Important: Do this for both the core puppetdb repo and the pe-puppetdb-extensions repo! These should be submitted as PRs and merged after tests pass, if there's anything remotely interesting about the merges. If the merges are boring, then direct push is fine. Then, prepare the branch for release:
Jira (PDB-5119) Check builds, promote to PE (PuppetDB 7.4.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5119 Check builds, promote to PE (PuppetDB 7.4.0) Issue Type: Task Assignee: Zachary Kent Created: 2021/04/28 2:44 PM Due Date: 2021/05/21 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. If a release branch has already been cut Rebuild the pacakge promotion job with the release branch set instead of master or 2018.1.x. Once it's promoted to the release branch checkout the release branch of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb bundle exec rake report:packages If there were any important dependency bumps, such as to fix a bug or CVE, verify that they were updated by navigating to the release and then to the pe-puppetdb package on [pebuildinfo|pebuildinfo.slice.puppetlabs.net/].
Jira (PDB-5116) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.4.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5116 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.4.0) Issue Type: Task Assignee: Zachary Kent Created: 2021/04/28 2:44 PM Due Date: 2021/05/18 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) Ensure all tickets referenced in the commit log have a the release's fixVersion, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by checking out the branches you will be releasing, ensuring they are in sync with the upstream puppetlabs repo and running the rake task bundle install; bundle exec rake release:reconcile[NEXT_VER,LAST_VER] This assumes you have the puppetdb repo as the cwd and the pe repo at ../pe-puppetdb-extensions. These can be overridden by the PDB_PATH and PDB_PE_PATH environment variables. The rake task will explain any mismatches that exist between Jira and the repos and ask you to investigate any tickets that do not start with a PDB ticket, (maint), (docs), or (i18n) Add Comment
Jira (PDB-5116) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.4.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5116 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.4.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397523.1619646248000.21231.1619646301797%40Atlassian.JIRA.
Jira (PUP-11044) Communicate scope and timeline of next release (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11044 Communicate scope and timeline of next release (Puppet Platform 7.7.0) Issue Type: Task Assignee: Pintu Sethi Created: 2021/04/28 2:43 PM Due Date: 2021/05/26 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-11044) Communicate scope and timeline of next release (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11044 Communicate scope and timeline of next release (Puppet Platform 7.7.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397505.1619646182000.21199.1619646240476%40Atlassian.JIRA.
Jira (PUP-11040) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11040 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.7.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397500.161964616.21183.1619646180864%40Atlassian.JIRA.
Jira (PUP-11043) Update Confluence and JIRA based on release (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11043 Update Confluence and JIRA based on release (Puppet Platform 7.7.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397504.1619646178000.21189.1619646181145%40Atlassian.JIRA.
Jira (PUP-11037) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11037 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.7.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397496.1619646144000.21177.1619646180629%40Atlassian.JIRA.
Jira (PUP-11042) Send release announcement (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11042 Send release announcement (Puppet Platform 7.7.0) Issue Type: Task Assignee: Jacklyn Kinsler Created: 2021/04/28 2:42 PM Due Date: 2021/05/25 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 7.7.0 is now available".
Jira (PUP-11036) Prepare JIRA and Confluence for release (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11036 Prepare JIRA and Confluence for release (Puppet Platform 7.7.0) Issue Type: Task Assignee: Pintu Sethi Created: 2021/04/28 2:42 PM Due Date: 2021/05/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 7.7.0 and puppet-agent 7.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-11041) Publish documentation and updates and release notes (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11041 Publish documentation and updates and release notes (Puppet Platform 7.7.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/04/28 2:42 PM Due Date: 2021/05/25 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-11036) Prepare JIRA and Confluence for release (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11036 Prepare JIRA and Confluence for release (Puppet Platform 7.7.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397495.161964614.21175.1619646180537%40Atlassian.JIRA.
Jira (PUP-11041) Publish documentation and updates and release notes (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11041 Publish documentation and updates and release notes (Puppet Platform 7.7.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397501.1619646164000.21185.1619646180957%40Atlassian.JIRA.
Jira (PUP-11043) Update Confluence and JIRA based on release (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11043 Update Confluence and JIRA based on release (Puppet Platform 7.7.0) Issue Type: Task Assignee: Pintu Sethi Created: 2021/04/28 2:42 PM Due Date: 2021/05/26 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the
Jira (PUP-11040) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11040 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.7.0) Issue Type: Task Assignee: Pintu Sethi Created: 2021/04/28 2:42 PM Due Date: 2021/05/24 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in #proj-puppet-releases Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-11038) Prepare documentation updates and release notes (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11038 Prepare documentation updates and release notes (Puppet Platform 7.7.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/04/28 2:42 PM Due Date: 2021/05/21 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-11039) Prepare release announcement (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11039 Prepare release announcement (Puppet Platform 7.7.0) Issue Type: Task Assignee: Claire Cadman Created: 2021/04/28 2:42 PM Due Date: 2021/05/24 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Claire Cadman for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-11042) Send release announcement (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11042 Send release announcement (Puppet Platform 7.7.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397503.1619646173000.21187.1619646181044%40Atlassian.JIRA.
Jira (PUP-11039) Prepare release announcement (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11039 Prepare release announcement (Puppet Platform 7.7.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397498.1619646152000.21181.1619646180808%40Atlassian.JIRA.
Jira (PUP-11037) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11037 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.7.0) Issue Type: Task Assignee: Pintu Sethi Created: 2021/04/28 2:42 PM Due Date: 2021/05/19 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-05-25) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in Slack) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-11038) Prepare documentation updates and release notes (Puppet Platform 7.7.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11038 Prepare documentation updates and release notes (Puppet Platform 7.7.0) Change By: Eric Griswold Epic Link: PUP-11035 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397497.1619646148000.21179.1619646180719%40Atlassian.JIRA.
Jira (PUP-11035) Puppet Platform 7.7.0 Release - 2021-05-25
Title: Message Title Eric Griswold created an issue Puppet / PUP-11035 Puppet Platform 7.7.0 Release - 2021-05-25 Issue Type: Epic Assignee: Pintu Sethi Created: 2021/04/28 2:42 PM Due Date: 2021/05/25 Priority: Normal Reporter: Eric Griswold Puppet Platform 7.7.0 Release - 2021-05-25 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11033) Fix bugs, not create new features
Title: Message Title otheus commented on PUP-11033 Re: Fix bugs, not create new features A Jira search shows more than 450 open bugs of Normal severity combining the pup, pa, server, enterprise projects. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.397468.161963727.21156.1619644620157%40Atlassian.JIRA.
Jira (PUP-11034) Unable to 'mask' a 'static' systemd service
Title: Message Title
Nick Maludy updated an issue
Puppet / PUP-11034
Unable to 'mask' a 'static' systemd service
Change By:
Nick Maludy
*Puppet Version: 7.6.1* *Puppet Server Version: N/A* *OS Name/Version: CentOS 8.3*I'm trying to translate the following command into Puppet:{code:java}systemctl stop systemd-coredump.socketsystemctl mask systemd-coredump.socket{code}The Puppet code i've written to do this is:{code:java}service { 'systemd-coredump.socket': ensure => 'stopped', enable => 'mask',}{code}*Desired Behavior:*I would expect the service to be stopped and masked.*Actual Behavior:*The service is a 'static' service on the system and is resulting in a debug log being printed:{code:java}debug - Puppet - Executing: '/bin/systemctl is-enabled -- systemd-coredump.socket'debug - Puppet - Unable to enable or disable static service systemd-coredump.socket{code}Running the systemctl commands manually, works just fine.Doing a little digging, i found the following code:[https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/service/systemd.rb#L42-L56]The comment in the block is accurate, however a little misleading because 'static' services are allowed to be 'masked'.
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11034) Unable to 'mask' a 'static' systemd service
Title: Message Title
Nick Maludy commented on PUP-11034
Re: Unable to 'mask' a 'static' systemd service
Workaround:
exec { "systemctl mask -- ${service}":
path => ['/usr/bin/', '/sbin', '/bin'],
unless => "systemctl status -- ${service} | grep -q masked",
}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
You received this message because you are subscribed to the
Jira (PUP-11034) Unable to 'mask' a 'static' systemd service
Title: Message Title
Nick Maludy updated an issue
Puppet / PUP-11034
Unable to 'mask' a 'static' systemd service
Change By:
Nick Maludy
*Puppet Version: 7.6.1* *Puppet Server Version: N/A* *OS Name/Version: CentOS 8.3*I'm trying to translate the following command into Puppet:{code:java} systemctl stop systemd-coredump.socketsystemctl mask systemd-coredump.socket{code}The Puppet code i've written to do this is:{code:java} service { 'systemd-coredump.socket': ensure => 'stopped', enable => 'mask',}{code}*Desired Behavior:*I would expect the service to be stopped and masked.*Actual Behavior:*The service is a 'static' service on the system and is resulting in a debug log being printed:{code:java} debug - Puppet - Executing: '/bin/systemctl is-enabled -- systemd-coredump.socket'debug - Puppet - Unable to enable or disable static service systemd-coredump.socket {code} ` Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting Running the issue systemctl commands manually, works just fine . Examples Doing a little digging, i found the following code : Run puppet agent with --test --trace --debugRelevant sections of {{ [https: / var / log github.com /puppetlabs/ puppetserver puppet / puppetserver blob/main/lib/puppet/provider/service/systemd . log}} or any applicable logs from the same directory. rb#L42-L56] For more detailed information turn up the server logs by upping the log level The comment in the server's logback.xmlRelevant sections of configurations files (puppet.conf block is accurate , hiera.conf, Server however a little misleading because ' s conf static' services are allowed to be 'masked' . d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.
Add Comment
Jira (PUP-11034) Unable to 'mask' a 'static' systemd service
Title: Message Title
Nick Maludy created an issue
Puppet / PUP-11034
Unable to 'mask' a 'static' systemd service
Issue Type:
Bug
Affects Versions:
PUP 7.6.0
Assignee:
Unassigned
Created:
2021/04/28 12:55 PM
Priority:
Normal
Reporter:
Nick Maludy
Puppet Version: 7.6.1 Puppet Server Version: N/A OS Name/Version: CentOS 8.3 I'm trying to translate the following command into Puppet:
systemctl stop systemd-coredump.socket
systemctl mask systemd-coredump.socket
The Puppet code i've written to do this is:
service { 'systemd-coredump.socket':
ensure => 'stopped',
Jira (PUP-10115) "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead
Title: Message Title Josh Cooper commented on PUP-10115 Re: "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead Thanks for writing this up otheus! FWIW the Dir.glob order behavior comes from ruby and they've changed the default behavior in ruby 3 Regardless, we should enforce a stable sorting order for older ruby versions, though we'll have to be careful about compatibility. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332258.1572282843000.21055.1619638920299%40Atlassian.JIRA.
Jira (PUP-11033) Fix bugs, not create new features
Title: Message Title otheus created an issue Puppet / PUP-11033 Fix bugs, not create new features Issue Type: Story Assignee: Unassigned Created: 2021/04/28 12:14 PM Priority: Major Reporter: otheus Aim for quality not features and development speed. System Admins have too much to do than to try to upgrade, test, and redeploy central systems such as puppet. They need stable, reliable software which relies either on non-disruptive component-upgrades. While puppet 3 had its share of shortcomings, from what I've seen, puppet 6 has even more shortcomings despite the marginal benefits. Before releasing any new version, ensure that the software test coverage approaches 100%, that all open bugs of "Normal" or higher have been addressed. If a bug has a dependency on another OSS project, go fix it or replicate the code and fix it locally. Add Comment
Jira (PUP-10115) "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead
Title: Message Title otheus updated an issue Puppet / PUP-10115 "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead Change By: otheus Priority: Normal Major Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332258.1572282843000.21019.1619636880028%40Atlassian.JIRA.
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7197 make type aliases from modules available on the agent Change By: Maggie Dreyer Sub-team: Language Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.174775.1486632721000.20963.1619634900284%40Atlassian.JIRA.
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7197 make type aliases from modules available on the agent Change By: Maggie Dreyer Epic Link: PUP- 8587 11032 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.174775.1486632721000.20962.1619634900237%40Atlassian.JIRA.
Jira (PUP-8600) plugin-sync the data-types from all modules
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8600 plugin-sync the data-types from all modules Change By: Maggie Dreyer Epic Link: PUP-11032 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.242740.1521815941000.20961.1619634900193%40Atlassian.JIRA.
Jira (PUP-11032) Pluginsync Improvements
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-11032 Pluginsync Improvements Issue Type: Epic Assignee: Unassigned Created: 2021/04/28 11:34 AM Priority: Normal Reporter: Maggie Dreyer This epic contains work to make pluginsync more efficient and sync more things (primarily puppet types) to the agent. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-7495) puppet lookup CLI ignores node level variables
Title: Message Title Maggie Dreyer commented on PUP-7495 Re: puppet lookup CLI ignores node level variables We're probably not going to get to this any time soon. If it's important or you have specific use cases for it, please reopen with that info. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.189247.1493856676000.20740.1619630820209%40Atlassian.JIRA.
Jira (PUP-10115) "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead
Title: Message Title otheus commented on PUP-10115 Re: "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead Confirming and expounding. After intense testing, I found that: Directory entries are read in directory order, not "alphanumeric" order (which is probably an incorrect way of describing standard unix shell behavior). Problem exists in 6.22.1 as well. The reason this is so important is that it affects Hiera merge strategies and can result in changing & unpredictable behavior in a system using this. For instance, imagine you have a.yaml and c.yaml . Normally, the merge would treat `a.yaml` with higher priority. But after renaming `a.yaml` to `b.yaml`, depending on the filesystem, `c.yaml` might now come first in the directory order, and thus have higher priority. As such, **this functionality becomes next to useless**. (It's not completely useless, but one basically now needs a syntax checker to ensure there aren't conflicts or unpredictable merge-conflicts every time there is a change). The problem extends also to the glob */ mechanism: sub-directories are also processed in directory-order (by depth). The documentation should be updated to explain that directory depth is a relevant factor in the determination of Hiera priority. At least in this regard, the behavior is close to what is expected. (ie, dir-a/.yaml is processed before any entries in dir-a/dir-b/.yaml when */.yaml is the glob pattern. Glob patterns (plural) that are specified in an array actually are processed in the order specified. I would argue this is desirable behavior, but it one surface is at variance with the documentation, which implies that all glob array entries will be processed, files collated, and then sorted. Thus: -name: "xxx" globs: - "dirA/dirX/**/*.yaml" - "dirB/*.yaml"
Jira (FACT-3033) make a proposal for often/out of band facter releases
Title: Message Title Ciprian Badescu created an issue Facter / FACT-3033 make a proposal for often/out of band facter releases Issue Type: Task Assignee: Unassigned Created: 2021/04/28 8:11 AM Priority: Normal Reporter: Ciprian Badescu during the last release (6.22/7.6) we discovered two facter bugs right after facter release and we had to do a quick patch-release to fix them the bugs were discovered during nightly spec test of puppet modules, which are using the last release facter as a gem. we should check whether releasing facter often (each 2 weeks/sprint) will bring enough benefits vs effort required Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title Ciprian Badescu commented on PUP-10946 Re: Recursive file resources generate dangerous numbers of resource events I updated implementation based on comments from Josh Cooper : Add a new parameter, `max-files`, to limit the number of resources that may be created by types supporting recursion(file, tidy). Default value for `max-files` is 0. In this case a warning is logged when the number of files exceeds hardcoded soft limit of 1000. In case `max-files` is set to a value different that 0 and the number of files is greater than `max-files`, a Puppet::Error is raised and the resource is marked as failed. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389668.1614728039000.20354.1619616420105%40Atlassian.JIRA.
Jira (PDB-5094) Add some initial query tests
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5094 Add some initial query tests Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.394361.1617754897000.20324.1619608380042%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 Sprint: NW-2021-04-28 , NW-2021-05-19 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392050.1616527457000.20274.1619603460388%40Atlassian.JIRA.
Jira (FACT-2928) Error: Facter: statvfs() function failed: No such file or directory
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2928 Error: Facter: statvfs() function failed: No such file or directory Change By: Mihai Buzgau Sprint: NW-2021-04-28 , NW-2021-05-19 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.385230.1611827086000.20278.1619603460526%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: Mihai Buzgau Sprint: NW - 2021-03-31, NW - 2021-04-14, NW-2021-04-28 , NW-2021-05-19 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389668.1614728039000.20273.1619603460343%40Atlassian.JIRA.
Jira (FACT-2938) Ship facter 4 nightly gems
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2938 Ship facter 4 nightly gems Change By: Mihai Buzgau Sprint: NW-2021-04-28 , NW-2021-05-19 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.386160.1612447345000.20279.1619603460572%40Atlassian.JIRA.
Jira (PUP-10999) Unable to update UserRightAssignment - Log on as service rights
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10999 Unable to update UserRightAssignment - Log on as service rights Change By: Mihai Buzgau Sprint: NW - 2021-04-14, NW-2021-04-28 , NW-2021-05-19 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.393117.1617029923000.20276.1619603460476%40Atlassian.JIRA.
Jira (FACT-3006) Centralize and document fact matching and filtering
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3006 Centralize and document fact matching and filtering Change By: Mihai Buzgau Sprint: NW-2021-04-28 , NW-2021-05-19 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.394894.1618225336000.20277.1619603460520%40Atlassian.JIRA.
Jira (FACT-2995) check.sh script failing randomly on Ubuntu 20.04
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2995 check.sh script failing randomly on Ubuntu 20.04 Change By: Mihai Buzgau Sprint: NW-2021-04-28 , NW-2021-05-19 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392573.1616600888000.20275.1619603460432%40Atlassian.JIRA.
Jira (PUP-10924) `module install` can't unpack modules with long paths because of minitar bug
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-10924 `module install` can't unpack modules with long paths because of minitar bug Change By: Ciprian Badescu Sprint: NW-2021-05-19 Triaged tickets Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387906.1613638812000.20268.1619603220037%40Atlassian.JIRA.
Jira (PUP-11031) (spike) study long file names/long file paths support in 3rd party software and puppet
Title: Message Title Ciprian Badescu created an issue Puppet / PUP-11031 (spike) study long file names/long file paths support in 3rd party software and puppet Issue Type: Task Assignee: Unassigned Created: 2021/04/28 2:41 AM Priority: Normal Reporter: Ciprian Badescu 3rd party items to check: FyleSystem/OS limitations for filenames (Windows/AIX/Solaris/OSX) C++/BOOST limitations (Facter3) (used in custom/external facts) Ruby limitations (eg: https://bugs.ruby-lang.org/issues/12551) TAR implementation limitations (puppet uses the available `tar` command on the box to unpack the module, we need to support all tar version available on workstation where puppet is running) For reference, similar rubygem issue (open on 2015): https://github.com/rubygems/rubygems/issues/1376) Internal code paths to check: Install LFN module in master/agent Pluginsync LFN (support for file transfer protocol used) File resource support for LFN Above steps work on all supported OSs(Windows/Solaris/AIX/EL5/etc.) on all supported Ruby versions R10K/code manager support for LFN Facter3/Facter4 (to load external/custom facts from modules)
Jira (PUP-11026) puppet cannot set/change password of a user resource on Big Sur
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11026 puppet cannot set/change password of a user resource on Big Sur Change By: Ciprian Badescu Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395612.1618492793000.20232.1619598780034%40Atlassian.JIRA.
Jira (PUP-11026) puppet cannot set/change password of a user resource on Big Sur
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11026 puppet cannot set/change password of a user resource on Big Sur Change By: Ciprian Badescu Similar changes done for osx 10.15: https://github.com/puppetlabs/puppet/commit/688779d43c770598ca72c83e14b555f342252150 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395612.1618492793000.20231.1619598480206%40Atlassian.JIRA.
Jira (PUP-11026) puppet cannot set/change password of a user resource on Big Sur
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11026 puppet cannot set/change password of a user resource on Big Sur Change By: Mihai Buzgau Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395612.1618492793000.20226.1619598300124%40Atlassian.JIRA.
Jira (PUP-11026) puppet cannot set/change password of a user resource on Big Sur
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11026 puppet cannot set/change password of a user resource on Big Sur Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395612.1618492793000.20227.1619598300168%40Atlassian.JIRA.
Jira (PUP-11026) puppet cannot set/change password of a user resource on Big Sur
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11026 puppet cannot set/change password of a user resource on Big Sur Change By: Mihai Buzgau Sprint: NW-2021-05-19 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395612.1618492793000.20225.1619598300059%40Atlassian.JIRA.
Jira (FACT-3032) Spec integration tests failing when IPv6 not set
Title: Message Title
Luchian Nemes created an issue
Facter / FACT-3032
Spec integration tests failing when IPv6 not set
Issue Type:
Bug
Affects Versions:
FACT 4.0.44
Assignee:
Unassigned
Created:
2021/04/28 12:35 AM
Priority:
Normal
Reporter:
Luchian Nemes
Randomized with seed 30125 .F..F.Failures: 1) Facter when calling the ruby API to_hash contains ipaddress6 Failure/Error: expect(fact_hash['ipaddress6']).to match(/([a-z0-9]{1,4}:{1,2})+[a-z0-9]{1,4}/) expected nil to match /([a-z0-9]{1,4}:{1,2})+[a-z0-9]{1,4}/
./spec_integration/facter_to_hash_spec.rb:93:in `block (3 levels) in ' 2) Facter when calling facter cli with user query returns ipaddress6 Failure/Error: expect(out).to match(/([a-z0-9]{1,4}:{1,2})[a-z0-9]{1,4}/) expected "\n" to match /([a-z0-9]{1,4}:{1,2})[a-z0-9]{1,4}/ Diff: @@ -1,2 +1 @@ -/([a-z0-9]{1,4}:{1,2})+[a-z0-9]{1,4}/ # ./spec_integration/facter_to_hash_spec.rb:54:in `block (4 levels) in 'Finished in 29.42 seconds (files took 0.31385 seconds to load) 122 examples, 2 failuresFailed examples:rspec ./spec_integration/facter_to_hash_spec.rb:90 # Facter when calling the ruby API to_hash contains ipaddress6 rspec ./spec_integration/facter_to_hash_spec.rb:51 # Facter when calling facter cli with user query returns ipaddress6
Jira (FACT-3032) Spec integration tests failing when IPv6 not set
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-3032
Spec integration tests failing when IPv6 not set
Change By:
Luchian Nemes
{code:java}Randomized with seed 30125.F..F.Failures: 1) Facter when calling the ruby API to_hash contains ipaddress6 Failure/Error: expect(fact_hash['ipaddress6']).to match(/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/) expected nil to match /([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ # ./spec_integration/facter_to_hash_spec.rb:93:in `block (3 levels) in ' 2) Facter when calling facter cli with user query returns ipaddress6 Failure/Error: expect(out).to match(/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/) expected "\n" to match /([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ Diff: @@ -1,2 +1 @@ -/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ # ./spec_integration/facter_to_hash_spec.rb:54:in `block (4 levels) in 'Finished in 29.42 seconds (files took 0.31385 seconds to load)122 examples, 2 failuresFailed examples:rspec ./spec_integration/facter_to_hash_spec.rb:90 # Facter when calling the ruby API to_hash contains ipaddress6rspec ./spec_integration/facter_to_hash_spec.rb:51 # Facter when calling facter cli with user query returns ipaddress6{code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3032) Spec integration tests failing when IPv6 not set
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-3032
Spec integration tests failing when IPv6 not set
Change By:
Luchian Nemes
{code:java} Randomized with seed 30125.F..F.Failures: 1) Facter when calling the ruby API to_hash contains ipaddress6 Failure/Error: expect(fact_hash['ipaddress6']).to match(/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/) expected nil to match /([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ # ./spec_integration/facter_to_hash_spec.rb:93:in `block (3 levels) in ' 2) Facter when calling facter cli with user query returns ipaddress6 Failure/Error: expect(out).to match(/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/) expected "\n" to match /([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ Diff: @@ -1,2 +1 @@ -/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ # ./spec_integration/facter_to_hash_spec.rb:54:in `block (4 levels) in 'Finished in 29.42 seconds (files took 0.31385 seconds to load)122 examples, 2 failuresFailed examples:rspec ./spec_integration/facter_to_hash_spec.rb:90 # Facter when calling the ruby API to_hash contains ipaddress6rspec ./spec_integration/facter_to_hash_spec.rb:51 # Facter when calling facter cli with user query returns ipaddress6 {code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
