Comment 1 for bug 2045995

I am not sure what would be the correct way to fix this.

Option 1: revert https://review.opendev.org/c/openstack/keystone/+/834181, change from warning to info for certain events (for example, for all NotFound). This is an easy and quick option. But for me it feels like we are swiping the issue under the rug.

Option 2: catch all those exceptions in keystone code, reraise Unauthorized based on them, or returning a proper response. This feels like a cleaner solution to me. But it feels like boiling an ocean: there are 321 errors in the tempest log alone, and i have a feeling that tempest is not covering 100% of our API, especially all the negative response codes.

I guess a mix of both 1 and 2 should be done?