Actions
Bug #21400
closedrgw: avoid logging keystone revocation failures when no keystone is configured
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Even when no keystone is configured, we still log the failures at level 0 for rgw keystone revocation thread which ends up with log messages like
ERROR: keystone revocation processing returned error r=22
Actions