openstack-ansible/releasenotes/notes/keepalived-upgrade-e63a11b7d4dcba20.yaml
Jean-Philippe Evrard 12a3fbafd0 Fixing keepalived bug when 2+ backup nodes have the same priority
The issue is present if you're running 2 or more nodes with
a keepalived < 1.2.8. This bumps the version of keepalived role
(installing a more recent version of keepalived by default) AND
edits the keepalived configuration file to avoid having nodes
with the same priority.

This will restart your keepalived service.

Please note this commit is not meant for backporting. The deployer
running on mitaka and below should follow the documentation here:
https://review.openstack.org/#/c/279664/

Bug: #1545066

Change-Id: Ie28d2d3fa8670212c64ecbdf5a87314e7ca0a2d9
2016-04-13 12:05:32 +00:00

22 lines
1.4 KiB
YAML

---
features:
- There is a new default configuration for keepalived, supporting more than 2 nodes.
- In order to make use of the latest stable keepalived version, the variable
``keepalived_use_latest_stable`` must be set to ``True``
issues:
- In the latest stable version of keepalived there is a problem with the priority
calculation when a deployer has more than five keepalived nodes. The problem causes the
whole keepalived cluster to fail to work. To work around this issue it is recommended that
deployers limit the number of keepalived nodes to no more than five or that the priority
for each node is set as part of the configuration (cf. ``haproxy_keepalived_vars_file``
variable).
upgrade:
- There is a new default configuration for keepalived. When running the haproxy playbook,
the configuration change will cause a keepalived restart unless the deployer has used a custom
configuration file. The restart will cause the virtual IP addresses managed by keepalived to
be briefly unconfigured, then reconfigured.
- A new version of keepalived will be installed on the haproxy nodes if the variable
``keepalived_use_latest_stable`` is set to ``True`` and more than one haproxy node is
configured. The update of the package will cause keepalived to restart and therefore will
cause the virtual IP addresses managed by keepalived to be briefly unconfigured, then
reconfigured.