Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 516609

Summary: Mirrored LV with corelog is not shown properly
Product: Red Hat Enterprise Linux 5 Reporter: Marek Grac <mgrac>
Component: system-config-lvmAssignee: Marek Grac <mgrac>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: agk, bbrock, cluster-maint, dwysocha, mbroz, prockai
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: system-config-lvm-1.1.5-2.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 08:42: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:    
Bug Blocks: 494127    
Attachments:
Description Flags
Proposed patch none

Description Marek Grac 2009-08-10 17:17:32 UTC 
Description of problem:

Bug similar to #440076 (already fixed in RHEL5). 


How reproducible:

Create mirrored lv with corelog 

  
Actual results:

Run s-c-lvm and you won't see picture of this volume group on the right. Also you will receive python traceback.

Expected results:

Show it as any other volume group
Comment 1 Marek Grac 2009-08-10 17:18:36 UTC 
Created attachment 356926 [details]
Proposed patch
Comment 8 errata-xmlrpc 2010-03-30 08:42:59 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-0267.html