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

overprovisionRatio can not be set to 1

    XMLWordPrintable

Details

    • 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

      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)

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-24396 overprovisionRatio can not be set to 1

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-27356 overprovisionRatio can not be set to 1

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub openshift/lvm-operator#522: [release-4.12] OCPBUGS-24480: Allow setting overprovision ratio to 1

          Web Link RHBA-2023:7823 OpenShift Container Platform 4.12.z bug fix update

          Web Link RHBA-2024:0198 OpenShift Container Platform 4.12.z bug fix update

          mentioned on

          GitLab Merge request - Updated US source to: 80df1fa Merge pull request #522 from suleymanakbas91/release-4.12

          Activity

            People

              sakbas@redhat.com Suleyman Akbas
              dfroehli42rh Daniel Fröhlich
              Rahul Deore Rahul Deore
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: