Description of problem: As mentioned in upstream doc[1] the correct value should be max_over_subscription_ratio - notice the extra _ UNDERSCORE Taken from stock cinder.conf: nfs_oversub_ratio = 1.0 (FloatOpt) This will compare the allocated to available space on the volume destination. If the ratio exceeds this number, the destination will no longer be valid. Note that this option is deprecated in favor of "max_oversubscription_ratio" and will be removed in the Mitaka release. [1]https://docs.openstack.org/liberty/config-reference/content/nfs-driver-options.html Version-Release number of selected component (if applicable): How reproducible: typo seems present in at least rhosp 7/8/9
Eric, Just to be sure before I verify, is this just the below typo which needed verification as the bz title suggests, or do I need to check something else? vi /usr/lib/python2.7/site-packages/cinder/volume/drivers/nfs.py cfg.FloatOpt('nfs_oversub_ratio', default=NFS_OVERSUB_RATIO_DEFAULT, help=('This will compare the allocated to available space on ' 'the volume destination. If the ratio exceeds this ' 'number, the destination will no longer be valid. ' 'Note that this option is deprecated in favor of ' '"max_over_subscription_ratio" and will be removed ' Was -> max_oversubscription_ratio" before the fix. Cinder.conf, also now "max_over_subscription_ratio"-> # This will compare the allocated to available space on the volume destination. # If the ratio exceeds this number, the destination will no longer be valid. # Note that this option is deprecated in favor of "max_over_subscription_ratio" # and will be removed in the Mitaka release. (floating point value) #nfs_oversub_ratio = 1.0
(In reply to Tzach Shefi from comment #3) > Eric, > > Just to be sure before I verify, > is this just the below typo which needed verification > as the bz title suggests, or do I need to check something else? > Correct, this is just fixing the typo in the description of the option, no runtime changes.
Verified on: openstack-cinder-7.0.3-9.el7ost.noarch according to comments #3-4
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3121