Troubleshooting: Document fix of corrupted redis AOF

Signed-off-by: Jan Horstmann <horstmann@osism.tech>

Author: janhorstmann

docs/guides/deploy-guide/services/infrastructure.md

@@ -6,7 +6,7 @@ sidebar_position: 10
 # Infrastructure
 
 Common issues with deploying infrastructure services required by OpenStack
-are documented in the [OpenStack Troubleshooting Guide](../../troubleshooting-guide/openstack.md).
+are documented in the [OpenStack Troubleshooting Guide](../../troubleshooting-guide/openstack.mdx).
 
 
 1. Optional: In order to reduce the active observation time for the deployment of the components,

docs/guides/deploy-guide/services/logging-monitoring.md

@@ -6,7 +6,7 @@ sidebar_position: 40
 # Logging & Monitoring
 
 Common issues with deploying logging & monitoring services provided by Kolla
-are documented in the [OpenStack Troubleshooting Guide](../../troubleshooting-guide/openstack.md).
+are documented in the [OpenStack Troubleshooting Guide](../../troubleshooting-guide/openstack.mdx).
 
 1. OpenSearch
 

docs/guides/deploy-guide/services/openstack.md

@@ -6,7 +6,7 @@ sidebar_position: 60
 # OpenStack
 
 Common issues with deploying OpenStack services are documented in the
-[OpenStack Troubleshooting Guide](../../troubleshooting-guide/openstack.md).
+[OpenStack Troubleshooting Guide](../../troubleshooting-guide/openstack.mdx).
 
 :::info
 

…uides/troubleshooting-guide/openstack.md …ides/troubleshooting-guide/openstack.mdxdocs/guides/troubleshooting-guide/openstack.md renamed to docs/guides/troubleshooting-guide/openstack.mdx docs/guides/troubleshooting-guide/openstack.md renamed to docs/guides/troubleshooting-guide/openstack.mdx

@@ -2,6 +2,8 @@
 sidebar_label: OpenStack
 sidebar_position: 40
 ---
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
 
 # OpenStack
 
@@ -254,3 +256,56 @@ sidebar_position: 40
 
 * Do not disable the offline compression with `COMPRESS_OFFLINE = False` to get rid of the error. The error
   disappears, but afterwards every page is compressed again on each request.
+
+## Redis/Valkey: "Bad file format reading the append only file..."
+
+<Tabs>
+<TabItem value="redis" label="Redis">
+
+* Problem: A `redis` instance refuses to start with error message: "Bad file format reading the append only file appendonly.aof.11.incr.aof: make a backup of your AOF file, then use ./redis-check-aof --fix &lt;filename.manifest&gt;"
+
+* Solution: Fix the append-only-file with the mentioned command.
+
+  :::note
+
+  The following commands apply to a redis instance belonging to the OpenStack control plane. Please make sure to adjust the commands if you are fixing this error on another redis instance, like the manager or netbox.
+
+  :::
+
+  On the node with the broken instance run
+
+  ```console
+  docker run --rm -it -v redis:/var/lib/redis <osism redis image>:<osism redis tag>  bash
+  redis-check-aof --fix /var/lib/redis/appendonlydir/redis-staging-ao.aof.manifest
+  ```
+
+  and follow the given instructions to fix any corruptions.
+  Once the append-only-file is fixed restart the `redis` instance.
+
+  ```console
+  docker restart redis
+  ```
+
+</TabItem>
+<TabItem value="valkey" label="Valkey">
+
+* Problem: A `valkey` instance refuses to start with error message: "Bad file format reading the append only file appendonly.aof.11.incr.aof: make a backup of your AOF file, then use ./valkey-check-aof --fix &lt;filename.manifest&gt;"
+
+* Solution: Fix the append-only-file with the mentioned command.
+
+  On the node with the broken instance run
+
+  ```console
+  docker run --rm -it -v valkey:/var/lib/valkey <osism valkey image>:<osism valkey tag>  bash
+  valkey-check-aof --fix /var/lib/valkey/appendonlydir/valkey-staging-ao.aof.manifest
+  ```
+
+  and follow the given instructions to fix any corruptions.
+  Once the append-only-file is fixed restart the `valkey` instance.
+
+  ```console
+  docker restart valkey
+  ```
+
+</TabItem>
+</Tabs>

docs/guides/upgrade-guide/openstack.md

@@ -103,4 +103,4 @@ of the APIs. This downtime is usually less than 1 minute.
 
     If Horizon answers with `Something went wrong!` afterwards, check its log for an `OfflineGenerationError`.
     That error and its solution are documented in the
-    [OpenStack Troubleshooting Guide](../troubleshooting-guide/openstack.md).
+    [OpenStack Troubleshooting Guide](../troubleshooting-guide/openstack.mdx).