Actions
Bug #46816
closedmon stat prints plain text with -f json
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Administration/Usability
Target version:
-
% Done:
0%
Source:
Community (dev)
Tags:
low-hanging-fruit
Backport:
octopus, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Monitor
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
master:~ # ceph mon stat
e1: 3 mons at {node1=[v2:192.168.100.16:3300/0,v1:192.168.100.16:6789/0],node2=[v2:192.168.100.71:3300/0,v1:192.168.100.71:6789/0],node3=[v2:192.168.100.206:3300/0,v1:192.168.100.206:6789/0]}, election epoch 12, leader 0 node1, quorum 0,1,2 node1,node2,node3
master:~ # ceph mon stat -f json
e1: 3 mons at {node1=[v2:192.168.100.16:3300/0,v1:192.168.100.16:6789/0],node2=[v2:192.168.100.71:3300/0,v1:192.168.100.71:6789/0],node3=[v2:192.168.100.206:3300/0,v1:192.168.100.206:6789/0]}, election epoch 12, leader 0 node1, quorum 0,1,2 node1,node2,node3
I guess the stat output doesn't have a json formatter yet. At least this should return valid json (maybe just {}) in order to not break tools that expect json.
Updated by Joao Eduardo Luis over 3 years ago
- Category set to Administration/Usability
- Status changed from New to Triaged
- Assignee set to Joao Eduardo Luis
- Source set to Community (dev)
- Tags set to low-hanging-fruit
- Component(RADOS) Monitor added
Updated by Joao Eduardo Luis over 3 years ago
- Pull request ID set to 37635
Updated by Nathan Cutler over 3 years ago
- Status changed from Triaged to Fix Under Review
Updated by Kefu Chai over 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47898: octopus: mon stat prints plain text with -f json added
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47899: nautilus: mon stat prints plain text with -f json added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions