Ensure that keystone can accept alternate config files
Bug #928565 reported by
Anthony Young
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
It seems that keystone-all is coded such that if a config file is present at keystone/
| Changed in keystone: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Joseph Heck (heckj) wrote | #1 |
| Changed in keystone: | |
| milestone: | none → essex-4 |
| Changed in keystone: | |
| status: | Fix Committed → Fix Released |
| Changed in keystone: | |
| milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Hey tony,
With the master using the openstack-common cfg.py, it uses the same CLI config mechanism as the rest of openstack - if this is still a valid concern, should this bug be aimed at the openstack-common project?
It also takes a --config-file option, which allows the specification of a specific config file, so I think we're squared away on this. If you disagree, please holler.