yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #58944
[Bug 1625120] Re: Keystone should provide more verbose messages in case of 401 and 403 errors
Reviewed: https://review.openstack.org/372433
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5ae4ca12a75f7463623293944d5136fe36020ab4
Submitter: Jenkins
Branch: master
commit 5ae4ca12a75f7463623293944d5136fe36020ab4
Author: Alexander Makarov <amakarov@xxxxxxxxxxxx>
Date: Mon Sep 19 15:01:31 2016 +0300
Verbose 401/403 debug responses
Add text to raised Unauthorized and Forbidden exception to show the client
what happened.
Change-Id: Id5de16d446cf4fdacfefdad0523e84821e4fd72c
Closes-Bug: 1625120
** Changed in: keystone
Status: In Progress => Fix Released
--
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):
Fix Released
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
References