Actions
Bug #42810
closedceph config rm does not revert debug_mon to default
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When we increase the debug_mon level to 10, then rm the setting, the effective log level is stuck at 10 in the ceph-mon log file.
1. Log level is 1/5 by default.
2. We increase the log level to 10, and the log file correctly:
# ceph config set mon.`hostname -s` debug_mon 10 # ceph daemon mon.`hostname -s` config get debug_mon { "debug_mon": "10/10" } # tail -n1 /var/log/ceph/ceph-mon.cepherin-mon-7cb9b591e1.log 2019-11-14 11:02:29.589 7f8940003700 10 mon.xxx@0(leader).mgr e1305 no change
3. Now we rm this custom config, which seems to be seen by the mon, but the log level doesn't change:
# ceph config rm mon.`hostname -s` debug_mon # ceph daemon mon.`hostname -s` config get debug_mon { "debug_mon": "1/5" } # tail -n1 /var/log/ceph/ceph-mon.cepherin-mon-7cb9b591e1.log 2019-11-14 11:03:46.457 7f8940003700 10 mon.xxx@0(leader) e19 reset/close on session unknown.0
For some reason the mon is not noticing this config change back to the default.
Thanks!
Updated by Neha Ojha over 4 years ago
- Is duplicate of Bug #42964: monitor config store: Deleting logging config settings does not decrease log level added
Updated by Nathan Cutler about 4 years ago
- Status changed from New to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions