Bug 1624646

Summary: "challenging authorizer" messenger debug messages spill into log at level 0
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Patrick Donnelly <pdonnell>
Component: RADOSAssignee: Patrick Donnelly <pdonnell>
Status: CLOSED ERRATA QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: low Docs Contact: Bara Ancincova <bancinco>
Priority: medium    
Version: 3.0CC: ceph-eng-bugs, dzafman, hnallurv, kchai, mmuir, nojha, pdonnell, tserlin
Target Milestone: z1Keywords: CodeChange
Target Release: 3.1   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.5-46.el7cp Ubuntu: ceph_12.2.5-31redhat1 Doc Type: Bug Fix
Doc Text:
.Fixed verbosity for a log message Ceph message passing stack had a message with low verbosity set unnecessarily. Consequently, debug log at low verbosity filled with inconsequential message. This update fixes the verbosity, and low debug logs no longer include the message.
Story Points: ---
Clone Of:
: 1665591 (view as bug list) Environment:
Last Closed: 2018-11-09 00:59:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1584264    

Description Patrick Donnelly 2018-09-02 19:48:52 UTC
Description of problem:

debug messages for normal events via the messenger appear at level 0:

e.g.

> 2018-08-31 08:18:33.868483 7f620bb9c700  0 -- 10.0XXX:6800/4163310420 >> 10.64.0.9:0/2176811386 conn(0xf00 :6800 s=STATE_ACCEPTING_WAIT_CONNECT_MSG_AUTH pgs=0 cs=0 l=0).handle_connect_msg: challenging authorizer

Messages was introduced by 5ead97120e07054d80623dada90a5cc764c28468 in Luminous.

This should be reproducible with "debug ms = 0/5" during normal cluster operation.

Comment 14 errata-xmlrpc 2018-11-09 00:59:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3530