The error message when adding an invalid Router is not formatted

Bug #1282232 reported by Rodrigo Antunes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Invalid
Low
Leandro Ignacio Costantino
python-neutronclient
Fix Released
Medium
Akihiro Motoki

Bug Description

I added a invalid Router (external network without subnet) The problem is on the displayed message:
Error: Failed to set gateway 400-{u'NeutronError': {u'message: u'BadUpdate Router request: No subnets defined on network 47......', u'type:u'BadRequest'u'dwtail:u"}}

Changed in horizon:
status: New → Confirmed
Revision history for this message
Victoria Martinez de la Cruz (vkmc) wrote :

This is happening in several notifications in Neutron because we are getting the error message from the API directly. I'll check if there is a way to format those messages.

Changed in horizon:
assignee: nobody → Victoria Martínez de la Cruz (vkmc)
David Lyle (david-lyle)
Changed in horizon:
importance: Undecided → Low
Revision history for this message
Victoria Martinez de la Cruz (vkmc) wrote :

This bug is affected by https://bugs.launchpad.net/horizon/+bug/1286104. Currently in progress.

Changed in horizon:
status: Confirmed → In Progress
assignee: Victoria Martínez de la Cruz (vkmc) → nobody
Changed in horizon:
assignee: nobody → Leandro Ignacio Costantino (leandro-i-costantino)
Revision history for this message
Leandro Ignacio Costantino (leandro-i-costantino) wrote :

Bug reassigned by gerrit, but actualy belongs to Victoria Martínez de la Cruz (vkmc)

Revision history for this message
Akihiro Motoki (amotoki) wrote :

I am working on neutronclient side as bug 1246271 (While the work is stopped for a couple of months, I just resumed the patch). This bug will remove JSON dumps of exception messages and extract messages.

Is this bug addressed if neutronclient extracts appropriate messages?

I believe fixing it in neutronclient is a good approach for Icehouse and horizon blueprint is better to be targeted to Juno.

Revision history for this message
Victoria Martinez de la Cruz (vkmc) wrote :

@Akihiro Thanks for filing this bug to python-neutronclient. As I checked, if it is fixed in python-neutronclient then it will be solved in the Horizon side. I agree with you that the Horizon blueprint (https://blueprints.launchpad.net/horizon/+spec/improve-error-message-details-for-usability) should be targeted to Juno since there is a lot of work to do to enhance error messages and it depends mostly on the clients (http://lists.openstack.org/pipermail/openstack/2014-January/004651.html).

Revision history for this message
Akihiro Motoki (amotoki) wrote :

As neutronclient bug, it was fixed in bug 1246271, so I will mark neutronclient bug as Invalid.

Revision history for this message
Akihiro Motoki (amotoki) wrote :

Changed to Fix Committed.

Changed in python-neutronclient:
status: New → Fix Committed
assignee: nobody → Akihiro Motoki (amotoki)
importance: Undecided → Medium
milestone: none → 2.3.7
Akihiro Motoki (amotoki)
Changed in python-neutronclient:
status: Fix Committed → Fix Released
Revision history for this message
Julie Pichon (jpichon) wrote :

This should be fixed by the Neutron client update, closing on the Horizon side.

Changed in horizon:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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