Bugfix missing for RabbitMQ 3.9 to allow upgrade from 3.8
Bug #2040255 reported by
Christian Rohmann
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rabbitmq-server (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Jammy |
Triaged
|
Undecided
|
Unassigned | ||
Bug Description
When upgrading a cluster from RabbitMQ 3.8 (via Ubuntu 20.04 LTS) to RabbitMQ 3.9 (via Ubuntu 22.04 LTS) there is a critical bug, causing new connections on the node running 3.9 to crash:
* https:/
This was fixed in version 3.9.21 of RabbitMQ, thus is version is definitely required on Ubuntu 22.04 to allow for a rolling upgrade of clusters! Currently 3.9.13 is the version shipping with Ubuntu 22.04 (Jammy)
| description: | updated |
Revision history for this message
| Athos Ribeiro (athos-ribeiro) wrote | #1 |
| Changed in rabbitmq-server (Ubuntu): | |
| status: | New → Triaged |
| Changed in rabbitmq-server (Ubuntu Jammy): | |
| status: | New → Triaged |
| Changed in rabbitmq-server (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
Thanks for reporting this bug, Christian.
As per the linked upstream bug, the fix was released in 3.11.0 and has been backported to 3.10.6 and 3.9.21. So, the only potentially affected series is jammy.
Christian would you be able to come up with a minimal reproducer for this one? For instance, setting up a minimal server configuration in a focal vm, upgrade to jammy and demonstrate the bug is present then?