Update Xray 3.83.9 to 3.111.24 via Ansible: RabbitMQ broken #447
Description
Hi,
after updating xray 3.83.9 to 3.111.24 via Ansible, xray wont start anymore because RabbitMQ cant start.
We found some hints in the logs:
Starting up RabbitMQ at Tue Apr 15 20:55:35 CEST 2025... 2025-04-15 20:55:37.040415+02:00 [error] <0.254.0> Feature flags:classic_mirrored_queue_version: required feature flag not enabled! It must be enabled before upgrading RabbitMQ. 2025-04-15 20:55:37.047379+02:00 [error] <0.254.0> Failed to initialize feature flags registry: {disabled_required_feature_flag, 2025-04-15 20:55:37.047379+02:00 [error] <0.254.0> classic_mirrored_queue_version} 2025-04-15 20:55:37.052892+02:00 [error] <0.254.0> BOOT FAILED 2025-04-15 20:55:37.052892+02:00 [error] <0.254.0> =========== 2025-04-15 20:55:37.052892+02:00 [error] <0.254.0> Error during startup: {error,failed_to_initialize_feature_flags_registry}
We also maintain some RabbitMQ-Clusters and we furtunately already know this problem. This is also documented:
https://www.rabbitmq.com/docs/rolling-upgrade#verify-all-stable-feature-flags-are-enabled
However, since attempting an upgrade with disabled feature flags may lead to serious issues, it's a good practice to check if all stable feature flags are enabled before starting the upgrade. You can safely run rabbitmqctl enable_feature_flag all - it will do nothing if all flags are already enabled.
So we rolled back our xray-VM, and enabled all feature-flags manually. before running the ansible-playbook. This way xray was able to start correctly. I also looked into your playbook and cant find any task/step for enabling the rabbitmq-feature-flags.
BR
Zen