Project

General

Profile

Bug #21400

rgw: avoid logging keystone revocation failures when no keystone is configured

Added by Abhishek Lekshmanan about 1 year ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
09/15/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

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

Related issues

Copied to rgw - Backport #21651: luminous: rgw: avoid logging keystone revocation failures when no keystone is configured Resolved

History

#1 Updated by Abhishek Lekshmanan about 1 year ago

  • Backport set to luminous

#3 Updated by Yuri Weinstein about 1 year ago

Abhishek Lekshmanan wrote:

master pr: https://github.com/ceph/ceph/pull/17775

merged

#4 Updated by Abhishek Lekshmanan about 1 year ago

  • Status changed from New to Pending Backport

#5 Updated by Nathan Cutler about 1 year ago

  • Copied to Backport #21651: luminous: rgw: avoid logging keystone revocation failures when no keystone is configured added

#6 Updated by Nathan Cutler 8 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF