Cannot connect to mariadb (so catalogdb). Password incorrect.
Description
Environment
Activity
Former user July 19, 2020 at 3:14 PM
Mariadb user account found in kube secrets.
So, the problem was solved.
Former user July 15, 2020 at 9:22 AM
O yeah ) you save my life. Thanks a lot.
It works. Now I can continue my experiments.
Ok, I think I can close this issue now.
Former user July 15, 2020 at 9:09 AMEdited
Hello , you're not disturbing me, no problem.
All passwords for db access (on mariadb and most of them on postgres) are auto generated and set into a secret.
In your particular example, you need "catalogdb" allowed user
on my instance, it's in onap-so-mariadb-catalog-db-creds secret (onap is the name of helm release)
when looking into it, you'll see the creds base64 encoded (login is the user, passrword is well the password )
if you decode, you'll see that auto generation of password is not really the case... (, is it the desired behavior)
Former user July 15, 2020 at 5:18 AM
Hello,Sylvain.
Sorry for disturb,but could you just give a little advice about the problem described in this bug?
Then I'll close it.
How I can know which password was generated for so_admin or so_user in mariadb during the deployment? Because there are still some processes working only after SO catalogdb data modification in direct DB access mode. For example, it's a adding new cloud site or 5G network slicing demo.
Now I've just found a mariadb root password viewing the mariadb-galera logs. Now it's ok for me,but have a differences with demo case deployment descriptions.
Thanks a lot for your time and help.
Former user July 13, 2020 at 5:09 PM
Just root password which I found in mariadb-galera logs was helpful.
So,I should use it. the user 'mu-user' dont have a rights to catalogdb schema.
Details
Assignee
Former userFormer user(Deactivated)Reporter
Former userFormer user(Deactivated)Labels
Fix versions
Affects versions
Priority
Medium
Details
Details
Assignee
Former userReporter
Former userLabels
Fix versions
Affects versions
Priority
Medium
Hello.
After Frankfurt release installation we need to create our cloud resources in a MULTICLOUD mode.
According to the latest document https://docs.onap.org/en/frankfurt/guides/onap-operator/cloud_site/openstack/index.html we should create a new row directly in catalogdb database through mysql. I entered the mariadb container,but then I tried to login to the database using the default credentials: so_admin/so_Admin123 got the error:
ERROR 1045 (28000): Access denied for user 'so_admin'@'localhost' (using password: YES)
Tried to login with root account:
sh-4.2$ mysql --user=root --password=Aa123456
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
sh-4.2$ mysql --user=root --password=Aa123456 --host portal-db was success
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 5578
Server version: 10.4.13-MariaDB-1:10.4.13+maria~bionic mariadb.org binary distribution
Copyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>
But cannot get any user.
MariaDB [(none)]> use mysql;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
MariaDB [mysql]> select * from user;
ERROR 1449 (HY000): The user specified as a definer ('mariadb.sys'@'localhost') does not exist
Is it possible,that so_admin password was autogenerated during installation using the master password? As I know in Frankfurt release all passwords generating during installation now.
Can we use any API for cloud site create in SO data model? Or it possible just directly through database?
The database pods in a good condition.
onap-mariadb-galera-0 1/1 Running 0 7h54m
onap-mariadb-galera-1 1/1 Running 0 7h52m
onap-mariadb-galera-2 1/1 Running 1 7h50m
The SO db config job was done.
onap-so-mariadb-config-job-9vcxf 0/1 Completed 0 7h45m