Actions
Bug #4639
closedOSD class load failure log should be on by default and as noticeable as possible
Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Too many people have gotten rbd failures because of some damage to /usr/lib/rados-classes in
their installation: they installed from their own build and didn't get the right symlink, or
they got a damaged package from somewhere, or something similar. Seeing that failure involves
osd debug level 20 and it's well-buried in other verbosity from the OSD.
That class-load failure should be a derr, IMO, and as up-front as possible; we might even want
to modify rbd to suggest the problem when it gets ENOTSUPP on certain operations.
Updated by Dan Mick almost 11 years ago
Just had another IRC user get caught in this trap today.
Updated by Sage Weil almost 11 years ago
- Status changed from New to Resolved
Actions