Public bug reported:

On many our environments we can see 401 and 403 errors during the
execution of Tempest tests, but after the execution of the tests we
can't debug the issue because we don't have any information about 401
errors in keystone logs. In the same time we can have many different
reasons why we got 401 error, and in the case of Tempest we sure that we
use correct credentials.

We need to have an ability to get the information about the reasons of
401/403 errors in Keystone, at least write short human-readable messages
in debug mode, so we will be able to understand the line of code where
the issue happened and try to guess how we can fix it.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1625120

Title:
  Keystone should provide more verbose messages in case of 401 and 403
  errors

Status in OpenStack Identity (keystone):
  New

Bug description:
  On many our environments we can see 401 and 403 errors during the
  execution of Tempest tests, but after the execution of the tests we
  can't debug the issue because we don't have any information about 401
  errors in keystone logs. In the same time we can have many different
  reasons why we got 401 error, and in the case of Tempest we sure that
  we use correct credentials.

  We need to have an ability to get the information about the reasons of
  401/403 errors in Keystone, at least write short human-readable
  messages in debug mode, so we will be able to understand the line of
  code where the issue happened and try to guess how we can fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1625120/+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

Reply via email to