Fix module-instances command
Bug #1554900 reported by
Peter Stachowski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
High
|
Amrith Kumar |
Bug Description
Due to the framework of handling queries and pagination in Trove, the module-instances portion of the module management blueprint was not implemented completely. This needs to be fixed.
Changed in trove: | |
assignee: | nobody → Peter Stachowski (peterstac) |
importance: | Undecided → High |
milestone: | none → mitaka-3 |
milestone: | mitaka-3 → mitaka-rc1 |
Changed in trove: | |
milestone: | mitaka-rc1 → mitaka-rc2 |
Changed in trove: | |
milestone: | mitaka-rc2 → newton-1 |
status: | New → Confirmed |
Changed in trove: | |
milestone: | newton-1 → ongoing |
Changed in trove: | |
assignee: | Peter Stachowski (peterstac) → Amrith Kumar (amrith) |
To post a comment you must log in.
Here's the code block in question:
if instance_ids and len(instance_ids) > 1: DatastoreOperat ionNotSupported (
operation= 'module- instances' , datastore= 'current' )
db_ infos = DBInstance. query() .filter_ by(**query_ opts)
query_ opts['id' ] = instance_ids[0]
db_ infos = DBInstance. find_all( **query_ opts)
raise exception.
else:
if instance_ids: