-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
module.mysql.user_present and state.mysql_user.present can't properly check user passord #52165
Comments
ping @garethgreenaway i know you have been doing some work in these modules lately any ideas here? |
Hi @Ch3LL and @garethgreenaway , I was first positive astonished that for my upgrade from 2017.7.8 to 2018.3.4 I had only to rename all occurrences of the opts['environment'] to opts['saltenv']. After rollout to production servers which are secured I stepped finally in this weird behavior that MySQL states did't check correctly. E.g these states:
produces in state run following log lines:
After several hours of unsuccessful searching for issues (where #50744 is also related to this bug), all latest changes in 2018.3 brach I made a local checkout and run a
This is a typical developer "I-run-all-states on-localhost-and-thats-sufficient-for-all-cases" thinking failure.
BTW:
The common problem also at Saltstack is the difference in thinking between feature orientated developers and stable running orientated admins/operations development which has to be used for systems like Saltstack and is very good explained in the speeches of: "Kristian Köhntopp: Go Away Or I Will Replace You With A Very Little Shell Script" where all thee public ones are sadly only available in German lanaguage. Here the visual picture of the difference ;)
Happy Easter |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Hello @Ch3LL and @garethgreenaway , Where is the fix for this bug? Is it in #50744 (comment) ?
And if this is the case, why it isn't working in released 2018.3.5 version ? |
Am I correct in presuming there still isn't a fix for this? |
Description of Issue/Question
For mariadb version > 10.2.0 the state
salt.state.mysql_user.present
and modulesalt.module.mysql.user_exist
can't check properly the user passwordon theses version, password check is done trough a simple connection on the mariadbl server using the
connection_args
dict. This dict contain theconnection_host
attribute that set the address of mysql server used to check this password.In case of the user is not authorized to connect trough this address, the password is detected as invalid and state will try to change it.
This issue break idempotence when the admin user and the managed user can't use the same interface to connect.
Setup
Steps to Reproduce Issue
an
connection_usercheck_host
parameter should be added to provides a reliable way to set the proper address to use to check the user authentication.Versions Report
issue is also present on salt 2018.3.4
The text was updated successfully, but these errors were encountered: