Bug 1780625 - local-storage-operator does not support LVM devices
Summary: local-storage-operator does not support LVM devices
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.2.z
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.4.0
Assignee: Hemant Kumar
QA Contact: Liang Xia
URL:
Whiteboard:
Depends On: 1783863
Blocks: 1781869 1781871
TreeView+ depends on / blocked
 
Reported: 2019-12-06 14:45 UTC by Jason Kincl
Modified: 2020-05-04 11:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1781869 (view as bug list)
Environment:
Last Closed: 2020-05-04 11:19:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:19:37 UTC

Description Jason Kincl 2019-12-06 14:45:04 UTC
Description of problem:

Specifying a device path like /dev/disk/by-id/dm-name-vg1-lvol0 does not work and the local storage cannot be used.

Also: https://github.com/openshift/local-storage-operator/issues/57

How reproducible:

always

Steps to Reproduce:

apiVersion: local.storage.openshift.io/v1
kind: LocalVolume
metadata:
  name: lvm-local-storage
  namespace: local-storage
spec:
  nodeSelector:
    nodeSelectorTerms:
    - matchExpressions:
        - key: region
          operator: In
          values:
          - local-storage-node
  storageClassDevices:
    - storageClassName: cadence-local
      volumeMode: Filesystem
      fsType: ext4
      devicePaths:
        - /dev/disk/by-id/dm-name-vg-vg0-lvol0

Actual results:

diskmaker cannot find any disks

Expected results:

diskmaker finds the LVM disk correctly

Comment 6 Liang Xia 2019-12-19 06:26:37 UTC
Verified with local-storage-operator.4.4.0-201912170523 on 4.4.0-0.nightly-2019-12-18-064553


$ oc get sc,pv
NAME                                             PROVISIONER                    AGE
storageclass.storage.k8s.io/local-sc             kubernetes.io/no-provisioner   5m41s
storageclass.storage.k8s.io/standard (default)   kubernetes.io/cinder           3h28m

NAME                                 CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM   STORAGECLASS   REASON   AGE
persistentvolume/local-pv-104b75f1   1Gi        RWO            Delete           Available           local-sc                5m20s



sh-4.4# lvdisplay 
  --- Logical volume ---
  LV Path                /dev/myvg01/mylv01
  LV Name                mylv01
  VG Name                myvg01
  LV UUID                mvT0Ww-eOaz-i0Dm-4ZZo-HoPu-3EHB-dVUxpV
  LV Write Access        read/write
  LV Creation host, time lxia19-48fdq-worker-dsf5s, 2019-12-19 06:15:56 +0000
  LV Status              available
  # open                 0
  LV Size                1.00 GiB
  Current LE             256
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1

Comment 8 errata-xmlrpc 2020-05-04 11:19:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581


Note You need to log in before you can comment on or make changes to this bug.