Fix image cache db query when limits are enabled
We were missing the context parameter... and apparently never tested with cache limits enabled. This fixes it and updates the unit tests to check for it too. I'll follow up with a devstack patch to set some limits by default too so we cover more of this code and have it behave like a production deployment in gate jobs. Change-Id: Ia6d43b35843682bd201e57bb2941ca0243606412 Closes-Bug: #1701696
This commit is contained in:
parent
d5ce948ab2
commit
70719d028a
@ -133,6 +133,7 @@ class ImageVolumeCache(object):
|
||||
|
||||
# Assume the entries are ordered by most recently used to least used.
|
||||
entries = self.db.image_volume_cache_get_all(
|
||||
context,
|
||||
**self._get_query_filters(volume))
|
||||
|
||||
current_count = len(entries)
|
||||
|
@ -254,6 +254,8 @@ class ImageVolumeCacheTestCase(test.TestCase):
|
||||
self.assertEqual(2, mock_delete.call_count)
|
||||
mock_delete.assert_any_call(self.context, entry2)
|
||||
mock_delete.assert_any_call(self.context, entry3)
|
||||
self.mock_db.image_volume_cache_get_all.assert_called_with(
|
||||
self.context, cluster_name=self.volume_ovo.cluster_name)
|
||||
|
||||
def test_ensure_space_need_count(self):
|
||||
cache = self._build_cache(max_gb=30, max_count=2)
|
||||
|
Loading…
Reference in New Issue
Block a user