-
-
Notifications
You must be signed in to change notification settings - Fork 123
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
:create
on mariadb_server_install restarts service on every chef-client run
#265
Comments
Pretty sure the server is stopped because of these lines in the server_install resource for the create action:
|
A workaround I might try is to not include :create as an action, and instead write something to test if create needs to be run, then signal server_install resource, but my general expectation is that my database won't get restarted unless there is some need for a restart. |
If anyone else is struggling with this, my initial fix is to put a not_if on the resource checking for the recovery.conf file.
Your data directory may differ. |
The server_configuration resource would call a ruby_block on every run, using internal logic for idempotency instead of resource guards. The server_install resource's create action would stop the server to reset the root password every chef run. Fixes sous-chefs#265
Cookbook version
2.1.0
Chef-client version
14.11.21
Platform Details
centos vagrant in test-kitchent
Scenario:
Adding mariadb_server_install resource with
:create
as an action causes the mariadb service to stop and reset the root password whenever chef-client is run, regardless of whether the root password needs to be changed or not.Steps to Reproduce:
Use
[:install, :create]
as the actions for a mariadb_server_installExpected Result:
When nothing has been changed, the mysql server is not be restarted
Actual Result:
The mysql service is stopped, the password reconfigured, then mysql is restarted on every chef-client run.
The text was updated successfully, but these errors were encountered: