yahoo-eng-team team mailing list archive

[OpenStack Infra <1654183@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/419441
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=9940e3fe0e47ff5f2f6d05c9564d17fc19ca0f5c
Submitter: Jenkins
Branch:    master

commit 9940e3fe0e47ff5f2f6d05c9564d17fc19ca0f5c
Author: Istvan Imre <istvan.imre@xxxxxxxxx>
Date:   Thu Jan 12 13:18:25 2017 +0100

    Pass relevant parameters to Token based authentication
    
    In case of token authentication is used pass relevant parameters
    to Token authenticator.
    
    Co-Authored-By: Andrey Kurilin <andr.kurilin@xxxxxxxxx>
    Change-Id: I9a04d89016a834fe96f1b77e91011f7fa4fdda51
    Closes-Bug: #1654183


** Changed in: python-novaclient
       Status: In Progress => Fix Released

-- 
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/1654183

Title:
  Token based authentication in Client class does not work

Status in OpenStack Dashboard (Horizon):
  New
Status in python-novaclient:
  Fix Released
Status in tripleo:
  Triaged
Status in OpenStack DBaaS (Trove):
  New

Bug description:
  With newly released novaclient (7.0.0) it seems that token base
  authentication does not work in novaclient.client.Clinet.

  I have get back the following response from Nova server:

  Malformed request URL: URL's project_id
  'e0beb44615f34d54b8a9a9203a3e5a1c' doesn't match Context's project_id
  'None' (HTTP 400)

  I just created the Nova client in following way:
  Client(
      2,
      endpoint_type="public",
      service_type='compute',
      auth_token=auth_token,
      tenant_id="devel",
      region_name="RegionOne",
      auth_url=keystone_url,
      insecure=True,
      endpoint_override=nova_endpoint #https://.../v2/e0beb44615f34d54b8a9a9203a3e5a1c
  )

  After it nova client performs a new token based authentication without
  project_id (tenant_id) and it causes that the new token does not
  belong to any project. Anyway if we have a token already why
  novaclient requests a new one from keystone? (Other clients like Heat
  and Neutron for example does not requests any token from keystone if
  it is already provided for client class)

  The bug is introduced by follwoig commit:
  https://github.com/openstack/python-novaclient/commit/8409e006c5f362922baae9470f14c12e0443dd70

  +        if not auth and auth_token:
  +            auth = identity.Token(auth_url=auth_url,
  +                                  token=auth_token)

  When project_id is also passed into Token authentication than
  everything works fine. So newly requested token belongs to right
  project/tenant.

  Note: Originally this problem appears in Mistral project of OpenStack,
  which is using the client classes directly from their actions with
  token based authentication.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1654183/+subscriptions