Merge branch 'stackhpc/2023.1' into bump-neutron

Author: priteau

doc/source/configuration/cephadm.rst

@@ -208,8 +208,8 @@ Pools
 ~~~~~
 
 The following example pools should be sufficient to work with the
-default `external Ceph
-configuration <https://docs.openstack.org/kolla-ansible/latest/reference/storage/external-ceph-guide.html>`__
+default :kolla-ansible-doc:`external Ceph
+configuration <reference/storage/external-ceph-guide.html>`
 for Cinder, Cinder backup, Glance, and Nova in Kolla Ansible.
 
 .. code:: yaml
@@ -236,8 +236,8 @@ Keys
 ~~~~
 
 The following example keys should be sufficient to work with the default
-`external Ceph
-configuration <https://docs.openstack.org/kolla-ansible/latest/reference/storage/external-ceph-guide.html>`__
+:kolla-ansible-doc:`external Ceph
+configuration <reference/storage/external-ceph-guide.html>`
 for Cinder, Cinder backup, Glance, and Nova in Kolla Ansible.
 
 .. code:: yaml
@@ -353,7 +353,7 @@ RADOS Gateways
 
 RADOS Gateway integration is described in the :kolla-ansible-doc:`Kolla Ansible
 documentation
-<https://docs.openstack.org/kolla-ansible/latest/reference/storage/external-ceph-guide.html#radosgw>`.
+<reference/storage/external-ceph-guide.html#radosgw>`.
 
 RADOS Gateways (RGWs) are defined with the following:
 

doc/source/configuration/ci-cd.rst

@@ -118,7 +118,7 @@ Runner Deployment
     The repository permissions for a fine-grained personal access token should be; :code:`Actions: R/W, Administration: R/W, Metadata: R`
     Once the key has been obtained, add it to :code:`secrets.yml` under :code:`secrets_github_access_token`
 
-7. If the host is an actual Infra VM then please refer to upstream `Infrastructure VMs <https://docs.openstack.org/kayobe/latest/configuration/reference/infra-vms.html>`__ documentation for additional configuration and steps.
+7. If the host is an actual Infra VM then please refer to upstream :kayobe-doc:`Infrastructure VMs <configuration/reference/infra-vms.html>` documentation for additional configuration and steps.
 
 8. Run :code:`kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/deploy-github-runner.yml`
 

doc/source/configuration/cloudkitty.rst

@@ -8,8 +8,8 @@ Configuring in kayobe-config
 By default, CloudKitty uses Gnocchi and Ceilometer as the collector and fetcher
 backends. Unless the system has a specific reason not to, we recommend instead
 using Prometheus as the backend for both. The following instructions explain
-how to do this. Also, see the `Kolla Ansible docs on CloudKitty
-<https://docs.openstack.org/kolla-ansible/latest/reference/rating/cloudkitty-guide.html>`__
+how to do this. Also, see the :kolla-ansible-doc:`Kolla Ansible docs on CloudKitty
+<reference/rating/cloudkitty-guide.html>`
 for more details.
 
 Enable CloudKitty and disable InfluxDB, as we are using OpenSearch as the

doc/source/index.rst

@@ -12,8 +12,8 @@ Overview
 ========
 
 This documentation covers the StackHPC Kayobe configuration. It is intended to
-complement, rather than replace, the upstream :kayobe-doc:`Kayobe </>`,
-:kolla-doc:`Kolla </>` and :kolla-ansible-doc:`Kolla Ansible </>`
+complement, rather than replace, the upstream :kayobe-doc:`Kayobe <>`,
+:kolla-doc:`Kolla <>` and :kolla-ansible-doc:`Kolla Ansible<>`
 documentation.
 
 The configuration includes various things, such as:

etc/kayobe/kolla-image-tags.yml

@@ -37,8 +37,8 @@ kolla_image_tags:
   manila:
     rocky-9: 2023.1-rocky-9-20240809T102431
   neutron:
-    rocky-9: 2023.1-rocky-9-20250303T162416
-    ubuntu-jammy: 2023.1-ubuntu-jammy-20250303T162416
+    rocky-9: 2023.1-rocky-9-20250311T093325
+    ubuntu-jammy: 2023.1-ubuntu-jammy-20250311T093325
   nova:
     rocky-9: 2023.1-rocky-9-20240926T151818
     ubuntu-jammy: 2023.1-ubuntu-jammy-20240926T151818

releasenotes/notes/fix-broken-links-150bf2dd009123d1.yaml

@@ -0,0 +1,4 @@
+---
+fixes:
+  - |
+    Fix some broken links in the docs.

releasenotes/notes/revert-track-all-interfaces-in-keepalived-371eea147fbebf36.yaml

@@ -0,0 +1,7 @@
+---
+fixes:
+  - |
+    Reverts "Track all interfaces in Keepalived" so only HA interfaces are
+    tracked. This prevents L3 HA router flapping when detaching floating IP
+    addresses, because non-HA router interfaces did not include "no_track".
+    Closes-Bug: #2097770