Red Hat Bugzilla – Bug 984752
Fix AWS version 4 signature management
Last modified: 2016-01-04 10:01:18 EST
Description of problem:
I'm looking to update python-boto in EPEL 6 to a reasonably current version, but the version of python-keystoneclient there is coded against a bug in boto's signature version 4 code that was fixed in version 2.9.3. Upstream recently committed a patch  for this; would you mind adding that to EPEL's python-keystoneclient package so we can add that to the update ?
Can you think of any other openstack components that this change might also affect?
Version-Release number of selected component (if applicable):
If I'm not mistaken, version 4 signature support was added by  which isn't present in 0.2.0.
However, RDO keystoneclient will be affected. After a discussion, Steven Hardy will propose a transitional hack to allow usage of both boto versions. So if possible, please wait with the update until this patch is accepted/rejected.
I'll post more information here on how's it proceeding.
Patch proposed, waiting for reviews.
python-keystoneclient-0.2.3-7.fc19 has been submitted as an update for Fedora 19.
Folsom in EPEL 6 isn't affected.
I backported Steven's transitional patch everywhere else (grizzly, havana @ Fedora and RDO) to prevent future problems.
python-keystoneclient-0.2.3-7.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.