Wrong exception in db api

Bug #1475556 reported by Madhuri Kumari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Low
Madhuri Kumari

Bug Description

In following db api,
1. get_rcs_by_bay_uuid
2. get_services_by_bay_uuid

The exception returned when bay is not found is wrong.

Changed in magnum:
assignee: nobody → Madhuri Kumari (madhuri-rai07)
importance: Undecided → Low
Changed in magnum:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/202946
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=a75b8f0f031b3ea0a861f961c934b8b876cde110
Submitter: Jenkins
Branch: master

commit a75b8f0f031b3ea0a861f961c934b8b876cde110
Author: Vilobh Meshram <email address hidden>
Date: Thu Aug 27 12:06:26 2015 -0700

    Correct exception raised in few db APIs

    This patch corrects wrong exception raised in below
    db APIs:
    1. get_rcs_by_bay_uuid
    2. get_services_by_bay_uuid

    Co-Authored-By: Vilobh Meshram <email address hidden>

    Closes-bug: #1475556
    Change-Id: I7c3307747f6ae905a9eecc2e755e5c7d6ddde91d

Changed in magnum:
status: In Progress → Fix Committed
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
status: Fix Committed → Fix Released
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.