Bug 1608986 – lvmlockd: new resource agent

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1608986 - lvmlockd: new resource agent

Summary:	lvmlockd: new resource agent

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	resource-agents (Show other bugs)
Sub Component:
Version:	7.6
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Oyvind Albrigtsen
QA Contact:	cluster-qe@redhat.com
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature, TechPreview

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-07-26 12:17 EDT by Corey Marthaler
Modified:	2018-10-30 07:40 EDT (History)
CC List:	11 users (show)

See Also:
Fixed In Version:	resource-agents-4.1.1-10.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-10-30 07:39:24 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	3067	None	None	None	2018-08-03 10:16 EDT
Red Hat Knowledge Base (Solution)	3551691	None	None	None	2018-08-03 10:14 EDT
Red Hat Product Errata	RHBA-2018:3278	None	None	None	2018-10-30 07:40 EDT

Groups: None (edit)

Description Corey Marthaler 2018-07-26 12:17:20 EDT

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 11:45:53 EDT

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 07:39:24 EDT

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.