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

Issue with mysql.login_create #64207

Open
ahendo13 opened this issue May 2, 2023 · 2 comments
Open

Issue with mysql.login_create #64207

ahendo13 opened this issue May 2, 2023 · 2 comments
Labels
Bug broken, incorrect, or confusing behavior info-needed waiting for more info needs-triage

Comments

@ahendo13
Copy link

ahendo13 commented May 2, 2023

I am managing a user for a mysql database via salt.

The salt state runs correctly and no errors are show in the state apply.

Looking at the specific log for the mysql.login_create shows successful, but the detailed log message reports an error.
{
“Ret”: “Could not create the login: (18456, d’DB-Lib error message 20018, severity 14:]]nGeneral SQL Server error: Check messages from the SQL server\nDB-Lib error message 20002, severity 9:\nAdaptive Server connection failed (localhost)\nDB-Lib error message 20002, severity 9:\nAdaptive Server connection failed (localhost)\n’)”
}

The state apply should report the failure.

saltsls
salterror

Salt Version:
Salt: 3005.1

Dependency Versions:
cffi: 1.11.5
cherrypy: Not Installed
dateutil: 2.6.1
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 3.0.1
libgit2: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.4
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: 2.14
pycrypto: Not Installed
pycryptodome: 3.16.0
pygit2: Not Installed
Python: 3.6.8 (default, Jan 14 2022, 11:04:20)
python-gnupg: Not Installed
PyYAML: 3.12
PyZMQ: 24.0.1
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.4

Salt Extensions:
saltext.vmware: 22.9.8.0rc1
SSEAPE: 8.10.1.6

System Versions:
dist: rhel 8.6 Ootpa
locale: UTF-8
machine: x86_64
release: 4.18.0-372.16.1.el8_6.x86_64
system: Linux
version: Red Hat Enterprise Linux 8.6 Ootpa

PASTE HERE

Additional context
Add any other context about the problem here.

@ahendo13 ahendo13 added Bug broken, incorrect, or confusing behavior needs-triage labels May 2, 2023
@welcome
Copy link

welcome bot commented May 2, 2023

Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at saltproject@vmware.com. We’re glad you’ve joined our community and look forward to doing awesome things with you!

@OrangeDog
Copy link
Contributor

OrangeDog commented May 3, 2023

Your issue says MySQL, but your code says MSSQL. They are completely different systems.

Once you've worked out what you're trying to use, how have you configured the connection properties?

@OrangeDog OrangeDog added the info-needed waiting for more info label May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior info-needed waiting for more info needs-triage
Projects
None yet
Development

No branches or pull requests

2 participants