[Bug 1864404] Re: fence_scsi and fence_mpath configuration issues (e.g. /var/run/cluster/fence_scsi.key)
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 Fix => Invalid ** Changed in: fence-agents (Ubuntu Focal) Status: Confirmed => Invalid ** Changed in: fence-agents (Ubuntu) Status: In Progress => Invalid -- 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. /var/run/cluster/fence_scsi.key) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] Re: fence_scsi and fence_mpath configuration issues (e.g. /var/run/cluster/fence_scsi.key)
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. https://bugs.launchpad.net/bugs/1864404 Title: fence_scsi and fence_mpath configuration issues (e.g. /var/run/cluster/fence_scsi.key) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] Re: fence_scsi and fence_mpath configuration issues (e.g. /var/run/cluster/fence_scsi.key)
** 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. /var/run/cluster/fence_scsi.key) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] Re: fence_scsi and fence_mpath configuration issues (e.g. /var/run/cluster/fence_scsi.key)
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 dependencies. After=resource-agents-deps.target Wants=resource-agents-deps.target Meaning that we just have to add OCF resources (or fencing agents) dependencies to this target... but it does not work =). I'm discussing with upstream this: https://lists.clusterlabs.org/pipermail/users/2020-June/027207.html -- 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. /var/run/cluster/fence_scsi.key) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] Re: fence_scsi and fence_mpath configuration issues (e.g. /var/run/cluster/fence_scsi.key)
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 paths to be online. PROBLEM: paths being added might take more time than the service to tell systemd it is ON. Note: Don't fully trust automated reboots for unfencing a node with mpath, do it manually. -- 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. /var/run/cluster/fence_scsi.key) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
