notary-db.log reports - "ERROR: 1049 Unknown database 'test'". Also /usr/bin/mysqladmin is not found

[andrewtchin]

Reported by @lgayatri under vmware/vic-product#564, which I closed
I verified this on a build from master. Please direct questions for additional details to @lgayatri

Deployed - chin-vic-c2506807-dev-upgrade.OVA
Post power on and registration at 9443 port, checked the logs under harbor and noticed that
notary-db.log says:

Aug 14 05:36:14 172.18.0.1 notary-db[405]: ERROR: 1049 Unknown database 'test'
Aug 14 05:36:14 172.18.0.1 notary-db[405]: 2017-08-14 5:36:14 139743514843072 [ERROR] Aborting
Aug 14 05:36:14 172.18.0.1 notary-db[405]:
Aug 14 05:36:16 172.18.0.1 notary-db[405]:
Aug 14 05:36:16 172.18.0.1 notary-db[405]: WARNING: OPENGIS REQUIRED SP-S WERE NOT COMPLETELY INSTALLED!
Aug 14 05:36:16 172.18.0.1 notary-db[405]: GIS extentions might not work properly.
Aug 14 05:36:16 172.18.0.1 notary-db[405]:
Aug 14 05:36:16 172.18.0.1 notary-db[405]: PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
Aug 14 05:36:16 172.18.0.1 notary-db[405]: To do so, start the server, then issue the following commands:
Aug 14 05:36:16 172.18.0.1 notary-db[405]:
Aug 14 05:36:16 172.18.0.1 notary-db[405]: '/usr/bin/mysqladmin' -u root password 'new-password'
Aug 14 05:36:16 172.18.0.1 notary-db[405]: '/usr/bin/mysqladmin' -u root -h f9736b8317f9 password 'new-password'
Aug 14 05:36:16 172.18.0.1 notary-db[405]:
Aug 14 05:36:16 172.18.0.1 notary-db[405]: Alternatively you can run:
Aug 14 05:36:16 172.18.0.1 notary-db[405]: '/usr/bin/mysql_secure_installation'
Aug 14 05:36:16 172.18.0.1 notary-db[405]:
Aug 14 05:36:16 172.18.0.1 notary-db[405]: which will also give you the option of removing the test
Aug 14 05:36:16 172.18.0.1 notary-db[405]: databases and anonymous user created by default. This is
Aug 14 05:36:16 172.18.0.1 notary-db[405]: strongly recommended for production servers.
Aug 14 05:36:16 172.18.0.1 notary-db[405]:
Aug 14 05:36:16 172.18.0.1 notary-db[405]: See the MariaDB Knowledgebase at http://mariadb.com/kb or the
Aug 14 05:36:16 172.18.0.1 notary-db[405]: MySQL manual for more instructions.
Aug 14 05:36:16 172.18.0.1 notary-db[405]:
Aug 14 05:36:16 172.18.0.1 notary-db[405]: Please report any problems at http://mariadb.org/jira
Aug 14 05:36:16 172.18.0.1 notary-db[405]:
Aug 14 05:36:16 172.18.0.1 notary-db[405]: The latest information about MariaDB is available at http://mariadb.org/.
Aug 14 05:36:16 172.18.0.1 notary-db[405]: You can find additional information about the MySQL part at:
Aug 14 05:36:16 172.18.0.1 notary-db[405]: http://dev.mysql.com
Aug 14 05:36:16 172.18.0.1 notary-db[405]: Support MariaDB development by buying support/new features from MariaDB
Aug 14 05:36:16 172.18.0.1 notary-db[405]: Corporation Ab. You can contact us about this at [email protected].

The installer does not ask to set the password for the DB.
If it is required to set the password, then we should mandate in the OVA deployment UI.
If it is NOT required to set the password, then we can skip showing the above messages
2.There is no file called /usr/bin/mysqladmin

what is 'test' database which we are referring to?

[reasonerjt]

This seems to be an issue of hard code configuration of the mariadb docker image.
dockerfile/mariadb#13
And we don't require the password but we can't skip showing the messages because it's generated by the official docker image of maria db.

We don't plan to make update for this issue in 1.2

However, given we plan to migrate the DB to photon, we may have a chance to fix the misleading message issue in next release.

[andrewtchin]

Cool thanks for looking into it

[lgayatri]

Verified on VIC 1.3 and this issue has been resolved.
Build on which the scenario was verified - vic-v1.3.0-rc3-2784-7d227d5c.ova