Michele Baldessari af8b1cfbf7 RabbitMQ: always allow promotion on HA queue during failover ... When the RabbitMQ experience a rolling restart of its peers, the master of an HA queue fails over from one replica to another. If there are messages sent to the HA queue while some rabbit nodes are restarting, the latter will reconnect as unsynchronized slaves. It can happen that during a rolling restart, all rabbit nodes reconnect as unsynchronized, which prevents RabbitMQ to automatically elect a new Master for failover. This has other side effects on fanout queues and may prevent OpenStack notification to be consumed properly. Change the HA policy to always allow a promotion even when all replicas are unsynchronized. When such rare condition happens, rely on OpenStack client to retry RPC if they need to. Closes-Bug: #1823305 Co-Authored-By: Damien Ciabrini <dciabrin@redhat.com> Change-Id: Id9bdd36aa0ee81424212e3a89185311817a15aee (cherry picked from commit 610c8d8d41)		2019-06-14 20:51:14 +00:00
..
notes	RabbitMQ: always allow promotion on HA queue during failover	2019-06-14 20:51:14 +00:00
source	Update reno for stable/rocky	2018-08-24 14:42:47 +00:00