-
Bug
-
Resolution: Done
-
Medium
-
Beijing Release
-
None
Tried installation of ONAP Beijing Release
git clone -b beijing http://gerrit.onap.org/r/oom
and followed steps here - http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_quickstart_guide.html#quick-start-label
After installation, noted all pods except following in Running state
onap dev-aaf-cm-6685b46b6-tcchx 0/1 CrashLoopBackOff 272 23h 10.42.81.51 sb4-k8s-2 onap dev-appc-dgbuilder-589bb888f8-m2pph 0/1 CrashLoopBackOff 332 1d 10.42.45.112 sb4-k8s-1 onap dev-sdnc-ansible-server-79fc9558b6-lw9hq 0/1 CrashLoopBackOff 402 1d 10.42.195.72 sb4-k8s-1 onap dev-sdnc-portal-64f5746fb6-pzd8s 0/1 CrashLoopBackOff 334 1d 10.42.105.174 sb4-k8s-3
Did a healthcheck and noted SDC and SO in FAIL state (report attached)
Checked the SO logs and found the following exception
Caused by: java.sql.SQLInvalidAuthorizationSpecException: Could not connect: Access denied for user 'mso'@'10.42.38.26' (using password: YES) at org.mariadb.jdbc.internal.util.ExceptionMapper.get(ExceptionMapper.java:123) at org.mariadb.jdbc.internal.util.ExceptionMapper.throwException(ExceptionMapper.java:71) at org.mariadb.jdbc.Driver.connect(Driver.java:109) at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:321) ... 96 moreCaused by: org.mariadb.jdbc.internal.util.dao.QueryException: Could not connect: Access denied for user 'mso'@'10.42.38.26' (using password: YES) at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.authentication(AbstractConnectProtocol.java:524) at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.handleConnectionPhases(AbstractConnectProtocol.java:472) at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.connect(AbstractConnectProtocol.java:374) at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.connectWithoutProxy(AbstractConnectProtocol.java:763) at org.mariadb.jdbc.internal.util.Utils.retrieveProxy(Utils.java:469) at org.mariadb.jdbc.Driver.connect(Driver.java:104) ... 97 more07:03:29,075 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (default task-20) SQL Error: 0, SQLState: null07:03:29,075 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (default task-20) javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/mso-requests
Further checked SO-db docker container
Tried login with root and password 'password' - succesfully logged in
Tried to login with mso and password 'password' - Access denied.
Using root login to mysql tried to list the databases and following databases were found
root@mariadb:/# mysql -uroot -ppassword Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 85218 Server version: 10.1.11-MariaDB-1~jessie-log mariadb.org binary distributionCopyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others.Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.MariaDB [(none)]> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | performance_schema | +--------------------+ 3 rows in set (0.00 sec)MariaDB [(none)]>
As per SO documentation following additional dbs need to be available by default after container initialization.
+--------------------+ | Database | +--------------------+ | camundabpmn | | information_schema | | mso_catalog | | mso_requests | | mysql | | performance_schema | +--------------------+
Checked the so-db docker container - /docker-entrypoint-initdb.d and found no files in there
- relates to
-
-
- Closed
-