Project

General

Profile

Actions
Copy link

Bug #21400

closed

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

Added by Abhishek Lekshmanan over 6 years ago. Updated about 6 years ago.

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

Related issues 1 (0 open — 1 closed)

Copied to rgw - Backport #21651: luminous: rgw: avoid logging keystone revocation failures when no keystone is configuredResolvedAbhishek LekshmananActions
Actions
Copy link
 #1

Updated by Abhishek Lekshmanan over 6 years ago

  • Backport set to luminous
Actions
Copy link
 #3

Updated by Yuri Weinstein over 6 years ago

Abhishek Lekshmanan wrote:

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

merged

Actions
Copy link
 #4

Updated by Abhishek Lekshmanan over 6 years ago

  • Status changed from New to Pending Backport
Actions
Copy link
 #5

Updated by Nathan Cutler over 6 years ago

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

Updated by Nathan Cutler about 6 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF