Oracle Linux Pacemaker/Corosync : A New Fence SCSI Device Fails When It's Starting Up (Doc ID 2618767.1)

Last updated on SEPTEMBER 17, 2021

Applies to:

Symptoms

Trying to create a Stonith SCSI resource (fence_scsi) for a Pacekamer/Corosync fails with "persistent reserve out: SCSI status: Reservation Conflict".

[root@<HOSTNAME>~]# mpathpersist --out --register --param-sark=0xABC123 /dev/mapper/mpathf
persistent reserve out: scsi status: Reservation Conflict <<<<<<<<<<<<
PR out: command failed

 
Also, The Stonith resource is not able to  start:

[root@<HOSTNAME>~]# pcs status
Cluster name: cluster-1
Stack: corosync
Current DC: server1 (version 1.1.20-5.el7-3c4c782f70) - partition with quorum
Last updated: Wed Nov 27 09:13:02 2019
Last change: Wed Nov 27 09:00:25 2019 by root via cibadmin on server1

2 nodes configured
1 resource configured

Online: [ <HOSTNAME1> <HOSTNAME2>]

Full list of resources:

scsi (stonith:fence_scsi): Stopped <<<<<<<<<<<<

Failed Resource Actions:
* scsi_start_0 on server1 'unknown error' (1): call=27, status=Error, exitreason='',
last-rc-change='Wed Nov 27 09:00:25 2019', queued=0ms, exec=1263ms <<<<<<<<<<<<
* scsi_start_0 on server2 'unknown error' (1): call=27, status=Error, exitreason='',
last-rc-change='Wed Nov 27 09:00:26 2019', queued=0ms, exec=1276ms <<<<<<<<<<<<

Daemon Status:
corosync: active/enabled
pacemaker: active/enabled
pcsd: active/enabled

Changes

 New setup issues.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.