[3.1-6] UI, Getting "Failed to parse JSON body" error for VN with special character'|' in Monitor->Networks page

Bug #1607667 reported by musharani
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
New
Low
VishnuVardhan V
R3.1
New
Low
VishnuVardhan V
R3.1.1.x
New
Low
VishnuVardhan V
R3.2
New
Low
VishnuVardhan V

Bug Description

Created a vn with the special character | say vn3|a. It got created in config page. But if you check in the monitor page it is throwing the below error.

Error: [SyntaxError: Failed to parse JSON body: Unexpected end of input]

When I checked uve, that vn vn3|a is not created.

Log:
----
07/29/2016 01:11:58 PM - ^[[31merror^[[39m: URL [http://10.204.217.99:8081/analytics/uves/virtual-network] returned error [{}]
07/29/2016 01:11:58 PM - ^[[31merror^[[39m: REST Server Error: [SyntaxError: Failed to parse JSON body: Unexpected end of input]
    at APIServer.retryMakeCall (/usr/src/contrail/contrail-web-core/src/serverroot/common/rest.api.js:180:13)
    at Request.<anonymous> (/usr/src/contrail/contrail-web-core/src/serverroot/common/rest.api.js:311:18)
    at Request.emit (events.js:98:17)
    at Request.mixin._fireError (/usr/lib64/node_modules/restler/lib/restler.js:204:10)
    at /usr/lib64/node_modules/restler/lib/restler.js:155:20
    at IncomingMessage.parsers.json (/usr/lib64/node_modules/restler/lib/restler.js:399:9)
    at IncomingMessage.parsers.auto (/usr/lib64/node_modules/restler/lib/restler.js:388:21)
    at Request.mixin._encode (/usr/lib64/node_modules/restler/lib/restler.js:194:29)
    at /usr/lib64/node_modules/restler/lib/restler.js:153:16
    at Request.mixin._decode (/usr/lib64/node_modules/restler/lib/restler.js:169:7)

Tags: ui
Revision history for this message
musharani (musharani) wrote :
Changed in juniperopenstack:
milestone: r3.1.0.0-fcs → none
Rahul (rahuls)
Changed in juniperopenstack:
assignee: Rahul (rahuls) → VishnuVardhan V (vishnuvv)
Manoj (manojgn)
Changed in juniperopenstack:
importance: High → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.