Neutron cli does not support non-ASCII symbols in resource's names

[Stanislav Kolenkin]

Neutron cli does not support non-ASCII symbols in resource's names.
Customer-found on MOS 7.0

neutron subnet-list
'ascii' codec can't encode character u'\ufffc' in position 8303: ordinal not in range(128)

python-based CLI stuff breaks up because of unsupported symbols is not related to openstack. But the fact that user is allowed to create such entities with unsupported symbols into Horizon is definitely related to OpenStack! User-oriented Web-interface should resist to user's attempts to do it.

# neutron -v subnet-list
.....
ERROR: neutronclient.shell 'ascii' codec can't encode character u'\ufffc' in position 8141: ordinal not in range(128)
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/neutronclient/shell.py", line 766, in run_subcommand
return run_command(cmd, cmd_parser, sub_argv)
File "/usr/lib/python2.7/dist-packages/neutronclient/shell.py", line 101, in run_command
return cmd.run(known_args)
File "/usr/lib/python2.7/dist-packages/neutronclient/common/command.py", line 29, in run
return super(OpenStackCommand, self).run(parsed_args)
File "/usr/lib/python2.7/dist-packages/cliff/display.py", line 92, in run
self.produce_output(parsed_args, column_names, data)
File "/usr/lib/python2.7/dist-packages/cliff/lister.py", line 56, in produce_output
parsed_args,
File "/usr/lib/python2.7/dist-packages/cliff/formatters/table.py", line 56, in emit_list
stdout.write(formatted)
UnicodeEncodeError: 'ascii' codec can't encode character u'\ufffc' in position 8141: ordinal not in range(128)
'ascii' codec can't encode character u'\ufffc' in position 8141: ordinal not in range(128)

[Eugene Nikanorov (enikanorov)]

Assigning to mos-horizon for evaluation.
It might be hard thing to fix on neutron side, but on horizon side some validation could be added.

The problem with the issue is that regular user may break operability of cli.
So this at least should be documented.

[Ilya Shakhat (shakhat)]

This issue affects CLI. The reason is in environment variable LC_ALL=C.

Workaround:
# unset LC_ALL

[Timur Sufiev (tsufiev-x)]

From Horizon POV, it's feasible to restrict the set of allowed symbols when creating something Network-related in Horizon to just ASCII symbols. Yet, the problem will still exist in neutronclient after that.