This bug was fixed in the package fence-agents - 4.0.25-2ubuntu1.1
---
fence-agents (4.0.25-2ubuntu1.1) bionic; urgency=medium
* Fix fence_scsi agent arguments and node detection (LP: #1865523):
+ d/p/lp1865523-01-fencing-add-consistency-cmdline-stdin.patch AND
+ d/p/lp18655
Okay, I had verified this from the day in it landed in -proposed. It is
working as expected (https://discourse.ubuntu.com/t/ubuntu-high-
availability-corosync-pacemaker-shared-disk-environments/). I'm marking
this as verification-done as it has stayed in -proposed for sometime now
and no bad feedba
Hello Rafael, or anyone else affected,
Accepted fence-agents into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/fence-
agents/4.0.25-2ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Description changed:
OBS: I have split this bug into 2 bugs:
- fence-agents (this) and pacemaker (LP: #1866119)
SRU: fence-agents
[Impact]
* fence_scsi is not currently working in a share disk environment
* all clusters relying in fence_scsi and/or fence_scsi
** Description changed:
OBS: I have split this bug into 2 bugs:
- - fence-agents (this) and pacemaker (LP: #1866119)
+ - fence-agents (this) and pacemaker (LP: #1866119)
SRU: fence-agents
[Impact]
* fence_scsi is not currently working in a share disk environment