Skip to content

1509: Fix ssl params issue for EL7 and newer mariadb versions #1511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

loopiv
Copy link

@loopiv loopiv commented Nov 8, 2022

#1509 Fix ssl params issue with newer versions of mariadb on el7

Note: previous PR had cla assistant problem that I could not resolve

@loopiv loopiv requested a review from a team as a code owner November 8, 2022 20:56
@puppet-community-rangefinder
Copy link

mysql::params is a class

Breaking changes to this file WILL impact these 2 modules (exact match):
Breaking changes to this file MAY impact these 1 modules (near match):

This module is declared in 140 of 580 indexed public Puppetfiles.


These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

@CLAassistant
Copy link

CLAassistant commented Nov 8, 2022

CLA assistant check
All committers have signed the CLA.

@fe80
Copy link
Contributor

fe80 commented Nov 9, 2022

I guess It's for https://jira.mariadb.org/browse/MDEV-29811 and MariaDB/server@32158be

That concern all distributions not just EL7 for information.

@LukasAud
Copy link
Contributor

Hi @loopiv, this issue has already been addressed in the following PR. If the issue still persists for you despite this update, please let us know. Otherwise, this PR can be closed.

@david22swan
Copy link
Member

@loopiv Hey, as you have not responded to the comment above I'm gonna assume this has been resolved and close the PR.
If this is not the case Feel free to re-open the PR and ping us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants