fence_scsi "Cannot get registration keys" on VMware environment
Issue
-
When Red Hat
pacemakerclusters usevmdkshared disks in VMware, thefence_scsiorfence_mpathfence devices fails duringunfencingprocess -
The
pcs status --fulloutput reports fencing failures:Failed Fencing Actions: * unfencing of node1 failed: delegate=, client=crmd.2220, origin=node2 * unfencing of node2 failed: delegate=, client=crmd.2220, origin=node1 -
The
/var/log/messagesreports " ERROR: Cannot get registration keys":stonith-ng[<PID>]: notice: fence_scsi_on_1:stderr [ 2024-05-09 19:17:05,088 ERROR: Cannot get registration keys ] stonith-ng[<PID>]: notice: fence_scsi_on_1:stderr [ ] stonith-ng[<PID>]: notice: fence_scsi_on_1:stderr [ 2024-05-09 19:17:05,088 ERROR: Please use '-h' for usage ] stonith-ng[<PID>]: notice: fence_scsi_on_1:stderr [ ] stonith-ng[<PID>]: error: Operation 'on' [<PID>] (call 22 from crmd.2220) for host 'node2' with device 'fence_scsi' returned: -201 (Generic Pacemaker error) stonith-ng[<PID>]: notice: Couldn't find anyone to fence (on) node1 with any device stonith-ng[<PID>]: notice: Couldn't find anyone to fence (on) node2 with any device stonith-ng[<PID>]: error: Operation 'on' targeting node2 on <no-one> for crmd.2220@node1: No route to host
Environment
- Red Hat Enterprise Linux Server 7, 8, 9 with the High Availability or Resilient Storage Add-Ons
- VMware environment using Storage Virtualization Software (
vSAN) - SCSI Persistent Reservation Fencing (
fence_scsi)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.