A way to workaround this issue is the following... in a 3 node cluster you can do this:
# node01
create a file /etc/fence_scsi.key containing: 62ed0000
# node02
create a file /etc/fence_scsi.key containing: 62ed0001
# node03
create a file /etc/fence_scsi.key containing: 62ed0002
In all 3 nodes create a file /etc/tmpfiles.d/fence_scsi.conf containing:
L /var/run/cluster/fence_scsi.key - - - - /etc/fence_scsi.key
This will make systemd to create a symlink /var/run/cluster/fence_scsi.key pointing to your /etc/fence_scsi.key file and will allow fence_scsi agent to use that file to do its SCSI persistent reservations.
After creating those files reboot all the nodes and check if the file got created after boot:
rafaeldtinoco@clubionic01:~$ ls /var/run/cluster/fence_scsi.key
/var/run/cluster/fence_scsi.key
# WORKAROUND:
A way to workaround this issue is the following... in a 3 node cluster you can do this:
# node01
create a file /etc/fence_scsi.key containing: 62ed0000
# node02
create a file /etc/fence_scsi.key containing: 62ed0001
# node03
create a file /etc/fence_scsi.key containing: 62ed0002
In all 3 nodes create a file /etc/tmpfiles. d/fence_ scsi.conf containing:
L /var/run/ cluster/ fence_scsi. key - - - - /etc/fence_scsi.key
This will make systemd to create a symlink /var/run/ cluster/ fence_scsi. key pointing to your /etc/fence_scsi.key file and will allow fence_scsi agent to use that file to do its SCSI persistent reservations.
After creating those files reboot all the nodes and check if the file got created after boot:
rafaeldtinoco@ clubionic01: ~$ ls /var/run/ cluster/ fence_scsi. key cluster/ fence_scsi. key
/var/run/
rafaeldtinoco@ clubionic01: ~$ cat /var/run/ cluster/ fence_scsi. key
62ed0000