Bug 2094535
Summary: | Is reading from /etc/multipath/wwids expected when scanning? | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | jhouston |
Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
lvm2 sub component: | Other | QA Contact: | cluster-qe <cluster-qe> |
Status: | CLOSED DUPLICATE | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | agk, heinzm, jbrassow, jpittman, msnitzer, prajnoha, teigland, zkabelac |
Version: | 8.6 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-06-08 13:52:58 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: |
Comment 1
David Teigland
2022-06-07 20:57:45 UTC
David, That's exactly what I was looking for and dealing with. So it looks like we have commands to deal with the wwid's file and there will be something implemented for LVM to consider the blacklist. We can close this out or mark it as a duplicate. Thanks, Josh yes, lvm will read wwids from the blacklist (and exceptions), but won't use the other possible blacklist keywords that indirectly identify devices. *** This bug has been marked as a duplicate of bug 2076262 *** |