RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1286292 - rgmanager - pacemaker LVM RA disparity in an ability to further limit the scope to specific LV on top of given VG
Summary: rgmanager - pacemaker LVM RA disparity in an ability to further limit the sco...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.2
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-27 20:19 UTC by Jan Pokorný [poki]
Modified: 2017-11-13 12:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-21 11:58:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jan Pokorný [poki] 2015-11-27 20:19:06 UTC 
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).
Comment 2 Jan Pokorný [poki] 2015-11-27 20:23:13 UTC 
This possibly applies to new RHEL 6 minor releases as well.
Comment 4 Jan Pokorný [poki] 2015-11-30 15:15:23 UTC 
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.
Comment 5 Jan Pokorný [poki] 2015-12-01 18:45:48 UTC 
Re clufter:
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.
Comment 7 Oyvind Albrigtsen 2015-12-23 14:14:58 UTC 
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
Comment 8 Jan Pokorný [poki] 2016-10-20 17:51:01 UTC 
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. 

then?

Any idea why there's such a contradiction or if I am missing something,
Oyvind?

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.
Note You need to log in before you can comment on or make changes to this bug.