Actions
Bug #8108
closedOSD json output uses strings for booleans
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
OSDMap
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
The output for osd stat using JSON format uses strings for booleans:
{"epoch":4,"num_osds":1,"num_up_osds":1,"num_in_osds":"1","full":"false","nearfull":"false"}
Those should not be strings if the intent is for them to be booleans.
This has the side effect of other tools loading that output and instead of seeing a boolean they interpret the
value as a string which is not correct.
Actions