** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/fence-agents/+git/fence-agents/+merge/380242
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
** Description changed:
+ 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 + watchdog won't
+ be able to start the fencing agents OR, in worst case scenarios, the
+ fence_scsi
** Description changed:
+ OBS: This bug was originally into LP: #1865523 but it was split.
+
+ SRU: pacemaker
+
+ [Impact]
+
+ * fence_scsi is not currently working in a share disk environment
+
+ * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't
+ be able to
This bug was fixed in the package corosync - 3.0.3-2ubuntu1
---
corosync (3.0.3-2ubuntu1) focal; urgency=medium
* Merge with Debian unstable (LP: #1864087). Remaining changes:
- Skip autopkgtest for unprivileged containers: (LP: 1828228)
- d/t/control: allow stderr and
Public bug reported:
OBS: This bug was originally into LP: #1865523 but it was split.
SRU: pacemaker
[Impact]
* fence_scsi is not currently working in a share disk environment
* all clusters relying in fence_scsi and/or fence_scsi + watchdog won't
be able to start the fencing agents
** No longer affects: pacemaker (Ubuntu)
** No longer affects: pacemaker (Ubuntu Bionic)
** 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
6 matches
Mail list logo
