Navigation Menu

Skip to content
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

fix install ordering for innodb data size #1160

Merged
merged 1 commit into from Apr 2, 2019

Conversation

fe80
Copy link
Contributor

@fe80 fe80 commented Feb 7, 2019

Hi,

Since release 5.4.0 MySQL package was install with default configuration, and after the configuration was set.

So we can not change innodb data size configuration for example (the default size is 12Mo and if you change this size MySQL can't be restart).

Someone have notify this conportement on the commit: d13c06b

I think it's better to rollback the ordering, and eventually change the resource /etc/mysql/conf.d/mysql.cnf in post-install class if it's needed

@elfranne
Copy link
Contributor

Any progress on this ?

@david22swan david22swan merged commit d48ff05 into puppetlabs:master Apr 2, 2019
@david22swan
Copy link
Member

@fe80 Thank you for your work and we are sorry that the module was broken for you for so long.

@yotles
Copy link

yotles commented Apr 23, 2019

Hello. Could you please describe why after this changes installation of mysql by this module with version 8.1.0 started to fail? datadir redeclared by $datadir not created before starting of configuring mysql package.

@fe80
Copy link
Contributor Author

fe80 commented May 10, 2019

Hello @yotles,

We create the datadir before installation in a custom module to create a dedicated logical volume. I think this is why we have this issue.

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

Successfully merging this pull request may close these issues.

None yet

7 participants