Project

General

Profile

Actions

Bug #57093

open

garbage in log line upon authentication failure w/ rgw_s3_auth_use_keystone enabled.

Added by Marcus Watts over 1 year ago. Updated about 1 year ago.

Status:
Fix Under Review
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When rgw_s3_auth_use_keystone is enabled in the log file, radosgw will try most authenticatoins against keystone. If these authentications fail, if debugging is turned on, an error message like this is produced:

2022-08-09T21:29:26.854-0400 7fbe72d85640 2 req 16539168955438517291 0.542001069s s3:put_obj s3 keystone: token validation ERROR: {"error": {"message": "Could not find credential: f15c16b99f82d8201767d3a841ff40849c8a1b812ffbfd2e393d2b6aa6682a6e.", "code": 404, "title": "Not Found"}}": "Not Found"}}����=ٕ�LjZ�e��Wed, 10 Aug 2022 01:29:26 GMT

The pat after "}}" that looks like binary junk is core garbage, in this case probably including part of a previous log message. This happens because the buffer logic "c_str" does not return a nul terminated C string, and it's necessary to use ".length" find the actual length.

Actions #1

Updated by Marcus Watts over 1 year ago

I have a candidate fix for this here:
https://github.com/ceph/ceph/pull/47546

Actions #2

Updated by Casey Bodley about 1 year ago

  • Status changed from New to Fix Under Review
  • Priority changed from Low to Normal
  • Pull request ID set to 47546
Actions

Also available in: Atom PDF