Keystone client fails to authorize during trust creation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Blazar |
Fix Released
|
Critical
|
Pablo Andres Fuente |
Bug Description
The current Keystone client for the V3 API fails to authorize during a trust creation.
2014-06-02 11:50:39.233 19207 ERROR climate.
File "/opt/stack/
return func(**kwargs)
File "/opt/stack/
return api_utils.
File "/opt/stack/
return getattr(
File "/opt/stack/
return func(self, *args, **kwargs)
File "/opt/stack/
trust = create_trust()
File "/opt/stack/
client = keystone.
File "/opt/stack/
self.
File "/opt/stack/
return func(*args, **kwargs)
File "/opt/stack/
resp = self.get_
File "/opt/stack/
'%s' % e)
AuthorizationFa
After checking the Keystone code, I found that the HTTPClient class is not storing internally the auth_url received during initialization (https:/
I'm on Keystone IRC trying to determine if this is a Keystone bug or we are using incorrectly the client.
As a quick patch, is possible to resend the auth_url as a parameter of the authenticate() method (https:/
Changed in blazar: | |
status: | Triaged → In Progress |
Changed in blazar: | |
milestone: | none → 0.1.1 |
Changed in blazar: | |
status: | Fix Committed → Fix Released |
Reviewed: https:/ /review. openstack. org/97565 /git.openstack. org/cgit/ stackforge/ blazar/ commit/ ?id=eec7f456b45 f222db296f2f29c e23309358decff
Committed: https:/
Submitter: Jenkins
Branch: master
commit eec7f456b45f222 db296f2f29ce233 09358decff
Author: Pablo Andres Fuente <email address hidden>
Date: Tue Jun 3 14:15:16 2014 -0300
Passing auth_url to keystoneclient. authenticate
During the creation of a trust, our Keystone client implementation calls
the authenticate method which fails due to the auth_url parameter is
missing. Seems that the current V3 Kestone client isn't honoring the auth_url
passed during initialization.
If you call the authenticate method without passing the auth_url
parameter, the authentication fails because that parameter was not
properly set, but should work because that parameter is passed during
initialization.
This commit tries to fix the issue until a patch from Keystone lands to
master.
Change-Id: Id242dcac31fe53 5836033dff95184 4a66bcc2100
Closes-Bug: #1326066