| noonedeadpunk | jrosser: sorry, just get to the laptop. I was thinking if using `RabbitMQ start` rather then `RabbitMQ restart` would be better? As we wanna ensure it's started after all, right? | 09:06 |
|---|---|---|
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Start 2025.1 (Epoxy) development https://review.opendev.org/c/openstack/openstack-ansible/+/936644 | 09:07 |
| noonedeadpunk | will also proceed with qdrouterd repository retirement next week | 09:08 |
| jrosser | we also need to drop the jammy jobs and switch a bunch to noble | 09:09 |
| jrosser | start vs restart yes we can change that | 09:10 |
| noonedeadpunk | well. then we need either to backport noble to 2024.1? as we can't drop jammy for 2025.1 completely | 09:12 |
| noonedeadpunk | but yes, switching "main" distro to test - that what we need to do indeed | 09:12 |
| jrosser | oh - well I don’t know - I guess I am confused by slurp again :) | 09:12 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-rabbitmq_server master: Service must always be restarted during an upgrade https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/938051 | 09:13 |
| noonedeadpunk | we can drop jammy only for 2025.2 | 09:13 |
| noonedeadpunk | as upgrade path 2024.1 -> 2025.1 should be present on the same platform | 09:13 |
| jrosser | ah ok - I was looking at ansible 2.18 upgrade so I think we cannot do that yet | 09:17 |
| noonedeadpunk | unless do a separate python version for deploy host | 09:20 |
| noonedeadpunk | there's 3.11 available as secondary version | 09:21 |
| noonedeadpunk | but probably easier to stick with 2.17 for 2025.1 | 09:21 |
| noonedeadpunk | btw, found anything around gather_subset deprecation? | 09:27 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!