Horizon doesn't use keystone v3-enabled neutronclient

Bug #1602624 reported by Vincent Untz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Confirmed
Low
Unassigned

Bug Description

The neutron client is built without passing a keystone session object, which results in neutronclient using its internal HTTPClient, and that one is not compatible with Keystone v3. The bad thing is that the auth URL that we pass is a v3 URL, so neutronclient may try to do v2.0 calls on the v3 endpoint.

This was noticed when neutronclient had to authenticate (which is usually not the case from horizon, since we have the token).

Tags: neutron
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

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

Changed in horizon:
assignee: nobody → Vincent Untz (vuntz)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Rob Cresswell (<email address hidden>) on branch: master
Review: https://review.openstack.org/341430
Reason: Due to inactivity

Akihiro Motoki (amotoki)
tags: added: neutron
Changed in horizon:
assignee: Vincent Untz (vuntz) → nobody
status: In Progress → New
Ivan Kolodyazhny (e0ne)
Changed in horizon:
status: New → Confirmed
importance: Undecided → Low
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.