Bug 1624646 - "challenging authorizer" messenger debug messages spill into log at level 0
Summary: "challenging authorizer" messenger debug messages spill into log at level 0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 3.0
Hardware: All
OS: All
medium
low
Target Milestone: z1
: 3.1
Assignee: Patrick Donnelly
QA Contact: ceph-qe-bugs
Bara Ancincova
URL:
Whiteboard:
Depends On:
Blocks: 1584264
TreeView+ depends on / blocked
 
Reported: 2018-09-02 19:48 UTC by Patrick Donnelly
Modified: 2021-12-10 17:26 UTC (History)
8 users (show)

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.
Clone Of:
: 1665591 (view as bug list)
Environment:
Last Closed: 2018-11-09 00:59:32 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 35251 0 None None None 2018-09-02 19:52:45 UTC
Red Hat Issue Tracker RHCEPH-2700 0 None None None 2021-12-10 17:26:57 UTC
Red Hat Product Errata RHBA-2018:3530 0 None None None 2018-11-09 01:00:29 UTC

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


Note You need to log in before you can comment on or make changes to this bug.