Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

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.

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