Actions
Bug #22341
closedceph tell mon.* prints non-tell <command> [options] for invalid commands
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
$ ./bin/ceph tell mon.c aoeu
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
2017-12-07 04:52:12.345 7ffbd8f7c700 -1 WARNING: all dangerous and experimental features are enabled.
2017-12-07 04:52:12.353 7ffbd8f7c700 -1 WARNING: all dangerous and experimental features are enabled.
no valid command found; 10 closest matches:
mon add <name> <IPaddr[:port]>
mon remove <name>
mon stat
mon getmap {<int[0-]>}
fs set-default <fs_name>
mon dump {<int[0-]>}
fs rm_data_pool <fs_name> <pool>
fs set_default <fs_name>
fs flag set enable_multiple <val> {--yes-i-really-mean-it}
fs add_data_pool <fs_name> <pool>
Error EINVAL: invalid command
Updated by Joao Eduardo Luis over 6 years ago
what is the behavior you were expecting?
Updated by Joao Eduardo Luis over 6 years ago
- Status changed from New to Rejected
After talking to Jos Collin on IRC, I realized this ticket results from Jos' misinterpretation of what are monitor commands and what are 'tell commands'. In this case, Jos was expecting 'tell' commands to be a specific set of commands that are not the monitor's default commands.
While I understand how this could be misunderstood, this is not a bug. If anything, we should make the ceph tool's output better in case of an invalid command, something a bit more obvious; or to better document the tell behavior. That should be another ticket though.
Actions