trove NoSuchOptError: no such option mysql57 in group [DEFAULT]

asked 2018-05-03 13:55:55 -0500

OSSftw gravatar image

Hello, I get the NoSuchOptError when I try to launch a db instance through horizon.

root@node1 trove]# tail /var/log/trove/trove-api.log 
2018-05-03 14:42:16.623 3038 ERROR trove.common.wsgi     return self[key]
2018-05-03 14:42:16.623 3038 ERROR trove.common.wsgi   File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2527, in __getitem__
2018-05-03 14:42:16.623 3038 ERROR trove.common.wsgi     return self.__getattr__(key)
2018-05-03 14:42:16.623 3038 ERROR trove.common.wsgi   File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2523, in __getattr__
2018-05-03 14:42:16.623 3038 ERROR trove.common.wsgi     raise NoSuchOptError(name)
2018-05-03 14:42:16.623 3038 ERROR trove.common.wsgi NoSuchOptError: no such option mysql57 in group [DEFAULT]
2018-05-03 14:42:16.623 3038 ERROR trove.common.wsgi

The data store list is shown below.

[root@node1 trove(customerA_admin)]# trove datastore-list
+--------------------------------------+---------+
| ID                                   | Name    |
+--------------------------------------+---------+
| a6c40ce6-5dc0-467e-8570-dc70b1800bb7 | mysql57 |
| c2e7697d-98c8-4e6f-8ddf-f79f24ec1e88 | mysql   |
+--------------------------------------+---------+
[root@node1 trove(customerA_admin)]#

Any idea?

edit retag flag offensive close merge delete

Comments

It looks like mysql57 appears as the first word in a line in a Trove configuration file. The config parser interprets this as a config option, and since Trove has no option named mysql57, it raises this exception.

Bernd Bausch gravatar imageBernd Bausch ( 2018-05-03 14:30:28 -0500 )edit

Ty for your comment. Which conf file should I check? I checked trove.conf file and I didn't come across any line related to mysql57.

OSSftw gravatar imageOSSftw ( 2018-05-04 00:56:06 -0500 )edit

The error output that you posted doesn't indicate which config file that would be, but I guess one that belongs to Trove. Perhaps the stack trace in /var/log/trove/trove-api.log provides a clue, or the messages that precede it. If you haven't configured DEBUG logging, you may want to do that, too.

Bernd Bausch gravatar imageBernd Bausch ( 2018-05-04 03:03:54 -0500 )edit

Hi Bernd, I turned the debug on (in trove conf files) and reviewed the extended information. I guess there was something wrong with the datastore name (mysql57). I attached my glance image to other datastore called mysql .

OSSftw gravatar imageOSSftw ( 2018-05-05 01:34:13 -0500 )edit

Now I am able launch a database instance but it gets stuck in building status. I guess there is something wrong with my .cloudinit file.

OSSftw gravatar imageOSSftw ( 2018-05-05 01:34:34 -0500 )edit