It's not a security problem, the python command line parser we used doesn't like to see unicode there and so it raised an exception. That tool actually does quite a lot of input validation and even gives suggestions in many cases (just apparently not for that kind. Still, it would be better if we returned a nicer error message there. I'll create an upstream ticket.
Not yet fixed upstream; re-targeting to 1.3.2
https://github.com/ceph/ceph/pull/5275 was in master (thanks Kefu), so this will be in RHCS 2.0 when we ship Jewel.
Tested in 10.2.0. Now no trace is printed but a ununderstandable message is printed. Needs a fix.
[ubuntu@magna003 ~]$ sudo ceph –w
error handling command target: 'ascii' codec can't encode character u'\u2013' in position 0: ordinal not in range(128)
we have a patch: https://github.com/ceph/ceph/pull/8943 but not in master yet. we can defer it to 2.1
Not a blocker - recommend moving to 2.z
merged in master. will be picked up by the RHCS 2.1.
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.