Bug #22151: rgw: log keystone errors at a higher level - rgw - Ceph

Actions

Copy link

Bug #22151

closed

rgw: log keystone errors at a higher level

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

Status:

Resolved

Priority:

Normal

Assignee:

Target version:

% Done:

Source:

Tags:

Backport:

luminous

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

A misconfigured keystone is not immediately obvious as even at level 5 we just log failed auth strategy, -1 which isn't easy to track down. Log the error response from keystone at level 5 as well so that it is easier to debug misconfigurations.

2017-11-17 14:57:34.245 7f842d03c700  1 ====== starting new request req=0x7f842d035b70 =====
2017-11-17 14:57:34.245 7f842d03c700  2 req 1:0.000062::HEAD /swift/v1::initializing for trans_id = tx000000000000000000001-005a0eeace-1145-default
2017-11-17 14:57:34.245 7f842d03c700  2 req 1:0.000150:swift:HEAD /swift/v1::getting op 3
2017-11-17 14:57:34.245 7f842d03c700  2 req 1:0.000169:swift:HEAD /swift/v1:stat_account:verifying requester
2017-11-17 14:57:34.249 7f842d03c700  5 Failed the auth strategy, reason=-1
2017-11-17 14:57:34.253 7f842d03c700  2 req 1:0.006667:swift:HEAD /swift/v1:stat_account:op status=0
2017-11-17 14:57:34.253 7f842d03c700  2 req 1:0.006673:swift:HEAD /swift/v1:stat_account:http status=401
2017-11-17 14:57:34.253 7f842d03c700  1 ====== req done req=0x7f842d035b70 op status=0 http_status=401 ====

Related issues 1 (0 open — 1 closed)