From 1abd592948b7864fc59022bbf7d9f884d8331b11 Mon Sep 17 00:00:00 2001 From: Jason Rayne Date: Thu, 9 Oct 2025 12:56:21 -0700 Subject: [PATCH] fix(docs): correct playbook commands and minor inconsistencies in Ubuntu Noble upgrade guide - Fix incorrect ceph-enter-maintenance.yml usage where ceph-exit-maintenance.yml should be used - Fix typo: "change" -> "chance" in storage section potential issues --- doc/source/operations/ubuntu-noble.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/operations/ubuntu-noble.rst b/doc/source/operations/ubuntu-noble.rst index b3e07c8be..c22268bb4 100644 --- a/doc/source/operations/ubuntu-noble.rst +++ b/doc/source/operations/ubuntu-noble.rst @@ -165,7 +165,7 @@ Always back up the overcloud DB before starting: Potential issues ---------------- -- If the system uses OVS as a network driver, there's a change that kolla +- If the system uses OVS as a network driver, there's a chance that kolla services can struggle to find reply queues from RabbitMQ during the upgrade. Currently this could be observed when rolling reboot of controllers are done or deploying Ubuntu Noble based Kolla containers are deployed after all @@ -236,7 +236,7 @@ Full procedure for one controller .. code-block:: console - kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-enter-maintenance.yml --limit + kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-exit-maintenance.yml --limit 3. Make sure that everything is back in working condition before moving on to the next host: @@ -321,7 +321,7 @@ Full procedure for one batch of hosts .. code-block:: console - kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-enter-maintenance.yml --limit + kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-exit-maintenance.yml --limit 3. Make sure that everything is back in working condition before moving on to the next host: