yahoo-eng-team team mailing list archive

[Akihiro Motoki <1284317@xxxxxxxxxxxxxxxxxx>]

It is better to define a base NotFound exception class in neutronclient
rather than dealing with specific NotFound error. If 404 response is
returned from Neutron, NotFound base exception class is used. (For
network/port not found, the existing class should be used.)

In Horizon, what we need to do is to add NotFound class above and remove
Network/PortNotFound class from horizon exceptions.NOT_FOUND list.


** Project changed: neutron => python-neutronclient

** Changed in: horizon
       Status: New => Triaged

** Changed in: python-neutronclient
       Status: New => Triaged

** Changed in: python-neutronclient
   Importance: Undecided => Medium

** Changed in: horizon
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1284317

Title:
  Not found router raises generic exception

Status in OpenStack Dashboard (Horizon):
  Triaged
Status in Python client library for Neutron:
  Triaged

Bug description:
  As a horizon developer, I use the neutronclient package, which
  currently provides several exceptions that horizon can catch,
  including NetworkNotFoundClient, and PortNotFoundClient.
  Unfortunately, there is no RouterNotFoundClient exception.  When an
  api call is made to get a router_id that doesn't exist, a very generic
  NeutronClientException is raised which is significantly problematic.
  (Though it does have a status_code of 404, and an error message saying
  "Router <id> could not be found" which is good.)

  I'd like for a new exception to be thrown so we can catch it and treat
  it as a NOT_FOUND error instead of having to parse it and fight
  changing-error-messages and the like.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1284317/+subscriptions