Bug 1193708

Summary:	cryptic error message in ceph interactive mode
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Federico Lucifredi <flucifre>
Component:	Unclassified	Assignee:	ceph-eng-bugs <ceph-eng-bugs>
Status:	CLOSED ERRATA	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.2.2	CC:	hnallurv, kchai, kdreyer, vumrao
Target Milestone:	rc
Target Release:	2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 19:25:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Federico Lucifredi 2015-02-17 22:51:39 UTC

Description of problem:

after entering interactive mode with 'ceph'

ceph> exit
no valid command found; 10 closest matches:
....[blah].....

Expected results:
recommend command "quit"

Comment 1 John Poelstra 2015-02-19 19:03:17 UTC

probably need a bug upstream

Comment 2 Ken Dreyer (Red Hat) 2015-04-23 15:47:22 UTC

I'm guessing this is still unresolved upstream, so I've filed a ticket in Redmine. Re-targeting this bug to 2.0 in the meantime; please feel free to re-target if necessary

Comment 3 Kefu Chai 2015-05-20 05:29:46 UTC

fixed in upstream https://github.com/ceph/ceph/commit/87433dabdd46ab13864afa88ad928dc97360794c

Comment 4 Kefu Chai 2015-06-16 02:45:30 UTC

this is not a critical bug fix, so it will be included in the next release (Infernalis).

Comment 6 Harish NV Rao 2016-05-03 10:56:14 UTC

Issue resolved. No error message found when 'exit' was issued.

[ubuntu@magna003 ~]$ sudo ceph
ceph> exit
[ubuntu@magna003 ~]$ sudo ceph
ceph> q
[ubuntu@magna003 ~]$ sudo ceph
ceph> quit

[ubuntu@magna003 ~]$ sudo ceph -v
ceph version 10.2.0-1.el7cp (3a9fba20ec743699b69bd0181dd6c54dc01c64b9)

Comment 8 errata-xmlrpc 2016-08-23 19:25:36 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1755