Jira (PUP-10572) Puppet cannot apply a cached catalog containing binary rich data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10572 Puppet cannot apply a cached catalog containing binary rich data Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364693.1593561127000.99295.1593565380050%40Atlassian.JIRA.
Jira (PUP-10572) Puppet cannot apply a cached catalog containing binary rich data
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10572 Puppet cannot apply a cached catalog containing binary rich data Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364693.1593561127000.99297.1593565380136%40Atlassian.JIRA.
Jira (PUP-10572) Puppet cannot apply a cached catalog containing binary rich data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10572 Puppet cannot apply a cached catalog containing binary rich data Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364693.1593561127000.99296.1593565380091%40Atlassian.JIRA.
Jira (PUP-10572) Puppet cannot apply a cached catalog containing binary rich data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10572 Puppet cannot apply a cached catalog containing binary rich data Change By: Josh Cooper Fix Version/s: PUP 6.17.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364693.1593561127000.99294.1593565320029%40Atlassian.JIRA.
Jira (PUP-10567) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10567 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.17.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/06/30 11:56 AM Due Date: 2020/06/13 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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-10572) Puppet cannot apply a cached catalog containing binary rich data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10572 Puppet cannot apply a cached catalog containing binary rich data Change By: Josh Cooper Labels: jira_escalated Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364693.1593561127000.99221.1593561420187%40Atlassian.JIRA.
Jira (PUP-10564) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10564 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.17.0) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364611.1593543373000.98666.1593543422239%40Atlassian.JIRA.
Jira (PUP-10572) Puppet cannot apply a cached catalog containing binary rich data
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-10572
Puppet cannot apply a cached catalog containing binary rich data
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/06/30 4:52 PM
Priority:
Normal
Reporter:
Josh Cooper
If a cached catalog contains rich data (such as Binary) then puppet will fail to load the cached catalog and fallback to loading a new catalog. This doesn't happen with Sensitive because that data type is handled differently:
Cached catalog for vernal-creator.delivery.puppetlabs.net failed: Could not parse JSON data for catalog vernal-creator.delivery.puppetlabs.net: Could not intern from rich_data_json: Internal Error: Puppet Context ':loaders' missing
To reproduce, create the following resource:
notify { 'message':
message => Binary.new('aGk=')
}
Jira (PUP-10565) Prepare documentation updates and release notes (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10565 Prepare documentation updates and release notes (Puppet Platform 6.17.0) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364612.1593543376000.98668.1593543422327%40Atlassian.JIRA.
Jira (PUP-10557) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10557 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.21) Change By: Morgan Rhodes Epic Link: PUP-10552 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364587.1593543238000.98610.1593543240575%40Atlassian.JIRA.
Jira (PDB-4794) Update winston (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-4794 Update winston (PuppetDB 6.11.2) Issue Type: Task Assignee: Zachary Kent Created: 2020/06/30 11:57 AM Due Date: 2020/06/15 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4794) Update winston (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4794 Update winston (PuppetDB 6.11.2) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364643.1593543469000.98692.1593543480650%40Atlassian.JIRA.
Jira (PDB-4789) Merge-up, branch, and create pipelines (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4789 Merge-up, branch, and create pipelines (PuppetDB 6.11.2) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364637.1593543452000.98682.1593543480207%40Atlassian.JIRA.
Jira (PUP-10555) Prepare documentation updates and release notes (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10555 Prepare documentation updates and release notes (Puppet Platform 5.5.21) Change By: Morgan Rhodes Epic Link: PUP-10552 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364584.1593543229000.98606.1593543240387%40Atlassian.JIRA.
Jira (PUP-10560) Update Confluence and JIRA based on release (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10560 Update Confluence and JIRA based on release (Puppet Platform 5.5.21) Change By: Morgan Rhodes Epic Link: PUP-10552 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364591.1593543251000.98616.1593543300343%40Atlassian.JIRA.
Jira (PUP-10570) Update Confluence and JIRA based on release (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10570 Update Confluence and JIRA based on release (Puppet Platform 6.17.0) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364619.1593543397000.98678.1593543422859%40Atlassian.JIRA.
Jira (FACT-2693) Add nspawn fact
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2693 Add nspawn fact Issue Type: Sub-task Assignee: Unassigned Created: 2020/06/30 12:48 PM Priority: Normal Reporter: Oana Tanasoiu For this fact, docker_lxc resolver should be extended and rename with 'cgroup_resolver' (maybe). Regex for nspawn @ https://github.com/puppetlabs/libwhereami/blob/c9666110a1bdec1c7034e4a607710c704603cbf9/lib/src/detectors/nspawn_detector.cc#L14 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4789) Merge-up, branch, and create pipelines (PuppetDB 6.11.2)
Title: Message Title
Morgan Rhodes created an issue
PuppetDB / PDB-4789
Merge-up, branch, and create pipelines (PuppetDB 6.11.2)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2020/06/30 11:57 AM
Due Date:
2020/07/07
Priority:
Normal
Reporter:
Morgan Rhodes
(Initial planned release date: 2020-06-14) 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 (FACT-2691) Add kvm fact
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2691 Add kvm fact Change By: Oana Tanasoiu (Facter::Resolvers::VirtWhat.resolve(:vm) == 'kvm' || [https://github.com/puppetlabs/facter/blob/8a3accd247940750e60f1fdc93c4f20c71b070a3/lib/facts/linux/virtual.rb#L44] == 'kvm' || Facter::Resolvers::Lspci.resolve(:vm ) == 'kvm' ) && product_name != 'VirtualBox' && !product_name.match(/^Parallels/) For other info the checks are identical as the ones from windows : [https://github.com/puppetlabs/facter/blob/8a3accd247940750e60f1fdc93c4f20c71b070a3/lib/facts/windows/hypervisors/kvm.rb#L24] Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PUP-10552) Puppet Platform 5.5.21 Release - 2020-07-14
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10552 Puppet Platform 5.5.21 Release - 2020-07-14 Issue Type: Epic Assignee: Nirupama Mantha Created: 2020/06/30 11:53 AM Due Date: 2020/07/14 Priority: Normal Reporter: Morgan Rhodes Puppet Platform 5.5.21 Release - 2020-07-14 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2689) Add docker fact
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2689 Add docker fact Change By: Oana Tanasoiu There is a resolver (docker_lxc) to retrieve this fact. [https://github.com/puppetlabs/facter/blob/4.x/lib/resolvers/docker_lxc.rb] The resolver should be called with :hypervisor and check if the result is a hash that has the key 'docker' Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364646.1593545458000.98841.1593545820319%40Atlassian.JIRA.
Jira (PUP-10558) Publish documentation and updates and release notes (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10558 Publish documentation and updates and release notes (Puppet Platform 5.5.21) Issue Type: Task Assignee: Claire Cadman Created: 2020/06/30 11:54 AM Due Date: 2020/07/14 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-07-14) 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-10558) Publish documentation and updates and release notes (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10558 Publish documentation and updates and release notes (Puppet Platform 5.5.21) Change By: Morgan Rhodes Epic Link: PUP-10552 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364588.1593543241000.98612.1593543300167%40Atlassian.JIRA.
Jira (PUP-10571) Communicate scope and timeline of next release (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10571 Communicate scope and timeline of next release (Puppet Platform 6.17.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/06/30 11:56 AM Due Date: 2020/06/15 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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-10563) Prepare JIRA and Confluence for release (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10563 Prepare JIRA and Confluence for release (Puppet Platform 6.17.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/06/30 11:56 AM Due Date: 2020/07/08 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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.17.0 and puppet-agent 6.17.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PDB-4792) Bump versions, push directly, and tag (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-4792 Bump versions, push directly, and tag (PuppetDB 6.11.2) Issue Type: Task Assignee: Zachary Kent Created: 2020/06/30 11:57 AM Due Date: 2020/07/10 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Check that puppetdb and pe-puppetdb-extensions are on the same version of clj-parent, and that is the same clj-parent version that puppetserver will release with. Disable automatic promotions: If a PE release branch has not been cut, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing.
Jira (PUP-10553) Prepare JIRA and Confluence for release (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10553 Prepare JIRA and Confluence for release (Puppet Platform 5.5.21) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/06/30 11:53 AM Due Date: 2020/07/01 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-07-14) 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.21 and puppet-agent 5.5.21 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PDB-4790) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4790 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.11.2) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364638.1593543455000.98684.1593543480295%40Atlassian.JIRA.
Jira (PUP-10569) Send release announcement (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10569 Send release announcement (Puppet Platform 6.17.0) Issue Type: Task Assignee: Sara Meisburger Created: 2020/06/30 11:56 AM Due Date: 2020/06/14 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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.17.0 is now available".
Jira (FACT-2697) Add xen fact
Title: Message Title
Oana Tanasoiu created an issue
Facter / FACT-2697
Add xen fact
Issue Type:
Sub-task
Assignee:
Unassigned
Created:
2020/06/30 2:10 PM
Priority:
Normal
Reporter:
Oana Tanasoiu
Facter::Resolvers::VirtWhat.resolve(:vm) =~ /xen/ || Facter::Resolvers::Xen.resolve(:vm) =~ /xen/ || https://github.com/puppetlabs/facter/blob/8a3accd247940750e60f1fdc93c4f20c71b070a3/lib/facts/linux/virtual.rb#L44 =~ /xen/ || Facter::Resolvers::Lspci.resolve(:vm) =~ /xen/ For xen other info: if 'xenhvm' is returned from resolvers => {context: 'hvm'} else {context: 'pv'} for 'privileged' info xen resolver should be extended to retrieve the following : https://github.com/puppetlabs/libwhereami/blob/c9666110a1bdec1c7034e4a607710c704603cbf9/lib/src/detectors/xen_detector.cc#L23
Add Comment
Jira (FACT-2689) Add docker fact
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2689 Add docker fact Issue Type: Sub-task Assignee: Unassigned Created: 2020/06/30 12:30 PM Priority: Normal Reporter: Oana Tanasoiu There is a resolver (docker_lxc) to retrieve this fact. https://github.com/puppetlabs/facter/blob/4.x/lib/resolvers/docker_lxc.rb Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10560) Update Confluence and JIRA based on release (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10560 Update Confluence and JIRA based on release (Puppet Platform 5.5.21) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/06/30 11:54 AM Due Date: 2020/07/15 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-07-14) 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 (PDB-4791) Draft release notes (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-4791 Draft release notes (PuppetDB 6.11.2) Issue Type: Task Assignee: Zachary Kent Created: 2020/06/30 11:57 AM Due Date: 2020/06/12 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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 (PUP-10559) Send release announcement (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10559 Send release announcement (Puppet Platform 5.5.21) Issue Type: Task Assignee: Sara Meisburger Created: 2020/06/30 11:54 AM Due Date: 2020/07/14 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-07-14) 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.21 is now available".
Jira (PUP-10571) Communicate scope and timeline of next release (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10571 Communicate scope and timeline of next release (Puppet Platform 6.17.0) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364620.159354340.98680.1593543422947%40Atlassian.JIRA.
Jira (PUP-10566) Prepare release announcement (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10566 Prepare release announcement (Puppet Platform 6.17.0) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364613.1593543379000.98670.1593543422507%40Atlassian.JIRA.
Jira (PUP-10561) Communicate scope and timeline of next release (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10561 Communicate scope and timeline of next release (Puppet Platform 5.5.21) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/06/30 11:54 AM Due Date: 2020/07/15 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-07-14) 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 (FACT-2696) Add vmware fact
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2696 Add vmware fact Issue Type: Sub-task Assignee: Unassigned Created: 2020/06/30 2:00 PM Priority: Normal Reporter: Oana Tanasoiu Facter::Resolvers::VirtWhat.resolve(:vm) == 'vmware' || https://github.com/puppetlabs/facter/blob/8a3accd247940750e60f1fdc93c4f20c71b070a3/lib/facts/linux/virtual.rb#L44 == 'vmware' || Facter::Resolvers::Lspci.resolve(:vm) == 'vmware' || Facter::Resolvers::Linux::DmiBios.resolve(:sys_vendor) == "VMware, Inc." For vmware version dmidecode command must be called and retrieve /^Address:\s([0-9A-F]+)/ (this regex should probably be improved) from it Add Comment This message was sent by Atlassian
Jira (PUP-10554) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10554 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.21) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/06/30 11:53 AM Due Date: 2020/07/01 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-07-14) 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-10565) Prepare documentation updates and release notes (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10565 Prepare documentation updates and release notes (Puppet Platform 6.17.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/06/30 11:56 AM Due Date: 2020/07/10 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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-10562) Puppet Platform 6.17.0 Release - 2020-06-14
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10562 Puppet Platform 6.17.0 Release - 2020-06-14 Issue Type: Epic Assignee: Nirupama Mantha Created: 2020/06/30 11:56 AM Due Date: 2020/06/14 Priority: Normal Reporter: Morgan Rhodes Puppet Platform 6.17.0 Release - 2020-06-14 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2695) Add virtualbox fact
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2695 Add virtualbox fact Issue Type: Sub-task Assignee: Unassigned Created: 2020/06/30 1:31 PM Priority: Normal Reporter: Oana Tanasoiu Facter::Resolvers::Linux::DmiBios.resolve(:product_name) == 'VirtualBox' || Facter::Resolvers::VirtWhat.resolve(:vm) =~ /virtualbox/ || ** Facter::Resolvers::Lspci.resolve(:vm) == 'virtualbox' For other info about version and revision of the virtualbox use the following regexs @ [https://github.com/puppetlabs/libwhereami/blob/c9666110a1bdec1c7034e4a607710c704603cbf9/lib/src/detectors/virtualbox_detector.cc#L26 ] to retrieve oem_string use dmidecode command (note: this command does not work on power pcs) Add Comment
Jira (PUP-10567) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10567 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.17.0) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364615.1593543385000.98672.1593543422595%40Atlassian.JIRA.
Jira (PDB-4793) Check builds, promote to PE (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4793 Check builds, promote to PE (PuppetDB 6.11.2) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364641.1593543463000.98690.1593543480560%40Atlassian.JIRA.
Jira (FACT-2694) Add openvz fact
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2694 Add openvz fact Issue Type: Sub-task Assignee: Unassigned Created: 2020/06/30 12:51 PM Priority: Normal Reporter: Oana Tanasoiu This fact can be retrieved with open_vz.rb, that resolver should be extended to retrieve container id . Regex for container id @ https://github.com/puppetlabs/libwhereami/blob/c9666110a1bdec1c7034e4a607710c704603cbf9/lib/src/detectors/openvz_detector.cc#L44 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10569) Send release announcement (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10569 Send release announcement (Puppet Platform 6.17.0) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364618.1593543394000.98676.1593543422771%40Atlassian.JIRA.
Jira (PUP-10570) Update Confluence and JIRA based on release (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10570 Update Confluence and JIRA based on release (Puppet Platform 6.17.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/06/30 11:56 AM Due Date: 2020/06/15 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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 (FACT-2692) Add lxc fact
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2692 Add lxc fact Issue Type: Sub-task Assignee: Unassigned Created: 2020/06/30 12:45 PM Priority: Normal Reporter: Oana Tanasoiu There is a resolver (docker_lxc) to retrieve this fact. https://github.com/puppetlabs/facter/blob/4.x/lib/resolvers/docker_lxc.rb The resolver should be called with :hypervisor and check if the result is a hash that has the key 'lxc' Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2691) Add kvm fact
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2691 Add kvm fact Issue Type: Sub-task Assignee: Unassigned Created: 2020/06/30 12:43 PM Priority: Normal Reporter: Oana Tanasoiu (Facter::Resolvers::VirtWhat.resolve(:vm) == 'kvm' || https://github.com/puppetlabs/facter/blob/8a3accd247940750e60f1fdc93c4f20c71b070a3/lib/facts/linux/virtual.rb#L44 == 'kvm') && product_name != 'VirtualBox' && !product_name.match(/^Parallels/) For other info the checks are identical as the ones from windows : https://github.com/puppetlabs/facter/blob/8a3accd247940750e60f1fdc93c4f20c71b070a3/lib/facts/windows/hypervisors/kvm.rb#L24 Add Comment This message was sent by Atlassian Jira
Jira (PUP-10566) Prepare release announcement (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10566 Prepare release announcement (Puppet Platform 6.17.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/06/30 11:56 AM Due Date: 2020/06/13 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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-10555) Prepare documentation updates and release notes (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10555 Prepare documentation updates and release notes (Puppet Platform 5.5.21) Issue Type: Task Assignee: Claire Cadman Created: 2020/06/30 11:53 AM Due Date: 2020/07/03 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-07-14) 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 (FACT-2690) Add HyperV fact
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2690 Add HyperV fact Issue Type: Sub-task Assignee: Unassigned Created: 2020/06/30 12:35 PM Priority: Normal Reporter: Oana Tanasoiu dmi.manufacturer =~ /Microsoft/ || dmi.product.name == 'Virtual Machine' Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4791) Draft release notes (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4791 Draft release notes (PuppetDB 6.11.2) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364639.1593543458000.98686.1593543480383%40Atlassian.JIRA.
Jira (PDB-4792) Bump versions, push directly, and tag (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4792 Bump versions, push directly, and tag (PuppetDB 6.11.2) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364640.159354346.98688.1593543480470%40Atlassian.JIRA.
Jira (PUP-10554) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10554 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.21) Change By: Morgan Rhodes Epic Link: PUP-10552 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364583.1593543226000.98604.1593543240300%40Atlassian.JIRA.
Jira (PDB-4793) Check builds, promote to PE (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-4793 Check builds, promote to PE (PuppetDB 6.11.2) Issue Type: Task Assignee: Zachary Kent Created: 2020/06/30 11:57 AM Due Date: 2020/07/10 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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 (PUP-10568) Publish documentation and updates and release notes (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10568 Publish documentation and updates and release notes (Puppet Platform 6.17.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/06/30 11:56 AM Due Date: 2020/06/14 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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-10559) Send release announcement (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10559 Send release announcement (Puppet Platform 5.5.21) Change By: Morgan Rhodes Epic Link: PUP-10552 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364590.1593543247000.98614.1593543300255%40Atlassian.JIRA.
Jira (PUP-10556) Prepare release announcement (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10556 Prepare release announcement (Puppet Platform 5.5.21) Issue Type: Task Assignee: Claire Cadman Created: 2020/06/30 11:53 AM Due Date: 2020/07/13 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-07-14) 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-10568) Publish documentation and updates and release notes (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10568 Publish documentation and updates and release notes (Puppet Platform 6.17.0) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364616.1593543388000.98674.1593543422683%40Atlassian.JIRA.
Jira (PUP-10563) Prepare JIRA and Confluence for release (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10563 Prepare JIRA and Confluence for release (Puppet Platform 6.17.0) Change By: Morgan Rhodes Epic Link: PUP-10562 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364610.159354337.98664.1593543422151%40Atlassian.JIRA.
Jira (PUP-10564) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.17.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10564 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.17.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/06/30 11:56 AM Due Date: 2020/07/08 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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 (PDB-4790) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.11.2)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-4790 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.11.2) Issue Type: Task Assignee: Zachary Kent Created: 2020/06/30 11:57 AM Due Date: 2020/07/07 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-06-14) 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 (PUP-10557) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10557 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.21) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/06/30 11:53 AM Due Date: 2020/07/13 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-07-14) 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-10561) Communicate scope and timeline of next release (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10561 Communicate scope and timeline of next release (Puppet Platform 5.5.21) Change By: Morgan Rhodes Epic Link: PUP-10552 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364592.1593543254000.98618.1593543300435%40Atlassian.JIRA.
Jira (PUP-10556) Prepare release announcement (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10556 Prepare release announcement (Puppet Platform 5.5.21) Change By: Morgan Rhodes Epic Link: PUP-10552 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364585.1593543232000.98608.1593543240474%40Atlassian.JIRA.
Jira (PUP-10553) Prepare JIRA and Confluence for release (Puppet Platform 5.5.21)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10553 Prepare JIRA and Confluence for release (Puppet Platform 5.5.21) Change By: Morgan Rhodes Epic Link: PUP-10552 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364582.1593543223000.98602.1593543240252%40Atlassian.JIRA.
Jira (PUP-10368) Checksums not validated when downloading file http(s):// sources
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10368 Checksums not validated when downloading file http(s):// sources Change By: Josh Cooper Sprint: Coremunity Hopper Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.349628.1584115737000.98514.1593539400104%40Atlassian.JIRA.
Jira (PUP-10368) Checksums not validated when downloading file http(s):// sources
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10368 Checksums not validated when downloading file http(s):// sources Change By: Josh Cooper Fix Version/s: PUP 6.17.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.349628.1584115737000.98515.1593539400147%40Atlassian.JIRA.
Jira (PUP-10368) Checksums not validated when downloading file http(s):// sources
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10368 Checksums not validated when downloading file http(s):// sources Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.349628.1584115737000.98516.1593539400192%40Atlassian.JIRA.
Jira (PUP-10549) HTTP 406 Not Acceptable error message should contain format names
Title: Message Title Josh Cooper commented on PUP-10549 Re: HTTP 406 Not Acceptable error message should contain format names Passed CI in efe50c1532 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364176.1593190474000.98511.1593539340050%40Atlassian.JIRA.
Jira (FACT-2686) Build Facter for JRuby on ubuntu-20.04-amd64
Title: Message Title Molly Waggett commented on FACT-2686 Re: Build Facter for JRuby on ubuntu-20.04-amd64 Mihai Buzgau Thanks! I'll close this. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364322.1593451087000.98363.1593534420125%40Atlassian.JIRA.
Jira (PUP-10548) Wrong SELinux contexts on files if puppet installs new rpm with SELinux policy
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10548 Wrong SELinux contexts on files if puppet installs new rpm with SELinux policy Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.363809.1593020161000.98237.1593529380031%40Atlassian.JIRA.
Jira (PUP-10550) rich_data enabled by default, error message is not informative and puppet should be able to process json report
Title: Message Title Patrick Grant commented on PUP-10550 Re: rich_data enabled by default, error message is not informative and puppet should be able to process json report The customer was using a cached catalog on the agents. I have attached a catalog and stack trace, each with rich data enabled and disabled Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364234.1593423699000.98209.1593526920022%40Atlassian.JIRA.
Jira (PUP-10550) rich_data enabled by default, error message is not informative and puppet should be able to process json report
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10550 rich_data enabled by default, error message is not informative and puppet should be able to process json report Change By: Patrick Grant Attachment: int-lcanary-01.integrafin.net-RICHENABLED.json Attachment: agentdebug-RICHENABLED.txt Attachment: agentdebug-RICHDISABLED.txt Attachment: int-lcanary-01.integrafin.net-RICHDISABLED.json Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop
Jira (FACT-2243) hypervisors fact for Linux
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2243 hypervisors fact for Linux Change By: Oana Tanasoiu Sprint: ready for triage Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338970.1576065938000.98162.1593518640033%40Atlassian.JIRA.
Jira (FACT-2686) Build Facter for JRuby on ubuntu-20.04-amd64
Title: Message Title Mihai Buzgau commented on FACT-2686 Re: Build Facter for JRuby on ubuntu-20.04-amd64 We're already building Facter for JRuby: https://github.com/puppetlabs/puppet-agent/blob/master/configs/components/facter.rb#L52 this was added in the initial Agent support. Molly Waggett can you please let us know if you encounter any issues with this. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.364322.1593451087000.98103.1593509640032%40Atlassian.JIRA.
Jira (FACT-2688) Promotion of Facter 4 in puppet-agent
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2688 Promotion of Facter 4 in puppet-agent Issue Type: Task Assignee: Unassigned Created: 2020/06/30 12:44 AM Priority: Normal Reporter: Bogdan Irimie Currently puppet agent cannot use facter repo for two components (Facter 3 and facter-ng) because Vanagon does not know to handle this case. To work around this issue, we can push the changes from facter:4.x to facter-ng:master. This process involves unarchiving the facter-ng repo. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2687) Rework error logging
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2687 Rework error logging Issue Type: Task Assignee: Unassigned Created: 2020/06/30 12:41 AM Priority: Normal Reporter: Bogdan Irimie Currently the Facter logger for errors is ambiguous. We should have something similar to --trace from external facts. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2682) facter -p returns NUL character on stdout when called from nested ruby on windows
Title: Message Title Mihai Buzgau assigned an issue to Ciprian Badescu Facter / FACT-2682 facter -p returns NUL character on stdout when called from nested ruby on windows Change By: Mihai Buzgau Assignee: Ciprian Badescu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.363822.1593026104000.98053.1593501780033%40Atlassian.JIRA.
Jira (FACT-2306) Add support for AWS IMDSv2
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2306 Add support for AWS IMDSv2 Change By: Mihai Buzgau Sub-team: ghost Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342859.1579626792000.98050.1593499560152%40Atlassian.JIRA.
