Project

General

Profile

Bug #21400

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

Added by Abhishek Lekshmanan 3 months ago. Updated 3 months ago.

Status:
Pending Backport
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:
Release:
Needs Doc:
No

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 In Progress

History

#1 Updated by Abhishek Lekshmanan 3 months ago

  • Backport set to luminous

#3 Updated by Yuri Weinstein 3 months ago

Abhishek Lekshmanan wrote:

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

merged

#4 Updated by Abhishek Lekshmanan 3 months ago

  • Status changed from New to Pending Backport

#5 Updated by Nathan Cutler 2 months ago

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

Also available in: Atom PDF