PolicyProfileNotFound exception not being raised
Bug #1440204 reported by
Shiv Prasad Rao
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networking-cisco |
Fix Committed
|
Undecided
|
Shiv Prasad Rao | ||
Bug Description
Sql query for retrieving policy profiles by name and by uuid was changed to return the first row (.first()) instead of one row(.one()) to accomodate for policy profiles being retieved from multiple VSM. But this first() does not raise an exception in case of no result found.
| Changed in networking-cisco: | |
| status: | New → Confirmed |
| tags: | added: n1kv |
| Changed in networking-cisco: | |
| assignee: | nobody → Shiv Prasad Rao (shivrao) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to networking-cisco (master) | #1 |
| Changed in networking-cisco: | |
| status: | Confirmed → Fix Committed |
| Changed in networking-cisco: | |
| milestone: | none → 1.0.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit fb358665bf6ece6
Author: Shiva Prasad Rao <email address hidden>
Date: Fri Apr 3 15:15:56 2015 -0700
PolicyProfi
A check is added to raise the PolicyProfileNo
This is needed after the filter .one() was replaced with .first()
which does not raise the exception and returns a None if policy
profile is not found
Change-Id: I3f05552f044424
Closes-Bug: 1440204