The problem here is really that keystone puts required default values in the config file and not in the code
My cfg re-factoring patches fixed this e.g. in https://review.openstack.org/#/c/4551/10/keystone/catalog/backends/templated.py I register a default in the code for template_file. Since we're likely not going ahead with those patches, I can pull out the defaults cleanups separately If the service can't start without a value for the config, then the option is essentially required. The user must specify a value. I don't think any of keystone options fall into that category, but I've added a blueprint for required options in cfg: https://blueprints.launchpad.net /openstack-common/+spec/cfg-required-options ** Changed in: openstack-common Status: In Progress => Invalid -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/983734 Title: Keystone fails badly if you miss one option Status in OpenStack Identity (Keystone): Confirmed Status in openstack-common: Invalid Bug description: If you misspell or forget one option in keystone.conf (like template_file for TemplatedCatalog backend), Keystone will fail with misguiding critical failure (in my case, "TypeError: coercing to Unicode: need string or buffer, NoneType found"). To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/983734/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
