[rabbitmq-discuss] rabbitmq 3.1.4 upgrade lost cluster config

[Morty]

On Wed, Aug 14, 2013 at 03:17:17PM -0400, Morty wrote:

> We use puppet.  The configurations are templated and enforced to be
> identical except for cluster node names, which are different between
> clusters.  If a config changes that is only read at server start, such
> as /etc/rabbitmq/rabbitmq.config, then rabbitmq is automatically
> restarted by puppet.

BTW: the workaround I described earlier worked even better than
expected.  I just moved aside /var/lib/rabbitmq/mnesia and started
rabbitmq.  The node rejoined the cluster immediately and all was good.

I'd prefer to understand the cause of this, or a way to detect
possible impending problems.  In particular, I've got one more cluster
still to upgrade, and it's the most important (left for last, for good
reason!)  And it would be nice to understand this for future
reference.

NB: I've done 3.0.x and 3.1.x upgrades on these three clusters before
without seeing this type of issue.

- Morty