-
Notifications
You must be signed in to change notification settings - Fork 364
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
[BUG] mysql.client state does not work out of the box #267
Comments
fyi (not sure why) it happens at least on Debian 11, but not on openSUSE Leap.
|
I just hit this issue and did some work investigating it. It turns out a simple workaround exists: # Pillar data.
mysql:
config_directory: /etc/mysql The configuration directory is only created if the mysql-formula/mysql/config.sls Lines 4 to 13 in 3c0568c
The problem comes from the absence of a default value for Debian: mysql-formula/mysql/osmap.yaml Lines 4 to 5 in 3c0568c
Unlike CentOS and Fedora (lines 19 and 35): mysql-formula/mysql/osmap.yaml Lines 18 to 35 in 3c0568c
I have only tested this workaround on Debian 11 so far. |
Your setup
Formula commit hash / release tag
master version b9b8792
Versions reports (master & minion)
Using Kitchen setup from the formula
Pillar / config used
No pillar (
test/salt/pillar/mysql.sls
empty)Kitchen.yml changed to call
mysql.client
state instead of the meta-statemysql
Bug details
Describe the bug
When running state
mysql.client
it executesmysql.config
which returns an Error if no pillar is providedSteps to reproduce the bug
You can see here the code https://github.com/daks/mysql-formula/tree/bug-client and the CI pipeline https://gitlab.com/daks/mysql-formula/-/pipelines/516218792
Expected behaviour
I expect this state to at minima install client packages. I don't necesary expect it to manage configuration but if it needs to be done, it should executed without errors
Attempts to fix the bug
None at the moment. I think the bug comes from one of the "if" in the state mysql.config
Additional context
The text was updated successfully, but these errors were encountered: