python-keystone 2012.1+stable~20120824-a16a0ab9-0ubuntu2.4 improperly pulled in patch from upstream
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keystone (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Precise |
Invalid
|
Undecided
|
Jamie Strandboge |
Bug Description
The configuration option is missing in: /usr/lib/
This leads to a completely broken keystone:
(root): 2013-02-06 23:24:43,480 ERROR no such option: max_param_size
Traceback (most recent call last):
File "/usr/lib/
result = method(context, **params)
File "/usr/lib/
if len(username) > CONF.max_
File "/usr/lib/
return self._substitut
File "/usr/lib/
info = self._get_
File "/usr/lib/
raise NoSuchOptError(
NoSuchOptError: no such option: max_param_size
Changed in keystone (Ubuntu): | |
status: | New → Invalid |
Changed in keystone (Ubuntu Precise): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in keystone (Ubuntu Precise): | |
status: | Incomplete → Invalid |
I am not seeing this: stable~ 20120824- a16a0ab9- 0ubuntu2. 4 OpenStack identity service - Python library
$ dpkg -l|grep python-keystone
ii python-keystone 2012.1+
$ grep max_param_size /usr/lib/ python2. 7/dist- packages/ keystone/ config. py int('max_ param_size' , default=64)
register_
In testing I also tried authenticating the with no changes to /etc/keystone/ keystone. conf: -+----- ------- ------- ------- ------- ------- ------- --+ -+----- ------- ------- ------- ------- ------- ------- --+ d2:c1:3f: 8b:c0:e6: 3f:de:cd: 48:8d:fe: 08 | -+----- ------- ------- ------- ------- ------- ------- --+
$ nova keypair-list
+------
| Name | Fingerprint |
+------
| mykey | ad:4f:2a:
+------
and also with using in the [DEFAULTS] section of /etc/keystone/ keystone. conf (and restarting keystone):
max_param_size = 4
$ nova keypair-list
ERROR: Request attribute username must be less than or equal to 4. The server could not comply with the request because the attribute size is invalid (too large). The client is assumed to be in error. (HTTP 400)
Can you provide the exact steps on how to reproduce along with your /etc/keystone/ keystone. conf (redacting any passwords or otherwise sensitive information)?