Project

General

Profile

Bug #44627

mgr/dashboard: Config option 'log_level' is not in Module.MODULE_OPTIONS

Added by Ernesto Puerta 8 months ago. Updated 8 months ago.

Status:
Can't reproduce
Priority:
Immediate
Category:
dashboard/backend
Target version:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
1 - critical
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

In master (and Octopus), the following exception appears when booting ceph-mgr:

2020-03-16T17:02:12.313+0000 7fdc97340700 -1 mgr load Traceback (most recent call last):
  File "/ceph/src/pybind/mgr/crash/module.py", line 37, in __init__
    super(Module, self).__init__(*args, **kwargs)
  File "/ceph/src/pybind/mgr/mgr_module.py", line 723, in __init__
    log_level = self.get_module_option("log_level")
  File "/ceph/src/pybind/mgr/mgr_module.py", line 1216, in get_module_option
    self._validate_module_option(key)
  File "/ceph/src/pybind/mgr/mgr_module.py", line 1198, in _validate_module_option
    format(key, self.__class__.__name__))
RuntimeError: Config option 'log_level' is not in Module.MODULE_OPTIONS

This is caused by a recent refactoring, which moved the logging options definition out of the initializer function of the MgrModule class, so now they happen after they are first [tried to be] used.

History

#1 Updated by Ernesto Puerta 8 months ago

  • Description updated (diff)

#2 Updated by Ernesto Puerta 8 months ago

  • Description updated (diff)

#3 Updated by Ernesto Puerta 8 months ago

  • Description updated (diff)
  • Target version changed from v16.0.0 to v15.0.0

#4 Updated by Ernesto Puerta 8 months ago

  • Status changed from In Progress to Can't reproduce

Cannot reproduce. It was an issue caused by running ceph-mgr Python code with RPMs built the previous day (some C++ code changes were missing).

Also available in: Atom PDF