This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
verified for python-keystoneclient-0.9.0-8.el6ost.noarch: - As noted by Jason, the backport has landed and, according to the customer that patched the environment, it is working for them. Below is a general checking of the ec2 signature method (the one affected): - Implemented a script to generate a signature: ... credentials = {'host': 'iam.amazonaws.com', 'verb': 'POST', 'path': '/', 'params': params, 'headers': headers, 'body_hash': body_hash} signature = signer.generate(credentials) print '========= SIGNATURE =========' print signature - The signature is equal to what is expected (ced6826de92d2bdeed8f846f0bf508e8559e98e4b0199114b84c54174deb456c): ========= SIGNATURE ========= ced6826de92d2bdeed8f846f0bf508e8559e98e4b0199114b84c54174deb456c - Changed the method to 'GET' so the params are included in the signature: ========= SIGNATURE ========= 3aebad39d75a1302a190a5a5bb0232803f4ded7b70c5e56de55f14f4641d9ad0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0166.html