Bug 1346172
| Summary: | vgck scan all devices even if filter is configured | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | lvm2 | Assignee: | Peter Rajnoha <prajnoha> |
| lvm2 sub component: | Devices, Filtering and Stacking | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | high | CC: | adevolder, agk, amureini, aperotti, cmarthal, dmoessne, fdeutsch, gklein, heinzm, jbrassow, lherbolt, luvilla, lvm-team, mjuricek, mkalinin, mkarg, mnavrati, msnitzer, nsoffer, pdwyer, prajnoha, prockai, pzhukov, rhodain, teigland, zkabelac |
| Version: | 7.2 | Keywords: | ZStream |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.130-5.el7_2.5 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the regular expressions filter was incorrectly positioned within other filters. As a consequence, running certain LVM2 commands, such as vgck and pvs, caused all block devices to be open for scanning, even though the settings in the lvm.conf file specified only devices that were allowed for scanning, while all other devices were supposed to be rejected. With this update, the regular expressions filter is evaluated first, before any other filters that need to open a device. As a result, only the desired devices are opened for scanning in the described situation.
|
Story Points: | --- |
| Clone Of: | 1344206 | Environment: | |
| Last Closed: | 2016-06-28 16:31:59 UTC | Type: | --- |
| 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: | 1344206 | ||
| Bug Blocks: | 1346012 | ||
|
Description
Marcel Kolaja
2016-06-14 07:42:25 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-2016:1349 |