Open jerr0328 opened 1 year ago
Hi @jerr0328
Seems it was an automatic upgrade so no guided steps are currently defined. I will open a task for the team to dive in the upgrade details and write those steps as soon as our workload allows us.
rabbitmqctl enable_feature_flag all
will do it. Tested with the upgrade from 3.11.20
to 3.12.2
.
When in a cluster running the command on the main node is enough:
kubectl exec -it rabbitmq-0 -- rabbitmqctl enable_feature_flag all
I ran into this too, is there a way to do this without running a manual command? I tried adding featureFlags: "classic_mirrored_queue_version"
to my values but I still got this error
also the manual command isn't working for me because my pod is crashing before I can shell into it
featureFlags: "classic_mirrored_queue_version"
should be added before the upgrade. We ended up deleting the pvc (unknown what data is lost but this was okay on our dev env) to spin up cleanly since we had not been aware of this.
Just enable all feature flags on your current version and then do upgrade, works perfectly
I think adding a paragraph like this should do the trick, because in the RabbitMQ instructions it is mentioned that all feature flags should be enabled.
This major version changes the default RabbitMQ image from 3.11.x to 3.12.x. Follow the official instructions to upgrade from 3.11 to 3.12.
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Name and Version
bitnami/rabbitmq 12.0.x
What architecture are you using?
amd64
What steps will reproduce the bug?
Are you using any custom parameters or values?
What is the expected behavior?
I would usually expect that an upgrade could be done without needing to manually specify anything. If there are new feature flags, the chart should provide those as default enabled to allow the upgrade to happen. At the very least, upgrade instructions in the README should point out that you can't upgrade from 11 to 12 without taking manual actions
What do you see instead?
Additional information
No response