Public bug reported:
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).
** Affects: horizon
Importance: Undecided
Assignee: Vincent Untz (vuntz)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1602624
Title:
Horizon doesn't use keystone v3-enabled neutronclient
Status in OpenStack Dashboard (Horizon):
In Progress
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).
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1602624/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
