Keystone should provide more verbose messages in case of 401 and 403 errors
Bug #1625120 reported by
Timur Nurlygayanov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
David Stanek |
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.
Changed in keystone: | |
assignee: | nobody → Alexander Makarov (amakarov) |
Changed in keystone: | |
assignee: | Alexander Makarov (amakarov) → Steve Martinelli (stevemar) |
Changed in keystone: | |
assignee: | Steve Martinelli (stevemar) → Dave Chen (wei-d-chen) |
Changed in keystone: | |
assignee: | Dave Chen (wei-d-chen) → Alexander Makarov (amakarov) |
Changed in keystone: | |
milestone: | none → ocata-2 |
Changed in keystone: | |
assignee: | Alexander Makarov (amakarov) → David Stanek (dstanek) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/372433
Review: https:/