Closed flyersa closed 7 months ago
The quorum queues are disabled by default in our defaults: https://github.com/osism/defaults/blob/main/all/001-kolla-defaults.yml#L274
The task works in a fresh testbed deployment with Bobcat. Have you set any other parameters for RabbitMQ?
TASK [rabbitmq : Enable feature flags] *****************************************
Thursday 11 April 2024 07:18:24 +0000 (0:00:00.315) 0:00:13.233 ********
[WARNING]: Could not match supplied host pattern, ignoring:
enable_outward_rabbitmq_True
[WARNING]: Could not match supplied host pattern, ignoring:
outward_rabbitmq_restart
ok: [testbed-node-2.testbed.osism.xyz] => (item=quorum_queue)
ok: [testbed-node-0.testbed.osism.xyz] => (item=quorum_queue)
ok: [testbed-node-1.testbed.osism.xyz] => (item=quorum_queue)
ok: [testbed-node-0.testbed.osism.xyz] => (item=implicit_default_bindings)
ok: [testbed-node-2.testbed.osism.xyz] => (item=implicit_default_bindings)
ok: [testbed-node-1.testbed.osism.xyz] => (item=implicit_default_bindings)
ok: [testbed-node-0.testbed.osism.xyz] => (item=virtual_host_metadata)
ok: [testbed-node-2.testbed.osism.xyz] => (item=virtual_host_metadata)
ok: [testbed-node-1.testbed.osism.xyz] => (item=virtual_host_metadata)
ok: [testbed-node-0.testbed.osism.xyz] => (item=maintenance_mode_status)
ok: [testbed-node-2.testbed.osism.xyz] => (item=maintenance_mode_status)
ok: [testbed-node-1.testbed.osism.xyz] => (item=maintenance_mode_status)
ok: [testbed-node-0.testbed.osism.xyz] => (item=user_limits)
ok: [testbed-node-1.testbed.osism.xyz] => (item=user_limits)
ok: [testbed-node-2.testbed.osism.xyz] => (item=user_limits)
ok: [testbed-node-0.testbed.osism.xyz] => (item=stream_queue)
ok: [testbed-node-1.testbed.osism.xyz] => (item=stream_queue)
ok: [testbed-node-2.testbed.osism.xyz] => (item=stream_queue)
ok: [testbed-node-0.testbed.osism.xyz] => (item=classic_queue_type_delivery_support)
ok: [testbed-node-1.testbed.osism.xyz] => (item=classic_queue_type_delivery_support)
ok: [testbed-node-2.testbed.osism.xyz] => (item=classic_queue_type_delivery_support)
ok: [testbed-node-0.testbed.osism.xyz] => (item=tracking_records_in_ets)
ok: [testbed-node-1.testbed.osism.xyz] => (item=tracking_records_in_ets)
ok: [testbed-node-2.testbed.osism.xyz] => (item=tracking_records_in_ets)
ok: [testbed-node-0.testbed.osism.xyz] => (item=stream_single_active_consumer)
ok: [testbed-node-1.testbed.osism.xyz] => (item=stream_single_active_consumer)
ok: [testbed-node-2.testbed.osism.xyz] => (item=stream_single_active_consumer)
ok: [testbed-node-0.testbed.osism.xyz] => (item=listener_records_in_ets)
ok: [testbed-node-1.testbed.osism.xyz] => (item=listener_records_in_ets)
ok: [testbed-node-2.testbed.osism.xyz] => (item=listener_records_in_ets)
ok: [testbed-node-0.testbed.osism.xyz] => (item=feature_flags_v2)
ok: [testbed-node-1.testbed.osism.xyz] => (item=feature_flags_v2)
ok: [testbed-node-2.testbed.osism.xyz] => (item=feature_flags_v2)
ok: [testbed-node-0.testbed.osism.xyz] => (item=direct_exchange_routing_v2)
ok: [testbed-node-1.testbed.osism.xyz] => (item=direct_exchange_routing_v2)
ok: [testbed-node-2.testbed.osism.xyz] => (item=direct_exchange_routing_v2)
ok: [testbed-node-0.testbed.osism.xyz] => (item=classic_mirrored_queue_version)
ok: [testbed-node-1.testbed.osism.xyz] => (item=classic_mirrored_queue_version)
ok: [testbed-node-2.testbed.osism.xyz] => (item=classic_mirrored_queue_version)
strange. i did nothing custom, i created a new config with cookiecutter and just did the apply job for rabbitmq
maybe network issue or something in the testbed on my side. I will try again in a new setup, if the issue comes up again i reopen. sorry
Hi,
doing a fresh testbed installation following osism docs and latest version i notice some issues.
The changelog refers to the quorum queues that they should not be used, but its the default in kolla now. So maybe we should add a hint that it needs to be disabled by setting om_enable_rabbitmq_quorum_queues: "no" ?
Then on rollout rabbitmq fails to properly finish the kolla task with enabling feature flags, it prints out that there is something wrong with the commandline passed. upon searching on this i found this https://www.reddit.com/r/openstack/comments/1bdn60q/kollaansible_rabbitmq_feature_flas/
rewriting the playbook as he suggests doesnt fix the problem directly, then it will complain on connections that it cannot connect with cli to the server because some kind of key is different from the server or something.
neverless rabbitmq itself is running fine but im not sure what comes after the feature flag task.