keystone-manage looks for default_config_files in the wrong place
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Colleen Murphy | ||
Mitaka |
Fix Released
|
Medium
|
Colleen Murphy | ||
Newton |
Fix Released
|
Medium
|
Colleen Murphy |
Bug Description
Summary:
The keystone-manage command searches for a default keystone.conf relative to the installed executable [1]. The result is that it will look in <venv name>/.
I can't find documentation stating keystone.conf should live at <venv name>/.
Steps to reproduce:
1) Follow the "Developing with Keystone" instructions (http://
2) Change the database connection string in etc/keystone.conf to sqlite:
3) Run a keystone-manage db_sync
Expected result:
A sqlite database is created in the current working directory called keystone2.db
Actual result:
A sqlite database is created in the current working directory called keystone.db.
[1] http://
[2] http://
[3] http://
Changed in keystone: | |
assignee: | nobody → Colleen Murphy (krinkle) |
status: | New → In Progress |
added to RC, as this seems like a small (but very useful) fix if we can squeeze it into mitaka