Skip to content

fix(docs): correct playbook commands and minor inconsistencies in Ubuntu Noble upgrade guide #1927

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.

Sign up for GitHub

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

Open
wants to merge 4 commits into
base: stackhpc/2025.1
Choose a base branch
from
Open

fix(docs): correct playbook commands and minor inconsistencies in Ubuntu Noble upgrade guide #1927

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
38b5a85
fix(docs): correct playbook commands and minor inconsistencies in Ubu…
jasonrayne Oct 9, 2025
550fdfd
Update doc/source/operations/ubuntu-noble.rst
jasonrayne Oct 9, 2025
af938b0
Update doc/source/operations/ubuntu-noble.rst
jasonrayne Oct 9, 2025
522f859
fix(docs): linebreak initial playbook command for consistency
jasonrayne Oct 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 12 additions & 6 deletions doc/source/operations/ubuntu-noble.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,15 +79,21 @@ To sync host packages:

.. code-block:: console

kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-sync.yml -e stackhpc_pulp_sync_ubuntu_jammy=true -e stackhpc_pulp_sync_ubuntu_noble=true
kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-publish.yml
kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-sync.yml \
-e stackhpc_pulp_sync_ubuntu_jammy=true \
-e stackhpc_pulp_sync_ubuntu_noble=true
kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-publish.yml \
-e stackhpc_pulp_sync_ubuntu_jammy=true \
-e stackhpc_pulp_sync_ubuntu_noble=true

Once the host package content has been tested in a test/staging environment, it
may be promoted to production:

.. code-block:: console

kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-promote-production.yml
kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-promote-production.yml \
-e stackhpc_pulp_sync_ubuntu_jammy=true \
-e stackhpc_pulp_sync_ubuntu_noble=true
Comment on lines +82 to +96
Copy link
Member

@priteau priteau Oct 21, 2025

Choose a reason for hiding this comment

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

The stackhpc_pulp_sync_ubuntu_jammy variable is gone from this branch.


To sync container images:

Expand Down Expand Up @@ -165,7 +171,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
Expand Down Expand Up @@ -236,7 +242,7 @@ Full procedure for one controller

.. code-block:: console

kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-enter-maintenance.yml --limit <host>
kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-exit-maintenance.yml --limit <host>

3. Make sure that everything is back in working condition before moving
on to the next host:
Expand Down Expand Up @@ -321,7 +327,7 @@ Full procedure for one batch of hosts

.. code-block:: console

kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-enter-maintenance.yml --limit <hosts>
kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-exit-maintenance.yml --limit <hosts>

3. Make sure that everything is back in working condition before moving
on to the next host:
Expand Down
Loading