b00b2fe9be
For some reason, probably because build requests are meant to be short lived and we don't get a lot of bugs about paging misbehavior, when paging instances with a marker, we didn't raise MarkerNotFound if we didn't find the marker in the list of build requests. Doing so would match what we do when paging over cells and listing instances using a marker. Once we find the marker, be that in build_requests, or one of the cells, we need to set the marker to None to stop looking for it elsewhere if we have more space to fill our limit. For example, see change I8a957bebfcecd6ac712103c346e028d80f1ecd7c. This patch fixes the issue by raising MarkerNotFound from BuildRequestList get_by_filters if there is a marker and we didn't find a build request for it. The compute API get_all() method handles that as normal and continues looking for the marker in one of the cells. Conflicts: nova/tests/unit/compute/test_compute_api.py NOTE(mriedem): The conflicts are due to not having |
||
---|---|---|
.. | ||
monitors | ||
__init__.py | ||
api.py | ||
build_results.py | ||
cells_api.py | ||
claims.py | ||
flavors.py | ||
instance_actions.py | ||
manager.py | ||
power_state.py | ||
resource_tracker.py | ||
rpcapi.py | ||
stats.py | ||
task_states.py | ||
utils.py | ||
vm_states.py |