Keystone client doesn't authenticate correctly and fails back to V2 consequently

Bug #1271959 reported by Sylvain Bauza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blazar
Fix Released
High
Sylvain Bauza
0.1.x
Fix Released
High
Sylvain Bauza

Bug Description

Hi,

With Keystone V3 authentication, if no endpoint provided, it goes look into the service catalog for knowing its management url.
Consequently, if not trust given, we need to provide endpoint value and use authenticate() method

See https://github.com/openstack/heat/blob/master/heat/common/heat_keystoneclient.py#L180 as example

Dina Belova (dbelova)
Changed in climate:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Sylvain Bauza (sylvain-bauza)
milestone: none → 0.1.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to climate (master)

Fix proposed to branch: master
Review: https://review.openstack.org/68666

Changed in climate:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to climate (master)

Reviewed: https://review.openstack.org/68666
Committed: https://git.openstack.org/cgit/stackforge/climate/commit/?id=8593a228b87c521354d0673e422b23ab10308fb8
Submitter: Jenkins
Branch: master

commit 8593a228b87c521354d0673e422b23ab10308fb8
Author: Sylvain Bauza <email address hidden>
Date: Thu Jan 23 16:28:11 2014 +0100

    Fix Authentication problem with Keystone V3

    Endpoint arg was missing when creating a Keystone client, and
    authenticate() method had to be used as it's now lazy authn

    Change-Id: Iaab491a8d7ea43814ac19b245e3dfdd886a978b3
    Closes-Bug: #1271959

Changed in climate:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.