Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-24427

overprovisionRatio can not be set to 1

XMLWordPrintable

    • Low
    • No
    • 2
    • OCPEDGE Sprint 246
    • 1
    • False
    • Hide

      None

      Show
      None
    • `spec.storage.deviceClasses.thinPoolConfig.overprovisionRatio` on an LVMCluster CR can now be set to as low as 1 instead of the previous minimum value of 2, which disables overprovisioning.
    • Bug Fix
    • In Progress

      Description of problem:

       overprovisionRatio can only be set to a value of 2 or greater. there is no reason for this. Customer who want to have guaranteed capacity need to be able to set this to 1 (== no overprovisioning).

      Version-Release number of selected component (if applicable):

       4.14

      How reproducible:

          always

      Steps to Reproduce:

      Take a look at the source code:
https://github.com/openshift/lvm-operator/blob/main/config/crd/bases/lvm.topolvm.io_lvmclusters.yaml#L194-L199

      Additional info:

      Slack Thread with discussion:

      https://redhat-internal.slack.com/archives/C048G31FLHJ/p1701695048904979

      Upstream also has a min value of 1 (https://github.com/topolvm/topolvm/pull/442/files#r830792492)

              sakbas@redhat.com Suleyman Akbas
              openshift-crt-jira-prow OpenShift Prow Bot
              Rahul Deore Rahul Deore
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: