Comment 2 for bug 1269789

ZhiQiang Fan: I agree with the general notion, but if you dig into the details of this behavior, it's far from expected.

At minimum, it's poor user feedback. When using the templated backend, two "catalogs" are stored in memory-- one that supports basic read/write, and one that is actually used to build the token catalog. Looking at the implementation, I think the templated catalog should be loaded into the KVS backend, and the KVS backend should be used to render the catalog.

Unfortunately, the scope of effort required to "fix" this wanders into blueprint / new features territory so I don't think it would be backportable to havana. "Fixing" this may also be dependent on https://blueprints.launchpad.net/keystone/+spec/dogpile-kvs-backends (which is re-writing the KVS driver).