Hide Forgot
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.