← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1075541] Re: quantum command fails with Unauthorized 401 when keystone token_format is PKI

 

Andrew- it sounds like you're describing the issue being fixed here
https://review.openstack.org/#/c/33851/ (for bug 1235252)

** Changed in: keystone
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1075541

Title:
  quantum command fails with Unauthorized 401 when keystone token_format
  is PKI

Status in OpenStack Identity (Keystone):
  Invalid
Status in OpenStack Neutron (virtual network service):
  Invalid
Status in Python client library for Keystone:
  Invalid

Bug description:
  When I run devstack master branch with KEYSTONE_TOKEN_FORMAT=PKI, quantum command fails with 401 Unauthorized.
  -----
  ubuntu@ostack05:~/devstack (master)$ quantum net-list
  401 Unauthorized

  This server could not verify that you are authorized to access the
  document you requested. Either you supplied the wrong credentials
  (e.g., bad password), or your browser does not understand how to
  supply the credentials required.

   Authentication required
  ----- 

  The log of quantum server is http://paste.openstack.org/show/24588/
  Note that I replaced all LOG.debug() in keystone/middleware/auth_token.py to LOG.info().

  If I set KEYSTONE_TOKEN_FORMAT to UUID, devstack works successfully.

  Does anyone experience it? is it only for me?

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