Bug 592220 - vgscan (with cluster locking) doesn't remove filtered devices from .cache after filter change
Summary: vgscan (with cluster locking) doesn't remove filtered devices from .cache aft...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lvm2-cluster
Version: 5.5
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Milan Broz
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On: 591861
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-14 09:48 UTC by RHEL Program Management
Modified: 2013-03-01 04:09 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-21 07:35:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2010:0432 0 normal SHIPPED_LIVE lvm2-cluster bug fix update 2010-05-21 07:34:56 UTC

Description RHEL Program Management 2010-05-14 09:48:46 UTC 
This bug has been copied from bug #591861 and has been proposed
to be backported to 5.5 z-stream (EUS).
Comment 4 Milan Broz 2010-05-14 13:33:37 UTC 
Fix commited in build
lvm2-2.02.56-8.el5_5.4
lvm2-cluster-2.02.56-7.el5_5.3
Comment 6 Corey Marthaler 2010-05-17 20:22:47 UTC 
Fix verified in lvm2-2.02.56-8.el5_5.4/lvm2-cluster-2.02.56-7.el5_5.3.

I filtered out existing devices, vgscaned, and verified that those devices were removed from the .cache files on all nodes in the cluster. I then did the opposite and verified that those devices reappeared in the .cache file.
Comment 7 errata-xmlrpc 2010-05-21 07:35:02 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

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