Project

General

Profile

Bug #21406

ceph.in: tell mds does not understand --cluster

Added by Patrick Donnelly over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Category:
Administration/Usability
Target version:
-
Start date:
09/15/2017
Due date:
% Done:

0%

Source:
Q/A
Tags:
Backport:
luminous jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
tools
Labels (FS):
Pull request ID:

Description

$ mv ceph.conf qetest.conf
$ bin/ceph --cluster qetest tell mds.a session ls
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
2017-09-15 15:11:51.778245 7fe18127e700 -1 WARNING: all dangerous and experimental features are enabled.
2017-09-15 15:11:51.805864 7fe18127e700 -1 WARNING: all dangerous and experimental features are enabled.
Traceback (most recent call last):
  File "bin/ceph", line 1121, in <module>
    retval = main()
  File "bin/ceph", line 1041, in main
    prefix='get_command_descriptions')
  File "/home/pdonnell/ceph/src/pybind/ceph_argparse.py", line 1347, in json_command
    raise RuntimeError('"{0}": exception {1}'.format(argdict, e))
RuntimeError: "None": exception "['{"prefix": "get_command_descriptions"}']": exception [Errno 2] error calling conf_read_file
$ bin/ceph --cluster qetest tell mon.a quorum_status
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
2017-09-15 15:13:53.833752 7f87f7d14700 -1 WARNING: all dangerous and experimental features are enabled.
2017-09-15 15:13:53.857603 7f87f7d14700 -1 WARNING: all dangerous and experimental features are enabled.
{"election_epoch":8,"quorum":[0,1,2],"quorum_names":["a","b","c"],"quorum_leader_name":"a","monmap":{"epoch":1,"fsid":"c47c4eae-9add-4588-9b0d-fb44951fe012","modified":"2017-09-15 15:08:50.436701","created":"2017-09-15 15:08:50.436701","features":{"persistent":["kraken","luminous","mimic"],"optional":[]},"mons":[{"rank":0,"name":"a","addr":"127.0.0.1:55000/0","public_addr":"127.0.0.1:55000/0"},{"rank":1,"name":"b","addr":"127.0.0.1:55001/0","public_addr":"127.0.0.1:55001/0"},{"rank":2,"name":"c","addr":"127.0.0.1:55002/0","public_addr":"127.0.0.1:55002/0"}]}}

Related issues

Duplicated by fs - Bug #21967: 'ceph tell mds' commands result in 'File exists' errors on client admin socket Resolved 10/30/2017
Copied to fs - Backport #22078: luminous: ceph.in: tell mds does not understand --cluster Resolved
Copied to fs - Backport #22590: jewel: ceph.in: tell mds does not understand --cluster Resolved

History

#1 Updated by Patrick Donnelly over 1 year ago

  • Description updated (diff)

#2 Updated by Patrick Donnelly over 1 year ago

  • Assignee set to Ramana Raja
  • Source changed from Development to Q/A

#3 Updated by Ramana Raja over 1 year ago

  • Description updated (diff)

#4 Updated by Patrick Donnelly over 1 year ago

Ramana, was removing the BZ in the description an accident?

#5 Updated by Ramana Raja over 1 year ago

Patrick Donnelly wrote:

Ramana, was removing the BZ in the description an accident?

I haven't seen Red Hat downstream BugZilla bugs linked in upstream Ceph community's tracker issues before. Isn't it sufficient if downstream bugs in their description link to upstream tracker IDs, and not have it other way around as well? I could be totally wrong about this, Patrick.

Also, you'd linked the wrong downstream BZ. Please instead add https://bugzilla.redhat.com/show_bug.cgi?id=1491170 if you think it's needed

#6 Updated by Ramana Raja over 1 year ago

  • Status changed from New to In Progress

To use `tell mds` with cluster having a non-default name, you can get around the issue for now by passing the corresponding conf file path argument, --conf <conf file path>

#7 Updated by Patrick Donnelly over 1 year ago

  • Priority changed from High to Normal

#8 Updated by Ramana Raja over 1 year ago

  • Assignee changed from Ramana Raja to Jos Collin

#9 Updated by Jos Collin over 1 year ago

The work around `--conf <conf file path>` doesn't work anymore with the latest source code in the Ceph master. I'm hitting the below error when `--conf` option is used:
http://tracker.ceph.com/issues/21967

However, the original issue reported in this tracker (in the Description) can still be reproduced.

#10 Updated by Patrick Donnelly over 1 year ago

  • Status changed from In Progress to Need Review
  • Assignee changed from Jos Collin to Patrick Donnelly

https://github.com/ceph/ceph/pull/18654

Found that the above PR also resolves this issue so I'm reassigning to myself.

#11 Updated by Jos Collin over 1 year ago

  • Status changed from Need Review to In Progress

#12 Updated by Patrick Donnelly over 1 year ago

  • Status changed from In Progress to Need Review

Jos, "In Progress" indicates the Assignee is working on a fix. "Need Review" indicates the fix is undergoing review/testing. (We don't use "Need Test".)

#13 Updated by Patrick Donnelly over 1 year ago

  • Status changed from Need Review to Pending Backport

#14 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #22078: luminous: ceph.in: tell mds does not understand --cluster added

#15 Updated by Ken Dreyer about 1 year ago

  • Backport changed from luminous to luminous jewel

#16 Updated by Nathan Cutler about 1 year ago

  • Copied to Backport #22590: jewel: ceph.in: tell mds does not understand --cluster added

#17 Updated by Nathan Cutler about 1 year ago

  • Duplicated by Bug #21967: 'ceph tell mds' commands result in 'File exists' errors on client admin socket added

#18 Updated by Nathan Cutler about 1 year ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF