From 2ca1fbb0e3ddcaa7168919cd17bd63ae5c26aac7 Mon Sep 17 00:00:00 2001 From: Rachel Elledge Date: Tue, 13 May 2025 17:18:08 -0500 Subject: [PATCH] DOC-5247 RS: Added shard migration status resolved issue to the RS 7.8.6-60 release notes --- .../operate/rs/release-notes/rs-7-8-releases/rs-7-8-6-60.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-6-60.md b/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-6-60.md index 4ed44d4493..127be1ed4a 100644 --- a/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-6-60.md +++ b/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-6-60.md @@ -6,7 +6,7 @@ categories: - operate - rs compatibleOSSVersion: Redis 7.4.0 -description: Bug fix for an LDAP connection issue caused by setting LDAP bind credentials that include `<` in the Cluster Manager UI. Deprecated required_version in the bootstrap cluster API. +description: Bug fixes for an LDAP connection issue caused by setting LDAP bind credentials that include `<` in the Cluster Manager UI and an issue where migrated shards can appear stuck on multiple nodes. Deprecated required_version in the bootstrap cluster API. linkTitle: 7.8.6-60 (April 2025) weight: 83 --- @@ -17,7 +17,7 @@ This is a maintenance release for ​[​Redis Enterprise Software version 7.8.6 This version offers: -- A bug fix for an LDAP connection issue caused by setting LDAP bind credentials that include `<` in the Cluster Manager UI. +- Bug fixes for an LDAP connection issue caused by setting LDAP bind credentials that include `<` in the Cluster Manager UI and an issue where migrated shards can appear stuck on multiple nodes. ## New in this release @@ -45,6 +45,8 @@ The following table shows which Redis modules are compatible with each Redis dat - RS155783: Fixed an issue where using the special character `<` when setting LDAP bind credentials in the Cluster Manager UI caused LDAP connection failures. +- RS144215: Fixed an issue where a shard's status might not update correctly after migration, causing it to appear stuck on multiple nodes even if the migration completed successfully. + ## Version changes ### Deprecations