Hello community, here is the log from the commit of package sbd for openSUSE:Factory checked in at 2016-09-01 14:03:35 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/sbd (Old) and /work/SRC/openSUSE:Factory/.sbd.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "sbd" Changes: -------- --- /work/SRC/openSUSE:Factory/sbd/sbd.changes 2016-07-21 08:19:49.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.sbd.new/sbd.changes 2016-09-01 14:03:36.000000000 +0200 @@ -1,0 +2,6 @@ +Wed Aug 31 15:56:53 UTC 2016 - [email protected] + +- man: Update man page to use pcmk_delay_max over start-delay (bsc#993032) + * bug-993032_sbd-man-pcmk_delay_max.patch + +------------------------------------------------------------------- New: ---- bug-993032_sbd-man-pcmk_delay_max.patch ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ sbd.spec ++++++ --- /var/tmp/diff_new_pack.fPHHla/_old 2016-09-01 14:03:37.000000000 +0200 +++ /var/tmp/diff_new_pack.fPHHla/_new 2016-09-01 14:03:37.000000000 +0200 @@ -26,6 +26,7 @@ Url: https://github.com/ClusterLabs/sbd Source: %{name}-%{version}.tar.xz Patch1: add-explicit-libs.patch +Patch2: bug-993032_sbd-man-pcmk_delay_max.patch BuildRequires: autoconf BuildRequires: automake BuildRequires: e2fsprogs-devel ++++++ bug-993032_sbd-man-pcmk_delay_max.patch ++++++ commit ca2fba836eab169f0c8cacf7f3757c0485bcfef8 Author: Gao,Yan <[email protected]> Date: Wed Aug 31 13:05:20 2016 +0200 Doc: man: Update man page to use pcmk_delay_max over start-delay diff --git a/man/sbd.8.pod b/man/sbd.8.pod index fd1efad..ef0ede6 100644 --- a/man/sbd.8.pod +++ b/man/sbd.8.pod @@ -546,16 +546,16 @@ configure fencing resource. This should be a primitive, not a clone, as follows: primitive fencing-sbd stonith:external/sbd \ - op start start-delay="15" + params pcmk_delay_max=30 This will automatically use the same devices as configured in F</etc/sysconfig/sbd>. -While you should not configure this as a clone (as Pacemaker will start -a fencing agent in each partition automatically), the I<start-delay> -setting ensures, in a scenario where a split-brain scenario did occur in -a two node cluster, that the one that still needs to instantiate a -fencing agent is slightly disadvantaged to avoid fencing loops. +While you should not configure this as a clone (as Pacemaker will register +the fencing device on each node automatically), the I<pcmk_delay_max> +setting enables random fencing delay which ensures, in a scenario where a +split-brain scenario did occur in a two node cluster, that one of the nodes +has a better chance to survive to avoid double fencing. SBD also supports turning the reset request into a crash request, which may be helpful for debugging if you have kernel crashdumping configured;
