Comment 1 for bug 966319

It appears that the package you are using is dated March 16, 2012, and this was fixed in bug 942793 on March 20, 2012.

For sanity, I attempted to reproduce on master in the following scenarios and it appears to behave as expected:

- Loading keystone-all both from the environment or relative to cwd works
- Both --config/--config-file appear to override the chosen config successfully
- Both having/missing an existing keystone.conf's on an expected paths (/etc/keystone) behaves as expected