Bug #51309
open'weight' property inconsistent between 'ceph report' crushmap and other ceph tooling
0%
Description
I am comparing the following for my 4 node testcluster:
ceph osd df: osd.0 has weight 1.0000
ceph report (key 'osd'): osd.0 has weight 1.0000
ceph report (key 'crushmap'):
"items": [
{
"id": 0, (This is osd.0)
"weight": 65536, => different from other tooling
"pos": 0
}
ceph osd dump: osd.0 has weight 1
crushmap.txt (ceph osd getcrushmap ... crushtool -d) osd.0 has weight 1
crushmap.json (ceph osd crush dump >crushdump.json) osd.0 has weight 65536
Other OSDs with weight 2 have 131072 in ceph report and the JSON crushmap
If I set weight 0.9 for osd.0 I get 58982 as the value in ceph_report and the JSON crushmap.
Same goes for all the other hierarchy layers (in my case host, pod, root)
Expectation: The weight of an OSD (and all the hierarchy layers above it should be consistent across all tooling and consistent with the actual value set by ceph osd crush reweight <osd> <weight>
As Ceph report is supposed to be the universal source of truth of all the cluster parameters the fact that it shows an entirely different value for weight for each component than the manually value and that the json and text versions of the crushmap differ in this property qualifies this as a major bug in my opinion.
The observation is from the current Ubuntu stable LTS version 20.04.2 with Ceph 15.2.11
No data to display