Jira (PUP-10225) Puppetserver 6 performance regression
Title: Message Title Iain Buclaw commented on PUP-10225 Re: Puppetserver 6 performance regression Nick Walker - everything is stable, is there a recommended tunings page where this can be put in? 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.341411.1578473781000.16424.1580979300419%40Atlassian.JIRA.
Jira (FACT-2318) Extend Facter 4.x API with fact
Title: Message Title Bogdan Irimie assigned an issue to Florin Dragos Facter / FACT-2318 Extend Facter 4.x API with fact Change By: Bogdan Irimie Assignee: Florin Dragos 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.344084.1580306071000.16485.1580985960131%40Atlassian.JIRA.
Jira (PUP-10270) Allow testing of data types with defined()
Title: Message Title
Matthias Baur created an issue
Puppet / PUP-10270
Allow testing of data types with defined()
Issue Type:
Improvement
Assignee:
Henrik Lindberg
Components:
Functions
Created:
2020/02/06 2:58 AM
Priority:
Normal
Reporter:
Matthias Baur
It would be nice if I could test if a data type exists. Henrik Lindberg suggested on Slack that this functionality might be easily implemented in the defined() function. The use case is: As a module maintainer I need to support Puppet 5 and 6. If I want to implemented Deferred I need to do the following to ensure Puppet 5 doesn't try to compile the Deferred data type. This would lead to a compile error.
# $serverversion is empty on 'puppet apply' runs. Just use clientversion.
$_serverversion= get('serverversion') ? {
undef => $clientversion,
default => $serverversion,
Jira (PUP-10270) Allow testing for data types with defined()
Title: Message Title Matthias Baur updated an issue Puppet / PUP-10270 Allow testing for data types with defined() Change By: Matthias Baur Summary: Allow testing of for data types with defined() 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.345289.1580986728000.16491.1580986800248%40Atlassian.JIRA.
Jira (PUP-10270) Allow testing for data types with defined()
Title: Message Title Henrik Lindberg commented on PUP-10270 Re: Allow testing for data types with defined() For anyone implementing this: it is important to know that when asking for a data type, all types that are not explicitly defined are by design a Resource datatype (yes, for historical reasons it needs to do this). Since the ask for a data type must use a string the logic ends up doing this: # Find a resource type, definition or class definition Puppet::Pops::Evaluator::Runtime3ResourceSupport.find_resource_type_or_class(scope, val) I think it may need to do that first, and if not found, then try the 4.x loaders to load the data type - i.e. something like this: loader = Puppet.lookup(:loaders).private_environment_loader() type = loader.load(:type, type_name) But, in Puppet 6 it may work to only use the 4.x loaders. Add Comment
Jira (PUP-10218) Puppet incorrectly detecting stale pidfile
Title: Message Title Ciprian Badescu commented on PUP-10218 Re: Puppet incorrectly detecting stale pidfile Marcin Deranek, can you provide us the steps to reproduce the issue? How did you start puppet process as LWP? 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.341249.1578386676000.16571.1580994540152%40Atlassian.JIRA.
Jira (PDB-4626) Investigate resource_events partitioning migration failure
Title: Message Title Michael Prokop commented on PDB-4626 Re: Investigate resource_events partitioning migration failure FTR, I've tested the upgrade to 6.8.1-1stretch today, but this still fails for us with the same error message, we had to revert/downgrade to 6.7.3-1stretch again. Is there anything special that needs to be taken care of to get this fixed? 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.342360.1579198905000.16631.1580999760315%40Atlassian.JIRA.
Jira (PUP-10225) Puppetserver 6 performance regression
Title: Message Title Nick Walker commented on PUP-10225 Re: Puppetserver 6 performance regression We have this page: https://puppet.com/docs/puppetserver/latest/tuning_guide.html What changes are you recommending? 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.341411.1578473781000.16655.1581003180308%40Atlassian.JIRA.
Jira (PUP-10269) Install sar & glance by using puppet module
Title: Message Title Josh Cooper commented on PUP-10269 Re: Install sar & glance by using puppet module There's not enough information in this ticket. Can you please join the slack channel I mentioned earlier and ask your questions there? 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.345279.1580963234000.16783.1581009120233%40Atlassian.JIRA.
Jira (PUP-10227) Close the http connection prior to sleeping retry-after seconds
Title: Message Title Charlie Sharpsteen commented on PUP-10227 Re: Close the http connection prior to sleeping retry-after seconds Sorry, missed this one in the sea of mail. Yes, this is a great change. Also, closing on the agent side seems like the best behavior going forward as the Connection: header was removed from HTTP/2. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341492.1578520569000.16820.1581010500167%40Atlassian.JIRA.
Jira (PUP-10273) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10273 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.13.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/02/06 10:50 AM Due Date: 2020/02/12 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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-10271) Puppet Platform 6.13.0 Release - 2020-02-18
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10271 Puppet Platform 6.13.0 Release - 2020-02-18 Issue Type: Epic Assignee: Nirupama Mantha Created: 2020/02/06 10:50 AM Due Date: 2020/02/18 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.13.0 Release - 2020-02-18 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10272) Prepare JIRA and Confluence for release (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10272 Prepare JIRA and Confluence for release (Puppet Platform 6.13.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/02/06 10:50 AM Due Date: 2020/02/12 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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.13.0 and puppet-agent 6.13.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X
Jira (PUP-10279) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10279 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.13.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/02/06 10:54 AM Due Date: 2020/02/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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-10278) Prepare release announcement (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10278 Prepare release announcement (Puppet Platform 6.13.0) Issue Type: Task Assignee: Kate Medred Created: 2020/02/06 10:54 AM Due Date: 2020/02/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Kate Medred 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-10275) Prepare JIRA and Confluence for release (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10275 Prepare JIRA and Confluence for release (Puppet Platform 6.13.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/02/06 10:54 AM Due Date: 2020/02/12 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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.13.0 and puppet-agent 6.13.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X
Jira (PUP-10276) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10276 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.13.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/02/06 10:54 AM Due Date: 2020/02/12 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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-10277) Prepare documentation updates and release notes (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10277 Prepare documentation updates and release notes (Puppet Platform 6.13.0) Issue Type: Task Assignee: Kate Medred Created: 2020/02/06 10:54 AM Due Date: 2020/02/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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-10274) Puppet Platform 6.13.0 Release - 2020-02-18
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10274 Puppet Platform 6.13.0 Release - 2020-02-18 Issue Type: Epic Assignee: Nirupama Mantha Created: 2020/02/06 10:54 AM Due Date: 2020/02/18 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.13.0 Release - 2020-02-18 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10282) Update Confluence and JIRA based on release (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10282 Update Confluence and JIRA based on release (Puppet Platform 6.13.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/02/06 10:55 AM Due Date: 2020/02/19 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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 th
Jira (PUP-10280) Publish documentation and updates and release notes (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10280 Publish documentation and updates and release notes (Puppet Platform 6.13.0) Issue Type: Task Assignee: Kate Medred Created: 2020/02/06 10:55 AM Due Date: 2020/02/18 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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-10281) Send release announcement (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10281 Send release announcement (Puppet Platform 6.13.0) Issue Type: Task Assignee: Sara Meisburger Created: 2020/02/06 10:55 AM Due Date: 2020/02/18 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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.13.0 is now available".
Jira (PDB-4647) Bump versions, push directly, and tag (PuppetDB 6.9.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4647 Bump versions, push directly, and tag (PuppetDB 6.9.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/02/06 10:55 AM Due Date: 2020/02/14 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in t
Jira (PDB-4648) Check builds, promote to PE (PuppetDB 6.9.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4648 Check builds, promote to PE (PuppetDB 6.9.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/02/06 10:56 AM Due Date: 2020/02/14 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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-4646) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.9.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4646 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.9.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/02/06 10:55 AM Due Date: 2020/02/11 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PUP-10283) Communicate scope and timeline of next release (Puppet Platform 6.13.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10283 Communicate scope and timeline of next release (Puppet Platform 6.13.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/02/06 10:55 AM Due Date: 2020/02/19 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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 (PDB-4645) Merge-up, branch, and create pipelines (PuppetDB 6.9.0)
Title: Message Title
Nirupama Mantha created an issue
PuppetDB / PDB-4645
Merge-up, branch, and create pipelines (PuppetDB 6.9.0)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2020/02/06 10:55 AM
Due Date:
2020/02/11
Priority:
Normal
Reporter:
Nirupama Mantha
(Initial planned release date: 2020-02-18) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> 6.3.x
Merge 6.3.
Jira (PDB-4649) Update winston (PuppetDB 6.9.0)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4649 Update winston (PuppetDB 6.9.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/02/06 10:56 AM Due Date: 2020/02/19 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2020-02-18) 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 (FACT-2300) Incomplete Facter results on Raspberry Pi 4 with "gem install puppet"
Title: Message Title Vijay Kumar commented on FACT-2300 Re: Incomplete Facter results on Raspberry Pi 4 with "gem install puppet" Mihai Buzgau Thank you for your response Much appreciated. 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.342640.1579363969000.17183.1581015480352%40Atlassian.JIRA.
Jira (PUP-10267) Need to be able to route to a specific file server given a URL
Title: Message Title Melissa Stone commented on PUP-10267 Re: Need to be able to route to a specific file server given a URL Merged into master with https://github.com/puppetlabs/puppet/commit/82e0977e4503e383b72e3a75ffbb1ceb0558df27 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.345063.158085944.17359.1581022440196%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Paul Reed updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Paul Reed Attachment: PDB-4642-psreed.zip 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.344931.1580780081000.17367.1581022800428%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Paul Reed commented on PDB-4642 Re: Puppet 2019.3 upgrade failure from 2019.2.2 Seems I've run into a similar issue. I've attached a zipfile with a copy of my resource_events table, as well as the pertinent bits from /var/log/messages and the clojure EDN file referenced in the error. Hopefully this will help. Thanks, Paul 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.344931.1580780081000.17372.1581022920267%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Austin Blatt Assignee: Austin Blatt 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.320599.1565648011000.17407.1581024060547%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Charlie Sharpsteen commented on PDB-4642 Re: Puppet 2019.3 upgrade failure from 2019.2.2 I can re-produce this using the ZIP archive that Paul Reed uploaded: Get a CentOS 8 VM Set the timezone to EST: timedatectl set-timezone 'America/New_York' Install PE 2019.2.2 Stop PuppetDB: systemctl stop pe-puppetdb Drop the resource_events table: sudo -u pe-postgres /opt/puppetlabs/server/bin/psql -d pe-puppetdb -c 'drop table resource_events' Unpack the ZIP archive, copy resource_events.sql somewhere world-readable, like /tmp, and edit it to remove the last statement (otherwise, import fails): ALTER TABLE ONLY public.resource_events ADD CONSTRAINT resource_events_report_id_fkey FOREIGN KEY (report_id) REFERENCES public.reports(id) ON DELETE CASCADE; Import the edited copy of resource_events.sql:
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Charlie Sharpsteen updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Charlie Sharpsteen Attachment: resource_events_migration.log 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.344931.1580780081000.17651.1581030180771%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Charlie Sharpsteen commented on PDB-4642 Re: Puppet 2019.3 upgrade failure from 2019.2.2 The migration does not create a table for Jan 31st: grep -o '\(CREATE TABLE IF NOT EXISTS [^[:space:]]\+\)' resource_events_migration.log|sort -u CREATE TABLE IF NOT EXISTS resource_events_20200123Z CREATE TABLE IF NOT EXISTS resource_events_20200124Z CREATE TABLE IF NOT EXISTS resource_events_20200130Z CREATE TABLE IF NOT EXISTS resource_events_20200202Z CREATE TABLE IF NOT EXISTS resource_events_20200203Z CREATE TABLE IF NOT EXISTS resource_events_20200204Z CREATE TABLE IF NOT EXISTS resource_events_20200205Z CREATE TABLE IF NOT EXISTS resource_events_20200206Z CREATE TABLE IF NOT EXISTS resource_events_20200207Z CREATE TABLE IF NOT EXISTS resource_events_20200208Z CREATE TABLE IF NOT EXISTS resource_events_20200209Z
Jira (PDB-4650) Issues w/ HA page in PDB docs
Title: Message Title Melissa Amos updated an issue PuppetDB / PDB-4650 Issues w/ HA page in PDB docs Change By: Melissa Amos Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.345425.1581032171000.17727.1581032221375%40Atlassian.JIRA.
Jira (PDB-4650) Issues w/ HA page in PDB docs
Title: Message Title
Melissa Amos created an issue
PuppetDB / PDB-4650
Issues w/ HA page in PDB docs
Issue Type:
Task
Assignee:
Unassigned
Created:
2020/02/06 3:36 PM
Priority:
Normal
Reporter:
Melissa Amos
Two issues with this page: https://puppet.com/docs/puppetdb/latest/ha.html
It seems to be orphaned, as it doesn't appear in the sidebar nav
The generic H1 title ("High Availability") means that this page appears first in docs search results. The H1 should be "Configuring PuppetDB for High Availability". This change would also fix the issue of having two headings in a row at the top of the page, which is not our practice for docs.
Add Comment
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9602 puppet 6 apply fails if puppet types have been generated Change By: Jarret Lavallee CS Priority: Needs Priority 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.302978.1554294806000.17817.1581034261091%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Jarret Lavallee CS Priority: Needs Priority Major 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.344931.1580780081000.17861.1581035580771%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Jarret Lavallee CS Rank: 1500 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.344931.1580780081000.17871.1581035940347%40Atlassian.JIRA.
Jira (PUP-9750) optionally add pe_serverversion to server_facts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9750 optionally add pe_serverversion to server_facts Change By: Josh Cooper Sprint: Community PRs Platform Core KANBAN 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.312257.156036703.18007.1581043260184%40Atlassian.JIRA.
Jira (FACT-2350) FacterNg integrated with Puppet 6.12
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2350 FacterNg integrated with Puppet 6.12 Issue Type: Bug Assignee: Unassigned Created: 2020/02/06 11:07 PM Priority: Normal Reporter: Sebastian Miclea There is an error thrown when activating the feature switch for FacterNG on Puppet 6.12 when running puppet facts Error: Could not initialize global default settings: wrong number of arguments (given 0, expected 1) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
