Project

General

Profile

Bug #39662

ceph-mgr should log an error if it can't find any modules to load

Added by Tim Serong almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
ceph-mgr
Target version:
-
% Done:

0%

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

Description

I had a downstream SUSE build of ceph-14.1.0, which was showing "7 mgr modules have failed" in `ceph status`, and `ceph mgr dump` showed "available_modules": [] (i.e. an empty list). The 7 failed modules were of course the always-on modules. I eventually figured out that mgr_module_path was somehow set to /usr/local/share/ceph/mgr in that build, but the modules were actually correctly installed in /usr/share/ceph/mgr, so mgr couldn't find them. We should log the path we're loading modules from, and log an error if none are found, so that if mgr_module_path is ever set incorrectly in future, the problem will be obvious.


Related issues

Copied to mgr - Backport #40090: nautilus: ceph-mgr should log an error if it can't find any modules to load Resolved

History

#1 Updated by Tim Serong almost 5 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 28055

#2 Updated by Nathan Cutler almost 5 years ago

  • Backport set to nautilus

#3 Updated by Kefu Chai almost 5 years ago

  • Status changed from Fix Under Review to Pending Backport

#4 Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40090: nautilus: ceph-mgr should log an error if it can't find any modules to load added

#5 Updated by Nathan Cutler almost 5 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF