Bug 802326 - Detect and use proper path for lvm binary in 69-dm-lvmetad.rules
Summary: Detect and use proper path for lvm binary in 69-dm-lvmetad.rules
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.3
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Peter Rajnoha
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-12 10:01 UTC by Peter Rajnoha
Modified: 2012-06-20 15:02 UTC (History)
11 users (show)

Fixed In Version: lvm2-2.02.95-2.el6
Doc Type: Bug Fix
Doc Text:
No documentation needed.
Clone Of:
Environment:
Last Closed: 2012-06-20 15:02:36 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0962 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2012-06-19 21:12:11 UTC

Description Peter Rajnoha 2012-03-12 10:01:23 UTC 
We can't use 'DM_SBIN_PATH' in lvmetad udev rules. This one is set only for dm devices but not for all block devices - the pvscan is run on all relevant block devices and hence the path needs to be always detected properly.

Patch: https://www.redhat.com/archives/lvm-devel/2012-March/msg00090.html
Comment 1 Peter Rajnoha 2012-03-12 10:02:40 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No documentation needed.
Comment 6 errata-xmlrpc 2012-06-20 15:02:36 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.

http://rhn.redhat.com/errata/RHBA-2012-0962.html
Note You need to log in before you can comment on or make changes to this bug.