** Description changed: [ Impact ] This bug tracks an update for the rabbitmq-server package in Ubuntu. This bug tracks an update to the following versions: - * Focal (20.04): rabbitmq-server 3.8.3 - * Jammy (22.04): rabbitmq-server 3.9.27 + * Focal (20.04): rabbitmq-server 3.8.3 + * Jammy (22.04): rabbitmq-server 3.9.27 (NOTE) - Jammy is only updating to 3.9.27 because 3.9.28 requires Erlang 24.3. If Erlang updates in the future, then we can upgrade further. (NOTE) - Focal is only updating to 3.8.3 from 3.8.2 because 3.8.4 requires etcd v3.4. This is the first MRE of rabbitmq-server. Upstream has a very rapid release cadence with micro releases that contain many bug fixes that would be good to bring into our LTS releases. One major hurdle with this is the lack of proper dep8 tests, which a limited suite of dep8 tests were created for this MRE, which is planned to get integrated into newer releases once approved. rabbitmq-server is a complicated package that the new dep8 tests will not be able to cover everything, therefore our openstack charms CI/CD ran the new verison to provide more confidence in the package, and to at least verify that our workflow works. The results of these runs can be found at https://review.opendev.org/c/openstack/charm-rabbitmq-server/+/915836. In addition to this, only Jammy has github workflows to build+test the package, where the results can be found at https://github.com/mitchdz/rabbitmq-server-3-9-27-tests/actions/runs/8955069098/job/24595393599. Changelogs can be found at https://github.com/rabbitmq/rabbitmq- server/tree/main/release-notes + Jammy included the introduction of a new ERL_MAX_PORTS variable in the + microrelease. A delta was introduced in Ubuntu to respect the previous + values on upgrade, making no action required by the user, and + eliminating unforeseen downtime due to a microrelease upgrade limiting + the max erlang ports. + [ Test Plan ] The test plan for rabbitmq-server involves 3 different types of tests. - 1. OpenStack CI/CD + (A) OpenStack CI/CD This is what we run for CI/CD. Testing the newer version in CI/CD tests real world use-cases, and is a minimum that should be done to ensure our own tooling should work. Tester will need to request the new version to be ran from the OpenStack team. An example of a run as mentioned before is: https://review.opendev.org/c/openstack/charm-rabbitmq-server/+/915836 - 2. dep8 tests + (B) dep8 tests New dep8 tests were added to the package which must pass. These cover simple, but real use-cases. - 3. Upgrade testing + (C) Upgrade testing 1. lxc launch ubuntu:jammy j-vm --vm 2. lxc shell j-vm 3. sudo apt install -y rabbitmq-server 4. Enable proposed 5. sudo apt install -y rabbitmq-server # ensure no errors or issues during upgrade - For jammy, also ensure ERL_MAX_PORTS and LimitNOFILE are correctly honored on upgrade. + For jammy, also ensure ERL_MAX_PORTS and LimitNOFILE are correctly honored on upgrade. Checking ERL_MAX_PORTS is easy to do with the following erlang command: + # rabbitmqctl eval 'erlang:system_info(port_limit).' + + To test this, the following steps will be performed. + 1. lxc launch ubuntu:jammy j-vm --vm + 2. lxc shell j-vm + 3. sudo apt install -y rabbitmq-server + 4. Set LimitNoFile to a higher value than the default + 5. Upgrade + 6. Check max open file handles && max erlang ports, they should match. + + A test should also be made for differing ERL_MAX_PORTS, specifically + where LimitNOFILE > ERL_MAX_PORTS, and ensure the max open file handles + and max erlang ports are respected on upgrade. This is the same as the + steps above, except step 4 also adds the ERL_MAX_PORTS environment + variable. + [ Where problems could occur ] * This is the first MRE of this package, so extra caution should be taken. - * Upgrading the server may cause downtine during upgrade. - * Reports of upgrade failures can happen if users have misconfigured rabbitmq-server and the maintainerscripts attempt to stop/start the server. + * Upgrading the server may cause downtime during upgrade. + * Reports of upgrade failures can happen if users have misconfigured rabbitmq-server and the maintainer scripts attempt to stop/start the server. + * a change was made to Jammy to respect the maximum Erlang ports on upgrade. This change could cause erratic behavior.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060248 Title: MRE updates of rabbitmq-server for Jammy,Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/2060248/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
