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

PVC provisioning fails with storageClass using default volumeGroup in a cluster where multiple VGs are present

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • Important
    • No
    • None
    • Rejected
    • OCPEDGE Sprint 247, OCPEDGE Sprint 248, OCPEDGE Sprint 249
    • 3
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      PVC provisioning fails with storageClass using default volumeGroup in a cluster where multiple VGs are present

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

          lvms 4.15.0-53

      How reproducible:

          Always

      Steps to Reproduce:

          1. Setup multi-node OCP cluster and install LVMS operator
          2. Create 3 deviceClasses (one deviceClass as default) with the device Selector only applying to one node each via node selector     
          3. Create a PVC,Pod using storageClass for default VG: 'lvms-vg1'
          

      Actual results:

      PV provisioning fails with error,
      "failed to provision volume with StorageClass "lvms-vg1": rpc error: code = Internal desc = failed to check volume existence"

      Expected results:

      PV provisioing successful with all lvms storageClasses

      Additional info:

       LVMCluster:
      
      apiVersion: lvm.topolvm.io/v1alpha1
      kind: LVMCluster
      metadata:
        name: test-lvmcluster
        namespace: openshift-storage
      spec:
        storage:
          deviceClasses:
            - default: true
              deviceSelector:
                paths:
                  - /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_cccc
              fstype: xfs
              name: vg1
              nodeSelector:
                nodeSelectorTerms:
                  - matchExpressions:
                      - key: topology.topolvm.io/node
                        operator: In
                        values:
                          - n1.us-east-2.compute.internal
              thinPoolConfig:
                name: thin-pool-1
                overprovisionRatio: 10
                sizePercent: 90
            - default: false
              deviceSelector:
                paths:
                  - /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_xxxx
              fstype: xfs
              name: vg2
              nodeSelector:
                nodeSelectorTerms:
                  - matchExpressions:
                      - key: topology.topolvm.io/node
                        operator: In
                        values:
                          - n2.us-east-2.compute.internal
              thinPoolConfig:
                name: thin-pool-1
                overprovisionRatio: 10
                sizePercent: 90
            - default: false
              deviceSelector:
                paths:
                  - /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_yyyy
              fstype: xfs
              name: vg3
              nodeSelector:
                nodeSelectorTerms:
                  - matchExpressions:
                      - key: topology.topolvm.io/node
                        operator: In
                        values:
                          - n3.us-east-2.compute.internal
              thinPoolConfig:
                name: thin-pool-1
                overprovisionRatio: 10
                sizePercent: 90

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

                Created:
                Updated:
                Resolved: