Hi, we upgraded to Epoxy last year as well. Since our cloud runs on (Ubuntu) packages (not containerized), we were kind of forced to upgrade RabbitMQ as well (if we didn't want to fiddle with locking packages etc.). The transition wasn't very smooth in that regard though, we had to use RabbitMQ containers to gradually upgrade from 3.9 to 3.10 and 3.11. The RabbitMQ package version for Ubuntu 24 was 3.12, and we couldn't just skip because of missing features which had to be enabled in 3.10/3.11. So there was a short downtime for the services because we couldn't make it work with mixed versions. So we shut down RabbitMQ, started a 3.10 container mapping the rabbit database, stopped it, started a 3.11 container, stopped it. Then started the rabbit systemd service again. I hope we don't have to do it this way too often. :-D Maybe at some point we will decide to migrate to kolla-ansible, I don't know. For now we'll stay on packages as long as possible. Regards, Eugen Zitat von Francesco Di Nucci <francesco.dinucci@na.infn.it>:
Hi all,
I'm upgrading from OpenStack Caracal to Epoxy on EL, using RDO packages. I see that CentOS Stream Messaging SIG still packages RabbitMQ 3.8, that is EOL.
Should I still use it or switch to a more recent release, like 3.13 or pass to 4.x series? Has anyone tried it?
Thanks in advance
-- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples
Email: francesco.dinucci@na.infn.it