Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 1050025

Summary: NeutronError API internals are shown in Horizon UI on error
Product: [Community] RDO Reporter: Ihar Hrachyshka <ihrachys>
Component: python-django-horizonAssignee: Matthias Runge <mrunge>
Status: CLOSED UPSTREAM QA Contact: Ami Jeain <ajeain>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: aortega, chrisw, jpichon, mrunge, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-08 10:06:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
horizon screenshot none

Description Ihar Hrachyshka 2014-01-08 16:05:05 UTC 
Created attachment 847227 [details]
horizon screenshot

Description of problem:
When I try to associate new floating IP address to an instance thru UI, Horizon shows the following error message:

Error: 404-{u'NeutronError': {u'message': u'External network 474eeb86-0ea1-4336-bbbd-6f24687eafb3 is not reachable from subnet 251fe529-1267-4563-a94f-ee39d0f284a7. Therefore, cannot associate Port 2113e0a8-6f79-498b-8aa0-0b6e57615782 with a Floating IP.', u'type': u'ExternalGatewayForFloatingIPNotFound', u'detail': u''}}

Obviously exposing internal details to user. Which is a bug.

Version-Release number of selected component (if applicable):


How reproducible:
Always.


Steps to Reproduce:
1. Install RHEL-6.5 with updates.
2. Add RDO repo from http://rdo.fedorapeople.org/openstack-icehouse/rdo-release-icehouse.rpm
3. Deployed openstack via packstack, allinone.
4. Logged into UI.
5. Created new public network (network1), subnet (subnet1) with DHCP enabled, pool 10.34.62.240-10.34.62.242.
6. Then invoked a new instance, and tried to assign new floating IP to it. The port is created, but once Associate IP button is pressed, the error is shown.

Actual results:
weird error message

Expected results:
error should be properly handled by UI, no internal uuids should be exposed to user.

Additional info:
Comment 1 Matthias Runge 2014-01-09 15:02:31 UTC 
I agree on a bug, but not on security issue. Nobody can do something with this. esp. it's information you will get via API access, too.
Comment 2 Ihar Hrachyshka 2014-01-09 15:09:57 UTC 
I haven't said it's a security issue. It's more of cosmetic one: the correct [user-friendly] error is shown anyway, it just looks weird with that JSON message with no real benefit to user [or maybe there is some benefit to user, since (s)he is informed about the reason of the failure, but in unfriendly way; then we need to think how to inform user about the reason without being that technical with all those uuids shown to the user].
Comment 3 Matthias Runge 2014-01-09 15:23:57 UTC 
I wonder, if it's a duplicate of this bug on launchpad

https://bugs.launchpad.net/horizon/+bug/1246525
Comment 4 Matthias Runge 2014-10-08 10:06:55 UTC 
We're collecting all those error messages in a blueprint to improve error messages in Horizon: https://blueprints.launchpad.net/horizon/+spec/improve-error-message-details-for-usability