-
Notifications
You must be signed in to change notification settings - Fork 11
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
Test Kitchen issues found on password setting #12
Comments
If more info is needed this is the select version() MariaDB [(none)]> select version(); |
This is strange. Actually, in my understanding the new mariadb/ mysql packages should use |
That's basically what was trying to say in this comment: #6 (comment) I never used mariadb so I can only tell you what I've found in documentation and give you my assumptions based on that. So mysql needs the edit: Made a mistake. I actually don't understand when mariadb actually makes use of |
My test didn't allowed me to login as root. mysql.user table had root user with 'Password' field empty and authentication_string with the password that i set as attribute. Solved it by setting the Password with the modified query i put here: message 1 |
More logs:
Then: kitchen login mariadb-101-ubuntu-1604
0 packages can be updated. *** System restart required *** Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> More data on mysql.user: MariaDB [mysql]> select User,Password,authentication_string from user; |
While coding the percona support, i have added a .kitchen.yml to verify the installations:
On ubuntu 16.04 found this:
run_list:
And set the root_password attribute:
But password is set on authentication string not on password field, i have accesed this mariadb but the password was not set, solved it using:
mysql --defaults-file=/etc/mysql/debian.cnf mysql -e "UPDATE user SET Password = PASSWORD('abcdef01234567890') WHERE User = 'root'; FLUSH PRIVILEGES;"
I dont know if this happened because using the mariadb.org repository.
The text was updated successfully, but these errors were encountered: