Red Hat Bugzilla – Bug 1286292
rgmanager - pacemaker LVM RA disparity in an ability to further limit the scope to specific LV on top of given VG
Last modified: 2017-11-13 07:20:03 EST
Currently, clufter (the stacks migration tool) cannot serve users that
had lvm resource defined specifically for selected LV pertaining given VG.
It can also be viewed as sort of a regression: something that was possible
in the past (with lvm.sh rgmanager agent) cannot be done anymore (with
LVM heartbeat agent).
(The same can be extrapolated to the whole set of RAs and their disparity,
i.e., some agents may be missed for those who migrate, but combo of that
agent with specified LV seems quite popular).
This possibly applies to new RHEL 6 minor releases as well.
From clufter perspective, we may may actually just raise the warning if
there is no more LVs for given VG referred to from another agent instance,
and have more accurate failure message otherwise.
I am now of the opinion that failing the conversion whenever lvm/@lv_name
is observed is a sanest way to do as one cannot make any safe conclusions
just by the content of cluster.conf.
The rgmanager resource agent only support 1 LV pr VG, so this is not an issue:
Dec 23 15:08:59 rgmanager [lvm] HA LVM requires Only one logical volume per volume group.
Dec 23 15:08:59 rgmanager [lvm] There are currently 2 logical volumes in test_vg
Dec 23 15:08:59 rgmanager [lvm] Failing HA LVM start of test_vg/test_lv
Returned to this and have to wonder why description of lv_name states:
> Name of the logical volume being managed. This
> parameter is optional if there are more than one
> logical volumes in the volume group to be managed.
Any idea why there's such a contradiction or if I am missing something,
If the description is indeed misleading, we would be better off fixing
it so that I am (and in turn, clufter users) not the only victim.