diff --git a/content/operate/rs/release-notes/rs-7-8-releases/_index.md b/content/operate/rs/release-notes/rs-7-8-releases/_index.md
index 7f1bbf0b2b..c402e7e15c 100644
--- a/content/operate/rs/release-notes/rs-7-8-releases/_index.md
+++ b/content/operate/rs/release-notes/rs-7-8-releases/_index.md
@@ -231,24 +231,6 @@ The following table provides a snapshot of supported platforms as of this Redis
 
 - RS131972: Creating an ACL that contains a line break in the Cluster Manager UI can cause shard migration to fail due to ACL errors.
 
-- After upgrading, clusters using Sentinel for service discovery might encounter an issue that requires a restart of the Sentinel service. To determine if your cluster is affected, check for the following symptoms:
-
-    1. The `sentinel masters` command is unresponsive.
-
-    1. Review `sentinel_service.log` for messages such as:
-
-    ```
-    INFO Failed to read ‘HGETALL node:##’, ERROR: ‘HGETALL node:##’ returned empty results (retry ######), will try again in 1s.
-    ```
-
-    Workaround: To resolve the issue, run the following command on each node:
-
-    ```sh
-    supervisorctl restart sentinel_service
-    ```
-    
-    If you are uncertain whether you are impacted or need assistance with remediation, [contact support](https://redis.io/support/).
-
 ## Known limitations
 
 #### New Cluster Manager UI limitations
diff --git a/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-34.md b/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-34.md
index 55e079bb70..83e006287e 100644
--- a/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-34.md
+++ b/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-34.md
@@ -408,24 +408,6 @@ The following table shows the SHA256 checksums for the available packages:
 
 - RS131972: Creating an ACL that contains a line break in the Cluster Manager UI can cause shard migration to fail due to ACL errors.
 
-- After upgrading, clusters using Sentinel for service discovery might encounter an issue that requires a restart of the Sentinel service. To determine if your cluster is affected, check for the following symptoms:
-
-    1. The `sentinel masters` command is unresponsive.
-
-    1. Review `sentinel_service.log` for messages such as:
-
-    ```
-    INFO Failed to read ‘HGETALL node:##’, ERROR: ‘HGETALL node:##’ returned empty results (retry ######), will try again in 1s.
-    ```
-
-    Workaround: To resolve the issue, run the following command on each node:
-
-    ```sh
-    supervisorctl restart sentinel_service
-    ```
-    
-    If you are uncertain whether you are impacted or need assistance with remediation, [contact support](https://redis.io/support/).
-
 ## Known limitations
 
 #### New Cluster Manager UI limitations