This bug was serving me as a base to track tested fencing agents in
Bionic, Focal and Groovy. No more reason to keep it opened, closing it
as invalid.
** Changed in: fence-agents (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: fence-agents (Ubuntu Eoan)
Status: Won't
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: fence-agents (Ubuntu Eoan)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: fence-agents (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864404
Title:
fence_scsi and fence_mpath configuration issues (e.g.
Turns out pacemaker.service already declares:
# Some OCF resources may have dependencies that aren't managed by the cluster;
# these must be started before Pacemaker and stopped after it. The
# resource-agents package provides this target, which lets system adminstrators
# add drop-ins for those
For the previous case (fence_mpath in Groovy), when rebooting the fenced
node automatically (by watchdog monitoring /dev/watchdog from softdog
module) perhaps pacemaker systemd unit should start only AFTER iscsid,
open-iscsi AND multipath-tools were already started. This would give
time to all
