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 582330

Summary:	rpm -V fails because of changed lvm.conf
Product:	Red Hat Enterprise Linux 5	Reporter:	Corey Marthaler <cmarthal>
Component:	lvm2	Assignee:	Milan Broz <mbroz>
Status:	CLOSED ERRATA	QA Contact:	Corey Marthaler <cmarthal>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.5	CC:	agk, dwysocha, heinzm, jbrassow, jkortus, joe.thornber, mbroz, prockai, pvrabec
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	lvm2-2.02.73-1.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-01-13 22:41:14 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:

Description Corey Marthaler 2010-04-14 16:36:05 UTC

Description of problem:
[root@hayes-01 ~]# rpm -V lvm2
S.5....T  c /etc/lvm/lvm.conf
[root@hayes-01 ~]# echo $?
1


Version-Release number of selected component (if applicable):
lvm2-2.02.56-9.el5

Comment 1 Milan Broz 2010-04-14 18:13:08 UTC

it means that
 S - size of file differs
 5 - MD5 sum differs
 T - mtime differs

Because lvm2-cluster calls in the post
/usr/sbin/lvmconf --lockinglibdir %{_libdir}

it causes this change:
@@ -220,6 +220,7 @@

 # Miscellaneous global LVM2 settings
 global {
+    library_dir = "/usr/lib"

     # The file creation mask for any files and directories created.
     # Interpreted as octal if the first digit is zero.


This change is useless now. But it is nothing new, I don't think it is blocker for z-stream release, anyway we should clean lvm2-cluster spec in 5.6 release.
(when installing lvm2-cluster, you want probably change locking_type too)

Updating only lvm2 is OK.

Comment 2 Alasdair Kergon 2010-04-14 18:26:56 UTC

Refer to the TPS people I think - the 'c' means config file.  It's quite reasonable for an installed config file to get updated!

Comment 3 Jaroslav Kortus 2010-04-15 09:44:18 UTC

<rbiba> %config(noreplace) %verify(not md5 mtime size)  ...

Please add this to spec file. As this is trivial fix in spec file, I would support including it before releasing any new package. Otherwise we'll be hitting this over and over again.

This is not TPS problem, TPS just revealed it.

Comment 4 Milan Broz 2010-04-15 10:14:25 UTC

It will be fixed in 5.6, not in this release, sorry.

If it is problem, I really must ask why QA found it in 5.5.z and not in 5.0....

Comment 5 Milan Broz 2010-04-15 10:19:40 UTC

(BTW fix also must also include modification of lvmconf and add the library_dir in base install/or remove it completely. Not run it in lvm2-cluster %post, no idea why it is done this way - we do not use external locking library in RHEL5 anyway. It is proibably some RHEL4 relic)

Comment 8 Milan Broz 2010-08-30 10:39:37 UTC

Fix in lvm2-2.02.73-1.el5.

Comment 10 Corey Marthaler 2010-11-01 22:17:03 UTC

[root@grant-01 ~]# rpm -V lvm2
[root@grant-01 ~]# echo $?
0

Fix verified in lvm2-2.02.74-1.el5.

Comment 12 errata-xmlrpc 2011-01-13 22:41:14 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-2011-0052.html