SLURP upgrade from 2023.1 to master (2024.1) fails with: restart_streams feature flag is not available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
In Progress
|
Undecided
|
Unassigned |
Bug Description
The error I am seeing is:
TASK [rabbitmq : Enable feature flags] *******
Wednesday 20 March 2024 13:33:14 +0000 (0:00:00.099) 0:00:21.630 *******
ok: [controller0] => (item=quorum_queue)
ok: [controller0] => (item=implicit_
ok: [controller0] => (item=virtual_
ok: [controller0] => (item=maintenan
ok: [controller0] => (item=user_limits)
ok: [controller0] => (item=stream_queue)
ok: [controller0] => (item=classic_
ok: [controller0] => (item=tracking_
ok: [controller0] => (item=stream_
ok: [controller0] => (item=listener_
ok: [controller0] => (item=feature_
ok: [controller0] => (item=direct_
ok: [controller0] => (item=classic_
ok: [controller0] => (item=stream_
failed: [controller0] (item=restart_
This is when attempting to upgrade rabbitmq. We seem to have 3.11.28 in 2023.1, but restart_streams wasn't added until 3.12:
https:/
It seems like in the upgrade job we do a reconfigure prior to the upgrade (which essentially gives us the master containers). This is not a documented step.
summary: |
- SLURP upgrade from 2023.1 to 2024.1 fails with: restart_streams feature - flag is not available + SLURP upgrade from 2023.1 to master (2024.1) fails with: restart_streams + feature flag is not available |
description: | updated |
The reconfigure step was added when we were using HA queues. Given we are now instead enabling quorum queues by default, we do not need this reconfigure step anymore. See docs here for the required steps: https:/ /docs.openstack .org/kolla- ansible/ latest/ reference/ message- queues/ rabbitmq. html#high- availability