Cue monitor should be accessing records through objects layer
Bug #1517174 reported by
Davide Agnello
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cue |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Cue monitor should be accessing records through objects layer.
| Changed in cue: | |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to cue (master) | #1 |
| Changed in cue: | |
| status: | New → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit bbe9a3f651462e5
Author: Saurabh Surana <email address hidden>
Date: Tue Dec 8 15:55:59 2015 -0800
monitor now uses objects layer to access db records
since we moved policy checks into the API layer, we
can now use objects layer to access db records from
cue monitor.
When objects layer was doing policy checks we couldn't use
object layer without a valid conext object, and since cue
monitor doesn't have a conext object earlier we couldn't
use objects layer in cue monitor.
Closes-Bug: 1517174
Change-Id: I1a66b1fd5e66a8