Horizon doesn't use keystone v3-enabled neutronclient
Bug #1602624 reported by
Vincent Untz
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).
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to horizon (master) | #1 |
| 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) | #2 |
| tags: | added: neutron |
| Changed in horizon: | |
| assignee: | Vincent Untz (vuntz) → nobody |
| status: | In Progress → New |
| Changed in horizon: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/