Ask Your Question
0

keystone_manage db_sync keystone fails on kilo in CentOS 7.1

asked 2015-07-14 09:34:47 -0500

edfsr777 gravatar image

updated 2015-07-14 19:27:20 -0500

sunnyarora gravatar image

Attempting to install keystone in a VMWare vSphere 6 VM running CentOS 7.1 with MariaDB. When I run the "keystone_manage db_sync keystone" command, no tables / data are created in the keystone database. The keystone.log file contains the following:

[root@XLHou008018 keystone]# keystone-manage db_sync keystone
[root@XLHou008018 keystone]# cat keystone.log
2015-07-14 08:41:19.969 30050 CRITICAL keystone [-] NoSuchOptError: no such option: Ri
2015-07-14 08:41:19.969 30050 TRACE keystone Traceback (most recent call last):
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/bin/keystone-manage", line 44, in <module>
2015-07-14 08:41:19.969 30050 TRACE keystone     cli.main(argv=sys.argv, config_files=config_files)
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/keystone/cli.py", line 585, in main
2015-07-14 08:41:19.969 30050 TRACE keystone     CONF.command.cmd_class.main()
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/keystone/cli.py", line 76, in main
2015-07-14 08:41:19.969 30050 TRACE keystone     migration_helpers.sync_database_to_version(extension, version)
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/keystone/common/sql/migration_helpers.py", line 242, in sync_database_to_version
2015-07-14 08:41:19.969 30050 TRACE keystone     _sync_common_repo(version)
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/keystone/common/sql/migration_helpers.py", line 145, in _sync_common_repo
2015-07-14 08:41:19.969 30050 TRACE keystone     engine = sql.get_engine()
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/keystone/common/sql/core.py", line 188, in get_engine
2015-07-14 08:41:19.969 30050 TRACE keystone     return _get_engine_facade().get_engine()
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/keystone/common/sql/core.py", line 176, in _get_engine_facade
2015-07-14 08:41:19.969 30050 TRACE keystone     _engine_facade = db_session.EngineFacade.from_config(CONF)
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/session.py", line 866, in from_config
2015-07-14 08:41:19.969 30050 TRACE keystone     return cls(sql_connection=conf.database.connection,
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2520, in __getattr__
2015-07-14 08:41:19.969 30050 TRACE keystone     return self._conf._get(name, self._group)
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2242, in _get
2015-07-14 08:41:19.969 30050 TRACE keystone     value = self._do_get(name, group, namespace)
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2279, in _do_get
2015-07-14 08:41:19.969 30050 TRACE keystone     return convert(opt._get_from_namespace(namespace, group_name))
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2274, in convert
2015-07-14 08:41:19.969 30050 TRACE keystone     self._substitute(value, group, namespace), opt)
2015-07-14 08:41:19.969 30050 TRACE keystone   File "/usr/lib ...
(more)
edit retag flag offensive close merge delete

Comments

NoSuchOptError: no such option: Ri

check the keystone.conf file and find what is Ri . If it is unwanted field which is not required then remove it and do the db_sync again.

Ranjit gravatar imageRanjit ( 2015-07-14 23:18:29 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-07-15 14:41:10 -0500

edfsr777 gravatar image

Issue is resolved. There were two problems.

The first is related to the "no such option: RI." Did a search in the keystone.conf file and found the "Ri" in the mysql connection password following a "$". Although the password was enclosed in single quotes because there were special characters in the password, the "$Ri" in the password was apparently being interpreted as a variable option which caused the error. Changing the password resolved the error.

Once the above error was resolved, a MySQL authentication error occurred, "Access denied for user 'keystone'@'controller' (using password: Yes)." Resolved this issue by removing the single quotes that enclosed the password in the "connection = mysql://keystone:DB_PASS@controller/keystone" entry in the keystone.conf file. When the single quotes were removed from enclosing the password, "keystone_manage db_sync keystone" ran successfully and populated the keystone database.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-07-14 09:34:47 -0500

Seen: 255 times

Last updated: Jul 15 '15