Bug 1298683

Summary:	fence_zvmip doesn't support pcmk_host_check=dynamic-list
Product:	Red Hat Enterprise Linux 7	Reporter:	Ken Gaillot <kgaillot>
Component:	fence-agents	Assignee:	Marek Grac <mgrac>
Status:	CLOSED WONTFIX	QA Contact:	cluster-qe <cluster-qe>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	cluster-maint
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	s390
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Reason: Allow s390 VMs used as Pacemaker cluster nodes to be migrated to a different LPAR. Result:	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-02 09:35:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ken Gaillot 2016-01-14 17:53:49 UTC

Description of problem: When fence_zvmip is used as a Pacemaker cluster fence agent for an s390 VM, the VM must be statically assigned to an LPAR (host) because fence_zvmip has no way to dynamically determine which LPAR the VM is assigned to.

Version-Release number of selected component (if applicable):


How reproducible: easily


Steps to Reproduce:
1. Configure a pacemaker cluster using s390 VMs as cluster nodes, and fence_zvmip as the fence agent for them.
2. Migrate one of the VMs to a new LPAR.
3. Try to fence the VM.

Actual results: The fencing reports success (because the VM is not on the statically configured LPAR) but the VM is not fenced (because it is now on a different LPAR).


Expected results: Node is fenced.


Additional info: This will require a new API from IBM for retrieving VM/LPAR mappings from the SSI. If fence_zvmip implements the list action, and dynamically chooses the right LPAR to specify to the SSI, pacemaker can be configured with pcmk_host_check=dynamic-list and a single fence device.

Comment 3 RHEL Program Management 2016-06-02 09:35:44 UTC

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.