Please backport rabbitmq-server 3.8.2-0ubuntu1 (main) from focal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bionic Backports |
Fix Released
|
Undecided
|
Unassigned | ||
elixir-lang (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
erlang (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Please backport rabbitmq-server 3.8.2-0ubuntu1 (main) from focal to bionic.
Reason for the backport:
=======
3.6 is EOL since 31 May 2018, which only leave us with 3.8 as supported
For more details:
https:/
Note:
rabbitmq-server (3.8.2) depends on erlang (21.3 -> which is the minimum required) which depends on elixir (1.6.6)
None of theses depends are found in Bionic at the moment:
erlang | 1:20.2.
elixir | 1.3.3-2 | bionic/universe | all
A backport of the erlang and elixir will also be needed.
[Compatibility between Elixir and Erlang/OTP]
https:/
[RabbitMQ and Erlang/OTP Compatibility Matrix]
https:/
Testing:
========
Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing.
You can test-build the backport in your PPA with backportpackage:
$ backportpackage -u ppa:<lp username>/<ppa name> -s focal -d bionic rabbitmq-server
* bionic:
[-] Package builds without modification
Package requires erlang (21.3) and elixir (1.6.6) as build-dep[0]
Very minor changes related to debhelper (debhelper-compat vs debhelper).
Otherwise the builder try to default to compat 5[1]
[0]
----
Build status:
----
Dependency wait on lcy01-amd64-021 Retry this build
Missing build dependencies: elixir (>= 1.6.6), erlang-base (>= 1:21.3), erlang-crypto (>= 1:21.3), erlang-dev (>= 1:21.3), erlang-edoc (>= 1:21.3), erlang-eldap (>= 1:21.3), erlang-erl-docgen (>= 1:21.3), erlang-eunit (>= 1:21.3), erlang-inets (>= 1:21.3), erlang-mnesia (>= 1:21.3), erlang-nox (>= 1:21.3), erlang-os-mon (>= 1:21.3), erlang-parsetools (>= 1:21.3), erlang-public-key (>= 1:21.3), erlang-
----
[1]
----
debian/rules:67: warning: overriding recipe for target 'override_
debian/rules:14: warning: ignoring old recipe for target 'override_
dh clean --with python3,systemd
dh: Compatibility levels before 5 are no longer supported (level 1 requested)
debian/rules:11: recipe for target 'clean' failed
make: *** [clean] Error 255
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
----
[X] rabbitmq-server installs cleanly and runs
# lsb_release -cs
bionic
# dpkg -l rabbitmq-server
ii rabbitmq-server 3.8.2-0ubuntu1+
Reverse dependencies:
=======
The following reverse-
rabbitmq-server
---------------
* debci-collector
[-] bionic (Reverse-
* pybit-web
[-] bionic (Reverse-Suggests)
* syslog-ng-mod-amqp
[-] bionic (Reverse-Suggests)
* nagios-
[-] bionic (Reverse-Suggests)
* neutron
[] bionic (Reverse-
* ceilometer
[] bionic (Reverse-
* aodh
[] bionic (Reverse-
* debci
[] bionic (Reverse-
[X] bionic (Reverse-
* nova
[] bionic (Reverse-
* ruby-bunny
[X] bionic (Reverse-
tags: | added: sts |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in erlang (Ubuntu): | |
importance: | Undecided → Critical |
Changed in elixir-lang (Ubuntu): | |
importance: | Undecided → Critical |
Changed in erlang (Ubuntu): | |
status: | New → In Progress |
Changed in elixir-lang (Ubuntu): | |
status: | New → In Progress |
Changed in bionic-backports: | |
status: | New → In Progress |
Changed in bionic-backports: | |
status: | In Progress → Fix Released |
Changed in elixir-lang (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in erlang (Ubuntu): | |
status: | In Progress → Fix Released |
We've extensively tested rabbitmq-server 3.8.2 from Eric's PPA on an existing, cleanly-built Bionic/Rocky OpenStack cluster and hammered it with multiple concurrent VM builds, deletes and live-migrations between compute hosts.
We also ran a full Rally suite against it with no errors or failures related to anything in the messaging workflow.
The customer pushing for this backport is satisfied with the testing they've done, and wants to push forward with the SRU into -backports, so they can consume it organically from their internal, daily aptly mirror ASAP, to mitigate some fatal issues they've seen with their 3.6.10 version on Rocky.
Thanks!