Skip to content

Add warning for OVS sites with SLURP rabbitmq upgrade #1379

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

Merged
merged 2 commits into from
Nov 19, 2024
Merged

Add warning for OVS sites with SLURP rabbitmq upgrade #1379

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3800287
Add warning for OVS clusters with rabbitmq upgrade
technowhizz Nov 19, 2024
161cbe6
Fix typo in upgrade docs
technowhizz Nov 19, 2024
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
6 changes: 5 additions & 1 deletion doc/source/operations/upgrading-openstack.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,10 +221,14 @@ to 3.12, then to 3.13 on Antelope before the Caracal upgrade. This upgrade
should not cause an API outage (though it should still be considered "at
risk").

Some errors have been observed in testing when the upgrades are perfomed
Some errors have been observed in testing when the upgrades are performed
back-to-back. A 200s delay eliminates this issue. On particularly large or slow
deployments, consider increasing this timeout.

Additionally errors have been observed at sites with OVS networking where after
the upgrade, tenant networking is broken and requires a reset of RabbitMQ. This
can be done by running the rabbitmq-reset playbook.

.. code-block:: bash

kayobe overcloud service configuration generate --node-config-dir /tmp/ignore -kt none
Expand Down