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 1064512 - OCF script for managing clvmd with pacemaker
Summary: OCF script for managing clvmd with pacemaker
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
urgent
urgent
Target Milestone: rc
: ---
Assignee: David Vossel
QA Contact: Cluster QE
URL:
Whiteboard:
: 1058400 (view as bug list)
Depends On:
Blocks: 1065498
TreeView+ depends on / blocked
 
Reported: 2014-02-12 18:30 UTC by David Vossel
Modified: 2014-06-17 23:56 UTC (History)
7 users (show)

Fixed In Version: resource-agents-3.9.5-25.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1065498 (view as bug list)
Environment:
Last Closed: 2014-06-13 12:51:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description David Vossel 2014-02-12 18:30:44 UTC 
Description of problem:

We have to take special consideration when managing clvmd with pacemaker. Because of this, an OCF style clvmd resource-agent is the best way to maintain this logic.

We need to introduce the clvmd OCF script and document it the only way to manage clvmd instances within the cluster.
Comment 1 David Vossel 2014-02-12 18:31:07 UTC 
This OCF script already exists upstream as a part of this pull request. https://github.com/ClusterLabs/resource-agents/pull/382
Comment 2 David Vossel 2014-02-12 22:35:49 UTC 
*** Bug 1058400 has been marked as a duplicate of this bug. ***
Comment 3 David Vossel 2014-02-14 00:34:29 UTC 
I have updated the clvmd agent to be able to manage the cmirrord daemon using the 'with_cmirrord' option.
Comment 4 David Vossel 2014-02-14 07:10:09 UTC 
I've created a test build with the new clvmd (ocf:heartbeat:clvmd) agent in it. 
https://brewweb.devel.redhat.com/taskinfo?taskID=7056668

I sanity checked the agent works using this phd scenario.
https://github.com/davidvossel/phd/blob/master/scenarios/gfs2-clvmd.scenario

-- Vossel
Comment 5 David Vossel 2014-02-18 18:57:54 UTC 
For a unit test, we are trying to solve the problems introduced in this issue, https://bugzilla.redhat.com/show_bug.cgi?id=1058400

From the description "While running revolver on an 8 node cluster, shooting 3 nodes sometimes ends up with inactive volumes on one or more nodes and failed mounts."

We should be able to increase the start timeout to something like 90-120 seconds for the clvmd now, allowing us to avoid the hardcoded 30s timeout imposed previously by the clvmd init script (which was part of what was causing the problem)

So, run the revolver scenario, but before that set 'op start timeout=120s' for the clvmd resource.  During the testing try and get a feeling for what we should recommend that timeout value to be in the documentation.

-- Vossel
Comment 7 David Vossel 2014-02-24 18:54:20 UTC 
Note that I have changed the name of the new clvmd agent from ocf:heartbeat:clvmd to ocf:heartbeat:clvm.  This is to avoid complications involved with having an agent named the exact same name as the binary the agent manages.
Comment 8 Nate Straz 2014-03-18 13:45:03 UTC 
I'm making it through revolver with the new clvm resource agent without issues from clvmd or pacemaker.  Marking this verified.
Comment 9 Ludek Smid 2014-06-13 12:51:35 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.