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 1608986 - lvmlockd: new resource agent
Summary: lvmlockd: new resource agent
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-26 16:17 UTC by Corey Marthaler
Modified: 2023-09-07 19:16 UTC (History)
11 users (show)

Fixed In Version: resource-agents-4.1.1-10.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 11:39:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3067 0 None None None 2018-08-03 14:16:03 UTC
Red Hat Knowledge Base (Solution) 3551691 0 None None None 2018-08-03 14:14:20 UTC
Red Hat Product Errata RHBA-2018:3278 0 None None None 2018-10-30 11:40:15 UTC

Description Corey Marthaler 2018-07-26 16:17:20 UTC 
Description of problem:
This is for the new rhel7.6 lvmlockd resource-agent only.

This feature is currently included with resource-agents-4.1.1-2.el7.x86_64.

To test, the whole of the lvmlockd lvm suite will be run using pacemaker and this agent to control lvmlockd. In addition resource specific operations will be tried as well (recover, relocation, etc).

# set up:
Setting up and starting dlm on
pcs property set no-quorum-policy=freeze
pcs resource create dlm_for_lvmlockd controld op monitor interval=30s clone interleave=true ordered=true
pcs resource create lvmlockd lvmlockd op monitor interval=30s clone interleave=true ordered=true

# QA-lvmlockd-activation is just a hack script to ensure shared activation of existing lvmlockd volumes at system start up time
pcs resource create QA-lvmlockd-activation systemd:QA-lvmlockd-activation op monitor interval=30s clone interleave=true ordered=true
pcs constraint order set dlm_for_lvmlockd-clone lvmlockd-clone QA-lvmlockd-activation-clone sequential=true
Running cleanup to fix any potential timing issues during setup
pcs resource cleanup

pcs cluster enable


[root@mckinley-01 ~]# pcs status
Cluster name: MCKINLEY
Stack: corosync
Current DC: mckinley-02 (version 1.1.19-3.el7-c3c624ea3d) - partition with quorum
Last updated: Thu Jul 26 11:16:44 2018
Last change: Thu Jul 26 11:14:14 2018 by root via cibadmin on mckinley-01

3 nodes configured
10 resources configured

Online: [ mckinley-01 mckinley-02 mckinley-03 ]

Full list of resources:

 mckinley-apc   (stonith:fence_apc):    Started mckinley-01
 Clone Set: dlm_for_lvmlockd-clone [dlm_for_lvmlockd]
     Started: [ mckinley-01 mckinley-02 mckinley-03 ]
 Clone Set: lvmlockd-clone [lvmlockd]
     Started: [ mckinley-01 mckinley-02 mckinley-03 ]
 Clone Set: QA-lvmlockd-activation-clone [QA-lvmlockd-activation]
     Started: [ mckinley-01 mckinley-02 mckinley-03 ]

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/disabled



Version-Release number of selected component (if applicable):
resource-agents-4.1.1-2.el7.x86_64    BUILT: Tue 03 Jul 2018 07:32:31 AM CDT
lvm2-2.02.179-4.el7    BUILT: Tue Jun 26 08:35:45 CDT 2018
lvm2-libs-2.02.179-4.el7    BUILT: Tue Jun 26 08:35:45 CDT 2018
lvm2-cluster-2.02.179-4.el7    BUILT: Tue Jun 26 08:35:45 CDT 2018
lvm2-lockd-2.02.179-4.el7    BUILT: Tue Jun 26 08:35:45 CDT 2018
lvm2-python-boom-0.9-3.el7    BUILT: Tue Jun 26 08:43:24 CDT 2018
cmirror-2.02.179-4.el7    BUILT: Tue Jun 26 08:35:45 CDT 2018
device-mapper-1.02.148-4.el7    BUILT: Tue Jun 26 08:35:45 CDT 2018
device-mapper-libs-1.02.148-4.el7    BUILT: Tue Jun 26 08:35:45 CDT 2018
device-mapper-event-1.02.148-4.el7    BUILT: Tue Jun 26 08:35:45 CDT 2018
device-mapper-event-libs-1.02.148-4.el7    BUILT: Tue Jun 26 08:35:45 CDT 2018
device-mapper-persistent-data-0.7.3-3.el7    BUILT: Tue Nov 14 05:07:18 CST 2017
Comment 17 Corey Marthaler 2018-09-25 15:45:53 UTC 
Marking the new *lvmlockd* resource agent verified.  We used this agent to manage lvmlockd across the cluster during 7.6 lvmlockd regression testing.

resource-agents-4.1.1-10.el7.x86_64
Comment 19 errata-xmlrpc 2018-10-30 11:39:24 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3278
Note You need to log in before you can comment on or make changes to this bug.