Image volume cache limits misbehave when only one is set
Bug #1792944 reported by
Alan Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Alan Bishop |
Bug Description
The image volume cache has two configurable limits:
- image_volume_
- image_volume_
The code functions correctly when both values are zero (i.e. unlimited), and
when both values are assigned a non-zero value (both limits enforced).
However, the system misbehaves when only one limit is configured and the
other is disabled.
If only one limit is enforced, the system always removes existing entries
before adding a new entry. In other words, it behaves as if the
image_volume_
actually configured.
Changed in cinder: | |
assignee: | nobody → Alan Bishop (alan-bishop) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/603145
Review: https:/