Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack RabbitMQ Server Charm |
Triaged
|
Undecided
|
Unassigned | ||
erlang (Ubuntu) |
Triaged
|
Undecided
|
Unassigned | ||
rabbitmq-server (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
While performing an openstack release upgrade from Pike to Queens following the charmers guide, we have upgraded Ceph-* and Mysql. After setting source=
We have reproduced this twice in the same environment by re-deploying a fresh pike rabbitmq cluster and upgrading to queens. The issue is not reproducable with generic workloads such as creating/deleting nova instances and creating/
This is happening on two of the three clouds on this site when RMQ is upgraded to Queens. The third cloud was able to upgrade to Queens without issue but was upgraded on 18.02 charms. Heat templates forthcoming.
tags: | added: sts |
Changed in erlang (Ubuntu): | |
status: | New → Triaged |
Attaching web.yaml, a heat template known to trigger this event.