Bug 773372

Summary:	any change to lvm.conf results in an invalid HA configuration
Product:	Red Hat Enterprise Linux 5	Reporter:	Corey Marthaler <cmarthal>
Component:	rgmanager	Assignee:	Jonathan Earl Brassow <jbrassow>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.8	CC:	agk, cluster-maint, dwysocha, edamato, heinzm, jbrassow, jpallich, lhh, mbroz, mjuricek, nperic, prajnoha, prockai, rmccabe, slevine, syeghiay, thornber, zkabelac
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	rgmanager-2.0.52-32.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	728365
Clones:	817060 818063 (view as bug list)		Environment:
Last Closed:	2013-01-08 07:05:18 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:	728365
Bug Blocks:	807971, 817060, 818063

Description Corey Marthaler 2012-01-11 16:56:40 UTC

+++ This bug was initially created as a clone of Bug #728365 +++

Description of problem:
This may end up being a WORKASINTENDED bug, but I think it's worth documenting. When setting up the "tag" method of HA LVM, it's required that a mkinirtd be run after the volume_list tag section is edited. A check when starting the service verifies that the initrd is newer then the lvm.conf file. The problem comes when any additional changes are made to the lvm.conf file. This causes the HA LVM service start up to start to fail. Should we really require a mkinitrd and potential reboot after each lvm.conf change? If so it should be added to the documentation.


Aug  4 13:51:34 hayes-01 rgmanager[5516]: I am node #1
Aug  4 13:51:34 hayes-01 rgmanager[5516]: Resource Group Manager Starting
Aug  4 13:51:34 hayes-01 rgmanager[5516]: Loading Service Data
Aug  4 13:51:38 hayes-01 rgmanager[5516]: Initializing Services
Aug  4 13:51:38 hayes-01 rgmanager[6347]: [fs] stop: Could not match /dev/HAYES1/ha with a real device
Aug  4 13:51:38 hayes-01 rgmanager[5516]: stop on fs "fs1" returned 2 (invalid argument(s))
Aug  4 13:51:38 hayes-01 rgmanager[6370]: [fs] stop: Could not match /dev/HAYES2/ha with a real device
Aug  4 13:51:38 hayes-01 rgmanager[5516]: stop on fs "fs2" returned 2 (invalid argument(s))
Aug  4 13:51:40 hayes-01 rgmanager[6455]: [lvm] HA LVM:  Improper setup detected
Aug  4 13:51:40 hayes-01 rgmanager[6463]: [lvm] HA LVM:  Improper setup detected
Aug  4 13:51:41 hayes-01 rgmanager[6496]: [lvm] * initrd image needs to be newer than lvm.conf
Aug  4 13:51:41 hayes-01 rgmanager[6509]: [lvm] * initrd image needs to be newer than lvm.conf
Aug  4 13:51:41 hayes-01 rgmanager[6540]: [lvm] WARNING: An improper setup can cause data corruption!
Aug  4 13:51:41 hayes-01 rgmanager[6551]: [lvm] WARNING: An improper setup can cause data corruption!


[root@hayes-03 ~]# clustat
Cluster Status for HAYES @ Thu Aug  4 15:21:40 2011
Member Status: Quorate

 Member Name   ID   Status
 ------ ----   ---- ------
 hayes-01         1 Online, rgmanager
 hayes-02         2 Online, rgmanager
 hayes-03         3 Online, Local, rgmanager

 Service Name     Owner (Last)   State
 ------- ----     ----- ------   -----
 service:halvm1   (hayes-02)     failed
 service:halvm2   (hayes-02)     failed

 

Version-Release number of selected component (if applicable):
2.6.32-174.el6.x86_64

lvm2-2.02.83-3.el6    BUILT: Fri Mar 18 09:31:10 CDT 2011
lvm2-libs-2.02.83-3.el6    BUILT: Fri Mar 18 09:31:10 CDT 2011
lvm2-cluster-2.02.83-3.el6    BUILT: Fri Mar 18 09:31:10 CDT 2011
udev-147-2.35.el6    BUILT: Wed Mar 30 07:32:05 CDT 2011
device-mapper-1.02.62-3.el6    BUILT: Fri Mar 18 09:31:10 CDT 2011
device-mapper-libs-1.02.62-3.el6    BUILT: Fri Mar 18 09:31:10 CDT 2011
device-mapper-event-1.02.62-3.el6    BUILT: Fri Mar 18 09:31:10 CDT 2011
device-mapper-event-libs-1.02.62-3.el6    BUILT: Fri Mar 18 09:31:10 CDT 2011
cmirror-2.02.83-3.el6    BUILT: Fri Mar 18 09:31:10 CDT 2011

--- Additional comment from slevine on 2011-08-15 13:48:00 EDT ---

Do we know yet whether we need to clone this as a documentation bug for RHEL 6.2 (and 5.8)?

--- Additional comment from pm-rhel on 2011-10-07 11:55:17 EDT ---

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 1 Corey Marthaler 2012-01-11 17:00:06 UTC

This exists in rhel5 as well. I updated the mirror allocation policy and sure enough, the next time I started rgmanager, it complained of a bad configuration.


Jan 11 10:53:22 taft-03 clurgmgrd: [9112]: <err> HA LVM:  Improper setup detected 
Jan 11 10:53:22 taft-03 clurgmgrd: [9112]: <err> - initrd image needs to be newer than lvm.conf 
Jan 11 10:53:22 taft-03 clurgmgrd: [9112]: <err> WARNING: An improper setup can cause data corruption! 2.6.18-301.el5


lvm2-2.02.88-5.el5    BUILT: Fri Dec  2 12:25:45 CST 2011
lvm2-cluster-2.02.88-5.el5    BUILT: Fri Dec  2 12:48:37 CST 2011
device-mapper-1.02.67-2.el5    BUILT: Mon Oct 17 08:31:56 CDT 2011
device-mapper-event-1.02.67-2.el5    BUILT: Mon Oct 17 08:31:56 CDT 2011
cmirror-1.1.39-14.el5    BUILT: Wed Nov  2 17:25:33 CDT 2011
kmod-cmirror-0.1.22-3.el5    BUILT: Tue Dec 22 13:39:47 CST 2009

Comment 2 RHEL Program Management 2012-04-02 10:35:06 UTC

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 4 Jonathan Earl Brassow 2012-04-23 22:05:59 UTC

I'm going to make it so that the script warns the user, but doesn't error out.  It is important that the initrd be updated with lvm.conf changes.  However, making HA LVM fail because of it is overkill.

Comment 13 errata-xmlrpc 2013-01-08 07:05:18 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-2013-0026.html