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 960555 - ocf:redhat:lvm.sh should check volume_list @tag based on clustername not hostname
Summary: ocf:redhat:lvm.sh should check volume_list @tag based on clustername not host...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Vossel
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 883874 1080147
TreeView+ depends on / blocked
 
Reported: 2013-05-07 11:39 UTC by michal novacek
Modified: 2015-08-24 06:35 UTC (History)
4 users (show)

Fixed In Version: resource-agents-3.9.5-5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-16 08:19:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description michal novacek 2013-05-07 11:39:13 UTC 
Description of problem:
ocf:redhat:lvm.sh is checking that "volume_list" contains @tag. It is looking
for the tag according to output of "hostname" command where it should check it
according to cluster name. 

It would seem logical to use the same names for lvm tags AND cluster node names.
In case "hostname" is fqdn in this case ocf:redhat:lvm.sh will not start.

This error message occurs in this case:
...[ <err> HA LVM:  Improper setup detected <err> * @virt-066.cluster-qe.lab.eng.brq.redhat.com missin g from "volume_list" in lvm.conf  ]

Version-Release number of selected component (if applicable):
resource-agents-3.9.5-4.el7.x86_64

Expected results:
lvm resource agent checking volume_list @tag according to clustername not hostname.

Additional info:
When talking about hostnames:
	fqdn: virt-066.cluster-qe.lab.eng.brq.redhat.com 
	short name: virt-066
Comment 2 David Vossel 2013-06-18 17:51:46 UTC 
This agent no longer requires any sort of hostname checking to be done to use the exclusive activation with tags.

The heartbeat:LVM agent now performs exclusive activation with tags for rhel7 instead of redhat:lvm.sh. This new agent works slightly different than the rgmanager one.

For exclusive activation to work, the 'exclusive' option must be set to true, and the 'volume_list' in lvm.conf must be defined.  The resource agent doesn't care what the volume_list is defined to as long as the special cluster tag "@pacemaker" and the volume group are not present in the list.  volume_list=[] would even work as a minimal config.

Volume groups are exclusively activated by having the the '@pacemaker' tag added to them by the resource agent.  On activation, the 'volume_list' is overridden by the resource agent to allow volume groups with the '@pacemaker' tag to be enabled. Outside of the resource agent, the volume_list defined in lvm.conf that does _NOT_ container '@pacemaker' or the volume group prevents the volume group from being activated outside of the cluster control. 

The upstream patch below is related to this issue.
https://github.com/ClusterLabs/resource-agents/commit/d7274446d79757d436b972892f00339fc28da13e
Comment 3 Ludek Smid 2014-06-16 08:19:58 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.