Bug 582330 - rpm -V fails because of changed lvm.conf
Summary: rpm -V fails because of changed lvm.conf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lvm2
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Milan Broz
QA Contact: Corey Marthaler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-14 16:36 UTC by Corey Marthaler
Modified: 2013-03-01 04:09 UTC (History)
9 users (show)

Fixed In Version: lvm2-2.02.73-1.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-13 22:41:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0052 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2011-01-12 17:15:25 UTC

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


Note You need to log in before you can comment on or make changes to this bug.