Skip to content

Support RabbitMQ minor version upgrades and Quorum migration #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from

Conversation

Alex-Welsh
Copy link
Member

Adds a new command - rabbit_migration to execute a RabbitMQ minor version upgrade and Quorum queue migration. Required for Antelope->Caracal upgrades

@Alex-Welsh Alex-Welsh requested a review from a team as a code owner September 10, 2024 13:23
@@ -89,6 +89,18 @@
vars:
kayobe_environment_path: "{{ src_directory }}/kayobe-config/etc/kayobe/environments/{{ kayobe_config_environment }}"

- name: Revert RabbitMQ changes to avoid git conflicts (upgrade)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This stuff gets a bit fiddly, and brittle when considering support for multiple releases. Longer term it probably needs a different solution, like writing the config overrides to a specific file that can be deleted on upgrade.

- name: Revert RabbitMQ changes to avoid git conflicts (upgrade)
ansible.builtin.shell:
cmd: >-
if grep "om_enable_rabbitmq_high_availability: false" {{ kayobe_environment_path }}/kolla/globals.yml ; then

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this do the right thing for:

  • yoga -> zed
  • zed -> antelope
  • antelope -> caracal (hopefully yes)
  • caracal -> epoxy

(bearing in mind SKC may change over time...)

@@ -336,6 +336,27 @@ function upgrade_overcloud() {
kayobe overcloud service upgrade
}

function rabbit_migration() {
# Ensure RabbitMQ is upgraded to 3.13
if kayobe overcloud host command run -l controllers -b --command "docker exec rabbitmq rabbitmqctl --version | grep 3.11" --show-output; then

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: It shouldn't be an issue here, but you need to be careful with . in grep

@@ -336,6 +336,27 @@ function upgrade_overcloud() {
kayobe overcloud service upgrade
}

function rabbit_migration() {
# Ensure RabbitMQ is upgraded to 3.13
if kayobe overcloud host command run -l controllers -b --command "docker exec rabbitmq rabbitmqctl --version | grep 3.11" --show-output; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not an issue right now, but RabbitMQ versions are split into three: e.g. 3.13.7. there is a chance they'll go all the way up to 3.13.11, which would also get caught by this grep

@Alex-Welsh
Copy link
Member Author

Superseded by #73

@Alex-Welsh Alex-Welsh closed this Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants