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

[release-4.17] Failed to extend the lvm thinpool when adding devicepaths

XMLWordPrintable

    • None
    • 1
    • OCPEDGE Sprint 264
    • 1
    • False
    • Hide

      None

      Show
      None
    • Previously, LVMS failed to extend thin pools when adding a new disk. With this fix, you can now extend thin pools when adding a new disk.
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-45868. The following is the description of the original issue:
      —
      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:

      When deploying an LVMCluster with the following configuration in spec.storage.deviceClasses.deviceSelector.optionalPaths, a volume group is created successfully:

      apiVersion: lvm.topolvm.io/v1alpha1
kind: LVMCluster
metadata:
  name: lvmcluster
  namespace: openshift-storage
spec:
  storage:
    deviceClasses:
      - deviceSelector:
          optionalPaths:
            - /dev/sdb
        fstype: xfs
        thinPoolConfig:
          chunkSizeCalculationPolicy: Static
          sizePercent: 90
          name: thin-pool-1
          overprovisionRatio: 10
        default: true
        name: vg1

      However, when attempting to add a new device path to spec.storage.deviceClasses.deviceSelector.optionalPaths afterward, 

      spec:
  storage:
    deviceClasses:
      - deviceSelector:
          optionalPaths:
            - /dev/sdb
            - /dev/disk/by-id/scsi-XXXXXXXXXXXXXXXXXXXXXXXXXXXXX   <<<==== add

      the following error occurs, and the device cannot be added:

      error on node openshift-storage/<node-name> in volume group openshift-storage/vg1: failed to create thin pool thin-pool-1 for volume group vg1: failed to extend the lvm thinpool thin-pool-1 in volume group vg1: VgSize (g) and lvSize (0), units do not match and cannot be used for extension

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

      4.17.2

      Steps to Reproduce:

      1. deploy LVMCluster and create thinpool
2. edit LVMCluster for adding devicepaths to optionalPaths

      Actual results:

      occuers error following:
error on node openshift-storage/<node-name> in volume group openshift-storage/vg1: failed to create thin pool thin-pool-1 for volume group vg1: failed to extend the lvm thinpool thin-pool-1 in volume group vg1: VgSize (g) and lvSize (0), units do not match and cannot be used for extension

      Expected results:

      ad devicepaths to Volume groups and expand storage.

      Additional info:

              sakbas@redhat.com Suleyman Akbas
              openshift-crt-jira-prow OpenShift Prow Bot
              Minal Pradeep Makwana Minal Pradeep Makwana
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: