Red Hat Bugzilla – Bug 204076
Installing of lvm2-cluster modifies lvm.conf file
Last modified: 2015-01-07 19:14:16 EST
Description of problem:
Should really be filed against the lvm2-cluster package, but that's not in the
listing so figured this would get to the right place. As part of the %post for
lvm2-cluster, we're running:
/usr/sbin/lvmconf --enable-cluster --lockinglibdir /usr/lib
which has the net effect of modifying the locking_type in the /etc/lvm/lvm.conf
file. We should think about one of a couple of things:
1) add another option to "lvmconf" which indicates at install-time that an
/etc/lvm/lvm.conf.rpmnew (or something) file should be created as opposed to
modifying the running lvm.conf file
2) don't run the "lvmconf" command as part of the %post; is there really a need
to bring up clvm during the install?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
We do want to run it at install time to ensure the conf file holds the correct
settings (incl. setting the library directory). But placing the changes into
rpmnew would make more sense. However this is still not sufficient: we risk
people not realising they need to change the file before using clustering and
believing they're clustered when they aren't. Perhaps the clvmd init script
needs to fail if clustering is not enabled in the live lvm.conf file.
Too funny . . . when I was writing the original comment, there were three
suggestions I was going to make . . . then I forgot one. That was to smarten up
the initscript to ensure the lvm.conf file was "correct."
*** Bug 203922 has been marked as a duplicate of this bug. ***
We don't distinguish bugs beta vs. live at the moment, and 'lvm2-cluster'
package is called 'clvm' in bugzilla for historic reasons and comes under RHCS
not RHEL. It's about time we decided to change this...
Renamed 'clvm' to 'lvm2-cluster'.
Well I've just rebuilt lvm2-cluster so that it no longer touches the
So to enable clustering in their lvm2 configuration after installing this
package, people just now need to run:
That should solve the urgent problem.
(initscript checks will have to wait till we've more time.)
beta-blocker because of bug 204793 dependency
Fix confirmed with lvm2-cluster-2.02.12-7.el5 which is included in the latest
Moving all RHCS ver 5 bugs to RHEL 5 so we can remove RHCS v5 which never existed.