Bug 2214498

Summary: [RFE] Add support for minimum/maximum volume size on vol_type
Product: Red Hat OpenStack Reporter: Apoorv Verma <apverma>
Component: openstack-cinderAssignee: Cinder Bugs List <cinder-bugs>
Status: NEW --- QA Contact: Evelina Shames <eshames>
Severity: low Docs Contact: Andy Stillman <astillma>
Priority: unspecified    
Version: 16.2 (Train)Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Apoorv Verma 2023-06-13 07:18:16 UTC
Description of problem:
Inclusion of upstream commit link https://review.opendev.org/c/openstack/cinder/+/713710 along with some additional patches.

How reproducible:
Every time

Actual results:
Not able to set minimum/maximum volume size in any specific volume_type.

Expected results:
Ability to set minimum/maximum volume size in any specific volume_type.

Additional info:
With present commit, the minimum and/or maximum volume size 
for any specific `volume_type` can only be added/modified if there are no volumes present in it.
As soon as the volume will be created (irrespective of the size) within any `volume_type`, the property 'provisioning:min_vol_size'/'provisioning:max_vol_size' becomes immutable.

There is a requirement of this property to be editable even when volumes are present under `volume_type`.