RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1329734 - utf8 characters in servers, routers, networks, etc cause issues with CLI being piped or redirected to a file
Summary: utf8 characters in servers, routers, networks, etc cause issues with CLI bein...
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-neutron
Version: Liberty
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
: Kilo
Assignee: lpeer
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-22 18:56 UTC by Kambiz Aghaiepour
Modified: 2016-05-19 15:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:47:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Kambiz Aghaiepour 2016-04-22 18:56:39 UTC
Description of problem:

Frequently we see commands such as :

   nova list
or 
   neutron router-list

error out, if the output is piped or redirected to another program or output file.  The error will read:

'ascii' codec can't encode characters in position 1754-1766: ordinal not in range(128)

and not output is given.  If however the same exact command is not redirected or piped, it is displayed on the screen without any issues.  This appears to happen when some user has created a router, or a vm, with a special character in the name.

To capture the output we have resorted to a workaround of running the command in screen and then working with the output file.  e.g.

   screen -L -D -m neutron router-list

will capture the output in ~/screenlog.0

This is a cludgy workaround and I was hoping there is a more proper fix.

Kambiz

Sorry I don't know which component this fits into.  It's not specifically a neutron issue but likely some common library.

Comment 1 Chandan Kumar 2016-05-19 15:47:46 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


Note You need to log in before you can comment on or make changes to this bug.