Bug 2010174
| Summary: | 2 PVs get created unexpectedly with different paths that actually refer to the same device on the node. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | yhe |
| Component: | Storage | Assignee: | Hemant Kumar <hekumar> |
| Storage sub component: | Local Storage Operator | QA Contact: | Chao Yang <chaoyang> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | unspecified | CC: | aos-bugs, hekumar, nhashimo, ori, tsmetana |
| Version: | 4.8 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-10 16:16:28 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: | |||
BTW, I keep seeing the "The assignee for this bug cannot see private comments!" messages on this Bugzilla, can I ignore this message safely or should I make the private comments public? Yes you can ignore those messages. This happens because default assignee is storage group (so as all of us receive new email notifications). 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.10.3 security 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-2022:0056 |
Description of problem: 2 PVs get created unexpectedly with a different path that actually refers to the same device on the node. The local-pv-96dcb1a7 gets created unexpectedly. [root@eit2-mng001 TEST_PV]# oc get pv | grep oam-sc-filesystem-02 local-pv-73818e0c 100Mi RWO Delete Available oam-sc-filesystem-02 4d12h local-pv-96dcb1a7 100Mi RWO Delete Available oam-sc-filesystem-02 2d22h The paths of the 2 PVs are different. [root@eit2-mng001 TEST_PV]# oc describe pv local-pv-73818e0c local-pv-96dcb1a7 | grep Path Path: /mnt/local-storage/oam-sc-filesystem-02/scsi-362cea7f05fc6fe0028a959eed8214c9c-part3 Path: /mnt/local-storage/oam-sc-filesystem-02/sda3 But the 2 paths are actually referring to the same device on the node. [root@eit2-worker001 ~]# ls -l /mnt/local-storage/oam-sc-filesystem-02/ total 0 lrwxrwxrwx. 1 root root 60 Sep 29 11:59 scsi-362cea7f05fc6fe0028a959eed8214c9c-part3 -> /dev/disk/by-id/scsi-362cea7f05fc6fe0028a959eed8214c9c-part3 lrwxrwxrwx. 1 root root 9 Oct 1 02:37 sda3 -> /dev/sda3 [root@eit2-worker001 ~]# ls -l /dev/disk/by-id/scsi-362cea7f05fc6fe0028a959eed8214c9c-part3 lrwxrwxrwx. 1 root root 10 Oct 1 10:01 /dev/disk/by-id/scsi-362cea7f05fc6fe0028a959eed8214c9c-part3 -> ../../sda3 Will upload the related information later. Version-Release number of selected component (if applicable): How reproducible: Unsure Steps to Reproduce: N/A Actual results: 2 PVs get created with different paths that refer to the same device Expected results: Only 1 PV gets created with the device Additional info: