Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title Josh Cooper commented on PUP-10013 Re: Update minitar version and call new fsync=false option Additional commit to 6.4.x in https://github.com/puppetlabs/puppet/commit/ce3de3e9b8a51a4607e1e68a04cd4a6af2fdd7dc Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.323877.1567788493000.127045.1570060860296%40Atlassian.JIRA.
Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title Josh Cooper commented on PUP-10013 Re: Update minitar version and call new fsync=false option Additional commit merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/a382cd57eb695812e0255dd7d5c11daff3d490be Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.323877.1567788493000.126698.1570053840187%40Atlassian.JIRA.
Jira (PDB-4539) Update winston (PuppetDB 6.3.5)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4539 Update winston (PuppetDB 6.3.5) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:15 PM Due Date: 2019/10/16 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4537) Bump versions, push directly, and tag (PuppetDB 6.3.5)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4537 Bump versions, push directly, and tag (PuppetDB 6.3.5) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:14 PM Due Date: 2019/10/09 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) (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. Disable automatic promotions: If this release will be released in a PE release, 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. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in
Jira (PDB-4535) Merge-up, branch, and create pipelines (PuppetDB 6.3.5)
Title: Message Title
Nirupama Mantha created an issue
PuppetDB / PDB-4535
Merge-up, branch, and create pipelines (PuppetDB 6.3.5)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/10/02 2:14 PM
Due Date:
2019/10/06
Priority:
Normal
Reporter:
Nirupama Mantha
(Initial planned release date: 2019-10-15) 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
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
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 -> 6.3.x
Merge
Jira (PDB-4538) Check builds, promote to PE (PuppetDB 6.3.5)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4538 Check builds, promote to PE (PuppetDB 6.3.5) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:14 PM Due Date: 2019/10/09 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4536) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.5)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4536 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.5) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:14 PM Due Date: 2019/10/06 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PUP-10078) Update Confluence and JIRA based on release (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10078 Update Confluence and JIRA based on release (Puppet Platform 6.4.4) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:12 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10079) Communicate scope and timeline of next release (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10079 Communicate scope and timeline of next release (Puppet Platform 6.4.4) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:12 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10077) Send release announcement (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10077 Send release announcement (Puppet Platform 6.4.4) Issue Type: Task Assignee: Molly Waggett Created: 2019/10/02 2:12 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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.4.4 is now available".
Jira (PUP-10074) Prepare release announcement (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10074 Prepare release announcement (Puppet Platform 6.4.4) Issue Type: Task Assignee: Bill Tang Created: 2019/10/02 2:11 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond 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-10073) Prepare documentation updates and release notes (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10073 Prepare documentation updates and release notes (Puppet Platform 6.4.4) Issue Type: Task Assignee: Jean Bond Created: 2019/10/02 2:11 PM Due Date: 2019/10/09 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10076) Publish documentation and updates and release notes (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10076 Publish documentation and updates and release notes (Puppet Platform 6.4.4) Issue Type: Task Assignee: Jean Bond Created: 2019/10/02 2:11 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10075) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10075 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.4) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:11 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10072) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10072 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.4) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:11 PM Due Date: 2019/10/07 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10071) Prepare JIRA and Confluence for release (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10071 Prepare JIRA and Confluence for release (Puppet Platform 6.4.4) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:10 PM Due Date: 2019/10/07 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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.4.4 and puppet-agent 6.4.4 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-10070) Puppet Platform 6.4.4 Release - 2019-10-15
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10070 Puppet Platform 6.4.4 Release - 2019-10-15 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/10/02 2:10 PM Due Date: 2019/10/15 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.4.4 Release - 2019-10-15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4534) Update winston (PuppetDB 5.2.10)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4534 Update winston (PuppetDB 5.2.10) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:09 PM Due Date: 2019/10/16 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4530) Merge-up, branch, and create pipelines (PuppetDB 5.2.10)
Title: Message Title
Nirupama Mantha created an issue
PuppetDB / PDB-4530
Merge-up, branch, and create pipelines (PuppetDB 5.2.10)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/10/02 2:08 PM
Due Date:
2019/10/01
Priority:
Normal
Reporter:
Nirupama Mantha
(Initial planned release date: 2019-10-15) 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
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
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 -> 6.3.x
Merge
Jira (PDB-4532) Bump versions, push directly, and tag (PuppetDB 5.2.10)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4532 Bump versions, push directly, and tag (PuppetDB 5.2.10) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:08 PM Due Date: 2019/10/04 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) (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. Disable automatic promotions: If this release will be released in a PE release, 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. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in
Jira (PDB-4533) Check builds, promote to PE (PuppetDB 5.2.10)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4533 Check builds, promote to PE (PuppetDB 5.2.10) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:08 PM Due Date: 2019/10/04 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4531) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.10)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4531 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.10) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/02 2:08 PM Due Date: 2019/10/01 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PUP-10069) Communicate scope and timeline of next release (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10069 Communicate scope and timeline of next release (Puppet Platform 5.5.17) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:06 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10068) Update Confluence and JIRA based on release (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10068 Update Confluence and JIRA based on release (Puppet Platform 5.5.17) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:06 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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
Jira (PUP-10067) Send release announcement (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10067 Send release announcement (Puppet Platform 5.5.17) Issue Type: Task Assignee: Molly Waggett Created: 2019/10/02 2:06 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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 5.5.17 is now available".
Jira (PUP-10063) Prepare documentation updates and release notes (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10063 Prepare documentation updates and release notes (Puppet Platform 5.5.17) Issue Type: Task Assignee: Jean Bond Created: 2019/10/02 2:05 PM Due Date: 2019/10/04 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10060) Puppet Platform 5.5.17 Release - 2019-10-15
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10060 Puppet Platform 5.5.17 Release - 2019-10-15 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/10/02 2:05 PM Due Date: 2019/10/15 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 5.5.17 Release - 2019-10-15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10062) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10062 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.17) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:05 PM Due Date: 2019/10/02 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10065) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10065 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.17) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:05 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10061) Prepare JIRA and Confluence for release (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10061 Prepare JIRA and Confluence for release (Puppet Platform 5.5.17) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/02 2:05 PM Due Date: 2019/10/02 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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 5.5.17 and puppet-agent 5.5.17 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform
Jira (PUP-10066) Publish documentation and updates and release notes (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10066 Publish documentation and updates and release notes (Puppet Platform 5.5.17) Issue Type: Task Assignee: Jean Bond Created: 2019/10/02 2:05 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 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-10064) Prepare release announcement (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10064 Prepare release announcement (Puppet Platform 5.5.17) Issue Type: Task Assignee: Bill Tang Created: 2019/10/02 2:05 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond 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-10013) Update minitar version and call new fsync=false option
Title: Message Title
Josh Cooper commented on PUP-10013
Re: Update minitar version and call new fsync=false option
minitar is a soft dependency (controlled through puppet's feature system, eg Puppet.features.minitar?). As a result, there's no guarantee that minitar is installed or which version is installed. We only package minitar in puppet-agent on systems without a sane tar command, like windows, etc. But if you're on redhat for example, and you install the older minitar version, then puppet will try to use it. For example if you install pe-r10k:
# rpm -qlp packages/el-6-x86_64/pe-r10k-2.6.6.0.4.g7094eb2-1.el6.x86_64.rpm | grep -e 'minitar.*gem'
/opt/puppetlabs/puppet/lib/ruby/gems/2.4.0/cache/minitar-0.6.1.gem
/opt/puppetlabs/puppet/lib/ruby/gems/2.4.0/specifications/minitar-0.6.1.gemspec
So puppet needs to be more defensive about only using minitar if it's at least 0.9, or detect when it's using an older version and omitting the fsync => false option. The former is possible using Gem::Specification.find_by_name('minitar').version >= Gem::Version.new("0.9"). The latter could be done by checking the arity of the unpack method.
Add Comment
This
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title
Thomas Kishel commented on PDB-2487
Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
The workaround used by Support is a single:
su - pe-postgres -s /bin/bash -c "/opt/puppetlabs/server/bin/psql -d pe-puppetdb -c 'TRUNCATE resource_events'"
and then a scheduled:
su - pe-postgres -s /bin/bash -c "/opt/puppetlabs/server/bin/psql -d pe-puppetdb -c \"DELETE FROM resource_events WHERE timestamp < NOW() - INTERVAL '2 days'\""';
like:
cron { 'sudo_resource_events_ttl':
ensure => 'present',
command => 'su - pe-postgres -s /bin/bash -c "/opt/puppetlabs/server/bin/psql -d pe-puppetdb -c \"DELETE FROM resource_events WHERE timestamp < NOW() - INTERVAL \'2 days\'\""',
hour=> ['8'],
minute => ['0'],
target => 'root',
user=> 'root',
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Thomas Kishel commented on PDB-2487 Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Does that mean in a .z of Lovejoy? Because this is a high-impact problem for the above PE users. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.119255.1456852336000.125850.1570040282259%40Atlassian.JIRA.
Jira (PDB-4527) (docs) More info needed on certs and keys in PuppetDB api docs
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4527 (docs) More info needed on certs and keys in PuppetDB api docs Change By: Austin Blatt Labels: docs-pdb Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.327683.1570034555000.125620.1570037640270%40Atlassian.JIRA.
Jira (PDB-4529) Update command docs to include mention of producer_timestamp in query params
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4529 Update command docs to include mention of producer_timestamp in query params Change By: Zachary Kent Our command submission docs [here|https://puppet.com/docs/puppetdb/6.3/api/command/v1/commands.html#command-submission] don't mention the need to include producer_timestamp producer-timestamp in the query params. The inclusion of this param is need to enable "bash-in-place" in the command queue. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.327688.1570037414000.125613.1570037520321%40Atlassian.JIRA.
Jira (PDB-4529) Update command docs to include mention of producer_timestamp in query params
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4529 Update command docs to include mention of producer_timestamp in query params Issue Type: Improvement Assignee: Unassigned Created: 2019/10/02 10:30 AM Priority: Normal Reporter: Zachary Kent Our command submission docs here don't mention the need to include producer_timestamp in the query params. The inclusion of this param is need to enable "bash-in-place" in the command queue. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4528) Should we reject/warn on improperly formated configure-expiration cmds
Title: Message Title
Zachary Kent created an issue
PuppetDB / PDB-4528
Should we reject/warn on improperly formated configure-expiration cmds
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/10/02 10:23 AM
Priority:
Normal
Reporter:
Zachary Kent
POST http://127.0.0.1:8080/pdb/cmd/v1?command=configure_expiration=haha=1&
Content-Type: application/json
{
"command": "configure expiration",
"version": 1,
"payload": {
"certname": "haha",
Jira (PDB-4527) (docs) More info needed on certs and keys in PuppetDB api docs
Title: Message Title Jean Bond updated an issue PuppetDB / PDB-4527 (docs) More info needed on certs and keys in PuppetDB api docs Change By: Jean Bond Url: /docs/puppetdb/5.1/api/query/v4/pql.html There are no links to further information on certs and keys, particularly howto generate/find them.The examples are too cryptic, and don't demonstrate (to me, anyway) how todeal with more deeply-nested data. I also looked athttps://puppet.com/blog/introducing-puppet-query-language-pql (not much help)and https://puppet.com/blog/getting-know-puppet-query-language-pql (better)but I was still struggling to create a query that worked, let alone returnedthe desired result. I ended up running a query that gave me almost what Iwanted, then filtered the output with awk - not optimal. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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,
Jira (PDB-4527) (docs) More info needed on certs and keys in PuppetDB api docs
Title: Message Title Jean Bond updated an issue PuppetDB / PDB-4527 (docs) More info needed on certs and keys in PuppetDB api docs Change By: Jean Bond There are no links to further information on certs and keys, particularly howto generate/find them.The examples are too cryptic, and don't demonstrate (to me, anyway) how todeal with more deeply-nested data. I also looked athttps://puppet.com/blog/introducing-puppet-query-language-pql (not much help)and https://puppet.com/blog/getting-know-puppet-query-language-pql (better)but I was still struggling to create a query that worked, let alone returnedthe desired result. I ended up running a query that gave me almost what Iwanted, then filtered the output with awk - not optimal. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (PDB-4527) (docs) More info needed on certs and keys in PuppetDB api docs
Title: Message Title Jean Bond commented on PDB-4527 Re: (docs) More info needed on certs and keys in PuppetDB api docs Based on user feedback received by the docs team Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.327683.1570034555000.125377.1570034640227%40Atlassian.JIRA.
Jira (FACT-2047) Compatibility
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2047 Compatibility Change By: Sebastian Miclea This epic will include tickets that are required in order to have 100% compatibility with Facter 3.x Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.327673.1570033384000.125374.1570034640214%40Atlassian.JIRA.
Jira (FACT-2050) Search External Method
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2050 Search External Method Change By: Sebastian Miclea Summary: search_external Search External Method Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.327680.1570034317000.125369.1570034580384%40Atlassian.JIRA.
Jira (FACT-2047) Compatibility
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2047 Compatibility Change By: Sebastian Miclea Summary: This epic will include tickets that are required in order to have 100% compatibility with Facter 3.x Compatibility Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.327673.1570033384000.125373.1570034580410%40Atlassian.JIRA.
Jira (PDB-4527) (docs) More info needed on certs and keys in PuppetDB api docs
Title: Message Title Jean Bond created an issue PuppetDB / PDB-4527 (docs) More info needed on certs and keys in PuppetDB api docs Issue Type: Improvement Assignee: Unassigned Created: 2019/10/02 9:42 AM Priority: Normal Reporter: Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2051) Add Method
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2051 Add Method Issue Type: Task Assignee: Unassigned Created: 2019/10/02 9:41 AM Priority: Normal Reporter: Sebastian Miclea Puppet uses Facter.add Puppet/puppet/lib/ruby/vendor_ruby/puppet.rb:160 Params: [:puppetversion] Puppet/puppet/lib/ruby/vendor_ruby/puppet.rb:164 Params: [:agent_specified_environment]
Jira (PDB-4526) (docs) More info needed on certs and keys in PuppetDB api docs
Title: Message Title Jean Bond updated an issue PuppetDB / PDB-4526 (docs) More info needed on certs and keys in PuppetDB api docs Change By: Jean Bond Summary: (docs) More info needed on certs and keys in PuppetDB api docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.325500.1568966729000.125365.1570034400622%40Atlassian.JIRA.
Jira (PDB-4526) More info needed on certs and keys in PuppetDB api docs
Title: Message Title Jean Bond moved an issue PuppetDB / PDB-4526 More info needed on certs and keys in PuppetDB api docs Change By: Jean Bond Team: PuppetDB Workflow: Documentation Scrum Team Workflow Key: DOC PDB - 4299 4526 Project: Documentation [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2050) search_external Method
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2050 search_external Method Issue Type: Task Assignee: Unassigned Created: 2019/10/02 9:38 AM Priority: Normal Reporter: Sebastian Miclea Puppet uses Facter.search_external puppet/lib/ruby/vendor_ruby/puppet/indirector/facts/facter.rb:86 Add Comment
Jira (FACT-2049) Reset Method
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2049 Reset Method Issue Type: Task Assignee: Unassigned Created: 2019/10/02 9:36 AM Priority: Normal Reporter: Sebastian Miclea Puppet uses Facter.reset puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:138 puppet/lib/ruby/vendor_ruby/puppet/indirector/facts/facter.rb:23
Jira (FACT-2048) Search Method
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2048 Search Method Issue Type: Task Assignee: Unassigned Created: 2019/10/02 9:34 AM Priority: Normal Reporter: Sebastian Miclea Puppet uses Facter.search puppet/lib/ruby/vendor_ruby/puppet/defaults.rb:1831 Params: ["C:/ProgramData/PuppetLabs/puppet/cache/lib/facter", "C:/ProgramData/PuppetLabs/puppet/cache/facts"] puppet/lib/ruby/vendor_ruby/puppet/indirector/facts/facter.rb:65
Jira (PDB-4502) PuppetDB command size metrics are missing
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4502 PuppetDB command size metrics are missing Change By: Zachary Kent Fix Version/s: PDB 6.8.0 Fix Version/s: PDB 6.3.5 Fix Version/s: PDB 5.2.10 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.323996.156781861.125322.1570033860312%40Atlassian.JIRA.
Jira (PDB-4502) PuppetDB command size metrics are missing
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4502 PuppetDB command size metrics are missing Change By: Zachary Kent Release Notes Summary: Fixed a bug that prevented command size metrics from being recorded and the max-command-size config option from working properly. This was done by adding a custom 'X-Uncompressed-Length' header to compressed requests sent from the terminus. The value of this header is the size in bytes of the command before it is compressed. This value is used to update the size metric and to decide when to discard commands based on'max-command-size'. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2047) This epic will include tickets that are required in order to have 100% compatibility with Facter 3.x
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2047 This epic will include tickets that are required in order to have 100% compatibility with Facter 3.x Issue Type: Epic Assignee: Unassigned Created: 2019/10/02 9:23 AM Priority: Normal Reporter: Sebastian Miclea Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Rob Browning commented on PDB-2487 Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Correction - it's not in Lovejoy, but the current plan for it to still end up in the LTS via the next Y release. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.119255.1456852336000.125178.1570032120954%40Atlassian.JIRA.
Jira (PUP-10059) Puppet won't install (some) packages with ensure => held
Title: Message Title
Andre Nathan updated an issue
Puppet / PUP-10059
Puppet won't install (some) packages with ensure => held
Change By:
Andre Nathan
*Puppet Version: 6.9.0-1bionic* *Puppet Server Version: 6.2.0-1bionic* *OS Name/Version: Ubuntu 18.04*I have postfix and installed and held: {code:java} package { 'postfix': ensure => 'held',}{code} {code:java} # dpkg -l | grep postfixhi postfix 3.3.0-1ubuntu0.2 amd64 High-performance mail transport agent{code} Now I'm trying to install a few sub-packages, also as held: {code:java} $packages = [ 'postfix-pcre', 'postfix-mysql',]package { $packages: ensure => 'held',}{code} When running puppet, the following messages are displayed:Notice: /Stage[main]/Main/Package[postfix-pcre]/ensure: createdNotice: /Stage[main]/Main/Package[postfix-mysql]/ensure: created*Desired Behavior:***Packages postfix-pcre and postfix-mysql should be installed and set to "held".*Actual Behavior:* Neither package is installed. The puppet resource command results in a package resource with ensure set to "purged":{code:java} # puppet resource package postfix-mysql ensure=heldNotice: /Package[postfix-mysql]/ensure: createdpackage { 'postfix-mysql': ensure => 'purged', provider => 'apt',}{code} This seems to only affect sub-packages like in this Postfix example; I have other packages set to ensure => held which have been installed properly.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10059) Puppet won't install (some) packages with ensure => held
Title: Message Title
Andre Nathan updated an issue
Puppet / PUP-10059
Puppet won't install (some) packages with ensure => held
Change By:
Andre Nathan
Summary:
{brief summary of issue} Puppet won't install (some) packages with ensure => held
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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.327639.157002023.124915.1570020360074%40Atlassian.JIRA.
Jira (PUP-10059) {brief summary of issue}
Title: Message Title
Andre Nathan created an issue
Puppet / PUP-10059
{brief summary of issue}
Issue Type:
Bug
Affects Versions:
PUP 6.9.0
Assignee:
Unassigned
Components:
Types and Providers
Created:
2019/10/02 5:43 AM
Priority:
Normal
Reporter:
Andre Nathan
Puppet Version: 6.9.0-1bionic Puppet Server Version: 6.2.0-1bionic OS Name/Version: Ubuntu 18.04 I have postfix and installed and held:
package { 'postfix':
ensure => 'held',
}
#
Jira (PUP-10021) User resource always reports password changed when account disabled for Win 2012 R2
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10021 User resource always reports password changed when account disabled for Win 2012 R2 Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.324443.1568255866000.124900.1570017060545%40Atlassian.JIRA.
Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo
Title: Message Title
Dorin Pleava commented on PUP-
Re: Puppet::Type.type('yumrepo') wrongly reports enabled repo
Hi Anthony Chevalet, I just finished setting up a similar environment with agent 4.10.12, and now I wait to see if anything strange happens. Can you try to reproduce the issue with puppet version 5.5.x? The version 4.10.12 is no longer supported, and it might be already fixed in future releases. Thanks
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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.323658.1567695504000.124887.1570014540104%40Atlassian.JIRA.
Jira (PUP-1537) Dpkg package provider misbehaving for held package with specific version
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-1537 Dpkg package provider misbehaving for held package with specific version Change By: Mihai Buzgau Sprint: PR NW - Triage 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.24894.1391021944000.124843.1570008600390%40Atlassian.JIRA.
Jira (PUP-1537) Dpkg package provider misbehaving for held package with specific version
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-1537 Dpkg package provider misbehaving for held package with specific version Change By: Mihai Buzgau Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.24894.1391021944000.124836.1570008540334%40Atlassian.JIRA.
Jira (PUP-9562) User resource does not respect forcelocal for the comment parameter
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9562 User resource does not respect forcelocal for the comment parameter Change By: Mihai Buzgau Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.300292.1552589325000.124825.1570008120229%40Atlassian.JIRA.
Jira (PUP-9562) User resource does not respect forcelocal for the comment parameter
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9562 User resource does not respect forcelocal for the comment parameter Change By: Mihai Buzgau Sprint: PR NW - Triage 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.300292.1552589325000.124827.1570008120238%40Atlassian.JIRA.
Jira (FACT-1991) Add Product Version to dmi Fact
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1991 Add Product Version to dmi Fact Change By: Mihai Buzgau Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.320973.1565808818000.124790.1570007580135%40Atlassian.JIRA.
Jira (PUP-10021) User resource always reports password changed when account disabled for Win 2012 R2
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10021 User resource always reports password changed when account disabled for Win 2012 R2 Change By: Mihai Buzgau Sprint: PR NW - Triage 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.324443.1568255866000.124787.1570007280235%40Atlassian.JIRA.
Jira (PUP-10021) User resource always reports password changed when account disabled for Win 2012 R2
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10021 User resource always reports password changed when account disabled for Win 2012 R2 Change By: Mihai Buzgau Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.324443.1568255866000.124783.1570007220259%40Atlassian.JIRA.
Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo
Title: Message Title
Mihai Buzgau updated an issue
Puppet / PUP-
Puppet::Type.type('yumrepo') wrongly reports enabled repo
Change By:
Mihai Buzgau
Sprint:
NW - 2019-10-02 , NW - 2019-10-16
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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.323658.1567695504000.124743.1570005606575%40Atlassian.JIRA.
Jira (PUP-9465) group resource type misunderstands/misuses libuser
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9465 group resource type misunderstands/misuses libuser Change By: Mihai Buzgau Sprint: NW - 2019-08-21, NW - 2019-09-03, NW - 2019-09-18, NW - 2019-10-02 , NW - 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.293306.1548368109000.124698.1570005606399%40Atlassian.JIRA.
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9719 Cannot run Puppet Agent as Administrator if first PA run is done as System Change By: Mihai Buzgau Sprint: PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23, NW - 2019-08-07, NW - 2019-08-21, NW - 2019-09-03, NW - 2019-09-18, NW - 2019-10-02 , NW - 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.310162.1558726819000.124678.1570005606294%40Atlassian.JIRA.
Jira (PUP-9978) dnf package provider should support modularity streams
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9978 dnf package provider should support modularity streams Change By: Mihai Buzgau Sprint: NW - 2019-10-02 , NW - 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.322208.1566835009000.124710.1570005606442%40Atlassian.JIRA.
Jira (FACT-2016) Add the scope of found ipv6 addresses (global/linklocal/...) as a fact
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2016 Add the scope of found ipv6 addresses (global/linklocal/...) as a fact Change By: Mihai Buzgau Sprint: NW - 2019-10-02 , NW - 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.324361.1568209514000.124740.1570005606564%40Atlassian.JIRA.
Jira (PUP-10023) Expand the apt provider to support virtual packages
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10023 Expand the apt provider to support virtual packages Change By: Mihai Buzgau Sprint: NW - 2019-09-18, NW - 2019-10-02 , NW - 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.324926.1568705952000.124746.1570005606587%40Atlassian.JIRA.
Jira (PUP-9471) User management fails on MacOS 10.14 (Mojave)
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9471 User management fails on MacOS 10.14 (Mojave) Change By: Mihai Buzgau Sprint: PR - 2019-03-06, NW - 2019-10-02 , NW - 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.294488.1549047148000.124756.1570005606624%40Atlassian.JIRA.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Mihai Buzgau Sprint: NW - 2019-08-07, NW - 2019-08-21, NW - 2019-09-03, NW - 2019-09-18, NW - 2019-10-02 , NW - 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.267945.153332494.124686.1570005606342%40Atlassian.JIRA.
Jira (FACT-2004) cloud fact does not detect Azure with NetworkManager
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2004 cloud fact does not detect Azure with NetworkManager Change By: Mihai Buzgau Sprint: NW - 2019-10-02 , NW - 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.322752.1567082147000.124716.1570005606465%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10017 Collapse dependency failures into Class level failures Change By: Mihai Buzgau Sprint: NW - 2019-10-02 , NW - 2019-10-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.324379.1568220393000.124737.1570005606548%40Atlassian.JIRA.
Jira (PUP-10023) Expand the apt provider to support virtual packages
Title: Message Title Gheorghe Popescu commented on PUP-10023 Re: Expand the apt provider to support virtual packages https://github.com/puppetlabs/puppet/pull/7701 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.324926.1568705952000.124586.1570001520134%40Atlassian.JIRA.
Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo
Title: Message Title
Dorin Pleava assigned an issue to Dorin Pleava
Puppet / PUP-
Puppet::Type.type('yumrepo') wrongly reports enabled repo
Change By:
Dorin Pleava
Assignee:
Dorin Pleava
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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.323658.1567695504000.124581.1570001220203%40Atlassian.JIRA.
