yahoo-eng-team team mailing list archive

[Akihiro Motoki <1296148@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Neutronclient now raises known exceptions (such as NetworkNotFound, PortNotFound,...) or generic NeutronClientException, and library users (like Horizon) cannot catch generic NotFound exception without checking the detail of NeutronClientException.
Obviously neutronclient should raise individual exceptions based on response status code (400, 404, 409 and so on).

By doing so, Horizon exception handling will be much simpler and I believe it brings the similar merits to other library users.
In Horizon it is targeted to Icehouse release.

It is related to bug 1284317, which is specific to Router Not Found
exception, and this bug is intended to address the issue in more generic
way.

** Affects: horizon
     Importance: Medium
     Assignee: Akihiro Motoki (amotoki)
         Status: New

** Affects: python-neutronclient
     Importance: High
     Assignee: Akihiro Motoki (amotoki)
         Status: In Progress

** Also affects: horizon
   Importance: Undecided
       Status: New

** Changed in: horizon
    Milestone: None => icehouse-rc1

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

** Changed in: horizon
     Assignee: (unassigned) => Akihiro Motoki (amotoki)

-- 
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/1296148

Title:
  neutronclient should raise generic per-code exceptions

Status in OpenStack Dashboard (Horizon):
  New
Status in Python client library for Neutron:
  In Progress

Bug description:
  Neutronclient now raises known exceptions (such as NetworkNotFound, PortNotFound,...) or generic NeutronClientException, and library users (like Horizon) cannot catch generic NotFound exception without checking the detail of NeutronClientException.
  Obviously neutronclient should raise individual exceptions based on response status code (400, 404, 409 and so on).

  By doing so, Horizon exception handling will be much simpler and I believe it brings the similar merits to other library users.
  In Horizon it is targeted to Icehouse release.

  It is related to bug 1284317, which is specific to Router Not Found
  exception, and this bug is intended to address the issue in more
  generic way.

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