Actions
Bug #48489
openosdmap cluster-only data is interpreted by the userspace client and causes crashes if it can't
Status:
New
Priority:
High
Assignee:
-
Category:
Dev Interfaces
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
OSD
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
We have a cluster-only portion of the OSDMap, which is carefully encoded separately from the portion which clients need to understand.
Unfortunately, the userspace client still tries to decode it, and throws errors if the compatv value prevents the client from doing so. That's because we have a single OSDMap encode/decode implementation (of course!), and there's nothing in it that knows whether it needs to read the cluster-only state or not.
This is deeply unfortunate since it means, any time we go through an incompatible cluster map change, or add data which we require the OSDs to understand, the userspace clients also have to be upgraded to keep being clients of the cluster.
No data to display
Actions