Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1886383

Summary: Additional PVs privisioned over a different dm-X symlink but sharing the same underlying devicePath
Product: OpenShift Container Platform Reporter: Robert Sandu <rsandu>
Component: StorageAssignee: Hemant Kumar <hekumar>
Storage sub component: Storage QA Contact: Chao Yang <chaoyang>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: aghadge, aos-bugs, hekumar, jsafrane
Version: 4.5Keywords: UpcomingSprint
Target Milestone: ---   
Target Release: 4.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1903361 1903362 (view as bug list) Environment:
Last Closed: 2020-12-15 20:28:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1903362    
Bug Blocks: 1903361    

Description Robert Sandu 2020-10-08 10:40:39 UTC
Description of problem: when using a LVM LogicalVolume as LocalVolume devicePath [0]. Sample config below (where /dev/elasticsearch/elasticsearch is the LVM LogicalVolume):

$ oc get localvolume -n local-storage es-disks -o json | jq .spec.storageClassDevices
[
  {
    "devicePaths": [
      "/dev/elasticsearch/elasticsearch"
    ],
    "fsType": "ext4",
    "storageClassName": "es-disks",
    "volumeMode": "Filesystem"
  }
]

This ends up 

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

Actual results:
- The LocalVolume PV points to an underlying /mnt/local-storage/${StorageClassName}/dm-X path, instead of the /dev/elasticsearch/elasticsearch LogicalVolume.
- /dev/elasticsearch/elasticsearch has different /mnt/local-storage/${StorageClassName}/dm-X symlinks pointing to the same /dev/elasticsearch/elasticsearch LogicalVolume
- Different PersistentVolumes can be provisioned pointing to different /mnt/local-storage/${StorageClassName}/dm-X symlinks, under the same /dev/elasticsearch/elasticsearch LogicalVolume, pointing to the same underlying data.

Expected results:
- Have one and only PV per LocalVolume object.

Additional info:
- Logs dumps and outputs to follow.

---
[0] https://github.com/openshift/local-storage-operator/blob/release-4.5/deploy/cr.yaml#L10

Comment 18 Hemant Kumar 2020-10-30 14:19:24 UTC
*** Bug 1892197 has been marked as a duplicate of this bug. ***

Comment 37 errata-xmlrpc 2020-12-15 20:28:44 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 (Moderate: OpenShift Container Platform 4.5.23 security and bug fix update), 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/RHSA-2020:5359