On 24/07/19 12:33 -0500, Ken Gaillot wrote:
> A recent bugfix (clbz#5386) brings up a question.
>
> A node may receive notification of its own fencing when fencing is
> misconfigured (for example, an APC switch with the wrong plug number)
> or when fabric fencing is used that doesn't cut the
On Thu, Jul 25, 2019 at 3:20 AM Ondrej wrote:
>
> Is there any plan on getting this also into 1.1 branch?
> If yes, then I would be for just introducing the configuration option in
> 1.1.x with default to 'stop'.
>
+1 for back porting it from someone who just recently hit this
(puzzling)
On 7/25/19 1:33 AM, Ken Gaillot wrote:
> Hi all,
>
> A recent bugfix (clbz#5386) brings up a question.
>
> A node may receive notification of its own fencing when fencing is
> misconfigured (for example, an APC switch with the wrong plug number)
> or when fabric fencing is used that doesn't
On 7/25/19 2:33 AM, Ken Gaillot wrote:
Hi all,
A recent bugfix (clbz#5386) brings up a question.
A node may receive notification of its own fencing when fencing is
misconfigured (for example, an APC switch with the wrong plug number)
or when fabric fencing is used that doesn't cut the cluster
Hi all,
A recent bugfix (clbz#5386) brings up a question.
A node may receive notification of its own fencing when fencing is
misconfigured (for example, an APC switch with the wrong plug number)
or when fabric fencing is used that doesn't cut the cluster network
(for example, fence_scsi).
