254100128d
Keystone was logging a warning saying "no configuration file was found" when one was clearly passed to keystone-manage. This was due to the fact that keystone-manage was really just checking for default configuration file values. This means that users passing a specific configuration file location to keystone-manage would see a warning that wasn't necessarily true since keystone-manage passes sys.argv to oslo.config, which resolves the argument properly. This change enhances the check to make sure keystone-manage isn't dealing with a configuration file passed in from an end-user before emitting the warning. This change also cleans up some of the interactions between keystone.cmd.manage and keystone.cmd.cli to make the variables more clear about their purpose. Change-Id: I6d58d9c499c447ef1cfd6edd4aeb1176130fb6ad Closes-Bug: 1782704
8 lines
259 B
YAML
8 lines
259 B
YAML
---
|
|
fixes:
|
|
- |
|
|
[`bug 1782704 <https://bugs.launchpad.net/keystone/+bug/1782704>`_]
|
|
Checking for non-existant configuration files is more robust to ensure
|
|
proper logging to users when passing configuration information to
|
|
``keystone-manage``.
|