Yes, I have just confirmed that in Bionic, the fence_scsi fails to
create the /var/run/cluster by itself:
rafaeldtinoco@clubionic01:~$ crm configure
crm(live)configure# primitive fence_clufocal stonith:fence_scsi \
> params pcmk_host_list="10.250.98.10 10.250.98.11 10.250.98.12"
devices="/dev/sdc" \
> meta provides=unfencing
crm(live)configure# commit
caused:
Failed Actions:
* fence_clufocal_start_0 on clubionic01 'unknown error' (1): call=8,
status=Error, exitreason='',
last-rc-change='Mon Feb 24 19:31:43 2020', queued=0ms, exec=1102ms
* fence_clufocal_start_0 on clubionic02 'unknown error' (1): call=6,
status=Error, exitreason='',
last-rc-change='Mon Feb 24 19:31:44 2020', queued=0ms, exec=1096ms
and, in logs, caused:
Feb 24 19:29:56 clubionic02 systemd[1]: Started Pacemaker High Availability
Cluster Manager.
Feb 24 19:29:56 clubionic02 pacemakerd[1787]: notice: Additional logging
available in /var/log/pacemaker.log
Feb 24 19:29:56 clubionic02 pacemakerd[1787]: notice: Switching to
/var/log/corosync/corosync.log
Feb 24 19:29:56 clubionic02 pacemakerd[1787]: notice: Additional logging
available in /var/log/corosync/corosync.log
Feb 24 19:31:44 clubionic02 fence_scsi[1840]: Failed: Cannot open file
"/var/run/cluster/fence_scsi.key"
Feb 24 19:31:44 clubionic02 fence_scsi[1840]: Please use '-h' for usage
Feb 24 19:31:45 clubionic02 fence_scsi[1846]: Failed: Cannot open file
"/var/run/cluster/fence_scsi.key"
Feb 24 19:31:45 clubionic02 fence_scsi[1846]: Please use '-h' for usage
--
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:
fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not
exist) after nodes are rebooted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions
--
Ubuntu-server-bugs mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
