-
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
State mysql_user.present fails first time on Salt 2018.3 #50744
Comments
this seems similar to #48204 (comment) but this should have been fixed in 2018.3.3. Is your minion also 2018.3.3? Also what version of mysql are you using? |
@Ch3LL ah, yes that definitely looks similar. After the first run of the state, the users are there, but I can't connect with their credentials. After the second run, the credentials work. Minion and master are both 2018.3.3:
MySQL version is 5.6.40. |
Hi @jessebye, Maybe related to saltstack-formulas/mysql-formula#194 (comment)? |
@danielpardorus-allenta thanks! that does appear to be related. |
Hi, the states are running fine when users are setup where localhost is allowed but even here as in yesterday referenced issue mentionedthe buggy verify_login call also creates unnecessary ERROR output lines which shouldn't be written for such pre-checks:
|
ping @garethgreenaway i'm pretty certain u have done some recent work around this, but i can't seem to find the PR. Can you comment here? |
Hello @Ch3LL and @garethgreenaway , |
I'm seeing this issue as well on 2019.2 and MariaDB 10.1 and 10.2.
Salt: 2019.2.0
Dependency Versions:
cffi: 1.6.0
cherrypy: Not Installed
dateutil: Not Installed
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
ioflo: Not Installed
Jinja2: 2.7.2
libgit2: 0.26.3
libnacl: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.5.6
mysql-python: 1.2.5
pycparser: 2.14
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: 0.26.4
Python: 2.7.5 (default, Apr 9 2019, 14:30:50)
python-gnupg: 0.4.3
PyYAML: 3.11
PyZMQ: 15.3.0
RAET: Not Installed
smmap: Not Installed
timelib: Not Installed
Tornado: 4.2.1
ZMQ: 4.1.4
System Versions:
dist: centos 7.6.1810 Core
locale: UTF-8
machine: x86_64
release: 3.10.0-957.12.2.el7.x86_64
system: Linux
version: CentOS Linux 7.6.1810 Core |
thanks for pointing that out. Can anyone try the fixes here: #53418 |
I was experiencing the error described by OP and using the fixed mysql module get's rid of that error: user_create runs through without errors on the first go. |
perfect okay to close then? |
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. |
Description of Issue/Question
We have many
mysql_user.present
states that were working fine in Salt 2017.7. After upgrading to 2018.3, the states fail the first time they run with no error given. The second time they run, they succeed. Using the mysql module instead of state resolves the problem.Setup
Steps to Reproduce Issue
mysql_user.present
states fail with a message like this:The minion debug log is not very helpful:
Possibly of interest, the following state doesn't exhibit this problem:
Versions Report
The text was updated successfully, but these errors were encountered: