Jira (FACT-1986) Test C++ Facter with custom facts
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1986 Test C++ Facter with custom facts Issue Type: Task Assignee: Unassigned Created: 2019/08/08 10:51 PM Priority: Normal Reporter: Bogdan Irimie As custom facts are written in Ruby we want to see what is the performance of C++ Facter when obtaining these facts. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1985) Compare JSON results for different versions of Facter
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1985 Compare JSON results for different versions of Facter Change By: Bogdan Irimie This might be done with beaker? 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.320310.1565329762000.49545.1565329800307%40Atlassian.JIRA.
Jira (FACT-1985) Compare JSON results for different versions of Facter
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1985 Compare JSON results for different versions of Facter Issue Type: Task Assignee: Unassigned Created: 2019/08/08 10:49 PM Priority: Normal Reporter: Bogdan Irimie 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 (BOLT-1451) Automatically call apply_prep before `resources` step in YAML plans
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1451 Automatically call apply_prep before `resources` step in YAML plans Change By: Chris Cowell Labels: docs_reviewed 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.315003.1562084948000.49541.1565328660269%40Atlassian.JIRA.
Jira (BOLT-1423) Bolt actions hang over ssh transport when ProxyCommand is set in openssh config
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1423 Bolt actions hang over ssh transport when ProxyCommand is set in openssh config Change By: Chris Cowell Labels: docs_reviewed 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.313738.1561387259000.49536.1565326380196%40Atlassian.JIRA.
Jira (BOLT-1407) Add publishing bolt image to dockerhub to CI package pipeline
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1407 Add publishing bolt image to dockerhub to CI package pipeline Change By: Chris Cowell Labels: docs_reviewed 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.312985.1560878372000.49534.1565323260260%40Atlassian.JIRA.
Jira (PUP-9471) User management fails on MacOS 10.14 (Mojave)
Title: Message Title Matt Cahill commented on PUP-9471 Re: User management fails on MacOS 10.14 (Mojave) Hi, I'd like to add a small piece of additional information in case it's of any use to whomever tackles this issue. I have done extensive troubleshooting and ratified all of the tests carried out by Gerard Kok white-listing various via our Intune MDM server, none of which worked as he also found. https://tickets.puppetlabs.com/browse/PUP-9502?focusedCommentId=635972=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-635972 The only way I can get puppet to run via launchd with full disk access that allows user management is by doing the following. Replace the link /opt/puppetlabs/bin/puppet with a shell script (the contents can be the same as the contents of /opt/puppetlabs/puppet/bin/wrapper.sh) OR rename /opt/puppetlabs/puppet/bin/wrapper.sh to /opt/puppetlabs/puppet/bin/wrapper and relink everything in /opt/puppetlabs/bin/puppet. Either way the important thing is that the script does not have a suffix. Give the path /opt/puppetlabs/bin/puppet Full Disk Access rights manually in System Preferences (not via MDM) It seems that MDM full disk access rights are different from granting them in System Preferences. This of course means you would have to do this manually as an admin on every machine which for us is untenable. Having this working via the MDM full disk access permission is very important for large fleets of puppet managed macs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9937) Docker Image - wrong version
Title: Message Title Morgan Rhodes commented on PUP-9937 Re: Docker Image - wrong version Hi Dennis, We're talking about container versioning right now and should figure something out within the next month or so. Thanks for the report! 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.319591.1565013862000.49499.1565309460171%40Atlassian.JIRA.
Jira (PUP-9937) Docker Image - wrong version
Title: Message Title Morgan Rhodes assigned an issue to Morgan Rhodes Puppet / PUP-9937 Docker Image - wrong version Change By: Morgan Rhodes Assignee: Morgan Rhodes 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.319591.1565013862000.49501.1565309460178%40Atlassian.JIRA.
Jira (PUP-9911) Guard against unexpected EOF from ruby/don't commit incomplete files
Title: Message Title Josh Cooper commented on PUP-9911 Re: Guard against unexpected EOF from ruby/don't commit incomplete files Marking this as a dup of PUP-9043, since the artifactory issues are covered in PUP-6114. 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.317325.1563571917000.49385.1565305440246%40Atlassian.JIRA.
Jira (BOLT-1401) Add 'upload_file' endpoint to bolt-server
Title: Message Title Sean McDonald updated an issue Puppet Task Runner / BOLT-1401 Add 'upload_file' endpoint to bolt-server Change By: Sean McDonald Sprint: Skeletor Kanban 20190814 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.312870.1560800684000.49370.1565305200289%40Atlassian.JIRA.
Jira (BOLT-1402) Add 'run_script' endpoint to bolt-server
Title: Message Title Sean McDonald updated an issue Puppet Task Runner / BOLT-1402 Add 'run_script' endpoint to bolt-server Change By: Sean McDonald Sprint: Skeletor Kanban 20190814 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.312873.1560801019000.49372.1565305200387%40Atlassian.JIRA.
Jira (PDB-4477) Update winston (PuppetDB 6.5.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4477 Update winston (PuppetDB 6.5.0) Issue Type: Task Assignee: Rob Browning Created: 2019/08/08 3:01 PM Due Date: 2019/08/22 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-4476) Check builds, promote to PE (PuppetDB 6.5.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4476 Check builds, promote to PE (PuppetDB 6.5.0) Issue Type: Task Assignee: Rob Browning Created: 2019/08/08 3:01 PM Due Date: 2019/08/16 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-4473) Merge-up, branch, and create pipelines (PuppetDB 6.5.0)
Title: Message Title
Nirupama Mantha created an issue
PuppetDB / PDB-4473
Merge-up, branch, and create pipelines (PuppetDB 6.5.0)
Issue Type:
Task
Assignee:
Rob Browning
Created:
2019/08/08 3:01 PM
Due Date:
2019/08/13
Priority:
Normal
Reporter:
Nirupama Mantha
(Initial planned release date: 2019-08-21) 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/
6.0.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:
Jira (PDB-4475) Bump versions, push directly, and tag (PuppetDB 6.5.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4475 Bump versions, push directly, and tag (PuppetDB 6.5.0) Issue Type: Task Assignee: Rob Browning Created: 2019/08/08 3:01 PM Due Date: 2019/08/16 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) (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 before pushing a non-snapshot version and tagging. Disable automatic promotions: Go to the CI pipeline for the version being released and select the Conditional Promotion Trigger job. Click the disable button (the job's circle indicator should be gray now). 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 the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch you're releasing.
Jira (PDB-4474) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.5.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4474 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.5.0) Issue Type: Task Assignee: Rob Browning Created: 2019/08/08 3:01 PM Due Date: 2019/08/13 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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) Add Comment
Jira (PUP-9952) Send release announcement (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9952 Send release announcement (Puppet Platform 6.8.0) Issue Type: Task Assignee: Sara Meisburger Created: 2019/08/08 2:58 PM Due Date: 2019/08/21 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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.8.0 is now available".
Jira (PUP-9954) Communicate scope and timeline of next release (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9954 Communicate scope and timeline of next release (Puppet Platform 6.8.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/08 2:58 PM Due Date: 2019/08/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-9953) Update Confluence and JIRA based on release (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9953 Update Confluence and JIRA based on release (Puppet Platform 6.8.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/08 2:58 PM Due Date: 2019/08/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-5069) Puppet's HTTP API does not allow callers to trust system cacerts
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5069
Puppet's HTTP API does not allow callers to trust system cacerts
Change By:
Josh Cooper
underlined textPuppet Puppet 's HTTP connection code does not allow callers to specify that they want to trust the default set of cacerts. To do so, you need to get access to the {{Net::HTTP#store}} and call {{OpenSSL::X509::Store#set_default_paths}}, but this is not currently possible.The PMT works around this by rolling its own {{Net::HTTP}} object, leading to duplicate proxy handling logic. It would be nice to DRY this up, but to do so, our HTTP code needs to provide a way for callers to trust the system's cacerts. This would also be useful for providers that need to make network connections, and not rely on open-uri to do so.
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
Jira (PUP-9946) Prepare JIRA and Confluence for release (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9946 Prepare JIRA and Confluence for release (Puppet Platform 6.8.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/08 2:57 PM Due Date: 2019/08/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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.8.0 and puppet-agent 6.8.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-9950) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9950 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.8.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/08 2:57 PM Due Date: 2019/08/20 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-9947) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9947 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.8.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/08 2:57 PM Due Date: 2019/08/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-5069) Puppet's HTTP API does not allow callers to trust system cacerts
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5069
Puppet's HTTP API does not allow callers to trust system cacerts
Change By:
Josh Cooper
Puppet underlined textPuppet 's HTTP connection code does not allow callers to specify that they want to trust the default set of cacerts. To do so, you need to get access to the {{Net::HTTP#store}} and call {{OpenSSL::X509::Store#set_default_paths}}, but this is not currently possible.The PMT works around this by rolling its own {{Net::HTTP}} object, leading to duplicate proxy handling logic. It would be nice to DRY this up, but to do so, our HTTP code needs to provide a way for callers to trust the system's cacerts. This would also be useful for providers that need to make network connections, and not rely on open-uri to do so.
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
Jira (PUP-9948) Prepare documentation updates and release notes (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9948 Prepare documentation updates and release notes (Puppet Platform 6.8.0) Issue Type: Task Assignee: Jean Bond Created: 2019/08/08 2:57 PM Due Date: 2019/08/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-9951) Publish documentation and updates and release notes (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9951 Publish documentation and updates and release notes (Puppet Platform 6.8.0) Issue Type: Task Assignee: Jean Bond Created: 2019/08/08 2:58 PM Due Date: 2019/08/21 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-9945) Puppet Platform 6.8.0 Release - 2019-08-21
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9945 Puppet Platform 6.8.0 Release - 2019-08-21 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/08/08 2:57 PM Due Date: 2019/08/21 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.8.0 Release - 2019-08-21 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9949) Prepare release announcement (Puppet Platform 6.8.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9949 Prepare release announcement (Puppet Platform 6.8.0) Issue Type: Task Assignee: Bill Tang Created: 2019/08/08 2:57 PM Due Date: 2019/08/20 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-21) 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-9043) Downloaded files are sometimes truncated
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9043 Downloaded files are sometimes truncated Change By: Josh Cooper Summary: file resource - mtime checksum does not seem to work Downloaded files are sometimes truncated 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.268200.1533583523000.48974.1565298540223%40Atlassian.JIRA.
Jira (PUP-9043) file resource - mtime checksum does not seem to work
Title: Message Title Josh Cooper commented on PUP-9043 Re: file resource - mtime checksum does not seem to work Specifying custom headers for artifactory is handled in PUP-6114, so I think the only remaining issue for this ticket is the ruby silent truncation problem. I'll look at the ruby PR I submitted awhile ago and see if I can move that forward. Worst case, we may need to handle that ourselves in our Connection#get and Connection#request_get methods. 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.268200.1533583523000.48970.1565298480318%40Atlassian.JIRA.
Jira (PUP-6114) Add support for Artifactory checksum headers and enable SHA1 checksum type
Title: Message Title Josh Cooper commented on PUP-6114 Re: Add support for Artifactory checksum headers and enable SHA1 checksum type The original PR was declined, so moving the status back to ready for engineering. To watchers on the ticket, we had to clean up puppet's SSL handling first, and I'm now working on cleaning up the agent's http client code (epic PUP-8550). Once that's done, next up is fixing http/https file sources (the epic associated with this issue). 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.124334.1459384692000.48958.1565298361059%40Atlassian.JIRA.
Jira (PUP-9941) Update jackson-databind in pcore-java
Title: Message Title Rob Braden assigned an issue to Rob Braden Puppet / PUP-9941 Update jackson-databind in pcore-java Change By: Rob Braden Assignee: Rob Braden 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.320003.1565196189000.48877.1565296500383%40Atlassian.JIRA.
Jira (PUP-9941) Update jackson-databind in pcore-java
Title: Message Title Rob Braden commented on PUP-9941 Re: Update jackson-databind in pcore-java merged: https://github.com/puppetlabs/pcore-java/pull/12 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.320003.1565196189000.48874.1565296500370%40Atlassian.JIRA.
Jira (PUP-9944) Catalog Compilation Fails on Empty Class String
Title: Message Title Michael Hashizume created an issue Puppet / PUP-9944 Catalog Compilation Fails on Empty Class String Issue Type: Task Assignee: Unassigned Created: 2019/08/08 1:25 PM Priority: Normal Reporter: Michael Hashizume Hello! Our team recently upgraded from PE 2017 to PE 2018. After the upgrade, we started encountering this error: michael.hashizume@bfs-hyperv-1-prod:~$ sudo puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Loading facts Error: Could not retrieve
Jira (BOLT-1423) Bolt actions hang over ssh transport when ProxyCommand is set in openssh config
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1423 Bolt actions hang over ssh transport when ProxyCommand is set in openssh config Change By: Cas Donoghue Fix Version/s: BOLT Next 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.313738.1561387259000.48815.1565295420246%40Atlassian.JIRA.
Jira (PUP-9943) User type has custom retrieve() with non-standard return values
Title: Message Title Sean Millichamp commented on PUP-9943 Re: User type has custom retrieve() with non-standard return values I have put up a proposed PR to address this issue: https://github.com/puppetlabs/puppet/pull/7664 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.320115.1565272699000.48529.1565292180100%40Atlassian.JIRA.
Jira (PDB-4472) Set up CI with Azure Pipelines
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4472 Set up CI with Azure Pipelines Issue Type: Bug Assignee: Unassigned Created: 2019/08/08 11:42 AM Priority: Normal Reporter: gepetto-bot 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 (BOLT-1501) Change AWS plugin config field
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1501 Change AWS plugin config field Change By: Chris Cowell Labels: docs_reviewed 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.319097.1564618066000.48253.1565283300259%40Atlassian.JIRA.
Jira (BOLT-1424) Vault plugin
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1424 Vault plugin Change By: Chris Cowell Labels: docs_reviewed 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.313814.1561405465000.48210.1565282280257%40Atlassian.JIRA.
Jira (PUP-8399) Exec onlyif and unless should support sensitive data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8399 Exec onlyif and unless should support sensitive data Change By: Josh Cooper Fix Version/s: PUP 6.4.0 Fix Version/s: PUP 6.0.7 Fix Version/s: PUP 5.5.12 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.233091.1516914842000.48186.1565280720357%40Atlassian.JIRA.
Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used
Title: Message Title Josh Cooper commented on PUP-7814 Re: HTTPS file sources with non-puppet-trusted certs can't be used Correct. Connections to puppet infrastructure (compiler, CA, report servers) would only trust the CA bundle that the agent downloads from the CA. Only file resources with "https" sources would trust the CA bundle and the system cacert store. 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.203766.1501710671000.48127.1565279580366%40Atlassian.JIRA.
Jira (PUP-2172) Don't use an http proxy when connecting to localhost
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-2172
Don't use an http proxy when connecting to localhost
Change By:
Josh Cooper
Summary:
Add exceptions Don't use an http proxy when connecting to http_proxy_{port,host} localhost
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.31144.1396893516000.48100.1565279160610%40Atlassian.JIRA.
Jira (PUP-9943) User type has custom retrieve() with non-standard return values
Title: Message Title Sean Millichamp commented on PUP-9943 Re: User type has custom retrieve() with non-standard return values As an additional note: It appears that the Puppet::Type.retrieve_resource() method was perhaps designed as a work-around to this particular problem. However, it is marked as a private API. https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type.rb#L1122-L1136 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.320115.1565272699000.48039.1565277060102%40Atlassian.JIRA.
Jira (BOLT-1487) Make it easier for users to know and turn off analytics at install time
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1487 Make it easier for users to know and turn off analytics at install time Change By: Chris Cowell Labels: docs_reviewed 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.318117.1564082501000.47967.1565274540262%40Atlassian.JIRA.
Jira (BOLT-1451) Automatically call apply_prep before `resources` step in YAML plans
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1451 Automatically call apply_prep before `resources` step in YAML plans Change By: Cas Donoghue Fix Version/s: BOLT Next 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.315003.1562084948000.47961.1565273280484%40Atlassian.JIRA.
Jira (BOLT-1407) Add publishing bolt image to dockerhub to CI package pipeline
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1407 Add publishing bolt image to dockerhub to CI package pipeline Change By: Cas Donoghue Release Notes Summary: Bolt container images are now published to https://hub.docker.com/r/puppet/puppet-bolt when new versions are released. 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.312985.1560878372000.47959.1565273280461%40Atlassian.JIRA.
Jira (BOLT-1407) Add publishing bolt image to dockerhub to CI package pipeline
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1407 Add publishing bolt image to dockerhub to CI package pipeline Change By: Cas Donoghue Fix Version/s: BOLT Next 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.312985.1560878372000.47956.1565273040173%40Atlassian.JIRA.
Jira (PUP-9943) User type has custom retrieve() with non-standard return values
Title: Message Title Sean Millichamp created an issue Puppet / PUP-9943 User type has custom retrieve() with non-standard return values Issue Type: Bug Affects Versions: PUP 6.7.2, PUP 5.5.16 Assignee: Unassigned Components: Types and Providers Created: 2019/08/08 6:58 AM Priority: Normal Reporter: Sean Millichamp The core user type has a custom retrieve() method which returns a Hash that is inconsistent with the data type returned by the common method in Puppet::Type.retrieve(). As a result, mechanisms expecting to use retrieve() will have problems with user resources. Here is the offending code in the user type: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/user.rb#L496-L513 I think it may be safe and desirable to just remove the user type's retrieve block and let the standard one take effect. The existing retrieve method seems to be 10+ years old and may just be an artifact of a much earlier time in Puppet's life. Regardless if the method is needed or not, it should have a return value consistent with the expected return value from the standard Puppet::Type.retrieve() method.
Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used
Title: Message Title Reid Vandewiele commented on PUP-7814 Re: HTTPS file sources with non-puppet-trusted certs can't be used This would be specific to the File resource provider's use of Net::HTTP, and would not extend to any of the Puppet agent's core PKI trust configuration, yes? That is, we wouldn't end up being able to trust and download a catalog from a "master" with a cert signed by Let's Encrypt or anything like that 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.203766.1501710671000.47922.1565270400333%40Atlassian.JIRA.
Jira (FACT-1968) Unable to compile facter 3.14.2 on latest Archlinux
Title: Message Title Gabriel Nagy commented on FACT-1968 Re: Unable to compile facter 3.14.2 on latest Archlinux This is interesting because the libfacter specs job is not being run on travis, probably because the docker container doesn't have ruby. In this case CMake probably sees that you have Ruby installed and also tries to run the specs. You need to bundle install inside facter/lib before running make test. 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.318296.1564333964000.47908.1565269800202%40Atlassian.JIRA.
Jira (FACT-1968) Unable to compile facter 3.14.2 on latest Archlinux
Title: Message Title Tim Meusel commented on FACT-1968 Re: Unable to compile facter 3.14.2 on latest Archlinux Tests are failing because the rake version is too new on Arch (version 12). The Gemfile expects Version 10. I'm currently working on a 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 https://groups.google.com/d/msgid/puppet-bugs/JIRA.318296.1564333964000.47904.1565269320184%40Atlassian.JIRA.
