[ClusterLabs] Issues found in Pacemaker 1.1.18, fixes in 1.1 branch

[Ken Gaillot]

On Tue, 2017-12-12 at 13:19 +0100, Ferenc Wágner wrote:
> Ken Gaillot <kgaillot at redhat.com> writes:
> 
> > A couple of regressions have been found in the recent Pacemaker
> > 1.1.18
> > release.
> > 
> > Fixes for these, plus one finishing an incomplete fix in 1.1.18,
> > are in
> > the master branch, and have been backported to the 1.1 branch for
> > ease
> > of patching. It is recommended that anyone compiling or packaging
> > 1.1.18 include all the commits from the 1.1 branch.
> 
> Hi Ken,
> 
> Did you consider cutting a new patch-level release with these fixes?
> That would help determining the presence of the fixes for bug reports
> and questions.  Which is even more important if you don't plan to
> make
> further 1.x releases.

We won't actively develop the 1.1 line any more, but some bugfixes may
be backported from the active branches (master and 2.0).

I expect we will eventually release 1.1.19 with any other backports
that accrue. I'd give it at least 6 months though.

* 1.1.18 improved scalability by eliminating redundant node
> > attribute
> > write-outs. This proved to be too aggressive in one case: when a
> > cluster is configured with only IP addresses (no node names) in
> > corosync.conf, attribute write-outs can be incorrectly delayed; in
> > the
> > worst case, this prevents a node from shutting down due to the
> > shutdown
> > attribute not being written.
> 
> I guess this applies all the same for clusters defined without a
> Corosync nodelist.  Right?

I didn't test that, but I would expect so.

Previously, the crmd would always explicitly clear a couple of
attributes at start-up. Now, attrd accomplishes the same thing without
an explicit setting. It turned out that, as a side effect, the explicit
setting allowed the other peers' attrd to immediately associate the new
node's ID with its node name. The fix was set to set a new attribute
explicitly at start-up.
-- 
Ken Gaillot <kgaillot at redhat.com>