Neutron cli does not support non-ASCII symbols in resource's names
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Confirmed
|
Medium
|
MOS Neutron | ||
6.0.x |
Confirmed
|
Medium
|
MOS Maintenance | ||
6.1.x |
Confirmed
|
Medium
|
MOS Maintenance | ||
7.0.x |
Confirmed
|
Medium
|
MOS Maintenance | ||
8.0.x |
Confirmed
|
Medium
|
MOS Neutron | ||
9.x |
Confirmed
|
Medium
|
MOS Neutron |
Bug Description
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/
return run_command(cmd, cmd_parser, sub_argv)
File "/usr/lib/
return cmd.run(known_args)
File "/usr/lib/
return super(OpenStack
File "/usr/lib/
self.produce_
File "/usr/lib/
parsed_args,
File "/usr/lib/
stdout.
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)
description: | updated |
summary: |
- Neutron does not support ASCII symbols into network's names + Neutron does not support non-ASCII symbols into network's names |
summary: |
- Neutron does not support non-ASCII symbols into network's names + Neutron cli does not support non-ASCII symbols into network's names |
summary: |
- Neutron cli does not support non-ASCII symbols into network's names + Neutron cli does not support non-ASCII symbols in resource's names |
description: | updated |
information type: | Public → Public Security |
tags: |
added: area-neutron removed: neutron |
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.