Skip to content

RS: Clarify module upgrade limitation fix #2781

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.

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion content/embeds/supported-platforms-embed.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ To avoid issues with SHA1 certificates, replace them with new certificates that
RHEL 7 clusters cannot be directly upgraded to RHEL 8 when hosting databases using modules.
Due to binary differences in modules between the two operating systems, you cannot directly update RHEL 7 clusters to RHEL 8 when those clusters host databases using modules. Instead, you need to create a new cluster on RHEL 8 and then migrate existing data from your RHEL 7 cluster. This does not apply to clusters that do not use modules.

This limitation is fixed for clusters using Redis Enterprise Software version 7.2 and later.
This limitation is fixed as of [Redis Enterprise Software version 7.2.4]({{<relref "/rs/release-notes/rs-7-2-4-releases">}}). After you upgrade the cluster to Redis Enterprise Software version 7.2.4 or later, you can also upgrade the RHEL version on the existing cluster.

### Modules not supported for Amazon Linux 2 release candidate

Expand Down