Thanks Andreas, I furthermore checked with "our" openstack team if that isn't something they've already hit, but they have no jammy -> noble upgrade path for their use of rabbitmq yet. Although they offered help to verify any fix we might propose by test upgrading their rabbitmq node using it.
This flag handling is indeed is a common practice, as for example in 3.11 needed all flags of 3.8.x just the same way [1]. The bonus problem that might make this harder, is that [2] states that 3.12 needs all flags of the 3.11.x series. But Jammy to Noble is 3.9.x -> 3.12 - so we might need an interim 3.11?!? That makes this quite complex unless e.g. a backport of the lastest 3.9.x makes that possible too the outcome will be quite complex. Yet on the other hand, while some text says "before upgrade" and I do not see that in the OpenStack solution [4] Andreas found - to be fair that is so abstracted that I'm even yet unsure what/when it exactly does. I must admit that I think we need a bit more time to get a better understanding of this [3] in general. And even then we might still want to avoid too many assumptions and just ask upstream if there is any 3.9->3.12 way without an interim 3.11 - and discuss a more detailed plan of action from there. Either way, big thanks to Hadmut to bring this to our attention! [1]: https://www.rabbitmq.com/blog/2022/07/20/required-feature-flags-in-rabbitmq-3.11 [2]: https://github.com/rabbitmq/rabbitmq-server/discussions/8456 [3]: https://www.rabbitmq.com/docs/feature-flags [4]: https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/919701 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074309 Title: rabbitmq-server upgrade 22.04 -> 24.04 completely broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2074309/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
