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

LVMCluster CR goes into degraded state when storage is above 32TiB

XMLWordPrintable

    • No
    • 5
    • Proposed
    • False
    • Hide

      None

      Show
      None

      This is an LVMS Bug Report:

      Please create & attach a must-gather as indicated by this Guide to collect LVMS relevant data from the Cluster (linked to the latest version, use older versions of the documentation for older OCP releases as applicable

      Please make sure that you describe your storage configuration in detail. List all devices that you plan to work with for LVMS as well as any relevant machine configuration data to make it easier for an engineer to help out.

      Description of problem:

       LVMCluster CR goes into degraded state when it's created using devices totaling over 32TiB and chunkSize is set to 512Ki

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

       4.17.0-18

      Steps to Reproduce:

       1. Create LVMCluster CR with devices totaling over 32TiB with 'chunkSize: 512Ki' set

      Actual results:

      LVMCluster CR goes into 'Degraded' state with vg-manager pod going into 'CrashLoopBackOff' state.

      Expected results:

      LVMCluster CR goes into 'Running' state with no issues.

      Additional info:

       LVMCluster CR:

apiVersion: lvm.topolvm.io/v1alpha1
kind: LVMCluster
metadata:
  name: test-lvmcluster
  namespace: openshift-storage
spec:
  storage:
    deviceClasses:
      - fstype: xfs
        name: vg1
        thinPoolConfig:
          chunkSize: 512Ki
          chunkSizeCalculationPolicy: Static
          name: thin-pool-1
          overprovisionRatio: 10
          sizePercent: 90

            sakbas@redhat.com Suleyman Akbas
            rh-ee-rdeore Rahul Deore
            Rahul Deore Rahul Deore
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: