change_since filter for server listing in V3 API does not work
Bug #1220045 reported by
Christopher Yeoh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Christopher Yeoh |
Bug Description
The V3 API changed the changes-since parameter to changes_since
for consistency with other parameters. However, the db level call
expects changes-since as the filter. We should transform the api parameter from
changes_since to changes-since before passing it to the compute api
Changed in nova: | |
assignee: | nobody → Christopher Yeoh (cyeoh-0) |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → Medium |
milestone: | none → havana-rc1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-rc1 → 2013.2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/44637 github. com/openstack/ nova/commit/ f85a6bba232afb4 c81ad5e7c9d0e2b 5ce6a83a5f
Committed: http://
Submitter: Jenkins
Branch: master
commit f85a6bba232afb4 c81ad5e7c9d0e2b 5ce6a83a5f
Author: Chris Yeoh <email address hidden>
Date: Mon Sep 2 16:24:14 2013 +0930
Fix changes_since for V3 API
The V3 API changed the changes-since parameter to changes_since
for consistency with other parameters. However, the db level
expects changes-since as the filter. So this change transforms
changes_since to changes-since before passing it to the compute
layer.
Closes-Bug: 1220045
Change-Id: Id34ffe8aa75b20 d11dcb1b4a9ba36 e2586dae1e3