# 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 /var/run/cluster/fence_scsi.key rafaeldtinoco@clubionic01:~$ cat /var/run/cluster/fence_scsi.key 62ed0000 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1864404 Title: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
