Option "user-name" does not set username option properly

[Dr. Jens Harbott]

When using a config like this in some service application like nova or heat

[keystone_authtoken]
username = user

I am getting this deprecation warning:

2016-03-03 09:47:25.520 20513 WARNING oslo_config.cfg [-] Option "username" from group "keystone_authtoken" is deprecated. Use option "user-name" from group "keystone_authtoken".

Now if I change my config to use "user-name" instead, the value doesn't get set properly, the result is:

2016-03-03 09:46:41.229 20250 DEBUG oslo_service.service [-] keystone_authtoken.username = None log_opt_values /usr/lib/python2.7/dist-packages/oslo_config/cfg.py:2233

and obviously authentication fails for that service afterwards.

[Dr. Jens Harbott (j-harbott)]

Hmm, seems like this is obsoleted now by https://bugs.launchpad.net/python-keystoneclient/+bug/1498247 . Also not clear whether the bug is in oslo.config or in the way that it is used by python-keystoneclient.

It still might be useful if one could get the now deprecated option "user-name" to at least work as it should.

[Dr. Jens Harbott (j-harbott)]

O.k., after looking a bit more, it turns out that the option parsing in nova is handled by the keystoneauth library instead of keystoneclient. And keystoneauth still has the deprecation policy the other way around, so I'm going to propose a patch there to bring the two into sync again.

[Colleen Murphy (krinkle)]

This was fixed in https://review.openstack.org/#/c/287754/ so this bug can probably be closed.