Pacemaker maintains an internal database, which is used for
configuration storage. Each update of this database increases a counter,
called "epoch", which should have the same value cluster-wide.
If an update operation comes to a previously detached node, a conflict
will occur. Pacemaker does not allow updating this database on a node,
which epoch value is lower than the epoch value of a cluster leader.
We should wait the epoch counter to come into sync by perodically
retrying the update command.
Closes-Bug: 1494314
Change-Id: I1f242bcd90264ec45da2aaa6bc030f244511761b
(cherry picked from commit 6134af0c6ec651e4feef45acdc5a291beab405cd)
Reviewed: https:/ /review. openstack. org/267487 /git.openstack. org/cgit/ openstack/ fuel-library/ commit/ ?id=1a947e855f0 c30bb20ae6acc0c 86b90f4d034a71
Committed: https:/
Submitter: Jenkins
Branch: stable/8.0
commit 1a947e855f0c30b b20ae6acc0c86b9 0f4d034a71
Author: Dmitry Bilunov <email address hidden>
Date: Tue Dec 15 12:29:07 2015 +0300
Fix detached keystone node epoch mismatch
Pacemaker maintains an internal database, which is used for
configuration storage. Each update of this database increases a counter,
called "epoch", which should have the same value cluster-wide.
If an update operation comes to a previously detached node, a conflict
will occur. Pacemaker does not allow updating this database on a node,
which epoch value is lower than the epoch value of a cluster leader.
We should wait the epoch counter to come into sync by perodically
retrying the update command.
Closes-Bug: 1494314 c45da2aaa6bc030 f244511761b 4feef45acdc5a29 1beab405cd)
Change-Id: I1f242bcd90264e
(cherry picked from commit 6134af0c6ec651e