Having a relative path for api_extensions_path no longer seems to work
Bug #1301660 reported by
Nikhil Manchanda
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Low
|
Shuichiro MAKIGAKI |
Bug Description
Having api_extensions_path = trove/extension
Giving it a full path still works.
Changed in trove: | |
importance: | Undecided → Low |
Changed in trove: | |
assignee: | nobody → Shuichiro MAKIGAKI (shuichiro-makigaki) |
Changed in trove: | |
milestone: | none → juno-2 |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
It took me ages to find that this was causing breakage. A typical symptom is:
$ trove list ------- ------- ------- ------- ----+-- ----+-- ------+ ------- ----+-- ----+ ------- ------- ------- ------- ----+-- ----+-- ------+ ------- ----+-- ----+ 6078-49cd- bc90-0d5a8847b6 ce | db0 | ACTIVE | 2 | 2 | ------- ------- ------- ------- ----+-- ----+-- ------+ ------- ----+-- ----+
+------
| id | name | status | flavor_id | size |
+------
| 5c1e2f20-
+------
$ trove database-list 5c1e2f20- 6078-49cd- bc90-0d5a8847b6 ce
ERROR: The resource could not be found.
i.e spome api calls failing. The cause being (of course) that no extensions have loaded.