rabbitmq-server 3.9.13 Mnesia Collector Throws Error

I didn't setup a reproducer for this one, but the situation looks pretty clear. Currently affected are:

 rabbitmq-server | 3.9.13-1 | jammy
 rabbitmq-server | 3.9.13-1 | kinetic

The 3.9.x releases are maintenance releases (see [1]), and as they appear to be bugfix only we could still fix this bug in Kinetic by packaging 3.9.15 (ahead of Debian).

I don't think the package has enough tests to do an "new upstream microrelease" upload: the autopkgtest is just a smoke tests, and the upstream tests are disabled in d/rules, so fixing the bug in Jammy will probably require cherry-picking the right commit.

[1] https://rabbitmq.com/github.html

The breakage is in https://github.com/deadtrickster/prometheus.erl 4.8.1 which is used as embedded code :-/ in rabbitmq. The "fix" to rabbitmq in their git repository that landed just updates the references to pull in the newer 4.8.2 (up from the former 06425c21 and doing so now via hex).

Indeed 3.9.15 is the latest release that would combine all of that (pulled the new fixes like this and others) to the 3.9.x series.

For the SRU we have to look inside or premetheus.erl where this was fixed via https://github.com/deadtrickster/prometheus.erl/pull/140 by this change:
https://github.com/deadtrickster/prometheus.erl/commit/ffe2bf711659f5ee11970b8a60f7f0f72fc68770

I'm not familiar enough with rabbitmq to move it to 3.9.15 so late in the Kinetic cycle.
But I've added it to the candidates of minor release upgrades. If things look stable enough that might happen later on.

For now I think we should fix the issue, ask the reporter to try it from a PPA and helping us to prep an SRU case then.

PPA: https://launchpad.net/~paelzer/+archive/ubuntu/lp-1988283-rabbitmq-crashes-mnesia/+packages

Hi Jasper,
could you give the test build in the referenced PPA a try.
Your confirmation that it fixes the issue should be enough to upload it to Kinetic.

For the SRU [1] Process into Jammy I will need some help form you.
In particular what someone would need to do from a fresh blank system to install&configure it to trigger the issue. That is needed to verify the case is existing and then after the update fixed.

I'll create the rest of the SRU template, but on that I'd really need your help.

Marking as incomplete until I got these information.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates

MPs:
- J: https://code.launchpad.net/~paelzer/ubuntu/+source/rabbitmq-server/+git/rabbitmq-server/+merge/429624
- K: https://code.launchpad.net/~paelzer/ubuntu/+source/rabbitmq-server/+git/rabbitmq-server/+merge/429625

Hi, there was no further feedback last week or over the weekend.
I just wanted to clarify that I really need someone hitting (and being able to recreate this issue) to help us driving this further into Kinetic, and from there as SRU into Jammy.

Unassigning myself for now since I can't continue, if updated it will show up in triage.
@triagers - if the feedback is good feel free to directly convert the MPs into an upload then.