keystone-all ignores the "--config-file" parameter

[Martin Gerhard Loschwitz]

Hello,

I have these versions of keystone installed:

root@netbook:/usr/lib/ocf/resource.d/openstack# dpkg --list | grep -ir keystone
ii keystone 2012.1~rc1~20120316.2145-0ubuntu1 OpenStack identity service - Daemons
ii python-keystone 2012.1~rc1~20120316.2145-0ubuntu1 OpenStack identity service - Python library
ii python-keystoneclient 2012.1~rc1~20120310.0-0ubuntu1 Client libary for Openstack Keystone API

I'm under the impression that the keystone-all included in these packages ought to support the "--config-file" parameter. However, it doesn't:

root@netbook:/root# keystone-all --config-file /etc/keystone/keystone2.conf
(keystone-all): 2012-03-27 17:24:54,170 DEBUG cfg log_opt_values ********************************************************************************
(keystone-all): 2012-03-27 17:24:54,171 DEBUG cfg log_opt_values Configuration options gathered from:
(keystone-all): 2012-03-27 17:24:54,171 DEBUG cfg log_opt_values command line args: []
(keystone-all): 2012-03-27 17:24:54,171 DEBUG cfg log_opt_values config files: ['/etc/keystone/keystone.conf']
(keystone-all): 2012-03-27 17:24:54,172 DEBUG cfg log_opt_values ================================================================================
(keystone-all): 2012-03-27 17:24:54,172 DEBUG cfg log_opt_values admin_port = 35357
(keystone-all): 2012-03-27 17:24:54,172 DEBUG cfg log_opt_values admin_token = hastexo
(keystone-all): 2012-03-27 17:24:54,173 DEBUG cfg log_opt_values bind_host = 0.0.0.0
(keystone-all): 2012-03-27 17:24:54,173 DEBUG cfg log_opt_values compute_port = 8774
(keystone-all): 2012-03-27 17:24:54,174 DEBUG cfg log_opt_values config_file = ['/etc/keystone/keystone.conf']

Please let me know if I can help to further debug this problem.

Best regards
Martin G. Loschwitz

[Dolph Mathews (dolph)]

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