Comment 18 for bug 1273273

I can reproduce this (on master of keystone, 3.9.0 of oslo.config). However it now manifests itself a bit differently, as I25b717d9616e9d31316441ae3671d2f86229c2bf created an implied connection default of 'sqlite:///keystone.db', so running `keystone-manage db_sync` while keystone.conf is unreadable or absent happily creates a sqlite database in the current working directory.

I don't see the the traceback Sagar sees unless also using the --config-file option with keystone-manage. It seems that oslo.config looks for keystone.conf in certain directories, and if it doesn't find any it returns empty without raising an error (http://git.openstack.org/cgit/openstack/oslo.config/tree/oslo_config/cfg.py#n562)